rc.local is fine, but it gets executed pretty late in the boot sequence, so the whole booting happens with poor I/O and no DMA. Thus, I put it in rc.S after the "enable swapping" line - it is probably possible to put it even earlier on somewhere perhaps, but I don't know that much about slack boot scripts.

Glad your problem is solved

Thanks for the tip mrpdaemon

This is normal if it is the first time you ran updatedb... you won't see it again when running it after that.

I see.
Weird...

I am working through all my issues with Slack with relative smoothness. I am going to like this distro

I seem to be having a hard time setting up permissions for r+w+x on my other partitions though. Cant access my shared FAT partition as user (all my mp3's are there ) It seems like even as root it denies me access to changing the file permissions. I would just like to do the parent folder- i.e. /mnt/fat -for each partition and have all subdirectories follow suit.

As per that: did you indicate during install (back when you were setting up your partitions) that you wanted to be able to reach your Windows partition from Slackware?

-zsejk

Yes. They are accessable as root and are automatically mounted at boot. I just can't even view the directory as normal user.

I haven't even really fooled with it aside from half hour or so. I am still working on this kupdated CPU problem. The hd tweaks made it run much quicker, but I still have the intermittent CPU @ 100% load thing. Been all over Google on it. TONS of people have this same problem and have done extensive research on their machines. I am learning from it, but no one seems to have to solution. All the info leads to different places where it eventually tapers off as if people give up on it. I personally, have put around 20 hrs in 2 days into it

About your FAT problem, you can try changing the way the drive is mounted in /etc/fstab

most probably, the "options" part of the line containing your FAT drive (lets say /dev/hda3) is set to "defaults" , or even "ro". The options you want to have are uid=1000 (user with id 1000 becomes the owner of the drive) and possibly umask=0000 (don't remember exactly what it did, but had to do something with the default permission of newly created files).

save fstab, umount /dev/hda3 , mount /dev/hda3

and see if you can write it with the user which has ID 1000.

That did it! Thanks again mrpdaemon.

HI,
I had this exact same problem with my mandrake 9.2 box. This may sound stupid but after installing the driver for my video card provided by nvidia, my cpu problem was solved. I guess It was channeling cpu power by some way. If you didn't resolve your problem, I hope it helps you and if not well somebody else might benefit from this small solution to a big problem.