But doesn't this then bork the mount of /boot with both menuentrys? I guess maybe it would still work as long as you leave the PARTUUID the default value? For both root volumes?
Once I'm comfortable running the scripts I'm working on I guess it doesn't much matter if it auto-mounts boot for me using the normal boot process. The current hard-coded detection of a fixed PARTUUID to then mount boot seems... a unique way to do it. Not that I'm offering a better solution at this time than an out-of-band script.
You both certainly can't be wrong. Well sweet baby jesus, one less thing to worry about. I just adjusted my currently booting grub menuentry to be root=/dev/sda3 and yep, boots just fine like I expected, but also automatically mounts /dev/sda1 to boot with the proper mount --bind remount. Excellent!
I think @grrr2 is just trying to make us envious with three root partitions... Showoff.
I guess the Attended Sysupgrade method doesn't preserve partitions layout and do the same as dd a combined image to the disk with MBR and altogether wiping everything? Is there a way to ask Attended Sysupgrade to build an image upgrade, download but not install? I can't see that option in man/help pages. I could then extract the rootfs partition image myself, dd it to a partition, extract the new kernel file to /boot and change menuentry.
It's still not how both works and still not relevant to my primary question.
Does the firmware selector pick all my currently installed packages? I doubt that, unless you pick them from opkg list-installed yourself and put them all in the box there. Do the firmware selector has online CLI? Nope it doesn't. Don't forget then, you need a secondary PC with a GUI for that. Does it also know about my current config and restores it? No it doesn't. On top of that, try to build an image with all your currently installed packages occupying along with the root more than the 104MB, lucky you getting an image this way. You've been here for centuries but coming with a such nonsense answer. Take a brake or better stay on topic.
another workaround, on a very high level, could be to move the
/etc/config folder to /boot.
since you don't want to dd the combined image, but manually copy/replace the kernel and dd the rootfs, the partition containing the kernel binary and grub remains untouched.
only problem I see, is a race condition between the mounting of /boot and the services.
in a worst case scenario, the services have to be started manually, during boot.
you also have to make sure you softlink the /etc/config to /boot dir during an upgrade, or the old config will not be there after you've booted.
I only tried to help. If you belive my answer was not respectful enough - dissregard it. However if you are typing in the forum you have access to browser and it is an option.
I understand and appreciate it.
The firmware selector is a good tool and to my knowledge AUC using it as a backend to generate images but it works slightly different to AUC as it's not picking all currently installed images and preserve config automatically, if chosen. You have to do a list of your installed packages and put them there.
The firmware selector and auc are completely independent. They both use the ASU build server to create their respective images (as does LuCI Attended Sysupgrade). Details on the build server backend here: https://sysupgrade.openwrt.org/ui/
hello, according to the script you post , i guess if i want to upgrade the linux kernel, the only things i should do is copy the 'openwrt-x86-64-generic-kernel.bin' file in my compile root directory "bin/targets/x86/64" to the x86 openwrt system's boot directoy, that is to override the vmlinuz file?