Messages in this thread | | | From | "Jim Crilly" <> | Date | Wed, 8 Feb 2006 11:53:30 -0500 | Subject | Re: CD writing in future Linux (stirring up a hornets' nest) |
| |
On 02/08/06 05:32:38PM +0100, Joerg Schilling wrote: > "Jim Crilly" <jim@why.dont.jablowme.net> wrote: > > > On 02/08/06 02:27:41PM +0100, Joerg Schilling wrote: > > > "Jim Crilly" <jim@why.dont.jablowme.net> wrote: > > > > > > > All you've explained is that using SCSI ID for device names is the way > > > > you want cdrecord to work, not why it's infinitely better than using real > > > > device names like every other userland program on every OS in existance. > > > > > > I did many times, but people don't seem to listen. > > > > But you've never answered the question as to why every other userland > > program on every OS uses device names when cdrecord insists on using SCSI > > IDs. Do you really think mount, fsck, tar, etc are broken because they let > > the user use device names that they're accustomed to like /dev/c0t0d0s0? If > > so, I look forward to the day that you try to patch OpenSolaris' userland > > to work like cdrecord. > > You just verify that you don't listen...
Yes, I have been listening and I haven't seen you list one reason why cdrecord absolutely has to use SCSI IDs when fsck can get away with using /dev/blah just fine.
> I did answer this many times and I will not repeat it another time. > > Note that you are of course wrong with your statement on other CD/DVD writing > software.
And of course you won't tell me exactly what I'm wrong about and/or point me to some proof because then you might actually come off as helpful.
> What you like to see does not work at all on MS-WIN.
That's not my problem, but I would assume that Windows users would also rather use a meaningful name like dev=D: instead of some random SCSI ID.
Jim. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |