Jan Engelhardt 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? Theoretically, yes, provided there was an application talking raw SCSI to the device in question. /dev/sg is a generic SCSI device that allows the sending of commands. It does not implement higher-level device models such as direct access (/dev/sd*), CD-ROM (/dev/sr*), sequential access (/dev/[n]st*) or similar. It's kind of "raw SCSI". OTOH, there is, according to kernel developers, no difference between /dev/sg and /dev/hd for SCSI command access via the SG_IO ioctl, so unless someone documents /dev/hd* bugs that /dev/sg* doesn't share, it appears as though the user space would have to live with a /dev/hd* that unifies the mid-level "raw SCSI command" and the high-level (block device) access. - 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) (was: Rationale for RLIMIT_MEMLOCK?)
- Prev by Date: swsusp done by migration (was Re: [RFC][PATCH 1/5] Virtualization/containers: startup)
- 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):