Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Distribution: Lots of distros in the past, now Linux Mint
You'll need vfat support compiled in for windows, but I'm assuming you meant that. As for the ext2 thing, you need to enable ext3 support in the kernel. Taken alone, these errors might be confusing, but I have a feeling that for some reason either you missed the fs portions of the configuration, or didn't save it once you configured it. Most likely, the first option. Go through it again, and see. Running ext3 as ext2 won't cause any problems, you simply get that warning so you know there's no journaling support. If you were to continue to run it, you'd want to set up e2fsck to check you disk every once in a while (the amount depends on how much you value your data versus time you want spent on those checks).
I just compiled it to support ext3 but am having problems... Its been a while since i've used this box and so i thought i was using ext2... But then given the error i figured you were right and i had to of been using ext3 so i recompiled the kerenel with ext3, fat, VIA82Cxxx chipset, Direct Rendering Manager, and Video mode selection. Now when i boot to my new kernel the screen is blank, and when i boot to my old kernel i get the following kernel panic:
EXT2 - fs: ide0(3.6) - couldn't mount because of unsupported optional features (4)
Kernel Panic: VFS : unable to mount root on fs on 03:06
So i guess i was using ext2. I can understand that the new kernel screwed up but i don't understand why the heck my old kernel is now giving me problems. It was supposed to be a backup right? How can i fix this? I've tried booting to the CD and can't get a console
Now if theres nothing wrong with the above, could i edit my /mnt/hda6/usr/src/linux/Makefile to have this line "export INSTALL_PATH=/boot" point to /mnt/hda6/boot and recompile my kernel from this slack LiveCD, then reboot?
when configureing the kernel i fixed it by compiling all the file system support i needed as modules.
when compiling there first few kernels a common mistake is to compile alot of things into the kernel rather than modular. modules are GOOD, plus, your distro will assume that certain things are compiled as modules, if you try to compile into the kernel, it will get upset when trying to insert these already in there modules.
I'm running Slack9 but have booted to a bootable Linux CD... Heres whats on my HD in /boot config-ide-2.4.20. So since i'm on the LiveCD with my Slackware installation mounted on /mnt/hda6 all i have to do is edit the /mnt/hda6/usr/src/linux/Makefile to put the new compiled kernel in /mnt/hda6/boot/, and then after that i can just go to the /mnt/hda6/usr/src/linux/ and make menuconfig and load up the /boot/config-ide-2.4.20 file and continue compiling the kernel?
Thanks, i'll be sure to make the file systems and iptables modules