Re: Problems with libz since libz.so.5 is gone...
On Fri, Jan 27, 2012 at 6:19 PM, Pierre-Luc Drouin pldro...@pldrouin.netwrote: On Fri, Jan 27, 2012 at 11:44 AM, Pierre-Luc Drouin pldro...@pldrouin.net wrote: On Fri, Jan 27, 2012 at 10:41 AM, Pierre-Luc Drouin pldro...@pldrouin.net wrote: On Fri, Jan 27, 2012 at 9:58 AM, Pierre-Luc Drouin pldro...@pldrouin.net wrote: On Fri, Jan 27, 2012 at 9:55 AM, Pierre-Luc Drouin pldro...@pldrouin.net wrote: On Thu, Jan 26, 2012 at 5:40 PM, Dan Nelson dnel...@allantgroup.comwrote: In the last episode (Jan 26), Pierre-Luc Drouin said: so various ports, in particular the java ports, are giving me headaches since /lib/libz.so.5 was replaced by /lib/libz.so.6. I managed to update most of my ports, but the binary java ports, such as diablo-jdk16, are now installing broken binary files. Even if I put an entry such as libz.so.4 libz.so.6 in /etc/libmap.conf libmap (or symlinking) only works for libraries that have a compatible ABI. The version number of libz was bumped precisely because the ABI changed :) Install the misc/compat8x port to get libz.so.5 back until you can replace diablo-jdk16 with openjdk6. -- Dan Nelson dnel...@allantgroup.com Hi, sorry I tried to install compat8x but it did not solve the problem, as that package does not install libz.so.5 Thanks Sorry it did install libz.so.5, but diablo-jdk16 is still crashing for some reason... Ok, so I installed linux-sun-jdk16 that does not seem to get broken by FreeBSD 9, then I hacked the port Makefile for openjdk16 to bootstrap itself with linux-sun-jdk16 and so far it seems to be compiling fine... That solution did ont work either because jni_md.h is missing with linux-sun-jdk16. So now I am trying to compile gcj by hand and use it to bootstrap openjdk. This chicken and egg problem is getting really annoying... So I discovered that openjdk cannot be bootstrapped with gcj, but then I discovered that there was an openjdk6 package available for FreeBSD 9 (generated on January 15th). I installed it, but event that one does not work. I am wondering if the problem is not with vsnprintf instead of libz: --- T H R E A D --- Current thread (0x2863d800): JavaThread Unknown thread [_thread_in_vm, id=100896, stack(0xbf9af000,0xbf9ff000)] siginfo:si_signo=SIGBUS: si_errno=0, si_code=3 (BUS_OBJERR), si_addr=0x2812718c Registers: EAX=0xbf9fddb0, EBX=0x281de884, ECX=0x28c77737, EDX=0xbf9fe5a0 ESP=0xbf9fdc48, EBP=0xbf9fdd50, ESI=0xbf9fe738, EDI=0x07d0 EIP=0x2812718c, EFLAGS=0x00010206 Top of Stack: (sp=0xbf9fdc48) 0xbf9fdc48: bf9fdf44 bf9fe76c bf9fe0f0 2889545e 0xbf9fdc58: bf9fe76c 0001 0003 28cd92d4 0xbf9fdc68: bf9fe76c bf9fe0f0 28bd5b19 0xbf9fdc78: bf9fe76c 00e1 28cd6108 28cd6208 0xbf9fdc88: b7f9 fff8 0001 0xbf9fdc98: bf9fdefc bf9fdd70 bf9fdd4c 28cd92d4 0xbf9fdca8: 28427284 28427270 bf9fdcc0 28c35c73 0xbf9fdcb8: 28cd92d4 bf9fdee0 bf9fdcf0 2896d834 Instructions: (pc=0x2812718c) 0x2812716c: 90 90 90 90 55 89 e5 53 57 56 81 ec fc 00 00 00 0x2812717c: e8 00 00 00 00 5b 81 c3 03 77 0b 00 66 0f ef c0 0x2812718c: 0f 29 45 d8 0f 29 45 c8 0f 29 45 b8 0f 29 45 a8 0x2812719c: 0f 29 45 98 0f 29 45 88 0f 29 85 78 ff ff ff 0f Register to memory mapping: EAX=0xbf9fddb0 is pointing into the stack for thread: 0x2863d800 EBX=0x281de884: __nsdefaultsrc+0xd38 in /lib/libc.so.7 at 0x280da000 ECX=0x28c77737: _ZTV18AdaptiveSizePolicy+0x1b7 in /usr/local/openjdk6/jre/lib/i386/client/libjvm.so at 0x2880 EDX=0xbf9fe5a0 is pointing into the stack for thread: 0x2863d800 ESP=0xbf9fdc48 is pointing into the stack for thread: 0x2863d800 EBP=0xbf9fdd50 is pointing into the stack for thread: 0x2863d800 ESI=0xbf9fe738 is pointing into the stack for thread: 0x2863d800 EDI=0x07d0 is an unknown value Stack: [0xbf9af000,0xbf9ff000], sp=0xbf9fdc48, free space=315k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [libc.so.7+0x4d18c] vsnprintf+0x1c I compiled FreeBSD (world+kernel) with clang. Is that possible that the clang compilation of FreeBSD makes any native JDK (jdk16, openjdk6, etc) unusable? Thanks! So it seems that vsnprintf is indeed broken on FreeBSD 9 when it is built with clang. I submitted a problem report... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with libz since libz.so.5 is gone...
On Thursday 26 January 2012 16:40:59 Dan Nelson wrote: In the last episode (Jan 26), Pierre-Luc Drouin said: so various ports, in particular the java ports, are giving me headaches since /lib/libz.so.5 was replaced by /lib/libz.so.6. I managed to update most of my ports, but the binary java ports, such as diablo-jdk16, are now installing broken binary files. Even if I put an entry such as libz.so.4 libz.so.6 in /etc/libmap.conf libmap (or symlinking) only works for libraries that have a compatible ABI. The version number of libz was bumped precisely because the ABI changed :) Install the misc/compat8x port to get libz.so.5 back until you can replace diablo-jdk16 with openjdk6. I did install openjdk6 with portmaster -o and I have two problems still (I did reinstall Opera and LibreOffice) Opera misses libz.so.5 (I didn't install yet compat-8x) and LibreOffice misses libjawt.so which is in /usr/local/openjdk6/jre/lib/i386/libjawt.so Mitja http://jpgmag.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with libz since libz.so.5 is gone...
On Thu, Jan 26, 2012 at 5:40 PM, Dan Nelson dnel...@allantgroup.com wrote: In the last episode (Jan 26), Pierre-Luc Drouin said: so various ports, in particular the java ports, are giving me headaches since /lib/libz.so.5 was replaced by /lib/libz.so.6. I managed to update most of my ports, but the binary java ports, such as diablo-jdk16, are now installing broken binary files. Even if I put an entry such as libz.so.4 libz.so.6 in /etc/libmap.conf libmap (or symlinking) only works for libraries that have a compatible ABI. The version number of libz was bumped precisely because the ABI changed :) Install the misc/compat8x port to get libz.so.5 back until you can replace diablo-jdk16 with openjdk6. -- Dan Nelson dnel...@allantgroup.com Hi, sorry I tried to install compat8x but it did not solve the problem, as that package does not install libz.so.5 Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with libz since libz.so.5 is gone...
On Fri, Jan 27, 2012 at 9:55 AM, Pierre-Luc Drouin pldro...@pldrouin.netwrote: On Thu, Jan 26, 2012 at 5:40 PM, Dan Nelson dnel...@allantgroup.comwrote: In the last episode (Jan 26), Pierre-Luc Drouin said: so various ports, in particular the java ports, are giving me headaches since /lib/libz.so.5 was replaced by /lib/libz.so.6. I managed to update most of my ports, but the binary java ports, such as diablo-jdk16, are now installing broken binary files. Even if I put an entry such as libz.so.4 libz.so.6 in /etc/libmap.conf libmap (or symlinking) only works for libraries that have a compatible ABI. The version number of libz was bumped precisely because the ABI changed :) Install the misc/compat8x port to get libz.so.5 back until you can replace diablo-jdk16 with openjdk6. -- Dan Nelson dnel...@allantgroup.com Hi, sorry I tried to install compat8x but it did not solve the problem, as that package does not install libz.so.5 Thanks Sorry it did install libz.so.5, but diablo-jdk16 is still crashing for some reason... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with libz since libz.so.5 is gone...
On Fri, Jan 27, 2012 at 9:58 AM, Pierre-Luc Drouin pldro...@pldrouin.netwrote: On Fri, Jan 27, 2012 at 9:55 AM, Pierre-Luc Drouin pldro...@pldrouin.netwrote: On Thu, Jan 26, 2012 at 5:40 PM, Dan Nelson dnel...@allantgroup.comwrote: In the last episode (Jan 26), Pierre-Luc Drouin said: so various ports, in particular the java ports, are giving me headaches since /lib/libz.so.5 was replaced by /lib/libz.so.6. I managed to update most of my ports, but the binary java ports, such as diablo-jdk16, are now installing broken binary files. Even if I put an entry such as libz.so.4 libz.so.6 in /etc/libmap.conf libmap (or symlinking) only works for libraries that have a compatible ABI. The version number of libz was bumped precisely because the ABI changed :) Install the misc/compat8x port to get libz.so.5 back until you can replace diablo-jdk16 with openjdk6. -- Dan Nelson dnel...@allantgroup.com Hi, sorry I tried to install compat8x but it did not solve the problem, as that package does not install libz.so.5 Thanks Sorry it did install libz.so.5, but diablo-jdk16 is still crashing for some reason... Ok, so I installed linux-sun-jdk16 that does not seem to get broken by FreeBSD 9, then I hacked the port Makefile for openjdk16 to bootstrap itself with linux-sun-jdk16 and so far it seems to be compiling fine... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with libz since libz.so.5 is gone...
On Fri, Jan 27, 2012 at 10:41 AM, Pierre-Luc Drouin pldro...@pldrouin.netwrote: On Fri, Jan 27, 2012 at 9:58 AM, Pierre-Luc Drouin pldro...@pldrouin.netwrote: On Fri, Jan 27, 2012 at 9:55 AM, Pierre-Luc Drouin pldro...@pldrouin.net wrote: On Thu, Jan 26, 2012 at 5:40 PM, Dan Nelson dnel...@allantgroup.comwrote: In the last episode (Jan 26), Pierre-Luc Drouin said: so various ports, in particular the java ports, are giving me headaches since /lib/libz.so.5 was replaced by /lib/libz.so.6. I managed to update most of my ports, but the binary java ports, such as diablo-jdk16, are now installing broken binary files. Even if I put an entry such as libz.so.4 libz.so.6 in /etc/libmap.conf libmap (or symlinking) only works for libraries that have a compatible ABI. The version number of libz was bumped precisely because the ABI changed :) Install the misc/compat8x port to get libz.so.5 back until you can replace diablo-jdk16 with openjdk6. -- Dan Nelson dnel...@allantgroup.com Hi, sorry I tried to install compat8x but it did not solve the problem, as that package does not install libz.so.5 Thanks Sorry it did install libz.so.5, but diablo-jdk16 is still crashing for some reason... Ok, so I installed linux-sun-jdk16 that does not seem to get broken by FreeBSD 9, then I hacked the port Makefile for openjdk16 to bootstrap itself with linux-sun-jdk16 and so far it seems to be compiling fine... That solution did ont work either because jni_md.h is missing with linux-sun-jdk16. So now I am trying to compile gcj by hand and use it to bootstrap openjdk. This chicken and egg problem is getting really annoying... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with libz since libz.so.5 is gone...
On Fri, Jan 27, 2012 at 11:44 AM, Pierre-Luc Drouin pldro...@pldrouin.netwrote: On Fri, Jan 27, 2012 at 10:41 AM, Pierre-Luc Drouin pldro...@pldrouin.net wrote: On Fri, Jan 27, 2012 at 9:58 AM, Pierre-Luc Drouin pldro...@pldrouin.net wrote: On Fri, Jan 27, 2012 at 9:55 AM, Pierre-Luc Drouin pldro...@pldrouin.net wrote: On Thu, Jan 26, 2012 at 5:40 PM, Dan Nelson dnel...@allantgroup.comwrote: In the last episode (Jan 26), Pierre-Luc Drouin said: so various ports, in particular the java ports, are giving me headaches since /lib/libz.so.5 was replaced by /lib/libz.so.6. I managed to update most of my ports, but the binary java ports, such as diablo-jdk16, are now installing broken binary files. Even if I put an entry such as libz.so.4 libz.so.6 in /etc/libmap.conf libmap (or symlinking) only works for libraries that have a compatible ABI. The version number of libz was bumped precisely because the ABI changed :) Install the misc/compat8x port to get libz.so.5 back until you can replace diablo-jdk16 with openjdk6. -- Dan Nelson dnel...@allantgroup.com Hi, sorry I tried to install compat8x but it did not solve the problem, as that package does not install libz.so.5 Thanks Sorry it did install libz.so.5, but diablo-jdk16 is still crashing for some reason... Ok, so I installed linux-sun-jdk16 that does not seem to get broken by FreeBSD 9, then I hacked the port Makefile for openjdk16 to bootstrap itself with linux-sun-jdk16 and so far it seems to be compiling fine... That solution did ont work either because jni_md.h is missing with linux-sun-jdk16. So now I am trying to compile gcj by hand and use it to bootstrap openjdk. This chicken and egg problem is getting really annoying... So I discovered that openjdk cannot be bootstrapped with gcj, but then I discovered that there was an openjdk6 package available for FreeBSD 9 (generated on January 15th). I installed it, but event that one does not work. I am wondering if the problem is not with vsnprintf instead of libz: --- T H R E A D --- Current thread (0x2863d800): JavaThread Unknown thread [_thread_in_vm, id=100896, stack(0xbf9af000,0xbf9ff000)] siginfo:si_signo=SIGBUS: si_errno=0, si_code=3 (BUS_OBJERR), si_addr=0x2812718c Registers: EAX=0xbf9fddb0, EBX=0x281de884, ECX=0x28c77737, EDX=0xbf9fe5a0 ESP=0xbf9fdc48, EBP=0xbf9fdd50, ESI=0xbf9fe738, EDI=0x07d0 EIP=0x2812718c, EFLAGS=0x00010206 Top of Stack: (sp=0xbf9fdc48) 0xbf9fdc48: bf9fdf44 bf9fe76c bf9fe0f0 2889545e 0xbf9fdc58: bf9fe76c 0001 0003 28cd92d4 0xbf9fdc68: bf9fe76c bf9fe0f0 28bd5b19 0xbf9fdc78: bf9fe76c 00e1 28cd6108 28cd6208 0xbf9fdc88: b7f9 fff8 0001 0xbf9fdc98: bf9fdefc bf9fdd70 bf9fdd4c 28cd92d4 0xbf9fdca8: 28427284 28427270 bf9fdcc0 28c35c73 0xbf9fdcb8: 28cd92d4 bf9fdee0 bf9fdcf0 2896d834 Instructions: (pc=0x2812718c) 0x2812716c: 90 90 90 90 55 89 e5 53 57 56 81 ec fc 00 00 00 0x2812717c: e8 00 00 00 00 5b 81 c3 03 77 0b 00 66 0f ef c0 0x2812718c: 0f 29 45 d8 0f 29 45 c8 0f 29 45 b8 0f 29 45 a8 0x2812719c: 0f 29 45 98 0f 29 45 88 0f 29 85 78 ff ff ff 0f Register to memory mapping: EAX=0xbf9fddb0 is pointing into the stack for thread: 0x2863d800 EBX=0x281de884: __nsdefaultsrc+0xd38 in /lib/libc.so.7 at 0x280da000 ECX=0x28c77737: _ZTV18AdaptiveSizePolicy+0x1b7 in /usr/local/openjdk6/jre/lib/i386/client/libjvm.so at 0x2880 EDX=0xbf9fe5a0 is pointing into the stack for thread: 0x2863d800 ESP=0xbf9fdc48 is pointing into the stack for thread: 0x2863d800 EBP=0xbf9fdd50 is pointing into the stack for thread: 0x2863d800 ESI=0xbf9fe738 is pointing into the stack for thread: 0x2863d800 EDI=0x07d0 is an unknown value Stack: [0xbf9af000,0xbf9ff000], sp=0xbf9fdc48, free space=315k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [libc.so.7+0x4d18c] vsnprintf+0x1c I compiled FreeBSD (world+kernel) with clang. Is that possible that the clang compilation of FreeBSD makes any native JDK (jdk16, openjdk6, etc) unusable? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Libz
Recently a bug was discoverd which affected various unix platforms including FreeBSD. ( ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-05:16.zlib.asc ) But it say it only affects the 5.x releases and not the 4. Is it true only the 5.x releases are affected? (I think it rather odd, because libz is pretty 'universal' Thanks in advanced, Frank ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Libz
Frank de Bot wrote: Recently a bug was discoverd which affected various unix platforms including FreeBSD. ( ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-05:16.zlib.asc ) But it say it only affects the 5.x releases and not the 4. Is it true only the 5.x releases are affected? (I think it rather odd, because libz is pretty 'universal' Hi, Yes, it's true. Only 5.3 and 5.4 are affected. Colin Percival has confirmed this on the freebsd-security list. Cheers, Gábor Kövesdán ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Libz
On Jul 7, 2005, at 5:31 PM, Frank de Bot wrote: Recently a bug was discoverd which affected various unix platforms including FreeBSD. ( ftp://ftp.freebsd.org/pub/FreeBSD/CERT/ advisories/FreeBSD-SA-05:16.zlib.asc ) But it say it only affects the 5.x releases and not the 4. Is it true only the 5.x releases are affected? (I think it rather odd, because libz is pretty 'universal' I believe FreeBSD-4.x ships with zlib-1.1.x, whereas the security problem described above affects only the zlib-1.2.x branch found in FreeBSD-5, Linux, and elsewhere. I seem to recall Colin Percival saying as much, but you can double-check with the security officer if you like... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Libz
On 07/07/05 11:37 PM, Kvesdn Gbor sat at the `puter and typed: Frank de Bot wrote: Recently a bug was discoverd which affected various unix platforms including FreeBSD. ( ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-05:16.zlib.asc ) But it say it only affects the 5.x releases and not the 4. Is it true only the 5.x releases are affected? (I think it rather odd, because libz is pretty 'universal' Hi, Yes, it's true. Only 5.3 and 5.4 are affected. Colin Percival has confirmed this on the freebsd-security list. Keep in mind, this is already fixed in both versions: Corrected: 2005-07-06 14:01:11 UTC (RELENG_5, 5.4-STABLE) 2005-07-06 14:01:30 UTC (RELENG_5_4, 5.4-RELEASE-p4) 2005-07-06 14:01:52 UTC (RELENG_5_3, 5.3-RELEASE-p18) 5.4-RELEASE-p4 was tagged yesterday. Lou -- Louis LeBlanc FreeBSD-at-keyslapper-DOT-net Fully Funded Hobbyist, KeySlapper Extrordinaire :) Please send off-list email to: leblanc at keyslapper d.t net Key fingerprint = C5E7 4762 F071 CE3B ED51 4FB8 AF85 A2FE 80C8 D9A2 Gilbert's Discovery: Any attempt to use the new super glues results in the two pieces sticking to your thumb and index finger rather than to each other. pgpOQ8B5k1yMg.pgp Description: PGP signature
ar, nm not reading library files (libz, etc.)
Hi List, I've been having problems with ar and nm not being able to use the library files installed on my system, though executables created with them seem to work fine. libz is not the only library this happens with, just using it as an example. The output: ar -t /usr/lib/libz.so.2 /usr/libexec/elf/ar: /usr/lib/libz.so.2: File format not recognized nm /usr/lib/libz.so.2 /usr/libexec/elf/nm: /usr/lib/libz.so.2: no symbols The problem was first noticed after a massive round of portupgrading (due to the threading change). Rebuilding the system with RELENG_4_9 as of today did not fix the issue. Any ideas? Regards, Clayton Rollins PS. please be sure to CC me, as I only receive the list in digest form. _ Say good-bye to spam, viruses and pop-ups with MSN Premium -- free trial offer! http://click.atdmt.com/AVE/go/onm00200359ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ar, nm not reading library files (libz, etc.)
On Sat, Feb 28, 2004 at 03:29:34AM +, clayton rollins wrote: Hi List, I've been having problems with ar and nm not being able to use the library files installed on my system, though executables created with them seem to work fine. libz is not the only library this happens with, just using it as an example. The output: ar -t /usr/lib/libz.so.2 /usr/libexec/elf/ar: /usr/lib/libz.so.2: File format not recognized nm /usr/lib/libz.so.2 /usr/libexec/elf/nm: /usr/lib/libz.so.2: no symbols The problem was first noticed after a massive round of portupgrading (due to the threading change). Rebuilding the system with RELENG_4_9 as of today did not fix the issue. Any ideas? ar and nm work with static libraries, not shared. Perhaps you're looking for objdump. Kris pgp0.pgp Description: PGP signature
Re: ar, nm not reading library files (libz, etc.)
On Feb. 27, 2004 Kris Kennaway [EMAIL PROTECTED] wrote: On Sat, Feb 28, 2004 at 03:29:34AM +, clayton rollins wrote: Hi List, I've been having problems with ar and nm not being able to use the library files installed on my system, though executables created with them seem to work fine. libz is not the only library this happens with, just using it as an example. The output: ar -t /usr/lib/libz.so.2 /usr/libexec/elf/ar: /usr/lib/libz.so.2: File format not recognized nm /usr/lib/libz.so.2 /usr/libexec/elf/nm: /usr/lib/libz.so.2: no symbols The problem was first noticed after a massive round of portupgrading (due to the threading change). Rebuilding the system with RELENG_4_9 as of today did not fix the issue. Any ideas? ar and nm work with static libraries, not shared. Perhaps you're looking for objdump. Kris Thanks Kris; I thought ignorance was partially to blame. I think the problem is actually a naughty makefile, an old version uses nm fine (for whatever it uses it for). Thanks for your time, Clayton _ Take off on a romantic weekend or a family adventure to these great U.S. locations. http://special.msn.com/local/hotdestinations.armx ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
