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!
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i have configured a kernel without FAT fs support from a base kernel version 8.This new kernel has ext2 ,ext3 support.now if i copy the fat directory into the second kernel and try to configure it using
./config
error msg : " file/dir not found" appears
if i try to insmod the fat.o of the base kernel into the new kernel(configured from base kernel) the error msg appears
" cannot find kernel version for which module was compiled"
how do i get the fat dir working on my configured kernel?
please help....
When you configure the kernel, with make menuconfig or make xconfig, add the support for the fat filesystem as a module.
It should be in the filesystem section, under DOS/FAT filesystems
Well, if you compiled your kernel, at some point you typed
"make menuconfig"
or
"make xconfig"
And got a list of all the options you could compile into the kernel, either directly (* in menuconfig), or as a module (M in menuconfig).
In the Filesystems section, you didn't specify that you wanted to use the fat filesystem. You need to either compile it into the kernel, in which case it's available all the time, or as a module,in which case it will be loaded as you need it.
alright now if fat fs is built as a module....can i use the fat.o formed on another kernel configured without fat fs support configured from the same base kernel?
stumbling blocks would be:
The module might not have been compiled with the same specs (cpu optimization, etc) or the same version of GCC as the kernel. This can lead to strange behaviour, something you DEFINATELY don't want with a filesystem.
The kernel might not realise it has a fat module if you didn't put it in the config - in trying to read a fat filesystem, it might decide it can't do it because it wasn't compiled to recognize fat, even if you stick fat.o in /lib/modules/<kernelversion>. I don't know since i've never tried.
Especially since it's a filesystem, just recompile.
... if you build it as a module, then you'll get a fat.o built for your kernel. So it'll work with your kernel. I don't see the difference between that fat.o and the one you have now except that the new one will work, and this one might not.
You can still insmod and rmmod the module - it will just be the RIGHT module.
.. I don't think I understand the problem. Perhaps rephrase?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.