On Thu, Dec 23, 2010 at 4:11 PM, Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx> wrote: > > > + > > +What: /sys/bus/scst_tgt_dev/device/*/exported/export<nr> > > +Date: December 2010 > > +KernelVersion: 2.6.38 > > +Contact: linux-scsi@xxxxxxxxxxxxxxx > > +Description: > > + Zero or more soft links to the LUNs through which this device > > + has been exported. An example: > > + > > + $ readlink /sys/bus/scst_tgt_dev/devices/disk01/exported/export0 > > + ../../scst_local_tgt/luns/0 > > + > > +What: /sys/bus/scst_tgt_dev/device/*/filename > > +Date: December 2010 > > +KernelVersion: 2.6.38 > > +Contact: linux-scsi@xxxxxxxxxxxxxxx > > +Description: > > + For virtual devices, the absolute path of the associated file > > + or device. Read-only. An example: > > + > > + # cat /sys/devices/disk01/filename > > + /dev/sdc > > + [key] > > Key? > > [ ... ] Hello Konrad, Thanks for the feedback. I'll do by best to clarify the documentation according to your remarks. Regarding the "[key]" indicator on the second line: that is an indicator that is either present or absent. That indicator is only used by a user-space tool (scstadmin) to find out which sysfs attributes differ from their default value. That indicator makes it possible to minimize the amount of information to be saved when making the SCST state persistent. Bart. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
