From owner-freebsd-current Sun Jan 10 02:27:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29231 for freebsd-current-outgoing; Sun, 10 Jan 1999 02:27:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29226 for ; Sun, 10 Jan 1999 02:27:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id CAA51116; Sun, 10 Jan 1999 02:26:36 -0800 (PST) To: Robert Nordier cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: /boot/boot.conf -> /boot/boot.rc In-reply-to: Your message of "Sat, 10 Jan 1999 12:19:33 +0200." <199901101019.MAA09062@ceia.nordier.com> Date: Sun, 10 Jan 1999 02:26:35 -0800 Message-ID: <51112.915963995@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The present boot.config is still needed to set serial options, > particularly for remote administration. (The idea being that the > bootblocks are more likely to survive a corruption of /, and can > boot an emergency ELF or a.out kernel if necessary.) OK, a fair point. > Most of the time, these files probably *won't* exist. However, when > they *do* exist, they might as well exist under more appropriate > names. Hmmm. How about a compromise, since I'm still hung up on the POLA argument for legacy users of boot2? Have it look in both locations, /boot/boot2.conf being first, and don't print an error message if it can't find one of them. Would that be too many speculative reads? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message