Re: CD writing in future Linux (stirring up a hornets' nest)

[Martin Mares <mj@ucw.cz>]

Hello!

> > How exactly does Linux prevent this???
> 
> By not treating ATAPI the same as all other SCSI devices.

Sorry, but that's false. Not treating ATAPI the same can at most
complicate it, but in no way prevent.

> > How do you perform -scanbus for TCP/IP? :-)
> 
> There are various programs that do that for you.
> You could e.g. send a ping to the broadcast address in order to find hosts
> that are on the local network.

Eh, so you are just going to treate the local network differently? ;-)

> If you understand this, why then insists other people in using names like 
> /dev/hd*?

Because at least on Linux, the NAMES are the primary identifier for user
space, not numbers of some virtual SCSI buses which don't exist in the
real world anyway.

For everything else (well, except network interfaces, but that's a different
story), we refer by names. Even when using the SCSI devices for other
purposes, we refer to them by names. Why should burning a CD be different?

I believe that this is the crucial question and the one you should
answer first, before trying to force others to share your view of the world.

> And while this kind of scanning works in case that you have all devices 
> integrated inside a single SCSI implementation, it does not work for ATAPI
> because someont artificially decided to exclude one single SCSI transport 
> from the global view.

No, you are just wrongly considering something to be a global view,
which it in fact isn't.

				Have a nice fortnight
-- 
Martin `MJ' Mares   <mj@ucw.cz>   http://atrey.karlin.mff.cuni.cz/~mj/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
How do I type 'for i in *.dvi ; do xdvi $i ; done' in a GUI?