Hello Everyone,
I am using OpenSUSE 13.1 with XFCE DE. What exactly does it mean “Squashfs capable kernel” and how to check it?
Thank You.
I never saw that message. So you better explain what you did and where it showed. Most people are better able to provide help when they know more then when they know almost nothing.
Sorry for the non detailed post. Actually when going through squash file system document they say that kernel should have a support for squashfs. The Kernel which I am using has squashfs module and I can load it with
modprobe squashfs
.
I have already done the following steps.
- Added squashfs to INITRD_MODULES in /etc/sysconfig/kernel and ran
mkinitrd
- After boot the module does not load.
How can I load that module at boot.
As far as I know, all opensuse kernels should support “squashfs”. The live media use squashfs.
Modules are supposed to be loaded when first needed. If putting it in the “initrd” doesn’t load it, then the “initrd” must not need it during boot. You can try
man modules-load.d
You might want to describe why and where you want to implement squashfs.
So, some food for thought…
In the following link I describe how to configure a shared folder using libvirt’s vm manager (share a folder between host and guest). The instructions I provide specify using squashfs as the intermediate file system format. No special steps to enable a special squashfs format was required. In fact, you’ll find that today’s Linux kernel has plenty of special features built in that used to require kernel re-compiling (particularly before 2.6.50 which was… maybe in 2001?)
https://en.opensuse.org/User:Tsu2/virtfs#Overview
HTH,
TSU
On 2015-05-02 21:06, nishanth9042 wrote:
> 1. Added squashfs to INITRD_MODULES in /etc/sysconfig/kernel and ran
I’m unsure, but I think I read that with dracut (ie, 13.2), this does
not work. Have a read of this thread: «No /etc/sysconfig/kernel
installed in 13.2. Where did those settings go?» in the opensuse.org
mail list.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
He says that he is using 13.1. But I think that sysconfig setting just puts the module in the “initrd” but does not force-load it.
On 2015-05-03 03:16, nrickert wrote:
>
> robin_listas;2707976 Wrote:
>> 'm unsure, but I think I read that with dracut (ie, 13.2), this does
>> not work.
>
> He says that he is using 13.1.
I missed that.
> But I think that sysconfig setting just
> puts the module in the “initrd” but does not force-load it.
Right.
There was a setting named something like “modules loaded on boot”, but I
can’t located it now, or it was deprecated.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
Actually I am working on thin client OS which should be of size 1GB.
OK. Thanks for all your replies.
What kind of thin client?
Squashfs is one of several fs that are generally used to provide a generic fs that other systems can access.
Unless your thin client is somehow being run on top of an existing (and unspecified) fs I don’t yet see why squashfs is being used.
And, as I alluded in my prior post, nowadays squashfs is probably automatically supported without re-compiling or adding modules to the kernel.
TSU
On 2015-05-03 03:58, Carlos E. R. wrote:
> On 2015-05-03 03:16, nrickert wrote:
>> But I think that sysconfig setting just
>> puts the module in the “initrd” but does not force-load it.
>
> Right.
>
> There was a setting named something like “modules loaded on boot”, but I
> can’t located it now, or it was deprecated.
I found a note that it went (2013) to the file:
/etc/modules.load.d/MODULES_LOADED_ON_BOOT
https://bugzilla.novell.com/show_bug.cgi?id=838185
This post explains how to do it now using dracut:
http://lists.opensuse.org/opensuse/2015-03/msg00788.html
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))