From owner-freebsd-current Wed Dec 16 12:45:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07872 for freebsd-current-outgoing; Wed, 16 Dec 1998 12:45:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07866 for ; Wed, 16 Dec 1998 12:45:34 -0800 (PST) (envelope-from rkw@nomad.dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.1/8.9.1) with ESMTP id OAA01018; Wed, 16 Dec 1998 14:45:19 -0600 (CST) (envelope-from rkw@nomad.dataplex.net) Date: Wed, 16 Dec 1998 14:45:19 -0600 (CST) From: Richard Wackerbarth To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: disklabel baggage. In-Reply-To: <199812162001.MAA81180@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I agree that we need to keep "/" clean. However, I do not feel that "/etc/" is at all appropriate for boot blocks. "/etc/" is a configuration directory. I routinely overwrite it or mount it remotely. "share/" was the original location for auxillary files. As for "/usr/?" vs "/?", that should be determined by the need to use the blocks in single user salvage mode when we assume that there is only one good disk mounted. Do we need to be able to disklabel another disk? The installed bootfiles are another matter. Obviously, they must be located on the root partition. Traditionally, the kernel was placed in the root so that the boot loader did not have to understand the complexities of traversing directories. Now that we have many more bootstrap files, the root seems cluttered. However, since these files are used only at boot time, they are easy to simply ignore. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message