I've been looking at Jack (http://jackit.sourceforge.net/) for inclusion
in the book because it is an optional dependency for several packages:
audacious, mplayer, alsa-plugins, and kdemultimedia.
The installation of the libraries is not hard. Randy told me he uses:
./configure --prefix=/usr \
--sysconfdir=/etc/${PACKAGE_NAME} \
--enable-static \
--with-default-tmpdir=/mnt/ramfs \
--enable-posix-shm
make
make install
It has some optional dependencies: alsa-libs and libcap.
libcap is required to gain realtime scheduling privileges. I found that
package at Debian.
The real reason to use Jack is to run a server, jackd. There is user
documentation, http://lau.linuxaudio.org/jack/, but it seems complicated
to me. I don't see how we can address them in a startup script.
Also http://jackit.sourceforge.net/docs/faq.php#a52 says that "The
simplest, and least-secure way to provide real-time privileges is
running jackd as root. This has the disadvantage of also requiring all
of JACK clients to run as root."
A picture of how things are supposed to work is at
http://jackit.sourceforge.net/docs/diagram/JACK-Diagram-screensize.png
Perhaps just: jackd [-R] -d alsa
And where should this go? In ~/.xinitrc or ~/.xsession?
These issues are complex. As I see it, there are about three options:
1. Don't include Jack in the book at all. Just reference it as we are
doing now.
2. Add Jack but not bother with libcap and starting the daemon.
3. Add Jack and libcap and try to puzzle out the best way to describe
the configuration.
Opinions?
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
