Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Jan 2001 16:23:13 -0700 (MST)
From:      Nate Williams <nate@yogotech.com>
To:        Doug Barton <DougB@gorean.org>
Cc:        Matt Dillon <dillon@earth.backplane.com>, Sheldon Hearn <sheldonh@uunet.co.za>, <obrien@FreeBSD.org>, <cvs-committers@FreeBSD.org>, <cvs-all@FreeBSD.org>
Subject:   Re: cvs commit: src/etc crontab rc src/etc/defaults rc.conf src/etc/mtree BSD.root.dist src/libexec Makefile src/libexec/save-entropy Makefile save-entropy.sh 
Message-ID:  <14942.16481.241677.610222@nomad.yogotech.com>
In-Reply-To: <Pine.BSF.4.31.0101111412320.11112-100000@dt051n37.san.rr.com>
References:  <200101111912.f0BJCst72747@earth.backplane.com> <Pine.BSF.4.31.0101111412320.11112-100000@dt051n37.san.rr.com>

next in thread | previous in thread | raw e-mail | index | archive | help
[ I've stayed out of this so far, and I probably shouldn't jump in, but
  I needed to state this one thing. ]

> Yes, periodically writing things into / is "non-traditional" to say
> the least, but I don't think it's going to set anyone's house on fire
> either.

Just to bring things back into perspective, periodically writing things
to / is actually going to burn someone *really* badly, especially in
-current.

Because the root's FS state is constantly changing with this code (we-re
not re-using files, we're rotating files, etc...), the chances of having
a latent kernel bug corrupt your FS went up by a couple orders of
magnitude.  The chances of having this code running when 'something bad
happens' which causes root filesystem are now higher than what I
consider acceptable.  Crashing a kernel in the middle of writing to the
file system tends to cause bad things to happen.  (Soft-updates
minimizes this, but soft-updates don't work well on /, and I don't yet
trust softupdates on /).

Not-writing to / is akin to having all of the binaries in / static.
It's not necessary when everything works fine, but when things go bad,
boy is it ever nice.

Finally, with -current not being confused with -stable at all lately
(ie; crashes are a fairly common occurance), I would hate to see Yarrow
et. al get blamed for trashed FreeBSD root partitions.  The real bugs
are the kernel bugs that causes the crash, but Yarrow will get blamed
for unbootable FreeBSD boxes.

'Nuff said.


Nate


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14942.16481.241677.610222>