(Posting in this thread since its a related problem.)
Hello guys, thanks for all that info, I'm saving it on a thumdrive to transfer over to my Slackware partition so I can hopefully get my internet working. I just thought I would post asking if the steps are any different for people with cable internet, and modems that connect via ethernet cables. Well, I'm off to try all this out, if I get it working I'll be sure to mention here.

I think it is safe to take it out. You can check if Linux still considers the drive connected by doing

df -mh

in a terminal. This will list all connected drives. If you see the /dev/sda1 (or whatever your flashdrive device is) mountpoint still listed, the drive is still mounted and you should NOT just pull it of the USB port.

Note that is if a disk does not want to unmount, you can force-unmount it with the -l option:

umount -l /mnt/flashdisk

This is not recommended though. I sometimes do get this (that a flashdrive won't unmount - for no reason I can determine) and it seems that waiting a few minutes and trying to unmount "conventionally" again seems to work. Use -l only if you are in a hurry, or you have already waited a while and the drive still won't unmount.

On the desktop? I see another poster has already supplied the ln -s example. On the KDE desktop I click right then select "Create New" then "Link to Location".

I encountered this problem just now:

Last night, after configuring my audio, mounting my thumbdrive, and sccessing the internet for the first time in one session, my PC hanged while trying to shut down. Today, I booted up Slackware then there was an error. I guess it's the equivalent of Window's ScanDisk(pardon me, it's still Wednesday - I still haev a lot to learn hehehehe). Then I was given the option to press Ctrl+D or enter as root. I logged in as root then everything seemed fine until I tried to log out of KDE. My PC hung up again. So I turned it off manually then turned it back on. This time, I couldn't go in. This was displayed:

Then after a few tries of getting pretty much the same thing, I found a little message that said "Run fsck manually without -p" or something like that. And all is well now. But I'm afraid that my PC might hang up again once I try to log-off or shutdown.

What caused the problem? And how may I avoid it?

It's official. My PC hangs every time I try to log off or turn it off.

Help.

In Linux, "hanging" is a pretty odd occurance, but thankfully fairly easy to debug!

First, you need to go and learn about run levels (in general, then the exact ones Slack uses):
Generally speaking, this is pretty good: http://en.wikipedia.org/wiki/Runlevel

Then, we need to do some experimenting as to *where* the lock occurs (we'll come back to run levels in a bit, promise!).

Step 1 is to have a look through some of your logs, see what's happening at the point of lock up. Logs you should peruse include ...

/var/log/messages
/var/log/messages.1

/var/log/syslog
/var/log/syslog.1

And if you were in X when you tried to shut down, then you should look at:

/var/log/Xorg.0.log
/var/log/Xorg.0.log.old

I would expect some of these other particularly smart guys can tell you what each log should contain (and what it all means!), but both messages and syslog are timestamped, so have a look at what's going around that stamp and familiarise yourself with the logs themselves, since you're about to start some debugging and I would bet your left leg, someone will ask to see those logs it helps enourmously if you can omit the worthless stuff - as i'm sure a smart guy like you is well aware (Slack since Sunday! I am in awe!) =D

You could also try doing some run-level debugging. Drop down one run level at a time and see what happens, where the lock occurs.

I would start at the top (Slack defaults to run level 3 ... you haven't specified what you're in ...) and move down until your PC is off.

So, from 3:

You can also do some trial & error work on services, by chmod -x 'ing some of the /etc/rc.d/rc.* scripts. Leave the run level ones like rc.S, rc.inet* and rc.sysvinit and so on, but the services like: samba, cups, udev, etc etc etc can be tweaked ...

Or a more sensible approach to turning off services may be to run:

And head to Setup --> Services, which won't break your startup scripts =D

So, not really a solution, but possibly a way of finding some information that we can use to find a solution. Keep at it!
- Piete.

How do I do this?

Uhm, I still haven't tried installing or uninstalling stuff yet. So I'm not yet familiar with packages. But I'll read up on it when I get home. ^_^

Thanks Piete.

*UPDATE*

These are my new observations...

-If I logoff from KDE using the start menu while using root, it freezes.

-If I shutdown while inside KDE through Konsole while using root, it also freezes.

-If I logoff as another user, it does what it's supposed to and goes back to the terminal. From there, I logout then login as root(w/o starting up the window manager again). Then type "shutdown -h now" without any trouble.

I guess the problem has to do with root logging off from KDE.

You shouldn't be logging in to KDE as root anyway. It's bad for security. Use kdesu to run graphical applications as root, if you need to.

I'll keep this in mind. Thanks.

I don't understand: from the shell I should type . Is this what you mean?

No, you need to type kdesu and then the command that you want to run. For example, if I wanted to modify my fstab using kwrite, I'd use the following command at the shell: 'kdesu kwrite /etc/fstab &'.

Under GNOME it's possible to do the same thing using gksu or gksudo. Note that you only need these commands for graphical programs. If you were editing fstab with a text mode editor such as nano then you'd either need to use sudo or change to root using su and then run the editor, e.g.
or
Another alternative if you want to edit a file that belongs to root is to find the file in Konqueror, right click on it and select "Actions->Edit as Root".

Hope that helps.

Thanks a lot
It helps, it helps a lot