Date: Wed, 18 Mar 1998 21:57:31 -0500 (EST) From: "John S. Dyson" <dyson@FreeBSD.ORG> To: dannyman@sasquatch.dannyland.org (dannyman) Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: A reminder of toxic -current Message-ID: <199803190257.VAA06394@dyson.iquest.net> In-Reply-To: <19980318204724.41485@arh0300.urh.uiuc.edu> from dannyman at "Mar 18, 98 08:47:24 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
dannyman said: > On Wed, Mar 18, 1998 at 09:16:56PM -0500, John S. Dyson wrote: > > Warning, todays -current is still toxic to your filesystems. I > > am still working on it, trying to isolate the problem(s). > > ermmm, i recently rebuilt a second time after the FS scare, and neither of my > -current's have shown any trouble. i've backed up my home directory just in > case, but if my fs hasn't been destroyed yet, and is stable enough to reliably > recompile the OS, I should worry? > Yes. It is an extremely elusive problem. Are you using SMP or UP? Also, any info about your system config might be useful (so I can see how you are using your system.) It has been difficult for me to reproduce the problems since my latest commits, but they still do happen. Current is not stable enough for production use, and I want to make sure that no-one gets hosed. Karl is helping regression test the system, and if you can somehow make the problems occur, it would be useful for me to hear how. If -current works for you, I am still concerned. I would be misleading you and others if I stated otherwise!!! I really do care about people getting messed up filesystems!!! -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803190257.VAA06394>