SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
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 am running Suse 10.0
kernelversion is 2.6.13-15
I want to include the filesystemdriver xfs in the kernel (not as module).
Compilation did run without problems; kernelmodules too.
But as I made mkinitrd, the script included xfs.ko in initrd.
i want to include the filesystemdriver xfs in the kernel and donīt want to compile the filesystemdriver as module.
I checked the xfs option as included in the kernel (not module), but after compiling the kernel and the modules, the filesystemdriver was loaded as module.
I think that you don't understand: it is up to you how you manage xfs: module or kernel. You need to recompile it.
If I remember it correctly SuSE's config requires to compile FS (any) as a module. In your case grab vanilla kernel then you will be able to compile fs in kernel.
I compiled the xfs filesystem directly into the kernel.
But mkinitrd added xfs.ko to initrd without need.
Cause: /etc/sysconfig/kernel must be changed; there is a list kernelmodules added to initrd.
1) check out your .config (after you compiled kernel, not before)
2) have you at least changed kernel name? If you havend, then module is still there from previous kernel.
mkinitrd reads only what's in your kernel, can't make modules. If you really compiled fs into kernel, then mkinitrd will not be able to make modules. initrd is only a helper image that allows to load modules before kernel starts to look for necessary crap (ie disk controllers, fs and so on), so obviously it can't make modules if there is none.
I have compiled the kernel: xfs is included in the kernel (not as module)
compiled the modules; installed the modules
edited /etc/sysconfig/kernel: deleted xfs.ko from the kernels module list.
mkinitrd.
Yes, the straight forward way should be:
configure kernel
compile kernel and modules, make mkinitrd
kernel should only load modules, which are necessary.
I included xfs in the kernel, but xfs.ko was loaded too. I proved that with lsmod.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.