>> Right. The question was rather like this: >> Say we have our non-stable /dev/sr0 mapping to /dev/sg0, and it has got BTL >> 1,1,0. Now, if the user starts `cdrecord -dev=1,1,0`, >> `ls -l /proc/$(pidof -s cdrecord)/fd/` should show (and in fact did when I >> used ide-scsi back then) /dev/sg0, right? >> >> If so, what's wrong with just opening /dev/sg0 directly (as per user >> request, i.e. cdrecord -dev=/dev/sg0) and sending the scsi commands down >> the fd? > >As I did write _many_ times, this was done by the program "cdwrite" on Linux >in 1995 and as cdwrite did not check whether if actually got a CD writer, >cdwrite did destroy many hard disk drives just _because_ the /dev/sg* >is non-stable. > >People did not believe this and did write shell scripts with e.g. /dev/sg0 >inside and later suffered from the non-stable /dev/sg* <-> device relation. > Exactly. But, if I now say -dev=1,1,0 instead of e.g. -dev=/dev/sg0, who or what makes sure that 1,1,0 {is not | does not map to} a harddisk? Jan Engelhardt -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Luke-Jr <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Peter Read <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Matthias Andree <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: "Jim Crilly" <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: "Jim Crilly" <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: "Jim Crilly" <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: "Jim Crilly" <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Jan Engelhardt <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Jan Engelhardt <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Jan Engelhardt <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- Prev by Date: Re: [linux-pm] Re: [PATCH, RFC] [1/3] Generic in-kernel AC status
- Next by Date: Re: preempt-rt, NUMA and strange latency traces
- Previous by thread: Re: CD writing in future Linux (stirring up a hornets' nest)
- Next by thread: Re: CD writing in future Linux (stirring up a hornets' nest)
- Index(es):