Date: Sun, 25 Jun 1995 00:01:35 +0100 From: "Jordan K. Hubbard" <jkh@freebsd.org> To: terry@cs.weber.edu (Terry Lambert) Cc: jkh@freebsd.org (Jordan K. Hubbard), peter@bonkers.taronga.com, hackers@freebsd.org Subject: Re: Announcing 2.0.5-950622-SNAP Message-ID: <28274.804034895@whisker.internet-eireann.ie> In-Reply-To: Your message of "Sat, 24 Jun 1995 16:24:36 MDT." <9506242224.AA16162@cs.weber.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Well, that's sort of what /etc/sysconfig is eventually supposed to > > become. Then you'd never overwrite the user's sysconfig file and > > would, at most, patch it to fold in whatever knobs had been added.. > > / needs to be mountable read only. /var/sysconfig (or similar). Heh?? What does a read-only root have to do with /etc/sysconfig? If you're going to do an update then obviously you NEED to have root be read/write for awhile or you won't be able to have things like /bin or /sbin updated either! If you're using a common root from a server then obviously you're going to run the update THERE, not on the diskless workstation. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?28274.804034895>