From owner-freebsd-current Mon Jul 21 11:31:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA01362 for current-outgoing; Mon, 21 Jul 1997 11:31:57 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA01357 for ; Mon, 21 Jul 1997 11:31:54 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id LAA12016 for current@freebsd.org; Mon, 21 Jul 1997 11:31:53 -0700 Date: Mon, 21 Jul 1997 11:31:53 -0700 From: Sean Eric Fagan Message-Id: <199707211831.LAA12016@kithrup.com> To: current@freebsd.org Subject: Re: /boot.foo madness Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <28688.869506407.kithrup.freebsd.current@time.cdrom.com> you write: >Hmmm. It's a slightly divergent topic, but I guess I should also say >that I favor putting these new foo.config files into a /boot >subdirectory here and now before they get doc'd in too many places. >I think too many new files have gone into / at this point. You know, there *is* something to be said about the SysVr4 method of having a "/boot" filesystem, with a simplified FS for it. (The simplified FS [no subdirectories, no non-file types, no indirect blocks] means that the boot program can generally be easier.) I don't know if we would be able to go this way, though, because it would require changing the partitioning, which would make doing an upgrade a lot harder. Still, it may be worth thinking about. Sean.