Date: Fri, 10 Mar 1995 23:20:25 +0930 (CST) From: Lucas James <jj@ldjpc.apana.org.au> To: David Greenman <davidg@Root.COM> Cc: Amancio Hasty Jr <hasty@netcom.com>, hackers@FreeBSD.org Subject: Re: SNAP or current? Message-ID: <Pine.BSF.3.91.950310231803.218B-100000@ldjpc> In-Reply-To: <199503100801.AAA04134@corbin.Root.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 10 Mar 1995, David Greenman wrote: > >> Umm, I wouldn't count on the next SNAP being too stable. I have a dozen > >>serious bugs (panics or system hangs) on the whiteboard, and I don't expect > >Care to elaborate ? > >Mostly because I am not seeing any panics over here (cross my fingers) and > >perhaps they could be due to a driver or option configured in the kernel. > The above is just a sample and doesn't include what I consider the most > serious of the bugs - the wild pointer that randomly corrupts kernel memory. > If I could reproduce that problem at will, I'd have it fixed by now. > Unfortunately, it happens about 1 in 100 times I boot the machine, just after > fsck finishes...or at random other times during normal system use. If you're > lucky, it will just cause the machine to die. If you're unlucky like John, it > will corrupt some FS buffers and destroy your superblock and root directory. Ah... so that's what happened on Tues... (It deleted the directory /sbin (and left a lot of unrefed files.... :( I've been trying to get my machine back up and running ever since :( > Don't get to comfortable with -current...and do regular backups. :-( What's a backup? <*grin*> Lucas James jj@ldjpc.apana.org.au <where did I put my .sig file?>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.950310231803.218B-100000>