SlackwareThis Forum is for the discussion of Slackware 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.
run mkinitrd -c ... ... as usual.
make your desired changes to the stuff in /boot/initrd-tree
run mkinitrd ... ... again, this time without the '-c' option.
Slackware doesn't have a "hooks" framework built into the initrd stuff.
run mkinitrd -c ... ... as usual.
make your desired changes to the stuff in /boot/initrd-tree
run mkinitrd ... ... again, this time without the '-c' option.
Slackware doesn't have a "hooks" framework built into the initrd stuff.
You should continue with if the OP intends to reuse his initrd modifications for another initrd (i.e. for another kernel), he should reapply all modifications BY HAND on the new initrd tree. Which is a real hassle of time and errors prone.
Apparently, they believes that their initrd is absolutely perfect, it covers absolutely all use cases and nobody ever needs to modify it...
Apparently, they believes that their initrd is absolutely perfect, it covers absolutely all use cases and nobody ever needs to modify it...
From "mkinitrd -h":
Code:
mkinitrd creates an initial ramdisk (actually an initramfs cpio+gzip
archive) used to load kernel modules that are needed to mount the
root filesystem, or other modules that might be needed before the
root filesystem is available. Other binaries may be added to the
initrd, and the script is easy to modify. Be creative. :-)
I see nothing in that thread that tells me what could go wrong. More and more people however, seem want to sit on their hands, requesting that Slackware do everything for them, and thus compromise the simplicity of this distro in an attempt to make it look more than Arch, or Ubuntu.
Another takeaway from the script-kiddie invasion is that I see more of the asking / demanding type of posts, and less of the 'here is a patch that will add desired behaviour' kind of posts. Obviously, the former is not going to help anyone, while the latter is how - historically - new functionality got added to Slackware.
You should continue with if the OP intends to reuse his initrd modifications for another initrd (i.e. for another kernel), he should reapply all modifications BY HAND on the new initrd tree. Which is a real hassle of time and errors prone.
When I was using a custom initrd I just made a script that did this:
That way I didn't have to concern myself with reapplying my changes. Slackware's mkinitrd could be improved, but it's really not as big a deal as you're making it.
Anyway, repeatedly complaining gets you nowhere. This is open source. If you don't like something fix it yourself. The code in the initrd that handles unlocking of multiple luks devices originally came from me: I had a need to do that and it wasn't supported, so I fixed it. It was eventually adopted into the stock package. You don't have to be a slackware team member to contribute, many of us have, and you only need to look at the changelog to see all the acknowledgements. Ofcourse, it helps if you're respectful. No one wants to deal with someone who makes it a habit to be a dick.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.