Jan Engelhardt <[email protected]> wrote: > >> >Please explain me: > >> > > >> >- how to use /dev/hd* in order to scan an image from a scanner > >> >- how to use /dev/hd* in order to talk to a CPU device > >> >- how to use /dev/hd* in order to talk to a tape device > >> >- how to use /dev/hd* in order to talk to a printer > >> >- how to use /dev/hd* in order to talk to a jukebox > >> >- how to use /dev/hd* in order to talk to a graphical device > >> > > >> With /dev/sg, this was possible? > > > >Of course! > > > But you need to open the correct /dev/sg[0-9] too, don't you? > (otherwise cdrecord would set the jukebox on fire) This is why the mapping engine is in the Linux adoption part of libscg. It maps the non-stable device <-> /dev/sg* relation to a stable b,t,l address. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily - 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/
- Follow-Ups:
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Martin Mares <[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: Matthias Andree <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- 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) (was: Rationale for RLIMIT_MEMLOCK?)
- Prev by Date: RE: [PATCH] kconfig: detect if -lintl is needed when linking conf,mconf
- Next by Date: Re: CD writing in future Linux (stirring up a hornets' nest)
- 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):