Date: Wed, 12 Jan 2000 08:29:44 -0500 From: Tom Embt <tom@embt.com> To: Christian Carstensen <cc@devcon.net>, Donn Miller <dmmiller@cvzoom.net> Cc: current@FreeBSD.ORG Subject: Re: why is my current so .... stable? Message-ID: <3.0.3.32.20000112082944.01636938@mail.embt.com> In-Reply-To: <Pine.BSF.4.10.10001121422430.97990-100000@pauling.research .devcon.net> References: <Pine.BSF.4.20.0001120706140.1479-100000@lcm97.cvzoom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 14:27 01/12/2000 +0100, Christian Carstensen wrote: >On Wed, 12 Jan 2000, Donn Miller wrote: > >> My guess is that once -current gets closer to the release date, it becomes >> more and more stable. I guess the period of greatest instability occurs >> somewhere about 1/4 to 1/2 through the -current life cycle. We could do a >> chart plotting stability vs. time for the life cycle of a given >> -current. That could help people decide whether or not they want to run >> -current. > >This would be great, but I wonder from what source we could take reliable >data about -current's stability. >But what I've meant was: I've had these ugly system freezes not perfactly >reproducable, but very often. From what I've read on current list, the >problems still exist, but not on my system. At least this system runs >stable for 1 day now. I'm wondering, why. > How 'bout some sort of client program that is run via the rc.d and rc.shutdown scripts? When run on bootup it checks dmesg for "WARNING: / was not properly dismounted", and tells a master server whether or not the last reboot was intentional. When run at shutdown it tells the master server the machine's uptime. Of course it would also help to send a 'uname -v' in both situations. This system would have statistical flaws, but it is still an interesting idea. Tom Embt tom@embt.com 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?3.0.3.32.20000112082944.01636938>