Re: I appear to have killed my T1000 by upgrading to the April 25th snap

Theo de Raadt wrote:
>> As subject really, I've pasted everything I have in my console buffer
>> below, but the significant bit is:
>>
>> {0} ok boot
>> Boot device: disk  File and args: bsd.mp
>> OpenBSD IEEE 1275 Bootblock 1.1
>> ..>> OpenBSD BOOT 1.3
>> open /pci@7c0/pci@0/pci@8/scsi@2/disk@0,0:a/bsd.mp: No such file or
>> directory
>>
>> Boot:
>>
>>
>> I can't easily work out where the command set for this prompt are, but I
>> fear I'm a bit stuffed. I had just upgraded to the April 25th snapshot,
>> and all appeared to have gone okay...
> 
> Use printenv and setenv in the prom.
> 
> You must at some point have changed the default kernel boot name.  It should
> be bsd, not bsd.mp
> 
> The new snapshots automatically move the right kernel to "bsd" when it
> detects that it is a MP machine.  On other machines in the future, if
> we have other kinds of kernels, it will make even more such decisions.
> 
> 

This was exactly it. I had set the boot-file to be bsd.mp so I could to
regular upgrades without having to juggle bsd and bsd.mp, and with the
new installer it broke. My own damn fault, especially when I read the
commit list daily, saw the bit about the new automatic stuff and didn't
join the dots. Interestingly, because it installed bsd.mp and then moved
it, rather than installing bsd.mp as bsd, it got rid of my old bsd.mp
without there being one in its place.

For the archives, the cleanest fix I could find was:

{0} ok set-default boot-file

 at the prom prompt, as this just clears the variable to use the default
so that OpenBSD Boot looks for a bsd

Would you like me to try and write a patch for current.html in case
someone else has the same problem?

Dave W