[BusyBox] Problems with getty not spawning correctly (more)

[jpswensen at comcast.net]

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 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/busybox/attachments/20050211/485a6475/attachment.htm