On Sat, Sep 23, 2023 at 09:55:03AM -0600, Theo de Raadt wrote:
> Mark Kettenis <mark.kette...@xs4all.nl> wrote:
> > > Date: Fri, 22 Sep 2023 23:19:30 +0000
> > > From: Klemens Nanni <k...@openbsd.org>
> > > 
> > > Does the tiny kexec kernel actually need network, bio(4) or HID devices?
> > > octeon/BOOT does not have any of this.
> > 
> > Well, we do need the USB keyboard stuff to allow users to type at the
> > bootloader prompt no?  The USB mouse is clearly not needed, even on a
> > RAMDISK kernel.  That's an oversight.
> Right.

Ah yes, rdboot does offer a boot prompt and I only accessed it via serial

octeon BOOT lacks keyboard drivers, but perhaps that's fine as those
machines are mostly accessed by serial console alone, anyway?

> > I'm not sure about trimming the pseudo-device stuff.  The fact that
> > you need that etherip line suggests that something is fishy.  I think
> > I would keep the loop line instead since that is what we do on the
> > floppy kernels for i386 and amd64.  The wsmux needs to be kept as well
> > of course.
> It suggests you are choosing some random network-device, to pull in the
> network support.

This is what octeon's BOOT does.

> When you delete stuff out of the kernel configuration, you are heading
> towards configurations that *noone has ever tested*.
> Do you really wish to be the first person to go there?  For a configuration
> where it is almost impossible to collect meaningful debug information?
> That doesn't seem sane.

No, I'd just like know better which options are used and which ones were
merely copied over.

Reply via email to