Joerg Schilling writes: > > Well we will just have to disagree on that, for me cdrw(1) is very > > simple and its list of options is just right > > for me; even though I hardly use any of them. > > For me cdrw is very non-intuitive. Cdrecord on the other side works completely > intuitive and it does not need the non-intuitive options you need with cdrw.
Count me among the folks who don't agree. The fact that "dev=1,0,0" seems to mean the same thing as /dev/dsk/c1t0d0p0 is perhaps intuitive if you understand the inner structure, but why should I have to? Why shouldn't "dev=c1t0d0p0" just work as expected? It isn't as though any of the 37 pages in cdrecord(1) explains this. Merely supporting the native device names (instead of some sort of canonical, but baffling, SCSI naming structure) would, I think, go a _long_ way to helping cdrecord users. I really don't want to learn how to use more than one name for any of my devices. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
