Slack 9.1 shuts down leaving file system dirty
 

I just did a fairly generic fresh install of Slack 9.1. I chose to install it on an EXT2 file system.

Now every time I do a shutdown (which is usually done by issuing an "init 0" from the console), it claims the root file system wasn't unmounted correctly the next time I start it up. Granted I haven't even started troubleshooting this myself, but I was wondering if anyone just knows what is going on here. Of course it worked just fine with the Slack 8.1 that was on this computer previously.

try shutdown -h now
 

use -> shutdown -h now ...or... shutdown -r now ...or... reboot

i think ... i not gonna test ur way but i think u are skipping some of the shutdown so u arent doing a complete shutdown.

u might want to check in lilo or grub or whatever u use and make sure u are mounting your root filesystem read-only.

I don't know if you have a love for ext2, but I'd choose a journled file system like reiser, ext3 or even jfs.

Oh sorry guys, I figured it out.

It wasn't the root file system but a hard disk installation of Knoppix Linux on a different partition that was dirty. I guess because it wasn't the root file system, Slack didn't try to fix it. I booted the computer into Knoppix and everything got fixed and stayed that way. I imagine I also could have run fsck manually and did the same thing.

So now I'm just playing around with some of the new stuff in Slack 9.1. Which includes epiphany and the new XFCE (I already miss the fast, simple, and clean file manager they had in the previous versions, but maybe I'll get over it).

It's nice to have Alsa sound installed by default. Somehow, it always sounds better on this ymfpci sound card than the OSS driver did, I don't know why.

Overall, Slack 9.1 seems to be doing fine on this machine, which is saying something because it is actually very sick hardware that won't even install a recent MS OS! (Which is why I got it for free in the first place)

Oh yea, and if this was any sort of mission critical machine, I certainly would use a journaled file system. Since this is mostly a test/backup machine, I am just going for the lowest common denominator (well, that isn't FAT anyway) that is compatible with most anything I might boot on this thing.