Before someone else comes along, I'll just mention that I don't understand "run dcopserver" at all.

For Slackware, if you're using the default method of starting in runlevel 3, you'll come to a "login:" prompt where you login to the system. This is where you need to login as a normal user. (And yes, even without being on a LAN or WAN, you should use the normal user account, except for needed system administration work. This keeps you from hosing your install, or messing up critical system files.)

After that, you can issue "xwmconfig" and choose your window manager. After you select one and enter OK and it takes you back to a user prompt, you will enter "startx" to start the X server.

With the system you have, I highly recommend you read Darrell Anderson's information I referred you to in my last post ... before going any further. Just give yourself a day or so to get familiar with what is in the Slackware Handbook earlier referenced, and the Slackware Desktop Enhancement Guide, then start configuring it.

I imagine you're anxious to "do something." However, if you do too much now, you'll more than likely hose your system (especially logged in as root) and decide that reinstalling becomes your only option to fix it.

Been there, done that, got the t-shirt!

Fair enough.

I'm getting different errors as a normal user.
Been messing around with xauth, and iceauth with root(i'm supposed to use root for that, right?). I just really don't know exactly what I should do.

do x run on this?

Never found a reason to mess with them here. I'd say don't.

As for this error:
That can be ignored. It's in every /var/log/Xorg.0.log I've ever had.

Where are you getting those other messages?

I think the first is a typo? It should be called "dbus-launch" with the trailing "h" and I have found it in /usr/bin. It came with my installation of Freerock Gnome but is not included in the stock Slackware packages (and should therefore not be essential I guess).

I'm wondering why you have to deal with xauth iceauth and that stuff. I never had to treat the X server as root despite the initial configuration with xorgconfig (and editing the file to get my scroll mouse working). So did you create those files as root or changed unintentionally the permissions of user worm's home folder?

Try to start a simpler window manager, not a desktop environment to check if your X server is configured right. Type "xwmconfig" as user and choose blackbox, fluxbox or something like that from the list but not KDE, Xfce or Gnome. You can change that again the same way easily but can hopefully be sure that the basic X server is running nice.

Did you run xorgsetup or xorgconfig before trying to startx? You may want to read this page: http://slackware.com/config/x.php

Possibly!
for fluxbox I get
mkdir: cannot create directory /home/worm/.fluxbox input/output error

Then it complains that no /.fluxbox exists

I attempted adding the user to 'disk'. But I'm really confused otherwise.

One more question. Why does it call my OS read-only on occassion?

Anyway, well trying to put a password on my root, I locked myself out of it. EDIT: I can fix this part.

Just as I suspected, and mentioned in earlier posts. You've gotten way off the beaten path, and messed up your installation. I'll not offer any new advice at this point, since you weren't willing to follow earlier advice. But you might find yourself reading Post #16.

Links for you...

http://www.catb.org/~esr/faqs/smart-questions.html
http://www.slackbasics.org/html/slackware-basics.html
http://humanreadable.nfshost.com/sdeg/
http://slackbook.org/html/

What output do you get from "ls -l /home/worm/" or even "ls -l /home/"? The files and folders should be owned by user "worm" and group "users".
If you screwed it up maybe you can fix it as root with "chown -R worm:users /home/worm/" so that the /home/worm folder and all files and folders below will get the right permissions ...

I think Chinaman is right, you screwed something up. May be that the changes are not soooooo great, but prepare to do a new install and take it as a learning experience.

Chinaman, although I agree with your initial assessment of his attitude, I'll say that it looks like he's definitely improved his approach since the first few posts. I think your last couple of posts were a bit harsh. (You and I have spoken before (irc and here), although not in a while, and I hope you'll see this as just my observation and not a personal dig).

Jbernoski, keep at it. This is what I imagine has happened:

You got slackware installed. The boot loader was installed improperly to the
root instead of to the MBR. You fixed that. Good on you. Now, there is either
a software or hardware problem prompting the 'input/output' error. The likely
hardware problem is a failing hard drive. Linux is typically much more tolerant
than most other OSes, so it's conceivable that you got it installed and partially
functional even with that.

The possible software problem could be one of two things:
1) While fixing the Lilo/mbr issue, you neglected to add an option which prompts
linux to remount the root filesystem / as read-write. When linux first boots, it
is mounted read-only by default, in the event that the machine was taken down by a power outtage, to prevent further corruption and allow an 'fsck' to run and fix it. If you do 'cat /proc/cmdline' you should see something similar to this:

BOOT_IMAGE=slack-2.6.15.4 ro root=302

If that 'ro' bit is missing, this is the problem.

The second possible software issue is that you ran 'useradd' isntead of 'adduser'. The 'useradd' command expects you to set up the user's details (home directory, permissions etc) manually. 'adduser' does this automatically. Checking the permissions as suggested above should fix this.

Since, however, you're getting the 'input/output' error as root, as well, I suspect it is either the failing hard drive scenario, or the 'ro' lilo configuration scenario.

For further help, please post up the output of 'cat /proc/cmdline' and 'mount'.

-- Shade

I just usermod -p'ed when I should have well whatever that other damn password command was. I searched a little on how to fix it and am starting with a fresh install. My HDA's are numbered wrong. I'm sure there's a way to fix it. But if it works, I'll live with it.

I appreciate the links. Erstwhile, someone hit the nail on the head.

On a personal note, do you really think linking to a FAQ on how to ask good questions is anything but trolling? Do you post these replies to people who you believe "don't know their place"? Has this condscending crap helped any of the people you linked it to? I'm not trying to insult you, I just really question your methods.

I'm getting perfectly good help from other members of this forum none of which have taken offense at my post. I just don't understand why you keep posting this non-help stuff.

No. It went from box to laptop. If it was a failure wouldn't uh I don't know. Wouldn't filling the entire part of the harddrive where I'm having errors have prompted an error in itself? I've really thought about this, and I just don't believe it's the harddrive.

This is probably it. Thanks.

On the contrary. That article has been very useful to me. It will not only teach you how to present your problem in a mature, thought-provoking way; it will also teach you how to get help from people who actually know about the software or hardware you're dealing with.

I chose to look at your thread because the title was "Finished full slackware install and nothing." After a few years of full Slackware installs, I wondered how anyone could do so and come up with nothing?

Upon reading your posts, I felt you would benefit from reading "How To Ask Questions The Smart Way" as much as I have.

Haha, I provoked a thought!

Anyway, fresh install and now it runs great. And we can print out this post and hang it on our fridges, and all give ourselves gold stars, because WE DESERVE IT!

One question. Will giving a 32mb system a load of swap space create a noticiable improvment in KDE?

KDE won't run on a box with only 32MB RAM.
If you give swap 512MB, it will help, but
swap still isn't as fast as RAM, so it will
be very slow at best.

No. It actually does run. Just a little slow.

It's like running one of those systems that are loaded up with spyware. I haven't tried Mozilla or anything like that of course. Though,it really doesn't run so bad with all the bells and whistles turned off.