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

Getting emdebian crush running: root passwort created by emsandboy and tty problem



Title: Getting emdebian crush running: root passwort created by emsandboy and tty problem

Hi everybody,
I posted previous threads regarding migrating from uC linux to emdebian. I am stuck right now with two problems which solutions I didn't find in the emdebian docs on emdebian.org.
After the scripts in rc.d are executed I get the repeating message that tty1, tty2 and tty3 cannot be opened:
.
.
Debian GNU/Linux 5.0 emdebian-arm ttyS2

process '/sbin/getty 38400 tty1' (pid 377) exited. Scheduling for restart.
process '/sbin/getty 38400 tty2' (pid 378) exited. Scheduling for restart.
process '/usr/bin/tail -f /var/log/messages' (pid 379) exited. Scheduling for restart.
Can't open /dev/tty1: No such file or directory
Can't open /dev/tty2: No such file or directory
Can't open /dev/tty3: No such file or directory
process '/sbin/getty 38400 tty1' (pid 380) exited. Scheduling for restart.
.
.
.

What I did is using telnet to log into the system to examine what is wrong (after removing the S20sendsigs and S30killprocs from /etc/rc.d which would halt the system). Thus I added telnetd to rc.local as well as a few debug commands (ps, ls /dev/* -l).
The telnet daemon is working, when I try to log into the emdebian system I get:
wks02-lin:~# telnet 192.168.99.245
Trying 192.168.99.245...
Connected to 192.168.99.245.
Debian GNU/Linux 5.0
emdebian-arm login: root
Password:
Login incorrect

So I thought either the emsandbox or secondstage script take the root password of the machine where the scripts where executed but both passwords don't work.

To fix the tty problem I printed out the current /dev/ folder and the ttys are indeed missing. Thus I wanted to create them with MAKEDEV console and
mknod /dev/tty0 c 4 64
mknod /dev/tty1 c 4 65
mknod /dev/tty2 c 4 66
mknod /dev/tty3 c 4 67

with adding the commands to /etc/rc.d by and checking by a following ls /dev/* -l. The creation of the character devices failed. The drivers are compiled
into the Kernel and I suppose the 4 terminal device nods have major number 4 and minor from 64 to 67. (That shows the ls /dev/* -l on the Elinos linux system).

Has anybody a hint for my how to proceed? It will be much appreciated.
Marco




Reply to: