I just installed slackware to see what it would be like, I am very new to linux so I was not expecting to get everything configured right. I even expected to get a little frustrated.

I was just looking around and playing in the shell. I used the dir command in the beginng just fine, five minutes later it would not work, "command not found". Why would it behave so stangely?

What exactly did you do?

Ehh...



But for future reference: use "ls" instead.



-zsejk

I tried startx, which did not work. I used the command #adduser shane. The dir command does not work in user or root shell? That is all I remember?

Forget about the dir command, that's like...DOS. As zsejk said, use ls. As for startx...did you configure your XF86Config? For that, use xf86config or xfree86setup. And why are you mentioning that you used the adduser command?

kernal asked what I did prior to my dir command stopping working. adduser was what I rember doing last. That must have been the problem. When I booted my machine this morning, I logged in as root, then my dir command worked. After su shane it no longer worked. If I rember correctly, I had to chose a shell for my new user? I think that is where the problem must have came from.

This morning I used x86config(still not working), I do not have /usr/X11R6/bin/XF86Setup.

just now I was looking at my slack partition(have it mounted from redhat) I have an xfree86setup, is this the same thing?

With Mandrake, dir has been aliased to ls.
It seems your distro does the same.
By creating a user manually, chances are that alias isn't included in that user's profile file. So if you put the same line [alias dir='ls' in bash] in the .bashrc file, you'll be just fine.

But you should use ls!

that makes sence, thanks everyone

This is the easiest way to configure X that I have found:

http://www.linuxquestions.org/questi...981#post515981