From owner-freebsd-current Mon Jul 21 07:57:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA17263 for current-outgoing; Mon, 21 Jul 1997 07:57:13 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA17252; Mon, 21 Jul 1997 07:57:03 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id AAA23939; Tue, 22 Jul 1997 00:26:55 +0930 (CST) From: Michael Smith Message-Id: <199707211456.AAA23939@genesis.atrad.adelaide.edu.au> Subject: Re: /boot.foo madness In-Reply-To: <28019.869496591@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 21, 97 07:49:51 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 22 Jul 1997 00:26:55 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, bde@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > That makes the files second-class citizens. If they're really meant > > to go along with the bootblocks, then they should be managed by the > > same tools. > > 1. I'm still not sure that it's true that they're supposed to go > along with the boot blocks. The boot blocks consider their absence as an error. Unless this is fixed (and Bruce has failed to do so despite being asked, so I have to assume he believes this is correct), they form part of the runtime bootstrap toolset. > 2. Even if so, I'm even less sure that adding them to the > `a' filesystem at disklabel -B time is an idea which > could be employed without inducing an understandable > "shock! horror!" reaction from users of disklabel. *shrug* Whatever degree of qualification it takes so that someone performing a routine update of the bootblocks on their root filesystem via the standard tools gets the entire set of boot components installed. I made my position clear some time back; while the bootstrap continues to preferentially read ufs filesystems, all the boot-time components should be in a separate directory. If we assume that this is /boot, then there would be no pain at all in updating /boot/help.default etc. when /usr/mdec was updated. > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[