As a server owner, I want a login as soon as the system is capable of
handling my requests. In fact, I would like a BIOS that would give me
"busybox" like access on a crashed machine.
Think of the bad days and what it takes to make them less bad.
Jim
On 2/20/08, Dustin Kirkland <email address hidden> wrote:
> On Tue, Feb 19, 2008 at 9:46 PM, peppergrower <email address hidden> wrote:
> > If you want a login available earlier, then there has to be a
> > better way to do it.
>
>
> You can swap over to tty2+ and get a login there.
>
> Perhaps it should avoid printing the login prompt on *tty1* until all
> init scripts have finished, but go ahead and display them on the rest
> of the tty's as soon as login is ready.
>
>
>
> :-Dustin
>
>
> --
> startup messages continue on screen after first login prompt appears
> https://bugs.launchpad.net/bugs/65230
> You received this bug notification because you are a member of Ubuntu
> Server Team, which is a direct subscriber.
>
As a server owner, I want a login as soon as the system is capable of
handling my requests. In fact, I would like a BIOS that would give me
"busybox" like access on a crashed machine.
Think of the bad days and what it takes to make them less bad.
Jim
On 2/20/08, Dustin Kirkland <email address hidden> wrote: /bugs.launchpad .net/bugs/ 65230
> On Tue, Feb 19, 2008 at 9:46 PM, peppergrower <email address hidden> wrote:
> > If you want a login available earlier, then there has to be a
> > better way to do it.
>
>
> You can swap over to tty2+ and get a login there.
>
> Perhaps it should avoid printing the login prompt on *tty1* until all
> init scripts have finished, but go ahead and display them on the rest
> of the tty's as soon as login is ready.
>
>
>
> :-Dustin
>
>
> --
> startup messages continue on screen after first login prompt appears
> https:/
> You received this bug notification because you are a member of Ubuntu
> Server Team, which is a direct subscriber.
>