From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 13 23:33:30 2012 Return-Path: <owner-freebsd-hackers@FreeBSD.ORG> Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (unknown [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8B97106566B for <freebsd-hackers@freebsd.org>; Wed, 13 Jun 2012 23:33:30 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from yoshi.bluerosetech.com (yoshi.bluerosetech.com [174.136.100.66]) by mx1.freebsd.org (Postfix) with ESMTP id C9FF78FC14 for <freebsd-hackers@freebsd.org>; Wed, 13 Jun 2012 23:33:30 +0000 (UTC) Received: from vivi.cat.pdx.edu (vivi.cat.pdx.edu [IPv6:2610:10:20:214::6]) by yoshi.bluerosetech.com (Postfix) with ESMTPSA id 6CA53E600B; Wed, 13 Jun 2012 23:26:12 -0700 (PDT) Received: from [IPv6:2001:470:8643:970:211:43ff:fe70:5826] (unknown [IPv6:2001:470:8643:970:211:43ff:fe70:5826]) by vivi.cat.pdx.edu (Postfix) with ESMTPSA id 38ED924C8A; Wed, 13 Jun 2012 16:26:11 -0700 (PDT) Message-ID: <4FD92190.1070900@bluerosetech.com> Date: Wed, 13 Jun 2012 16:26:08 -0700 From: Darren Pilgrim <list_freebsd@bluerosetech.com> User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.4) Gecko/20120421 Thunderbird/10.0.4 MIME-Version: 1.0 To: Eitan Adler <lists@eitanadler.com> References: <4FD66F7E.2060404@brandonfa.lk> <alpine.BSF.2.00.1206130909310.73934@wojtek.tensor.gdynia.pl> <1339593689.73426.8.camel@revolution.hippie.lan> <201206132155.22111.hselasky@c2i.net> <CAF6rxgng+Y=egdiZ_kT4UTt5nVbEAA1-TsmmvZh7WpOLc40dwg@mail.gmail.com> <CAM-i3ig2QSDRqu-eTNEjdBFURVCQ7qFom=Utg-_XbkzNoMh5gA@mail.gmail.com> <CAF6rxg=6QaSFT9=_K+0-fkCnH+g=WGajaTuChwapydPwkEoSdg@mail.gmail.com> In-Reply-To: <CAF6rxg=6QaSFT9=_K+0-fkCnH+g=WGajaTuChwapydPwkEoSdg@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Boot Times X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD <freebsd-hackers.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers> List-Post: <mailto:freebsd-hackers@freebsd.org> List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 13 Jun 2012 23:33:31 -0000 On 2012-06-13 14:18, Eitan Adler wrote: > On 13 June 2012 14:16, claudiu vasadi<claudiu.vasadi@gmail.com> wrote: >> If you simplky do "sysctl -d hw.usb.no_boot_wait" you will see the >> explanation ;) > > No, you see a one liner that only explains things if you already > understand what is going on: I believe it pertains to mounting root from a USB device. When set to 0, usb_attach tells VFS to wait on the USB device being attached. This results in not mounting root until the USB busses are all fully explored. If you don't rely on any USB devices for multi-user start-up, set this to 1 and let the kernel launch multi-user without waiting for USB probing. This is nice for those systems where the BIOS takes a long time to release control of any hubs with keyboards attached. IMO I'd rather have my gear do the boot process in a well-ordered fashion and get everything right, than try to shave off a handful of seconds at the risk of unreliable booting. For servers, the baseboard, OOB management, and SCSI BIOSes can mean minutes between power-on and OS bootstrap, so an extra 20 seconds is nothing. :)