[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Reading boot messages on the fly



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 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


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]