[uClibc] problem with SiS board and buildroot-built uclibc/busybox init process

Seb James seb at hypercubesystems.co.uk
Mon Jun 14 13:54:09 UTC 2004


On Mon, 2004-06-14 at 11:40, Seb James wrote:
> BusyBox v1.00-pre8 (2004.06.12-18:46+0000) Built-in shell (ash)
> Enter 'help' for a list of built-in commands.
> 
> -sh: can't access tty: job control turned off
> #
> 
> So I need to find out how I can turn job control on... Anyone know which
> kernel option turns job control on and off for 2.4.x kernels?

Ok, I've found that the difference is in what devfs does, in 2.6.4 and
2.4.26-pre5-erik. The uclibc initscripts open consoles on tty0, tty1 and
tty3; the 2.4.26-pre5-erik kernel creates device files vc/0, vc/1 etc. I
have changed inittab to reflect this, and now getty runs.

There's still a difference, however. With 2.6.4, I get the login prompt,
(remember this is pretty much the stock filesystem generated by
buildroot) and then I enter the username "root" and just press return
for no password and gain access.

With my 2.4.26-pre5-erik kernel in charge, I can't get access as root. I
know I can fix this, as I've done it before; I need to add a user and a
password in /etc/passwd and /etc/shadow. Then I'll be able to log in and
su (with no password) to become root, but I'm puzzled as to why this
behaviour can be different between the two kernel versions. I have a
feeling I may also then have trouble with carrying out some commands as
root.

Is there a fundamental difference between using vc/1 and tty1?

Seb




More information about the uClibc mailing list