Which makes option 2 (dynamically generate an mfs /dev or devfs)
	more attractive. The code is already there - it just needs to be
	generalised. It also saves people who forget to populate /dev
	when installing, but that is a minor point :)

	The only concern would be providing a well documented procedure
	for converting a mfs /dev system into a 'standard' /dev system.

		David/absolute

	 -=-  "There will not be a send-off, a funeral or mass"  -=-

On Sun, 3 Jan 1999, Paul Kranenburg wrote:

> > NEITHER mknod nor gtar will help you here - both work with split major and
> > minor device numbers instead of a 32-bit combined dev_t.
> > 
> > What we ned to have is some sort of cross-mknod that can DTRT with NetBSD
> > device numbering.  See <sys/types.h> for the arrangement of NetBSD dev_t's.
> 
> Actually, you may have severe problems using "wide dev_t's" via NFS
> on servers that do not natively use "wide dev_t's".  E.g. on an NFS server
> running SunOS, which has 16-bit device node representations, you'll
> not be able to use any of the high 16 bits in your diskless client's
> /dev directory. All those high bits are simply snipped off by the
> SunOS NFS server code.
> 
> -pk
>