AUTOCONF(4) | Device Drivers Manual (hp300) | AUTOCONF(4) |
autoconf
—
diagnostics from the autoconfiguration code
When NetBSD bootstraps it probes the innards of the machine on which it is running and locates controllers, drives, and other devices, printing out what it finds on the console. This procedure is driven by a system configuration table which is processed by config(1) and compiled into each kernel.
Autoconfiguration on the HP300s is similar to that on the VAX, the primary difference is in the naming conventions. On the HP300, if devices exist which are not configured they will be ignored; if devices exist of unsupported type they will be ignored.
Normally, the system uses the disk from which it was loaded as the
root filesystem. If that is not possible, a generic system will use
‘rd0
’ if it exists. If such a system
is booted with the RB_ASKNAME
option (see
reboot(2)), then the name
of the root device is read from the console terminal at boot time, and any
available device may be used.
%s%d
’ will look like
‘rd0
’, for tapes like
‘ct0
’. The
‘%s
’ in the first line will be a
product type like ``7945A'' or ``9144''. The slave number comes from the
address select switches on the drive.%s
’ will be one of
com(4) (single-port serial
interfaces),
hp300/dcm(4)
(four-port serial interfaces), or
le(4) (LAN cards). The slave
number comes from the address select switches on the interface card.config(1), hp300/intro(4), boot(8)
4.3BSD for the HP300, in the distribution documentation package.
June 17, 2022 | NetBSD 10.99 |