Greg KH wrote:
On Sat, Jun 29, 2013 at 12:34:14AM +0200, Jan Engelhardt wrote:
On Friday 2013-06-28 21:56, Linda Walsh wrote:
# # /etc/mkinitcpio.conf MODULES="ahci sd_mod ext4" BINARIES="fsck fsck.ext4" HOOKS="base"
And that’s it. We don’t need udev, since anything in the MODULES variable will be explicitly loaded. udev (or something like it) does not just load modules, it also creates the required device nodes.
No it doesn't, devtmpfs does that. udev sets the proper permissions on those device nodes, that's all.
BTW, I didn't write the above, it was from the webpage. However, doesn't some type of program or driver (specifically /devtmpfs) pre-create basic device nodes as a stop gap measure? What , they didn't realize that the thing that loads the devices isnt' the same driver that creates the nodes,_and_, I'm under the impression that devtmpfs's list of devices that it creates is fairly static.
But the point that seems to escape some people on this thread, is that an initrd really is needed in order to be able to support the huge number of systems that the distro supports, so it isn't going away, sorry. greg k-h
But you can support all the hardware with just the above modules on the initrd, right? That is from a general page for creating a minimal initRD to optimize & speed up boot. In the PC world, once you've loaded your drivers, now you can go to the HW abstraction layer in the kernel and run your startup daemon from the hard disk. Right? That is what the article is saying -- that the above is the minimum necessary to get the kernel running with enough on any given system so that it can continue the boot off of the hard disk (with fsck utils included for those file systems that need them). Or does suse need something else to handle the wide variety of pc-compatibles out there? Now lets suppose your root file system didn't need an "fsck". Example: "xfs". A fs on a solid state drive should be as safe as a ramdisk if not safer -- so maybe BRT_FS might not need a check either? If that's the case, then you only need those few modules for your machine. Now wouldn't it be possible to recompile a kernel and include those? Either you aren't telling us some other need than hardware, or I'm missing part of the requirements. So what am I missing? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org