Re: xdm....HELP!!!!!!???????
Brian V Bonini [EMAIL PROTECTED] writes: I started to set up the .xsession file and instead of doing this for my user account until I got it right for some reason I did it for my root account. [snip] As well as the other solutions mentioned (Ctrl-Alt-F1, su, linux -single, rescue disk), you should also be able to log on using [F1] after the password insted of [Enter], which will pop up a single xterm without running your .xsession. Actually, I *never* log in to X as root, but just use `su'. -- Carey Evans * http://home.clear.net.nz/pages/c.evans/ gc As a concept, virtual reality seems to appeal to people who spend a lot of time indoors. - Gregory Benford -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: xdm....HELP!!!!!!???????
Alan Su [EMAIL PROTECTED] writes: Brian V Bonini wrote (Thu, 11 Dec 1997 14:28:59 -0500 ): |What I need to do is somehow stop xdm at boot up (I'm booting Linux from a |floppy) so I can get access to the console as root and delete the |.xsession file that resides in /root. Please HELP |Thanks |-Brian, ([EMAIL PROTECTED]) | Why don't you just log in with your user account and su to or even login as root? You can also wait for the X server to start up and then hit Ctrl-alt-f1 to get to a console... I could add to this that in order to stop xdm from starting up at boot time, you need to edit the file /etc/X11/config (as root). Change the line start-xdm to no-start-xdm. - Sten Anderson -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
xdm....HELP!!!!!!???????
Hello, Ok I checked the FAQ but there is no info on this potentially really dumb question. When I installed the server I chose to have xdm start at boot up. This works great noprob there. But I messed up. I started to set up the .xsession file and instead of doing this for my user account until I got it right for some reason I did it for my root account. So now I have an .xsession file in /root that is not written correctly it times out and just keeps returning me to the login screen. With my user account I do not have the correct permissions to change anything related to this so it does me no good. What I need to do is somehow stop xdm at boot up (I'm booting Linux from a floppy) so I can get access to the console as root and delete the .xsession file that resides in /root. Please HELP Thanks -Brian, ([EMAIL PROTECTED]) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: xdm....HELP!!!!!!???????
Brian V Bonini wrote (Thu, 11 Dec 1997 14:28:59 -0500 ): |What I need to do is somehow stop xdm at boot up (I'm booting Linux from a |floppy) so I can get access to the console as root and delete the |.xsession file that resides in /root. Please HELP |Thanks |-Brian, ([EMAIL PROTECTED]) | Why don't you just log in with your user account and su to or even login as root? You can also wait for the X server to start up and then hit Ctrl-alt-f1 to get to a console... If there's some reason why you don't want to do this, you can try to boot into single user mode. This would probably require you to have LILO installed on your floppy. If you do, at the LILO prompt, hit Shift, and a boot: prompt should appear. type the image name you want to boot (probably linux, hit tab to get a list), followed by -single. So, the whole boot line will look something like: LILO boot: linux -single Once in single user mode, just go to /root and make the fix. Alternatively, if you still have the Debian rescue/install disk, stick that in there, and boot. Once the install starts, you can use alt-f2 to switch to the virtual console which runs ash (a striped down shell). From there, mount the appropriate file system in /mnt or something and modify the file. Then remove the install/rescue disk, stick in your own, and you should be fine. -alan -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
