Reading boot messages on the fly
Peter Jones
pjones at redhat.com
Wed Oct 4 15:25:21 UTC 2006
On Tue, 2006-10-03 at 08:37 -0500, Jay Cliburn wrote:
> On Mon, Oct 02, 2006 at 11:24:53PM -0400, Bill Nottingham wrote:
> > Jay Cliburn (jacliburn at bellsouth.net) said:
> > > Bill Nottingham wrote:
> > > >
> > > >boot_delay affects kernel messages only; it does not affect userspace
> > > >messages (such as the initrd, etc.).
> > >
> > > Is a printk from the bowels of, say, a network driver considered a kernel
> > > message or a userspace message?
> >
> > Anything printk is kernel, anything else is userspace.
>
> Thanks. That's what I thought. Then boot_delay doesn't work as advertised.
> Try it.
It does -- once the initramfs is loaded and init has been executed,
userland is running. It's "boot" delay for a reason. From the kernel's
perspective, once userland is running, it's finished booting.
--
Peter
More information about the fedora-test-list
mailing list