Red HatThis forum is for the discussion of Red Hat 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.
Okay, this is a kind of strange question, but here goes...
As of Red Hat 5.3 and 5.4 (and all derived distros, such as Scientific and CentOS) there is a bug in nash that adds significantly to boot time (the "waiting for driver initialization" bug). There is a patch for this bug but it hasn't made it into the repos, so for now, users are stuck with long boot times.
What I'm wondering is, are there any linuxrc interpreters out there that can substitute for nash? If so, how would I change the routine for generating the initrd so that the substitute program would be used?
(Yes, I realize I could patch nash myself. Unfortunately that would be quite a pain in the neck to actually do... Which is why I'm looking for alternatives.)
Six of one half dozen of the other - Substituting interpreters would be a wash as far as maintenance, etc... when compared to applying this patch. The patch is available below, and it's a piece of cake to apply.
Six of one half dozen of the other - Substituting interpreters would be a wash as far as maintenance, etc... when compared to applying this patch. The patch is available below, and it's a piece of cake to apply.
<snip>
In my situation (using CentOS on my own laptop) I tend to think that maintenance wouldn't be such a big deal. Installing all the stuff I need to compile nash, on the other hand, and recompiling it after each update... I'd much rather just reconfigure the initrd generation to produce something that didn't use nash. If that's actually possible.
Well, if you want to be cutting edge, look at the Dracut project. It is being released as part of Fedora 12. Basically it is a nash/mkinitrd replacement.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.