From owner-freebsd-hackers Sun Jun 4 16:59:10 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA21266 for hackers-outgoing; Sun, 4 Jun 1995 16:59:10 -0700 Received: from rover.village.org (rover.village.org [198.137.146.49]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA21237 for ; Sun, 4 Jun 1995 16:59:01 -0700 Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.6.11/8.6.6) with SMTP id RAA03498 for ; Sun, 4 Jun 1995 17:58:48 -0600 Message-Id: <199506042358.RAA03498@rover.village.org> To: FreeBSD-hackers@FreeBSD.ORG Subject: Re: It's new floppy time, folks! In-reply-to: Your message of Fri, 02 Jun 1995 09:19:37 PDT Date: Sun, 04 Jun 1995 17:58:48 -0600 From: Warner Losh Sender: hackers-owner@FreeBSD.ORG Precedence: bulk : All he needs is to boot with '-c' :-) True. However, what if I don't want the machine on the network while I upgrade (to preclude the accidental possibility that mail will go to it)? I could either physically disconnect it, or just boot it in a way that I know ed0 won't be configured. What if I know that I'll have a ed0 card tomorrow, but want to finish installing and configuring tonight? What if I have a driver for xp0, but that isn't in the GENERIC kernel yet? What if I didn't notice that ed0 wasn't configured until I've entered other configuration data and I don't want to take the time out for a reboot? I think there are good reasons to allow the configuration of devices that aren't configured, even if I could, in my case, solve it by rebooting. Rebooting is a work around for this short coming, imho, it is not a solution. Warner