On Sun, 07 Feb 2010 23:13:49 +0100 Hans de Goede <hdegoede@xxxxxxxxxx> wrote: > Both of which is needlessly complicated and fragile. So as for as I'm concerned > Fedora and the next RHEL will have these files under /dev. And if upstream > does not want this, then we will just keep patching mdadm / mdmon to do this > till the end of time. Note that /dev is already (ab)used in the same way > for passing dhcp leases from the initramfs to the running system when / lives > on a network device, and a few other state things which need to be passed > between the initramfs and the real root. > > Pretty? No but effective and simple, and anytime you have this state passing > problem the most likely solution you will end up with, because it is > KISS and KISS is good. You admit that /dev is being abused, yet you seem proud of it. Odd. Maybe I misunderstand. Your dhcp lease example is perfect (thanks!) for demonstrating that something is needed beyond devices. i.e. some sort of generic place to pass files from 'before' and 'after' pivot root is needed. The thing I like about /lib/init/rw is that it is clearly admitting this need and trying to address it. I have no particular attachment to the name (and would much rather use /var/run!) but it is the honesty and forward thinking that I like. By contrast /dev/.udev seems dishonest (as it tries to hide) and not forward thinking (as it appear to be udev specific). If it was /dev/udev or /dev/UDEV it would be better. If it was /dev/RUN/udev it would be better still. Though I would really like the carry-over filesystem to be /init and it contain 'dev' and 'var/run' and anything else needed, and after pivotroot, the interesting parts are bind mounted to their final home. mount --bind /init/dev /dev Yes. "Keep it simple" is very important. So is being generic and forward-looking. I haven't seen much evidence of being forward looking in the various suggestions and reference examples that have been put forward. Yes, the only difference among a lot of the options put forward is the name of a directory. Are names really so important. Emphatically YES. They guide the way people think. Bad names confuse people, good names educate people. So my leaning is still to default to the best name currently available which seems to be /lib/init/rw, and to make it easy to choose a distro-specific name at compile time. -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
