Well, thanks to the many people that responded. Most everyone suggested
some variant of building the kernel, rebooting, and running netsetup. In
the course of putting the board in last night, I spoke with DEC, and got
some good hints:
o If you don't want to go through the entire list of questions in
doconfig, you can simply boot genvmunix, then issue the command:
sizer -n <filename>
The result of this are two files in /tmp called <filename> and
<filename>.devs. The first file is a config file with all the device
support built in. Simply find the line for the device you're trying
to install, cut it, and paste it into your present config file.
Build the kernel with doconfig, and you're done! The <filename>.devs
file is a MAKEDEV script that will make all the necessary device
files.
o The drivers for network devices don't use device special files (maybe
this is one that *everyone* knows, but hey, I didn't!).
o If you're going to replace one network interface with another (ie,
you aren't going to run them both), it's easier to edit
/etc/rc.config, and change the "NETDEV_0" line to indicate the
appropriate device (in my case, I switched from "tu0" to "fta0".
Anyway, that's about it. Hopefully this will be useful to someone in
similar circumstances...
Thanks again, everyone!
Ed
--
Ed Bailey, Information Systems and Networks
(contracted to: National Institute of Environmental Health Sciences)
4915 Prospectus Dr, Suite C-2
Durham, NC 27713
Internet: bailey_at_niehs.nih.gov
BITnet: BAILEY_at_NIEHS.BITNET
Voice: (919)361-9422, extension 239
FAX: (919)361-9136
Received on Tue Sep 05 1995 - 19:18:54 NZST