A question about lilo and automatically booting to the desktop
 

I'm trying to get my computer, which runs Backtrack 3 to automatically boot to the desktop using kdm.

The thing is, usually I have to log in as root and then run kdm to go to the desktop. Then once in the desktop as root, I would have to click on the konqueror start button --> switch user --> start new session and log into my server account. What do I need to do to get my machine to boot up automatically to the desktop as my server account?

I know that if you use grub you can use this line

title Backtrack 3 KDE
rootnoverify (hd0,2)
kernel /boot/vmlinuz vga=791 root=/dev/sda3 ro autoexec=xconf;kdm
boot

in the grub.conf to take you directly to the desktop. However, lilo.conf does not have that option. Would I have to change lilo.conf or use one of the startup scripts rc.* ??

Also, the fact that I first have to login as root to launch kdm then login as server account makes the situation more complicated. Maybe I should chmod u+s kdm? Any suggestions?

Hi.

Have you made sure that /etc/inittab has this line:
?
Note the "5" here. You probably already has a similar line, but make sure it's a "5" there.

omg that's right, forgot about that one. works great, now I just need to get it to automatically login to my server account instead of root. I found a login manager but I need root privs to edit it. For some weird reason the root password will not work?!?!?! However, the root password works fine for everything else, just not this.


Also, another question, if I'm running a program with sudo [program] then do I run the program as user root or as the current user but with root privileges? So, if someone runs an exploit on me on that program will they get a shell as root?

Got it. I was able to access the control center as root and enabled auto login for server. Sweet. Thanks guys.

AFAIK, when you run sudo you execute our commands as if you were that user (typically root). So if you run a script of application that has an exploit in it, they will get the same privileges as the user you running as (again, typically root).