2015-11-15 18:09 GMT+03:00 Andreas Färber <[email protected]>: > Am 15.11.2015 um 09:18 schrieb Matwey V. Kornilov: >> They are device agnostic to the some extend. But currently oemboot for >> armv7l doesn't support networking and that means that initial initrd >> cannot run nbd-client to mount root. > > Could you be a little more specific what you propose? If you want nbd > support in the initrd, you could just do an SR against the JeOS package > for review. If it's not enabled in the kernel, please send me a patch.
I suppose nbd should be introduced (or checked) into KIWI and Dracut. I will look into but not now. >> But, I think that It worth to stop bloating oemboot and introduce nbdboot > > How would that help? You still need per-board fdt packages and initrd > drivers to be able to use the network. For booting the kernel from > network I believe you'd need PXE/TFTP instead. I mean that I would be able to drop all modules except networking from KIWI Initrd > If someone wants to boot from AHCI (like I do on Jetson TK1 / IFC6410) > they can boot with an SD image, format, mount and untar rootfs, update > the bootargs and reboot. An SD card may still be needed for U-Boot. A > similar approach should work for switching to nbd, iSCSI, AoE, FCoE or > NFS, too. Maybe I'm not understanding correctly? I want to deploy system automatically. And this should be possible if bootloader takes kernel and initrd through PXE (and I can replace images on the server) and initrd takes root from the server (where I can replace root image) using nbd. -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://[email protected] -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
