Mark Kettenis <[email protected]> wrote: > > > The installer considers a disk a root disk if 'a' is FFS and contains > > > expected files. > > > > > > Furthermore, unattended upgrades will always install to the first root > > > disk that is found. > > > > > > This works fine on machines with only one root disk, but it quickly > > > behaves unexpectedly when having multiple disks/installations in one > > > machine. > > > > > > I run such machines, esp. since fiddling with softraid and installboot.
I don't understand the situation. I suspect you are intentionally creating very weird setups, and now you want install script to help people create such weird setups. Then it becomes an additional weird thing we must anticipate in the future. Please show a valid reason why boot are different. It is very hard to reason about this when the rest of your email shows an example where they are the same. > > > The installer/sysupgrade experience can definitely be improved here, but > > > that takes some consideration. > > > > > > One requirement, imho, is knowing > > > 1. which disk we booted from, i.e. > > > from which disk the kernel (/bsd.rd or /bsd.upgrade) was loaded > > > 2. which disk the root filesystem is on, i.e. > > > likely the same disk holding /home where sysupgrade put the sets Prove it.
