summaryrefslogtreecommitdiff
path: root/audio/jack/MESSAGE
diff options
context:
space:
mode:
authorbjs <bjs@pkgsrc.org>2008-07-31 03:58:05 +0000
committerbjs <bjs@pkgsrc.org>2008-07-31 03:58:05 +0000
commit283ce280f860246434d2f53e8b72ee0abeebe94f (patch)
tree770e17b43c12b69ad42039e9b44224ca64c912e0 /audio/jack/MESSAGE
parent1b2aff6afd05b57c9e38ecfafe5bb547e5f5347e (diff)
downloadpkgsrc-283ce280f860246434d2f53e8b72ee0abeebe94f.tar.gz
Move audio/jack-devel to audio/jack: jack 0.100.0 was broken on many
platforms and a hideous anachronism. On NetBSD-current/i386 and amd64, at least, I can say that this package works very well. If you have issues with the audio skipping and are running NetBSD 4.99.x, try updating to rev. 1.241 of sys/dev/audio.c; the changes to audio_poll() and the pause attribute handling (in large part thanks to help from jakemsr@openbsd.org) are important for proper functioning of jack (though you may find it works regardless, depending upon your audio driver, how demanding your "workload" is, etc.). I will submit a pullup request for this change for NetBSD 4 as well. JACK now supports both our native audio API and OSS--I recommend trying both.
Diffstat (limited to 'audio/jack/MESSAGE')
-rw-r--r--audio/jack/MESSAGE24
1 files changed, 24 insertions, 0 deletions
diff --git a/audio/jack/MESSAGE b/audio/jack/MESSAGE
new file mode 100644
index 00000000000..8e7908f9eea
--- /dev/null
+++ b/audio/jack/MESSAGE
@@ -0,0 +1,24 @@
+===========================================================================
+$NetBSD: MESSAGE,v 1.1 2008/07/31 03:58:05 bjs Exp $
+
+NOTE: Unfortunately, JACK wants to use a linux /proc filesystem to
+perform shared memory housekeeping tasks. Therefore, if your platform
+supports a "Linux-compliant" proc filesystem, we recommend mounting one
+prior to using jack. On NetBSD, this can be accomplished with the
+following command:
+
+ mount_procfs -orw,linux /proc <mount point>
+
+Conventionally, the mount point is /proc. If you wish to use a different
+pathname for this filesystem, you may define the JACKD_PROCFS_PATH
+variable in your build environment or mk.conf as shown below.
+
+ JACKD_PROCFS_PATH= /emul/linux/proc
+
+ATTENTION: NetBSD-current users who wish to run jackd with real-time
+ scheduling will likely find that the loader fails to mmap
+ the driver module(s) when using -R. Until this issue is re-
+ solved, one may work around this problem by using the -m
+ (--no-mlock) option.
+
+===========================================================================