Re: Proposal to enhance boot path selections

Paul Goyette <[email protected]>
Newsgroups gmane.os.netbsd.ports.x86-64,gmane.os.netbsd.devel.kernel,gmane.os.netbsd.ports.i386
Message-ID <[email protected]>
On Sun, 11 May 2025, Greg Troxel wrote:

> Paul Goyette <[email protected]> writes:
>
>>> Yup, I think you're missing the fact that all of this relates to the
>>> ratther new-ish KERNEL_DIR option, support for which was only recently
>>> completed (by myself).  KERNEL_DIR is described briefly in options(4),
>>> and it is noted in both CHANGES and UPDATING.
>>
>> Correction, KERNEL_DIR is described in mk.conf(5).  It is a build.sh
>> option.
>
> Is how one interacts with it described in boot(8)?  It seems like it
> should be.  (The build where I went to read that man page is from May
> 5.)

I am updating x86/boot(8) now.

> Beyond that, if one uses that by specifying a directory, which contains
> a kernel and modules, then I don't see why slashes should have anything
> to do with it.   It would simply be
>
>  if filename(which is really pathname?) refers to a directory
>  AND
>  the KERNEL_DIR option is enabled in the boot loader(?)

KERNEL_DIR is always enabled in the current boot loader, to enable
smoother transition.

>
>  then
>
>  bootcode tries to find a kernel and modules in that directory, and if
>  so, boots them, and if not prints an error
>
> so I don't understand the discussiion about if/then rules relating to slashes.

All of this is to ease transition and retain usefulness of existing
"muscle memory".


+---------------------+--------------------------+----------------------+
| Paul Goyette (.sig) | PGP Key fingerprint:     | E-mail addresses:    |
| (Retired)           | 1B11 1849 721C 56C8 F63A | [email protected]    |
| Software Developer  | 6E2E 05FD 15CE 9F2D 5102 | [email protected]  |
| & Network Engineer  |                          | [email protected] |
+---------------------+--------------------------+----------------------+
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.