From owner-freebsd-current Sat May 22 11:15:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id BF91A14E26 for ; Sat, 22 May 1999 11:15:15 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id MAA09033; Sat, 22 May 1999 12:11:52 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <199905221811.MAA09033@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: "Justin T. Gibbs" , Mike Smith , current@FreeBSD.ORG Subject: Re: "hanging root device to da0s1a" In-reply-to: Your message of "Sat, 22 May 1999 19:48:37 +0200." <5827.927395317@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 May 1999 12:01:53 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>CAM has finished probing at this point, but it holds off on announcing >>devices until it has all necessary info. The drives may need to >>be spun up, etc. I believe the printf happens before the device has >>been opened and CAM blocks in the open until the device is really >>ready for service. > >I think we should hold off the rootdev determination until after the >printfs, unless you tell me that this will delay the boot by many >seconds in too many cases. It will probably add 5->15 seconds for anyone with a cdrom drive with even greater delays for people with more than 2 or 3 devices. There are also devices like scanners and older WORM devices that can take up to a minute to become ready. It seems quite silly to me to hold up booting for devices that are not even referenced during boot. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message