Re: Proposal to enhance boot path selections
Greg Troxel <[email protected]> Sun, 11 May 2025 09:29:02 -0400
| Newsgroups | gmane.os.netbsd.ports.x86-64,gmane.os.netbsd.devel.kernel,gmane.os.netbsd.ports.i386 |
|---|---|
| Message-ID | <[email protected]> |
Paul Goyette <[email protected]> writes: > With the recent changes, specifying /onetbsd will only look for a > kernel in /onetbsd and /onetbsd.gz (both being regular files); it > will not look in /onetbsd/kernel or /onetbsd/kernel.gz as might be > expected. > > If one is accustomed to booting with the leading slash it could be > disconcerting (or worse) to not having ingrained muscle-memory boot > the old kernel as expected. My $0.02 is that I had no idea that 'boot foo' would try to load foo/kernel, and that I find this unintuitive and not really helpful. Reading boot(8) on current amd64, I see that boot is specified to take "filename" and there is no mention of directories. The man page kind of implies that filename must be the name of a file in the root directory. There's no suggestion that it makes sense to have leading slash. There's no suggestion that one can give a pathname rather than a filename. Thus I suspect I am missing something.