[ removed linux-kernel for the time being ]
On Tue, 29 Feb 2000, WANG,YIDING (HP-SanJose,ex1) wrote:
> set up persistent binding environment for Linux. This happens to Fibre
> Channel world when new device plugged into the loop or Fibric, the existing
> device address could change which leads to target id changes. The persisten
So you not only want to be configured, but also you need to write out this
information somewhere ? The closest I can see is a *user process* doing
one of:
a. cat /proc/thing > /etc/thing.information
b. ioctl() on your device and output to a file.
just before rmmod or shutdown. At insmod you pass the
/etc/thing.information or you cat it to /proc or ioctl().
Having a kernel driver modifying files is possible, but certainly not very
good from a software engineering/decoupling point of view.
Or maybe I misunderstood you. I have been doing very small FC things
lately (point-to-point), and in that case the target ID is static. But I
am not a FC specialist, far from that.
Alternatively, why not start a complete loop detection (request a LIP)
when you start up ?
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
