From owner-freebsd-current  Mon Jul 21 07:50:48 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id HAA16818
          for current-outgoing; Mon, 21 Jul 1997 07:50:48 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA16810;
          Mon, 21 Jul 1997 07:50:41 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id HAA28023; Mon, 21 Jul 1997 07:49:51 -0700 (PDT)
To: Michael Smith <msmith@atrad.adelaide.edu.au>
cc: bde@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: /boot.foo madness 
In-reply-to: Your message of "Tue, 22 Jul 1997 00:08:53 +0930."
             <199707211438.AAA23834@genesis.atrad.adelaide.edu.au> 
Date: Mon, 21 Jul 1997 07:49:51 -0700
Message-ID: <28019.869496591@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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

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.

				Jordan