"Jim Crilly" <jim@why.dont.jablowme.net> wrote: > > 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. Are you _really_ missing basic know how to understand that fsck is using the block layer of a virtual "block device" emulated by UNIX while libscg is offering _direct_ acces to _any_ type of device allowing you to send _commands_ understood by the device? fsck is just sending abstract instructions to a virtual device and does not care about 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 Jörg -- EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) schilling@fokus.fraunhofer.de (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 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/
- Follow-Ups:
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Alexander Samad <alex@samad.com.au>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Jan Engelhardt <jengelh@linux01.gwdg.de>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Ralf Müller <ralf@bj-ig.de>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Martin Mares <mj@ucw.cz>
- 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 <luke@dashjr.org>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Peter Read <peter.read@gmail.com>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: "Jim Crilly" <jim@why.dont.jablowme.net>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: "Jim Crilly" <jim@why.dont.jablowme.net>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: "Jim Crilly" <jim@why.dont.jablowme.net>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: "Jim Crilly" <jim@why.dont.jablowme.net>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- Prev by Date: [patch] sb_set_blocksize cleanup
- Next by Date: Re: USB Host Stack Debugging
- 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):
![]() |