[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: DevFS question



	Yes, but given my /dev/sg contains the following:

lr-xr-xr-x    1 root     root           39 Jul 18 22:23 c0b0t1u0 ->
../scsi/host0/bus0/target1/lun0/generic
lr-xr-xr-x    1 root     root           39 Jul 18 22:23 c0b0t2u0 ->
../scsi/host0/bus0/target2/lun0/generic
lr-xr-xr-x    1 root     root           39 Jul 18 22:23 c0b0t5u0 ->
../scsi/host0/bus0/target5/lun0/generic
lr-xr-xr-x    1 root     root           39 Jul 18 22:23 c1b0t0u0 ->
../scsi/host1/bus0/target0/lun0/generic

	It would assume I would actually need sg[0-3] would it not? So
if I were to not be using DevFS how would this be setup properly? And
then once that is establish'd figuring out how to emulate with DevFS for
software that will not use DevFS should fall together...

	Would be so nice if software that uses device nodes from /dev
would be able to tell the difference in DevFS or non-DevFS and handle
this without need for anything more... Hey I can dream can't I?

	Jeremy

On Fri, Jul 19, 2002 at 01:17:28PM -0400, Robin wrote:
> hmm... don't think I replied to "debian-user@lists.debian.org" the first 
> time...
> 
> anyway...
> now that I think of it, I'm not 100% sure what sg* points to if the SCSI 
> controller has more than one bus... that setup of mine assumes there's 
> only one device per SCSI host. (USB-SCSI emulation)
> I can think of one other option, not use the regex pattern (manually or 
> multiple entries) and just have:
> 
> # assuming your cdrom is the slave device on the first bus, etc
> REGISTER    ^scsi/host0/bus0/target1/lun0/generic CFUNCTION GLOBAL 
> symlink $devname sg0
> # second controller, IDE-SCSI emulated burner
> REGISTER    ^scsi/host1/bus0/target0/lun0/generic CFUNCTION GLOBAL 
> symlink $devname sg1
> 
> UNREGISTER    ^scsi/host0/bus0/target1/lun0/generic CFUNCTION GLOBAL 
> unlink sg0
> UNREGISTER    ^scsi/host1/bus0/target0/lun0/generic CFUNCTION GLOBAL 
> unlink sg1
> 
> 
> beyond that, I can't be of much help... my other thought was to match 
> hostX/busY/targetZ/lun0 to sgXYZ, but that wouldn't work, something 
> about the max number of SCSI devices I'd imagine.
> what other methods does devfs have for pattern matching/replacing?
> 
> - robin
> 
> Jeremy T. Bouse wrote:
> 
> >Not sure if I'm following this completely... On my system I have 2 scsi
> >hosts... scsi0 is an actual Adaptec SCSI controller with a SCSI 4x CDROM
> >and 2 SCSI harddrives, scsi1 is the ide-scsi emulation host with the
> >CDRW... In order to use both drives I had to create 2 symlinks sg0 and
> >sg1... Are you saying that this could work for either? Or would I need
> >to create multiple entries?
> >
> >	Jeremy
> >
> >On Fri, Jul 19, 2002 at 12:13:15PM -0400, Robin wrote:
> > 
> >
> >>I added this to /etc/devfs/compat_symlinks:
> >>--
> >>REGISTER                ^scsi/host([0-9])/bus0/target0/lun0/generic 
> >>CFUNCTION GLOBAL symlink $devname sg\1
> >>UNREGISTER      ^scsi/host([0-9])/bus0/target0/lun0/generic CFUNCTION 
> >>GLOBAL unlink sg\1
> >>--
> >>it's mostly just for my USB cd burner, but it picks up my USB zip drive 
> >>as well...
> >>might have to change busX/targetY/lunZ, however I don't believe you'll 
> >>need to.
> >>
> >>Jeremy T. Bouse wrote:
> >>
> >>   
> >>
> >>>	Has anyone else had problems with using DevFS and software not
> >>>operating properly? I've tried to turn on as much backwards
> >>>compatibility as possible for some software that I've found have no
> >>>other choice but I tend to notice a lot of it resolves around SCSI.
> >>>
> >>>	My recent situation was in getting cdrecord to recognize my
> >>>CDROM and CD-RW that are using IDE-SCSI emulation. For some reason it
> >>>was lookin for /dev/sg? but with DevFS what I have is like the following
> >>>/dev/sg/c1b0t0u0 which doesn't get look'd at... However if I make the
> >>>symlink for /dev/sg0 point to that it works... 
> >>>
> >>>	Any thoughts are ideas? Am I missing something in my
> >>>configuration for DevFS completely?
> >>>
> >>>
> >>>     
> >>>
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact 
> listmaster@lists.debian.org

Attachment: pgpBarzfp7Iex.pgp
Description: PGP signature


Reply to: