Add support for version update on netboot

  • When the "boot" argument on cmdline.txt points to ISCSI, NBD or NFS, then updates are not supported and the file "/dev/.update_disabled" is created.

    What is the reason for this? If done properly, a networked boot should be upgradable.

    Please, add an option to cmdline.txt for allowing upgrades when using a networked boot.

    • Official Post

    Netbooting is used by a microscopic percentage of our total users, and zero project staff. As long as we continue to receive the occasional "it still works" post when we make major changes there's no reason for us to remove netboot support, but we're equally not looking to expand support. Sorry.

  • My setup is described here: RE: LibreELEC v9 RPI3 PXE

    For updates, I just do this:

    Download the image for my Raspi, create an update directory and move the image in the new directory:

    root:/nfs/Raspi# wget
    root:/nfs/Raspi# mkdir -p upd/p1
    root:/nfs/Raspi# mv LibreELEC-RPi2.arm-9.2.7.img upd/p1

    Mount the first partition of the image:

    root:/nfs/Raspi# mount $(losetup --show -r -f -P upd/LibreELEC-RPi2.arm-9.2.7.img)p1 upd/p1
    mount: /nfs/Raspi/upd/p1: WARNING: device write-protected, mounted read-only.

    Overwrite the SYSTEM over my old one

    root:/nfs/Raspi# cp -vax upd/p1/SYSTEM 3X84XbXf.boot/SYSTEM
    'upd/p1/SYSTEM' -> '3X84XbXf.boot/SYSTEM'

    Overwrite the rest to the tftpboot directory:

    root:/nfs/Raspi# rsync -av upd/p1/* /var/lib/tftpboot/3X84XbXf/ --exclude SYSTEM* --exclude cmdline.txt --exclude config.txt

    Clean up

    [email protected]:/nfs/Raspi# umount upd/p1
    [email protected]:/nfs/Raspi# losetup|grep LibreELEC-RPi2.arm-9.2.7.img
    /dev/loop2         0      0         0  1 /nfs/Raspi/upd/LibreELEC-RPi2.arm-9.2.7.img   0     512
    [email protected]:/nfs/Raspi# losetup -d /dev/loop2
    [email protected]:/nfs/Raspi# rm -fr upd
    [email protected]:/nfs/Raspi#

    Well done :)