Related; would be nice to have a supported atomic update method (rollforward/back) and/or adapt sysupgrade/opkg to cope with full sys-upgrade style opperation.
Fedora CoreOS and OSTree may be a possible inspiration point. Either way I am getting tired of need to have to stand up a new VM - clone config/opkg update and then switch over from running VM as being the only decent way of doing sysupgrades on x86 targets. -Joel On Thu, 16 Apr 2020 at 10:02, Daniel Golle <dan...@makrotopia.org> wrote: > On Tue, Apr 14, 2020 at 03:08:09PM -1000, Paul Spooren wrote: > > Hi all, > > > > the x86 been recently reworked (cb007a7bf6) and now it is easily > possible to > > define multiple profiles. Currently only a `generic` profile is offered > which > > builds mbr and efi grub images with a standard selection of packages > (common > > device drivers). > > > > I'd suggest to have multiple profiles for common x86 devices, including > the > > correct drivers. An example is the APU2 board, which requires additional > kmods > > to shine[0]. > > > > A first split could be to have mbr and efi images separated and the APU2 > board. > > +1 > also for splitting EFI and MBR generic images, because EFI image > should have some different packages (efibootmgr, kmod-fs-efivars, ...) > installed which are useless when booting from MBR. > > > > > > Please share your opinions. > > > > Best, > > Paul > > > > [0]: https://openwrt.org/toh/pcengines/apu2#kernel_modules > > > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel >
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel