Damn Small Linux - Not!

hobbiest_2k3 · Joined: 11 May 2006 Posts: 1

Hi
I am new to this forum, and downloaded the ISO file I got this ERRER:-

Xauth: creating new autherity file /home/dsl/.xautherity

giving up

xinit : no such file or directery (errer 2)

unable to connect to X server
:~ $ x server

Pls help me how to RUN my DSL-N Live CD.

Thanks

hobbiest_2k3
agaur10@yahoo.com

tripes_inn · Joined: 29 Apr 2006 Posts: 6

at :~ $
have you tried xsetup.sh to configure x and after startx ?

djringjr · Joined: 08 Aug 2006 Posts: 3

I am getting the exact error message. I don't see the answer in "How to run DSL-N" or any page that deals with this.

Is this normal? Or does it mean that my computer can't run DSL-N?

I would think if you had to configure the X server, a script would lead to those questions, but I woudn't expect such a persistant error in even a Release Candidate CD.

Anyone give good clear advice?

Thanks

David

djringjr · Joined: 08 Aug 2006 Posts: 3

You WILL find yourself in this situation. The easiest thing to do at the end when your computer stops loading and you get the message that it is giving a task up, is to type:

startx

Then it will return the command to configure X and you will go through some screens. You will need to know what keyboard you want and what kind of mouse you have and your screen resolution, etc.

I hope this helps - there "should" be a script to type "To start the x server, type: startx

I know this will help many,

Best wishes,

David

roberts · Joined: 17 Apr 2006 Posts: 320 Location: OC CA USA

For most situations X starts up normally.
When there are problems when booting the system, one should use the F2 and F3 help screens provided at the initial boot prompt. There one will find the boot time option of xsetup as well as mnay others. Using xsetup provides the X seup screens that you mentioned.

djringjr · Joined: 08 Aug 2006 Posts: 3

Oh, I didn't know that - I guess if the automatic X setup fails, it gives this result. I thought the program normally exited here - it isn't a bad place to exit, it just looks (and I now see that it is) like an error.

Too bad a subroutine couldn't be written at that point to tell the user to type "startx" - then if x wouldn't start, there already is a message about the config command.

Just a small suggestion.

Be well,

D