Date: Sat, 28 Jan 1995 18:01:41 +1100 From: Bruce Evans <bde@zeta.org.au> To: dufault@hda.com, julian@tfs.com Cc: freebsd-hackers@freefall.cdrom.com, freebsd-scsi@freefall.cdrom.com, hsu@fx7.cs.hut.fi Subject: Re: SCSI device configuring.. (was scsi renames devices) Message-ID: <199501280701.SAA22269@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>there are several ways around the problem.. >1/ The NetBSD approach.. NetBSD have changed their config code almost entirely, >to use the same system as (I believe) BSDI.. wherever it came from, it allows Does config.new do this? >2/ the /DEVFS approach.. the kernel creates the devices purely as it finds them >and assignes names that are descriptive of WHERE it found them. >Needs devfs, and I've just scrapped my 3rd try at it.. devfs will change the problems for config and booting. Config will have have to output names instead of numbers. This should be slightly easier - it can just copy the names given in the input file. However, conventions such as the b partition being for swap may still have to be handled to support old config files. >3/ the /dev/scsi approach (aka the 'Peter (dufault) Principle' :) >looks promising but unfortunatly, doesn't allow vnode locking between >(say) /dev/rsd0d and /dev/scsi/dev3-lun0-part4 (for want of a better name). >because they are different vnodes.. The driver probably has to handle this anyway. Aliased devices should be easier to handle than overlapping devices (partitions) provided the driver knows about the aliases. However, I think supporting the old names is too hard. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199501280701.SAA22269>