My boot.cfg file looks like this:
=========
banner=Please select from the following menu:
userconf=disable dwiic*
userconf=disable genfb*
dev=NAME=NVME-sys:
menu=Boot normally:rndseed /var/db/entropy-file;boot NAME=NVME-sys:/netbsd
menu=Boot single user:rndseed /var/db/entropy-file;boot NAME=NVME-sys:/netbsd -s
menu=Boot GENERIC kernel normally:rndseed /var/db/entropy-file;boot
NAME=NVME-sys:/netbsd-GENERIC.gz
menu=Boot GENERIC kernel single user:rndseed /var/db/entroopy-file;boot
NAME=NVME-sys:/netbsd-GENERIC.gz -s
menu=Boot previous netbsd.old kernel single user:rndseed
/var/db/entropy-file;boot NAME=NVME-sys:/netbsd.old -s
menu=Drop to boot prompt:prompt
menu=Boot normally:rndseed /var/db/entropy-file;boot /netbsd
default=3
=========
If I just let it boot and take the default option 7, the ``dev'' is not
set and the boot fails since the default dev is NAME=NVME-efi which
doesn't have a /netbsd
If instead I interrupt the timer and manually enter the dev command,
re-enter the menu, and select the default option it works.
SO,
* Why does dev command work only in interactive mode?
* Does the rndseed command work the same way?
Making these commands workk non-interactively could greatly reduce the
size of the boot.cfg file, and shorten the boot commands to something
more readable (reduce line wrap) and more easily etered manually.
+---------------------+--------------------------+----------------------+
| Paul Goyette (.sig) | PGP Key fingerprint: | E-mail addresses: |
| (Retired) | 1B11 1849 721C 56C8 F63A | p...@whooppee.com |
| Software Developer | 6E2E 05FD 15CE 9F2D 5102 | pgoye...@netbsd.org |
| & Network Engineer | | pgoyett...@gmail.com |
+---------------------+--------------------------+----------------------+
