Re: Proposal to enhance boot path selections

Paul Goyette <[email protected]> Fri, 16 May 2025 06:36:06 -0700 (PDT)
Newsgroups gmane.os.netbsd.ports.x86-64,gmane.os.netbsd.devel.kernel,gmane.os.netbsd.ports.i386
Message-ID <[email protected]>
On Fri, 16 May 2025, Christoph Badura wrote:

> On Sun, May 11, 2025 at 07:34:29AM -0700, Paul Goyette wrote:
>> 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.
>
> x86/boot(8) now states:
>
>  If the specified
>  .Pa filename
>  does not contain an embedded slash character, the boot loader will also
>  try
>  .Pa filename/kernel
>  and
>  .Pa filename/kernel.gz .
>
> Is the emphasis on an *embedded* slash to be taken literally?  I.e. are
> leading and trailing slashes considered embedded or not?  In the former
> case, why specifically mention embedded and not just say "contains a slash
> character?"
>
> The code just checks if filename *contains* a slash.  I'm wondering what is
> actually intended here.

A leading slaash is ignored.  Any other slash (traiing or embedded)
will prevent looking for filename/kernel and filename/kernel.gz


+---------------------+--------------------------+----------------------+
| 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] |
+---------------------+--------------------------+----------------------+