hernan007
asked on
Using Linux Debian Lenny without graphic mode
Dear experts,
I have Linux debian Lenny running in an AMD geode processor I need work without of graphic mode, it is possible?
Is possible that my username and password they are provided (ej. readed from a file) in order to start automatically ?.
my best regards,
cheers,
I have Linux debian Lenny running in an AMD geode processor I need work without of graphic mode, it is possible?
Is possible that my username and password they are provided (ej. readed from a file) in order to start automatically ?.
my best regards,
cheers,
This article at TLDP should help with autologin:
http://www.tldp.org/LDP/LG/issue27/kodis.html
http://www.tldp.org/LDP/LG/issue27/kodis.html
By experimenting on my own system, I think I have a solution for you. You need to substitute your user name for mine ("dunc"). This does not require any modifications to existing software, but it does hang on to the virtual console (VC) for ever - if you exit then you get a prompt from a fresh shell.
In /etc/inittab, for each console that you want to log in, put an entry like (for vc 6):
t1:3:respawn:/bin/sh -c "exec /bin/bash 1<>/dev/tty6 2>&1 0<&1 --rcfile /root/t6 -i"
This breaks down as follows:
t1: unique inittab identifier "test 1"
respawn: init will start another process when this one finishes (as I said above, this hangs on to the VC for ever)
/bin/sh -c "exec /bin/bash 1<>/dev/tty6 2>&1 0<&1 --rcfile /root/t6 -i": Start an interactive bash shell opening /dev/tty6 for input and output, set stderr and stdin to also go to /dev/tty6 (VC 6). As it happens, /dev/tty also points there as well. The shell is to initially obey the commands in /root/t6. This leads us on to:
/root/t6 is the file of initial commands that bash should obey:
20:44:10# cat /root/t6
chown dunc /dev/vc/6
exec su - dunc
The first line sets the ownership of the target VC to be owned by the desired eventual user (init starts everything as root). You need to set ownership on /dev/vc/6 and not /dev/tty6, because /dev/tty6 is a symbolic link and chown doesn't follow it for some reason (maybe because the target is a device special file). If you miss out that line it seems to work anyway, but you get a mystery error message "/dev/vc/6: Operation not permitted".
The second line sets the process to be run by the desired user. Because of doing exec, he cannot get back to being root by doing an exit. Because of "su -" and not just "su", the target user goes through a complete login sequence, reading .bash_profile etc.
In /etc/inittab, for each console that you want to log in, put an entry like (for vc 6):
t1:3:respawn:/bin/sh -c "exec /bin/bash 1<>/dev/tty6 2>&1 0<&1 --rcfile /root/t6 -i"
This breaks down as follows:
t1: unique inittab identifier "test 1"
respawn: init will start another process when this one finishes (as I said above, this hangs on to the VC for ever)
/bin/sh -c "exec /bin/bash 1<>/dev/tty6 2>&1 0<&1 --rcfile /root/t6 -i": Start an interactive bash shell opening /dev/tty6 for input and output, set stderr and stdin to also go to /dev/tty6 (VC 6). As it happens, /dev/tty also points there as well. The shell is to initially obey the commands in /root/t6. This leads us on to:
/root/t6 is the file of initial commands that bash should obey:
20:44:10# cat /root/t6
chown dunc /dev/vc/6
exec su - dunc
The first line sets the ownership of the target VC to be owned by the desired eventual user (init starts everything as root). You need to set ownership on /dev/vc/6 and not /dev/tty6, because /dev/tty6 is a symbolic link and chown doesn't follow it for some reason (maybe because the target is a device special file). If you miss out that line it seems to work anyway, but you get a mystery error message "/dev/vc/6: Operation not permitted".
The second line sets the process to be run by the desired user. Because of doing exec, he cannot get back to being root by doing an exit. Because of "su -" and not just "su", the target user goes through a complete login sequence, reading .bash_profile etc.
ASKER
Hi thanks,
in my /etc/inittab I have
id:2initdefault
where in runlevel is
0 is halt
1 is single user
2-5 are multi-user
6 is reboot
for multi-user are 2-5 ..what is the difference?
on the other hand, I need use administrative services with c++ for sample I need use the date function
but I have problems because I need use "su" or "sudo" , I dont know how I can use it
system ("su mypassword");
system ("date mydate");
but its not work ...
thanks thanks
in my /etc/inittab I have
id:2initdefault
where in runlevel is
0 is halt
1 is single user
2-5 are multi-user
6 is reboot
for multi-user are 2-5 ..what is the difference?
on the other hand, I need use administrative services with c++ for sample I need use the date function
but I have problems because I need use "su" or "sudo" , I dont know how I can use it
system ("su mypassword");
system ("date mydate");
but its not work ...
thanks thanks
ASKER
Thanks omarfarid,
but your suggestion is the same for
id:5initdefault to change to id:3initdefault
:(
but your suggestion is the same for
id:5initdefault to change to id:3initdefault
:(
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
For running console with no gui, change the below line in /etc/inittab
From
id:5:initdefault:
To
id:3:initdefault:
For login with specific user with no password, I need to search for it and come back to you.