Slackware - ARMThis forum is for the discussion of Slackware ARM.
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.
Hi , I just started to play a bit with my RPi v1 and the excellent guide from rpi.fatdog.eu . Thanks for making this site and packages to drmozes and whoever is the creator.
So I would like to understand one thing, do I need a initrd.gz file with the jfs filesystem inside if I want to install it on my root partition ?
Do I create it with the standard slackware way mkinitrd script or am I missing something ?
Probably I could use also btrfs in that same way correct ?
It depends if the kernel has jfs compiled into the kernel or as module, and that may depend on what kernel you are running.
The only PI I have running on fatdog's kernel is a rPI2 with the hardfloat miniroot which has JFS compiled as module.
I'm not sure if the rPI1 kernel is compiled the same (chances are that it is) but I can tell you how to check:
If it's "CONFIG_JFS_FS is not set" then your kernel does not support JFS,
if it's "CONFIG_JFS_FS=y" then you don't need initrd to load the module ... the kernel should be able to mount jfs root as long as the cmdline.txt is set accordingly in the PI's boot partition with something like this:
If you need to create an initrd you can use slackware's mkinitrd to do so provided you build the initrd tree in a filesystem that supports soft links. I read a note about that somewhere but I forgot where. Look at the mkinitrd man page, in particular "-s" option for this issue because the default is /boot/initrd-tree and if that's on the PI's fat partition even if it's big enough it will not support soft links and the creation will fail.
In fact I checked the source file and it seems that the config used for the kernel is with JFS as a module. So most probably it is same for all the different ARM versions. I have already tried to reboot, and of course it have not restarted again.
Since I do not want to loose other few hours reinstalling the system I will simply convert the stuff I have on that SD card to ext4. But I still think that JFS is better .
I also made that modification in the comandline.txt file and it have not boot. So the confirmation that JFS is as a module compiled comes here.
About creating the initrd image I saw the README in the boot dir and it explains everything clearly also about the -s option. So for now I will just try to play a bit and see if I can make it go, otherwise I simply convert the SD card file system into ext4.
With the officially supported devices, JFS is included in the default initial ram disks, so all you'd not need to do anything - your file system would be detected. If it was not you could specify Kernel command operators
rootfs=jfs
(or rootfstype=jfs -- it's a synonym in the init script).
Ok, never looked at that page to be honest, I thought it was supporte as I saw it listed on fatdog.eu Nevermind, when I have some time I make it work .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.