The NetBSD 1.6 installation CD comes only with entries for wd0-wd3 in /dev.
The drives which are attached to my Highpoint 404 (HPT374) are assigned
wd0-wd3, and soon there will be another 4, while the actual boot disk which
is attached to the onboard controller is wd4, as recognized during the boot
phase. There is no entry in /dev for wd4 and MAKEDEV fails due to a disk
space error. The installation procedure only works with wd0-wd3. I like to
boot from the small disk that is attached to the internal controller and
leave the RAID system as pure scratch disk for data. Any idea how to fix
the installation procedure without changing the CD (no OS on disk yet, so
the fix needs to be simple;-).

I created a RAID array (RAID0) through the controller's BIOS. Does NetBSD
access the RAID array as one disk or will I get 4 (later 8) disks? I like
to see only one disk and let the controller do the striping (if the
hardware actually performs this task).

Does the NetBSD NFS server support 1.6 Tbyte disks?

Does NetBSD 1.6 support DECnet (Phase IV or V, possibly V over IP) ? There
has been some talk about this project a few years ago, but it is not clear
to me if this is an option by now. I read in the NetBSD Guide (9.1.2.
Supported Networking Protocols) that said DECnet would be not available,
because it is a proprietary protocol and some references to RFCs and
standards (just wondering what xns, appletalk etc. are, who can't read the
available DECnet documentation and which letter stands for Standard in
RFC). The arguments in the NetBSD Guide are counterproductive. If anybody
has something working, then please let me know. After all it is working
with Linux since a few years. How about MSCP (VMS cluster), in particular
for disk access?

Thanks!