OpenBSD 5.8 install bug - "reboot" doesn't work in the end

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

OpenBSD 5.8 install bug - "reboot" doesn't work in the end

Andrey Utkin
When the installation is complete, it tells that I should issue "reboot"
command to boot to new system. But this doesn't work unless I issue
"hash" command. See screenshot attached.

Where is the source code for the installer? I'd love to make a patch for
it by myself.
http://www.openbsd.org/anoncvs.html is unclear where the installer
source is.
Also the following point from http://www.openbsd.org/report.html is
quite disappointing given you follow Full Disclosure principle:
> Remember that the anoncvs servers are updated significantly behind the
actual working source tree.

--
OpenPGP usage is appreciated (it also helps your letter to bypass spam
filters). To email me with encryption easily, go
https://encrypt.to/0xC6FCDB11

openbsd.png (17K) Download Attachment
signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD 5.8 install bug - "reboot" doesn't work in the end

Stuart Henderson-6
On 2015/12/02 21:46, Andrey Utkin wrote:
> When the installation is complete, it tells that I should issue "reboot"
> command to boot to new system. But this doesn't work unless I issue
> "hash" command. See screenshot attached.

There's something odd there, that shouldn't be necessary (and never has
been for me). Any chance some stray (nonprinting?) character was typed
before 'reboot'?

> Where is the source code for the installer? I'd love to make a patch for
> it by myself.
> http://www.openbsd.org/anoncvs.html is unclear where the installer
> source is.

src/distrib/miniroot

> Also the following point from http://www.openbsd.org/report.html is
> quite disappointing given you follow Full Disclosure principle:
> > Remember that the anoncvs servers are updated significantly behind the
> actual working source tree.

That's usually between an hour and 24h, with most anoncvs servers <6h.
So significant in the sense "a problem you're thinking of reporting that
was recently introduced to -current may have already been fixed" but it's
not like there are any deliberate delays, just normal sync schedules.