Date: Wed, 13 Jun 2012 23:27:32 +0200 From: claudiu vasadi <claudiu.vasadi@gmail.com> To: Richard Yao <ryao@gentoo.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, openrc@gentoo.org, Nathan Whitehorn <nwhitehorn@freebsd.org> Subject: Re: FreeBSD Boot Times Message-ID: <CAM-i3ihatmUJa1BBX3JHibVKg=atLtXus3NybUzfORo9jTBRgQ@mail.gmail.com> In-Reply-To: <4FD8DD76.4080001@gentoo.org> References: <4FD66F7E.2060404@brandonfa.lk> <71dc991c8d1b4d2c91ff942fc5f8f340@HUBCAS2.cs.stonybrook.edu> <4FD7CA24.6080405@gentoo.org> <e81ec0a76e5244a99ac2a8e5d26c382d@HUBCAS2.cs.stonybrook.edu> <4FD8DD76.4080001@gentoo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 13, 2012 at 8:35 PM, Richard Yao <ryao@gentoo.org> wrote: > The OpenRC is sysvinit compatible, but it has few of sysvinit's flaws. > It has named runlevels, the presence of an init script does not cause it > to start and it is in my opinion a joy to use. > > I suggest that you try OpenRC before drawing conclusions. You can > install Gentoo FreeBSD in a jail. There are instructions for this on the > Gentoo wiki: > > > http://wiki.gentoo.org/wiki/Gentoo_FreeBSD#Howto_run_G.2FFBSD_in_vanilla_FreeBSD.27s_jail > > If you find deficiencies, I am certain that the OpenRC developers would > appreciate feedback regarding them. > > On 06/13/12 10:19, Nathan Whitehorn wrote: > > On 06/12/12 18:00, Richard Yao wrote: > >> On 06/11/12 18:51, Garrett Cooper wrote: > >>> On Mon, Jun 11, 2012 at 3:21 PM, Brandon Falk<bfalk_bsd@brandonfa.lk> > wrote: > >>>> Greetings, > >>>> > >>>> I was just wondering what it is that FreeBSD does that makes it take > so long > >>>> to boot. Booting into Ubuntu minimal or my own custom Linux distro, > >>>> literally takes 0.5-2 seconds to boot up to shell, where FreeBSD > takes about > >>>> 10-20 seconds. I'm not sure if anything could be parallelized in the > boot > >>>> process, but Linux somehow manages to do it. The Ubuntu install I do > pretty > >>>> much consists of a shell and developers tools, but it still has a > generic > >>>> kernel. There must be some sort of polling done in the FreeBSD boot > process > >>>> that could be parallelized or eliminated. > >>>> > >>>> Anyone have any suggestions? > >>>> > >>>> Note: This isn't really an issue, moreso a curiosity. > >>> The single process nature of rc is a big part of the problem, as > >>> is the single AP bootup of FreeBSD right before multiuser mode. There > >>> are a number of threads that discuss this (look for parallel rc bootup > >>> or something like that in the current, hacker, and rc archives -- the > >>> most recent discussion was probably 6~9 months ago). > >>> Given past experience, a big part of getting past the parallelized > >>> rc mess would be to make services fail/wait gracefully for all their > >>> resources to come up before proceeding. It's not easy, but it's > >>> possible with enough resources. > >>> HTH, > >>> -Garrett > >>> _______________________________________________ > >>> freebsd-hackers@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > >>> To unsubscribe, send any mail to " > freebsd-hackers-unsubscribe@freebsd.org" > >> Gentoo FreeBSD shares OpenRC with Gentoo Linux. OpenRC is a BSD 2-clause > >> licensed System V init system replacement that supports parallel boot. > >> Its boot performance is competitive with systemd and Ubuntu's upstart. > >> > >> If FreeBSD's init system is serializing the boot process, it might be > >> worthwhile to consider importing OpenRC. > >> _______________________________________________ > >> freebsd-hackers@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > >> To unsubscribe, send any mail to " > freebsd-hackers-unsubscribe@freebsd.org" > > Please don't change any of the user-facing aspects of the RC system. One > > of the things that brought me (and many others I know) to FreeBSD, > > besides working sound, was having an rc.conf that was easy to configure > > instead of the nightmare that is System V init. > > -Nathan > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to " > freebsd-hackers-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > @Eitan: I think is simply does what it says (does not wait for the usb devices to be ready, instead just activates the usb hub and then the device will signal when it;s ready). My low level programming sucks and this is just a hunch. PS: I tried it on my laptop and as far as I've seen, it behaves like that. corrections are welcomed. -- Best regards, Claudiu Vasadi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM-i3ihatmUJa1BBX3JHibVKg=atLtXus3NybUzfORo9jTBRgQ>