On 3/2/06, Dimitrios Apostolou <[EMAIL PROTECTED]> wrote: > I see now, thank you for your thourough answer. Academically speaking, > do you think that by only statically compiling modprobe (while keeping > the static /dev) and inserting it in the initrd would work?
It can be done. Like Thomas said, it's going to require making sure the entire path for each module exists, along with the modules.dep and modules.alias files and things like that. While this is not a problem in-and-of itself, it's yet another change to make all this stuff work. With all these changes, you're looking at a complete rewrite of a system that's already caused a bit of grief to everyone. 8) > Hmmm, I don't have a clue about klibc/kinit. I'd better google a bit... Good luck, the information out there is very sparse - you can check the kernel documentation under "early-userspace" for a brief overview. > > For now, though, I would recommend following the wiki. You will > > achieve exactly what you want without massive changes to the initrd > > process which may be going away in the near future. > > Actually I had this problem solved before by fine-tuning myself the > initrd. I just wanted sometime to post my questions, since I couldn't > exactly understand the situation. Yup. It's easiest to try to use mkinitrd.conf, but if you're up to it, fine-tuning the initrd by hand works as well. - phrak _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
