Date: Tue, 29 Sep 1998 18:18:22 +0930 From: Greg Lehey <grog@lemis.com> To: Terry Lambert <tlambert@primenet.com>, "Justin T. Gibbs" <gibbs@narnia.plutotech.com> Cc: current@FreeBSD.ORG Subject: Compelling reason for SCSI device name change (was: time for some new man pages) Message-ID: <19980929181822.T15172@freebie.lemis.com> In-Reply-To: <199809290550.WAA20551@usr08.primenet.com>; from Terry Lambert on Tue, Sep 29, 1998 at 05:50:27AM %2B0000 References: <199809290516.XAA16815@narnia.plutotech.com> <199809290550.WAA20551@usr08.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 29 September 1998 at 5:50:27 +0000, Terry Lambert wrote: >>> How about we call the new SCSI disk driver "sd" and the new SCSI >>> tape driver "st"? >>> >>> Is there a compelling reason to rename the frigging things? >> >> Come on Terry. You're on every FreeBSD mailing list, read every >> posting, and usually respond to every posting you didn't originate. >> You of all people should know that this has been discussed before >> and what the rational was. If you don't recall, search the archives >> for "CAM FAQ". > >> Why are disks now called "da" and tapes called "sa"? >> I now have to change all of my scripts/fstab entries/whatever! >> >> The names were changed to be more consistent with the >> SCSI standards and to better indicate the scope of devices >> each driver supports. For example, "direct access" driver supports >> memory, optical, and disk devices. >> >> The impact on system configuration is limited. The system accesses >> devices my their major and minor number and, with the exception of >> the removal of the od device, these have not been changed. >> If it suits you better to call "da" devices by the name "sd", >> simply create your device nodes with that name. /dev/MAKEDEV >> will continue to support building of nodes by the old names >> for some time to come. > > Is there a *compelling* reason to rename the frigging things? OK, let's try again, since Jordan obviously wasn't able to guess what your question means. No. Nothing compels us (or you personally) to use these names. I'm running CAM on my development machine (FWIW, vinum seems to work fine with CAM), and I still haven't changed the device nodes: === root@razzia (/dev/ttyp0) /usr/src 25 -> ls /dev/sa* ls: /dev/sa*: No such file or directory === root@razzia (/dev/ttyp0) /usr/src 26 -> ls /dev/sd* /dev/sd0 /dev/sd0s1f /dev/sd1s1b /dev/sd2e /dev/sd3a /dev/sd3s1g /dev/sd4s1c /dev/sd0a /dev/sd0s1g /dev/sd1s1c /dev/sd2f /dev/sd3b /dev/sd3s1h /dev/sd4s1d /dev/sd0b /dev/sd0s1h /dev/sd1s1d /dev/sd2g /dev/sd3c /dev/sd3s2 /dev/sd4s1e /dev/sd0c /dev/sd0s2 /dev/sd1s1e /dev/sd2h /dev/sd3d /dev/sd4 /dev/sd4s1f /dev/sd0d /dev/sd1 /dev/sd1s1f /dev/sd2s1 /dev/sd3e /dev/sd4a /dev/sd4s1g /dev/sd0e /dev/sd1a /dev/sd1s1g /dev/sd2s1a /dev/sd3f /dev/sd4b /dev/sd4s1h /dev/sd0f /dev/sd1b /dev/sd1s1h /dev/sd2s1b /dev/sd3g /dev/sd4c /dev/sd4s2 /dev/sd0g /dev/sd1c /dev/sd1s2 /dev/sd2s1c /dev/sd3h /dev/sd4d /dev/sd4s3 /dev/sd0h /dev/sd1d /dev/sd1s3 /dev/sd2s1d /dev/sd3s1 /dev/sd4e /dev/sd4s4 /dev/sd0s1 /dev/sd1e /dev/sd1s4 /dev/sd2s1e /dev/sd3s1a /dev/sd4f /dev/sd0s1a /dev/sd1f /dev/sd2 /dev/sd2s1f /dev/sd3s1b /dev/sd4g /dev/sd0s1b /dev/sd1g /dev/sd2a /dev/sd2s1g /dev/sd3s1c /dev/sd4h /dev/sd0s1c /dev/sd1h /dev/sd2b /dev/sd2s1h /dev/sd3s1d /dev/sd4s1 /dev/sd0s1d /dev/sd1s1 /dev/sd2c /dev/sd2s2 /dev/sd3s1e /dev/sd4s1a /dev/sd0s1e /dev/sd1s1a /dev/sd2d /dev/sd3 /dev/sd3s1f /dev/sd4s1b Did I guess the correct meaning of your question? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980929181822.T15172>