Carlos E. R. wrote:
WHY should one need initrd -- just for systemd, no?
I don't really know. And it doesn't matter, the decision was made.
The decision to not have to have /usr mounted in order to boot from the root partition was also made. It's broken. That's the part I am complaining about. If you want to require initrd for loading a generic kernel to allow it to be adaptable to a wide range of hardware -- that is entirely understandable. But to mis-use initrd to duplicate /usr/bin as a kludge to support a broken design is NOT OK.
Initrd is needed for many things,
It is NEEDED for nothing in 12.1. This need has been sprung because someone corrupted the rpm's and did BAD engineering design to make the root-boot partition dependent on another file system. That's bad design and seriously bad morals to have snuck the dependency in after it was specifically agreed on this list NOT to be done. This is incredibly 'Microsoftian' -- insomuch as their paladium design was horribly rejected and hated in reviews on all levels. So they put it in the next OS Visa, under the covers and in the guise of increased security. They solidify it more in win7 and take away the desktop in win8 -- moving toward being able to sell win8 as a DRM-safe-from-tampering solution delivery platform. Now I see some similar behaviors and motivations at oSuS, with similar requirements for a giant-blob to boot from that is not easily scrutinized or modifiable. I see the requirement that systemd be started by the boot loader rather than allowing it to be loaded by init -- as an alternate to the boot scripts -- why? Because if it is init users, could alter inittabs to put in their layers before systemd gets loaded and there goes the secure execution guarantee that would be needed to make oSuse into another secure DRM appliance OS -- safe from user tampering. I am NOT saying that is necessarily the motivation here, but it looks bad -- and smells bad. There's no reason why systemd can't be launched by the kernel and mount the disks it needs in its earliest steps, or are you saying it is not even close to being as flexibile as the initrc system? If that's the case, it needs to be launched by init after init has executed it's boot scripts. Then it will be happy. This solution was proposed and is still on the table unless there is a compelling engineering reason not to do such -- otherwise, that bad smell smells worse.
it just happens that the solution for /usr handling in a separate partition has to be done as well with initrd.
Why? Why not in /etc/boot.d/xxx?
If you have another solution... up to you. :-)
The consensus at the time was to not use systemd if it had such requirements . I was told that it no longer had those requirements. Was that also a "misdirection"? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org