Re: sysupgrade confused by additional disk?

2020-05-26 Thread Florian Obser
On Mon, May 25, 2020 at 12:26:43PM -0400, Nick Holland wrote: > While OpenBSD itself is great about using duids, those are defined in > the 'a' partition of the boot disk..which is usually the first disk. But > in your case, the "first disk" doesn't include the 'a' partitionand the > /etc/fstab

Re: sysupgrade confused by additional disk?

2020-05-26 Thread Joseph A Borg
shouldn’t sysupgrade default to use the disk where bad.rd launched from? I assume it’s the same disk that was running the system before boot. This would be ideal default behaviour since this is an upgrade. regards > On 25 May 2020, at 18:26, Nick Holland wrote: > > On 2020-05-25 10:21, Why

Re: sysupgrade confused by additional disk?

2020-05-25 Thread Nick Holland
On 2020-05-25 10:21, Why 42? The lists account. wrote: ,,, > At some point I added a second (larger) disk to hold my user data (i.e. > home). It seems that this new disk took over the name sd0 and the OpenBSD > system disk itself became known as sd1. yep. Things like that are where the duids

sysupgrade confused by additional disk?

2020-05-25 Thread Why 42? The lists account.
Hi All, I use sysupgrade to update to new snapshot versions (of 6.6). Brilliant! At some point I added a second (larger) disk to hold my user data (i.e. home). It seems that this new disk took over the name sd0 and the OpenBSD system disk itself became known as sd1. The OpenBSD OS still boots