Re: can someone explain this change to bsd.lib.mk ?
On Fri, Mar 08, 2002 at 12:26:16PM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Luigi Rizzo writes: : The attached portion of the 1.100 - 1.101 patch to src/share/mk/bsd.lib.mk ... : I wonder, how does a make world get around this problem : (so i can try to reproduce the 'fix' in the picobsd script) ? Make world gets around this problem by doing things in stages so that the build tools are built first using the host environment, then the target binaries are built using the host tools. you mean the newly built tools, right ? cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
On Fri, 8 Mar 2002, Matthew Jacob wrote: And FWIW, alpha kernels on some Uniprocessor boxes freeze up. I managed to panic my 4-cpu 4100 yesterday with a 'make -j8 buildworld' I'm going to look at that today. -- Doug Rabson Mail: [EMAIL PROTECTED] Phone: +44 20 8348 6160 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
On Fri, 8 Mar 2002, Chris Hedley wrote: ... about a crash ... Just in case anyone needs to know, I had another couple of panics today when trying to newfs_msdos /dev/fd0, seems something in readdisklabel isn't too happy. Chris. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
New i386 5.0 packages uploaded (and toolchain problems)
I've uploaded a new set of packages to ftp-master for -current on i386; they should be picked up by the mirrors shortly. As I mentioned in a previous mail, there were compilation problems which caused a number of ports to fail, including qt2 and gnomelibs, meaning there were no KDE or GNOME packages built (hey, at least it's a symmetric failure!). The failures were caused by compiled utilities dumping core with sig11 or sig10 during compilation of the port. Toolchain people, please look into this; the error logs are at http://bento.freebsd.org/errorlogs/5-latest/ I also tried upgrading to a more recent 5.0 snapshot in which to perform the builds, but it seems there have been syscall changes and you can no longer cheat and run a 5.0 world inside a chroot on a 4.x machine: for example, sh dies with signal 12. Perhaps I'll have to upgrade the cluster to 5.0 to do the package building after all, but that on its own won't fix the toolchain problems. Kris msg35881/pgp0.pgp Description: PGP signature
gvim weird linkage
Hi Gvim will link against nonexistent libraries, some of them seem to be derived from libXThrStub library name and some Xlib function names, very weird. I'm unable to build working gvim either from ports or by hand, also doesn't matter is it newest version or older 6.0 release. First thought something is wrong with my hand-compiled XFree 4.2.0, but it isn't, XFree-4 port gave same results. I've -current as of yesterday, certainly past of the latest md5-crypt.c bug.. In the light of past events it seems to be something with linker or perhaps binutils. Non-X vim will work fine. myhakas:root# pwd /opt/portbuild/usr/ports/editors/vim/work/vim61a/src myhakas:root# ls -la vim -rwxr-xr-x 1 root wheel 1202570 Mar 9 15:01 vim myhakas:root# ldd vim vim: libXaw.so.7 = /usr/X11R6/lib/libXaw.so.7 (0x28158000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x281ab000) libncurses.so.5 = /usr/lib/libncurses.so.5 (0x281b8000) libc.so.5 = /usr/lib/libc.so.5 (0x281fa000) libXThrStub.XDeleteProperty = not found (0x0) libXThrStubXtVaGetValues = not found (0x0) libXThrStub.XDefaultScreen = not found (0x0) libXThrStub.XpmFreeAttributes = not found (0x0) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0x282b) libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x282c5000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x2830e000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x28317000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x2832d000) libXpm.so.4 = /usr/X11R6/lib/libXpm.so.4 (0x283e5000) libXThrStub.so.6 = /usr/X11R6/lib/libXThrStub.so.6 (0x283f3000) myhakas:root# exit -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 03:36:20PM +0200, Vallo Kallaste wrote: Hi Gvim will link against nonexistent libraries, some of them seem to be derived from libXThrStub library name and some Xlib function names, very weird. I'm unable to build working gvim either from ports or by hand, also doesn't matter is it newest version or older 6.0 release. Update your -CURRENT. I noticed this problem a month or two ago, but with a recent build of -CURRENT, gvim finally works again. Cheers, -- Jacques A. Vidrine [EMAIL PROTECTED] http://www.nectar.cc/ NTT/Verio SME . FreeBSD UNIX .Heimdal Kerberos [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 07:39:00AM -0600, Jacques A. Vidrine [EMAIL PROTECTED] wrote: Update your -CURRENT. I noticed this problem a month or two ago, but with a recent build of -CURRENT, gvim finally works again. Hm, thanks for confirming, but I'm running the very latest -current as I wrote. Actually I've switched back to -current some weeks ago after using -stable for a while because -current was very unstable after beginnings of SMPng. To be clear I did fresh install of the -current snapshot which I found in ftp.ee.freebsd.org, not 4.5- -current upgrade. I've built several worlds and kernels from that onward. Any hints? Seems like some environment configuration problem or latent bug somewhere.. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 03:55:13PM +0200, Vallo Kallaste wrote: On Sat, Mar 09, 2002 at 07:39:00AM -0600, Jacques A. Vidrine [EMAIL PROTECTED] wrote: Update your -CURRENT. I noticed this problem a month or two ago, but with a recent build of -CURRENT, gvim finally works again. Hm, thanks for confirming, but I'm running the very latest -current as I wrote. Actually I've switched back to -current some weeks ago after using -stable for a while because -current was very unstable after beginnings of SMPng. To be clear I did fresh install of the -current snapshot which I found in ftp.ee.freebsd.org, not 4.5- -current upgrade. I've built several worlds and kernels from that onward. Any hints? Seems like some environment configuration problem or latent bug somewhere.. I just rebuild my current today and gvim has started working for me again now -- Simon Dick [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: binutils (libintl.h) problem (was: weird binutils problem)
Please verify my hypothesis by applying this patch: Index: contrib/binutils/bfd/sysdep.h === RCS file: /home/ncvs/src/contrib/binutils/bfd/sysdep.h,v retrieving revision 1.1.1.6 diff -u -r1.1.1.6 sysdep.h --- contrib/binutils/bfd/sysdep.h 27 Jan 2002 11:58:14 - 1.1.1.6 +++ contrib/binutils/bfd/sysdep.h 9 Mar 2002 03:22:17 - -132,6 +132,7 #endif #ifdef ENABLE_NLS +#error ENABLE_NLS defined !! #include libintl.h /* Note the use of dgetext() and PACKAGE here, rather than * gettext(). Hi, I have tested your patch, and it seems it gives me the following output, which I beleive, is trying to say that ENABLE_NLS has been defined somewhere. :( -- start of attached log -- make all-recursive Making all in doc Making all in po /bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I. -D_GNU_SOURCE -I. -I. -I./../include -I./../intl -I../intl -W -Wall -g -O2 -c archive.c gcc -DHAVE_CONFIG_H -I. -I. -I. -D_GNU_SOURCE -I. -I. -I./../include -I./../intl -I../intl -W -Wall -g -O2 -c archive.c -o archive.o In file included from archive.c:131: sysdep.h:135: #error ENABLE_NLS defined !! sysdep.h:136: libintl.h: No such file or directory *** Error code 1 Stop in /data/dev/src/contrib/binutils/bfd. *** Error code 1 Stop in /data/dev/src/contrib/binutils/bfd. *** Error code 1 Stop in /data/dev/src/contrib/binutils/bfd. -- end of attached log -- -- Hiten Pandya http://jfs4bsd.sf.net - JFS for FreeBSD (JFS4BSD) http://www.FreeBSD.org - The Power to Serve msg35886/pgp0.pgp Description: PGP signature
Re: binutils (libintl.h) problem (was: weird binutils problem)
--- David Wolfskill [EMAIL PROTECTED] wrote: I'm not obrien, but yes, that is exactly what it means. Hmm, but I haven't defined it anywhere, and trust me on that, as I cvsup'ed a clean copy of the 'src' tree today, an deleting the old one. __ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
I'm able to compile kdelibs now, no problem as well as QT, but when I run configure on kdebase it locks my system up. I can switch terminals but that's it. It locks up on configure when detecting QT(I believe line 5612). The first time it did this I decided that was because I need to rebuild QT, so I did that, but it still locks up. Is anyone else seeing this with a very recent -current? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 04:35:20AM -0800, Kris Kennaway wrote: I've uploaded a new set of packages to ftp-master for -current on i386; they should be picked up by the mirrors shortly. As I mentioned in a previous mail, there were compilation problems which caused a number of ports to fail, including qt2 and gnomelibs, meaning there were no KDE or GNOME packages built (hey, at least it's a symmetric failure!). QT built fine for me with a -current as of yesterday night, and so does kdelibs, but as I posted earlier kdebase locks up the system on configure, but I believe this is known as the (Subject: Keyboard (quasi-)lockup running script) or sounds similar. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 03:36:20PM +0200, Vallo Kallaste wrote: Gvim will link against nonexistent libraries, some of them seem to be derived from libXThrStub library name and some Xlib function What revision of port/editors/vim/Makefile do you have? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 04:35:20AM -0800, Kris Kennaway wrote: The failures were caused by compiled utilities dumping core with sig11 or sig10 during compilation of the port. Toolchain people, please look into this; the error logs are at I am not sure we can say anything about the errors due to the 5.0 world under a 4.5 kernel. Can you update just one of the slaves to very -current and try some manual builds of the most problematic failing ports? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 04:35:20AM -0800, Kris Kennaway wrote: http://bento.freebsd.org/errorlogs/5-latest/ This isn't good: http://bento.freebsd.org/errorlogs/5-latest/TenDRA-4.1.2.log building TenDRA-4.1.2 on gohan17 in directory /x/tmp/5/chroot/31459 with arguments: TenDRA-4.1.2.tgz /usr/ports/lang/TenDRA maintained by: [EMAIL PROTECTED] build started at Sat Mar 9 00:37:43 GMT 2002 ... Operating system version = 4.4-STABLE I thought uname was faked out to return the proper value. I wonder if things like this could be one of the problems. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
kern_linker.c rev. 1.75 and newer cause loading problem
Well, I finally have narrowed the problem down to Revision 1.75 Fri Feb 22 04:14:49 2002 UTC (2 weeks, 1 day ago) by arr Branch: MAIN Changes since 1.74: +1295 -1271 lines Diff to previous 1.74 (colored) - Massive style fixup. Reviewed by: mike Approved by: dfr To recap: root[202] cat /boot/loader.conf miibus_load=YES if_rl_load=YES snd_pcm_load=YES snd_maestro3_load=YES linux_load=YES agp_load=YES hint.acpi.0.disable=1 root[203] kldstat Id Refs AddressSize Name 1 12 0xc010 262e40 kernel 21 0xc0363000 18330linux.ko 32 0xc037c000 15480miibus.ko 41 0xc0392000 7798 if_rl.ko 52 0xc039a000 1a14csnd_pcm.ko 61 0xc03b5000 9538 snd_maestro3.ko 71 0xc03bf000 c860 agp.ko 81 0xcb052000 2000 blank_saver.ko root[204] kldload linprocfs kldload: can't load linprocfs: Exec format error root[206] tail -1 /var/log/messages Mar 9 10:00:27 kernel: KLD linprocfs.ko: depends on \ linux - not available root[209] kldunload linux root[210] kldload linux root[211] kldload linprocfs root[213] kldstat Id Refs AddressSize Name 1 15 0xc010 262e40 kernel 32 0xc037c000 15480miibus.ko 41 0xc0392000 7798 if_rl.ko 52 0xc039a000 1a14csnd_pcm.ko 61 0xc03b5000 9538 snd_maestro3.ko 71 0xc03bf000 c860 agp.ko 81 0xcb052000 2000 blank_saver.ko 92 0xcb425000 14000linux.ko 101 0xcab88000 5000 linprocfs.ko If I back up to revision 1.74 of kern_linker.c, then this problem of Exec format error and KLD linprocfs.ko: depends on linux - not available goes away. As the commit message for revision 1.75 states Massive style fixup, I suspect a typo slipped in. However, this is a +1200 line diff and I haven't been able to find it. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 09:55:50AM -0800, David O'Brien [EMAIL PROTECTED] wrote: On Sat, Mar 09, 2002 at 03:36:20PM +0200, Vallo Kallaste wrote: Gvim will link against nonexistent libraries, some of them seem to be derived from libXThrStub library name and some Xlib function What revision of port/editors/vim/Makefile do you have? /usr/ports/editors/vim/Makefile: $FreeBSD: ports/editors/vim/Makefile,v 1.185 2002/03/04 21:13:20 obrien Exp $ -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 02:19:40PM +, Simon Dick [EMAIL PROTECTED] wrote: Any hints? Seems like some environment configuration problem or latent bug somewhere.. I just rebuild my current today and gvim has started working for me again now I did cvsup, world and new kernel, just in case.. but it really doesn't matter. Same problem. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 10:41:32PM +0200, Vallo Kallaste wrote: On Sat, Mar 09, 2002 at 02:19:40PM +, Simon Dick [EMAIL PROTECTED] wrote: Any hints? Seems like some environment configuration problem or latent bug somewhere.. I just rebuild my current today and gvim has started working for me again now I did cvsup, world and new kernel, just in case.. but it really doesn't matter. Same problem. You may try to compile vim with ./configure --disable-xim too. It worked for me. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
A MUST for all IT-Executives!
A MUST for all IT-Executives! In March 2002 the new, free it-REPORT has started for IT Executives with TOP-news, highlights and interesting topics from the sectors of eCommerce, Internet, Computer, Telecommunications etc (and so on). It will be sent to over 150.000 IT-Executives, free of charge, every week. Everyone, who orders this free-of-charge subscription by 25 March 2002 under www.it-report.co.uk will automatically be included in a draw for a handheld COMPAQ iPAQ Pocket PC. Yours it-REPORT editorial staff ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 09:42:07PM +0100, Olivier Houchard [EMAIL PROTECTED] wrote: I did cvsup, world and new kernel, just in case.. but it really doesn't matter. Same problem. You may try to compile vim with ./configure --disable-xim too. It worked for me. Tried without XIM support only, then without multibyte, fontset and XIM support, no joy. Exactly same linkage happens. Perhaps I should also note that using Motif for GUI will not change anything. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 10:00:10AM -0800, David O'Brien wrote: On Sat, Mar 09, 2002 at 04:35:20AM -0800, Kris Kennaway wrote: http://bento.freebsd.org/errorlogs/5-latest/ This isn't good: http://bento.freebsd.org/errorlogs/5-latest/TenDRA-4.1.2.log building TenDRA-4.1.2 on gohan17 in directory /x/tmp/5/chroot/31459 with arguments: TenDRA-4.1.2.tgz /usr/ports/lang/TenDRA maintained by: [EMAIL PROTECTED] build started at Sat Mar 9 00:37:43 GMT 2002 ... Operating system version = 4.4-STABLE I thought uname was faked out to return the proper value. Hmm, I thought it was too..let me look into it. I wonder if things like this could be one of the problems. Kris msg35899/pgp0.pgp Description: PGP signature
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 10:00:10AM -0800, David O'Brien wrote: This isn't good: http://bento.freebsd.org/errorlogs/5-latest/TenDRA-4.1.2.log building TenDRA-4.1.2 on gohan17 in directory /x/tmp/5/chroot/31459 with arguments: TenDRA-4.1.2.tgz /usr/ports/lang/TenDRA maintained by: [EMAIL PROTECTED] build started at Sat Mar 9 00:37:43 GMT 2002 ... Operating system version = 4.4-STABLE I thought uname was faked out to return the proper value. I wonder if things like this could be one of the problems. More like, the port builds in a chroot which contains the environment of a 5.0 world. So the chroot tarball for 5.0 being used here must be the wrong one, or it's screwed up. Thanks for pointing this out. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, 9 Mar 2002, Will Andrews wrote: On Sat, Mar 09, 2002 at 10:00:10AM -0800, David O'Brien wrote: This isn't good: http://bento.freebsd.org/errorlogs/5-latest/TenDRA-4.1.2.log building TenDRA-4.1.2 on gohan17 in directory /x/tmp/5/chroot/31459 with arguments: TenDRA-4.1.2.tgz /usr/ports/lang/TenDRA maintained by: [EMAIL PROTECTED] build started at Sat Mar 9 00:37:43 GMT 2002 ... Operating system version = 4.4-STABLE I thought uname was faked out to return the proper value. I wonder if things like this could be one of the problems. More like, the port builds in a chroot which contains the environment of a 5.0 world. So the chroot tarball for 5.0 being used here must be the wrong one, or it's screwed up. uname extracts the various strings it can report from the running kernel using sysctl. Unless you have a faked uname, it will return the properties of the host non-chroot environment, rather than the chroot environment. Increasingly, it's going to be harder and harder to run 5.0 in a 4.x chroot, due to divergence in system calls, especially once threaded applications start using KSE. Running 4.x in a 5.0 chroot should (hopefully) continue to work fine. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 07:30:21PM -0500, Robert Watson wrote: uname extracts the various strings it can report from the running kernel using sysctl. Unless you have a faked uname, it will return the properties of the host non-chroot environment, rather than the chroot environment. Increasingly, it's going to be harder and harder to run 5.0 in a 4.x chroot, due to divergence in system calls, especially once threaded applications start using KSE. Running 4.x in a 5.0 chroot should (hopefully) continue to work fine. You are right. I made a thinko, and later realized it while talking to Kris. I was hoping nobody would notice... :) We are screwed if anybody uses sysctl() or sysctlbyname(), unless someone decides to allow us to change kernel variables and the like inside chroot() (or perhaps jail()).. -- wca dunce cap To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 09:58:05AM -0800, David O'Brien wrote: On Sat, Mar 09, 2002 at 04:35:20AM -0800, Kris Kennaway wrote: The failures were caused by compiled utilities dumping core with sig11 or sig10 during compilation of the port. Toolchain people, please look into this; the error logs are at I am not sure we can say anything about the errors due to the 5.0 world under a 4.5 kernel. Can you update just one of the slaves to very -current and try some manual builds of the most problematic failing ports? Yep, I'll try that next once the current build finishes. Kris msg35903/pgp0.pgp Description: PGP signature
Upgrading to 5-CURRENT via sources
So, I've got a CVS checkout of 5-CURRENT on my 4.5-STABLE box and I'd like to upgrade to a spare partition that I have on the machine (making it dual boot). Can I just do: make world DESTDIR=/mnt/tmp And then build + drop the kernel into place + reboot? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 07:30:21PM -0500, Robert Watson wrote: uname extracts the various strings it can report from the running kernel using sysctl. Unless you have a faked uname, it will return the The cluster has used a faked out uname(1) for a long time. The problem turned out to be with its generation by the scripts. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Preparing innocent users for -current
On Fri, Mar 08, 2002 at 04:55:29PM -0500, Garance A Drosihn wrote: One thing to keep in mind here is that this is still going to be a snapshot of -current, and not a production release of -stable. We want a snapshot that does not have any serious problems, but innocent users should still realize that there are definitely going to be a lot of loose ends and rough edges around. Exactly. This text was included on the back of the 5.0 snapshot CDROM from last year : The FreeBSD 5.0-CURRENT SNAPshots are works in progress, and are intended solely for developers who are developing software on FreeBSD. There are no guarantees about the stability of these snapshot releases, although we make every attempt to thoroughly test the releases before production. It's hard for me to have sympathy for a user who doesn't read the warning labels posted all over the CD and release documentation. - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
