On Wed, 8 Nov 2017 06:20:40 +0100 Adam Borowski <kilob...@angband.pl> wrote:
> I don't get why you'd want to keep moving things around on the real > system if you can isolate it into initrd. Because putting it into initramfs not only isolates it, but in fact hides it in a black box. You can't just pop up in your initramfs and tweak things: You need to tweak, recompile and rerun. Very slow process. But wait: It's worse. Although it's currently hip to say "The only thing we put in initramfs are the things needed to mount the root partition", this isn't really true, is it. Those initramfs systems are now so complex you need a product like dracut or initramfs-tools to create it. Have you ever used shorewall to create an iptables firewall? You end up with a monstrosity, just trying to do a simple firewall. Same with these initramfs builders: You end up with something taking several hours to fully understand, when all you really needed to do, in the simple case, is load the ext4 driver, mount the root partition, and run an rc file on the root partition to get everything else mounted. And now I hear talk of it being an excellent idea to run systemd inside the initramfs.[1] What could POSSIBLY go wrong? Besides all that: Your sentence starts with "I don't get why you'd want to". Well, I do. I don't see why anyone would want to use KDE, but that doesn't mean I suggest removing it from Devuan unless it becomes a human shield for systemd. If you don't speak up when they remove the use cases of others, one day *your* use case will be dispensed with. [1]https://www.freedesktop.org/wiki/Software/systemd/InitrdInterface/ SteveT Steve Litt October 2017 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
