From owner-freebsd-hackers  Sat Jun 24 16:01:34 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id QAA28887
          for hackers-outgoing; Sat, 24 Jun 1995 16:01:34 -0700
Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA28877
          ; Sat, 24 Jun 1995 16:01:12 -0700
Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id AAA28277; Sun, 25 Jun 1995 00:01:36 +0100
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 
In-reply-to: Your message of "Sat, 24 Jun 1995 16:24:36 MDT."
             <9506242224.AA16162@cs.weber.edu> 
Date: Sun, 25 Jun 1995 00:01:35 +0100
Message-ID: <28274.804034895@whisker.internet-eireann.ie>
From: "Jordan K. Hubbard" <jkh@freebsd.org>
Sender: hackers-owner@freebsd.org
Precedence: bulk

> > 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