Date: Wed, 18 Mar 1998 23:20:12 -0500 (EST) From: "John S. Dyson" <toor@dyson.iquest.net> To: dannyman@sasquatch.dannyland.org (dannyman) Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: A reminder of toxic -current Message-ID: <199803190420.XAA00526@dyson.iquest.net> In-Reply-To: <19980318211402.23977@arh0300.urh.uiuc.edu> from dannyman at "Mar 18, 98 09:14:02 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> On Wed, Mar 18, 1998 at 10:07:57PM -0500, John S. Dyson wrote: > > John S. Dyson said: > > > > > > 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!!! > > > Following up on my own posting: Maybe I am not being strong enough in > > my suggestion: Please do not use the -current kernel unless you know > > that the consequences will be that you will likely loose filesystem(s). > > > > Karl is trying to help with testing and advice, and unless you want to > > participate in trying to narrow down the problem, please don't use > > -current until we figure out what is going on. > > John: > > I am aware of the consequences, but to be honest, I don't know how to "revert" > or anything. Some cvsup option that'll reverse the code on my system? > > I've backed a few things up, I'll back some more up. I'm happy to "ride out > the storm" as it were, especially since things have been fine so far. I am > happy to share system information if it will help any. > Try checking out a kernel like: cvs co -D12-mar sys build and use that. It is likely safer than current as of today. It took me an entire day to recover my system during the weekend. I can't say it strongly enough to avoid using -current until we figure out the problem! John 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?199803190420.XAA00526>