Wed May 7 12:15:02 2008 UTC ()
Add note about workaround for loader's mmap of driver modules failing
on NetBSD-current.


(bjs)
diff -r1.1.1.1 -r1.2 pkgsrc/audio/jack-devel/MESSAGE
cvs diff -r1.1.1.1 -r1.2 pkgsrc/audio/jack-devel/Attic/MESSAGE (expand / switch to unified diff)

--- pkgsrc/audio/jack-devel/Attic/MESSAGE 2008/03/16 09:26:46 1.1.1.1
+++ pkgsrc/audio/jack-devel/Attic/MESSAGE 2008/05/07 12:15:02 1.2
@@ -1,18 +1,24 @@ @@ -1,18 +1,24 @@
1=========================================================================== 1===========================================================================
2$NetBSD: MESSAGE,v 1.1.1.1 2008/03/16 09:26:46 bjs Exp $ 2$NetBSD: MESSAGE,v 1.2 2008/05/07 12:15:02 bjs Exp $
3 3
4NOTE: Unfortunately, JACK wants to use a linux /proc filesystem to 4NOTE: Unfortunately, JACK wants to use a linux /proc filesystem to
5perform shared memory housekeeping tasks. Therefore, if your platform 5perform shared memory housekeeping tasks. Therefore, if your platform
6supports a "Linux-compliant" proc filesystem, we recommend mounting one 6supports a "Linux-compliant" proc filesystem, we recommend mounting one
7prior to using jack. On NetBSD, this can be accomplished with the 7prior to using jack. On NetBSD, this can be accomplished with the
8following command: 8following command:
9 9
10 mount_procfs -orw,linux /proc <mount point> 10 mount_procfs -orw,linux /proc <mount point>
11 11
12Conventionally, the mount point is /proc. If you wish to use a different 12Conventionally, the mount point is /proc. If you wish to use a different
13pathname for this filesystem, you may define the JACKD_PROCFS_PATH 13pathname for this filesystem, you may define the JACKD_PROCFS_PATH
14variable in your build environment or mk.conf as shown below. 14variable in your build environment or mk.conf as shown below.
15 15
16 JACKD_PROCFS_PATH= /emul/linux/proc 16 JACKD_PROCFS_PATH= /emul/linux/proc
17 17
 18ATTENTION: NetBSD-current users who wish to run jackd with real-time
 19 scheduling will likely find that the loader fails to mmap
 20 the driver module(s) when using -R. Until this issue is re-
 21 solved, one may work around this problem by using the -m
 22 (--no-mlock) option.
 23
18=========================================================================== 24===========================================================================