[BusyBox] Problems with getty not spawning correctly (more)
olivier.delouya at takimaging.com
olivier.delouya at takimaging.com
Sat Feb 12 11:47:39 UTC 2005
Hi John
Do you really need getty?
I personally use to have direct login in my initab:
0:12345:respawn:login olivier
The system continues to use /dev/console and that works fine,
with the benefit of not having to specify the precise device to that.
The only drawback is that I had to patch a kernel file to get back the
<control c> task interrupt action.. I can give you it if needed..
I must add that it may not necessarily solve your issue,
because, in the past, I was also using getty without any trouble...
Olivier
jpswensen at comcast.net
Sent by: busybox-bounces at mail.codepoet.org
11/02/2005 19:07
To
"Vijay Padiyar" <vijay_padiyar at hotmail.com>, "BusyBox Support"
<busybox at mail.codepoet.org>
cc
Subject
Re: [BusyBox] Problems with getty not spawning correctly (more)
Well, neither of those suggestions worked. We tried any number of inittab
and boot argument combinations, with no success. I guess our
misunderstanding is of what getty does exactly. Our understanding is as
follows.
1) /dev/console and /dev/ttyS0 access the serial port hardware
2) when the kernel is booting, it uses /dev/console
3) the getty respawn step basically stops /dev/console from using the
serial port hardware and switches it to /dev/ttyS0, then runs login on the
tty
Is this correct?
John
-------------- Original message --------------
> Hi
>
> Or before you do that, try changing your /etc/inittab line to:
>
> tty0::respawn:/sbin/getty -L tty0 9600 vt100
>
> with the same boot arguments.
>
> See if it works.
>
> Regards
>
> Vijay Padiyar
>
> http://www.vijaypadiyar.eu.tf
>
>
> > ----- Original Message -----
> > From:
> > To: "Vijay Padiyar"
> > Sent: Thursday, February 10, 2005 9:09 PM
> > Subject: Re: [BusyBox] Problems with getty not spawning correctly
> >
> >
> > > We are using the following bootline:
> > > console=ttyS0,9600 console=tty0 eth0=162.18.182.10
> > >
> > > It is the same bootline we used last November with success. We are
able
> > to see the output of the kernel booting until it reaches the getty
> portions
> > of the inittab script. In our inittab we commented out the lines
> involving
> > tty1, tty2, and tty3.
> > >
> > > Thanks for the help.
> > >
> > > John Swensen
> > > jpswensen at comcast.net
_______________________________________________
busybox mailing list
busybox at mail.busybox.net
http://busybox.net/mailman/listinfo/busybox
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/busybox/attachments/20050212/5a5bc463/attachment.htm
More information about the busybox
mailing list