On Tue, Mar 06, Douglas Gilbert wrote:
> In summary sg_luns is probably not what you want!
Yes, it can be done in bash.
cd /sys/block/sde/device ; i=`pwd -P` ; printf '%x%012x\n' ${i##*:}
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL P
On Tue, Mar 06, Doug Maxey wrote:
> So to me, using
> sg_luns |tail -1
> should get the line with the singleton lun in it, albeit with some
> amount of leading whitespace.
In the example above, if installing onto sdc, tail -n 1 would give the
lun value from sdd.
> Can you extract some value f
On Tue, 06 Mar 2007 19:04:28 +0100, Olaf Hering wrote:
>
> Upcoming IBM pSeries firmware can boot from iscsi. To configure the
> openfirmware boot-device string, we need to construct a correct
> devicepath. This path includes the lun. Its currently not 100% clear
> how exactly this lun value has
Olaf Hering wrote:
> Upcoming IBM pSeries firmware can boot from iscsi. To configure the
> openfirmware boot-device string, we need to construct a correct
> devicepath. This path includes the lun. Its currently not 100% clear
> how exactly this lun value has to look like.
>
> sg_luns may be the to
Upcoming IBM pSeries firmware can boot from iscsi. To configure the
openfirmware boot-device string, we need to construct a correct
devicepath. This path includes the lun. Its currently not 100% clear
how exactly this lun value has to look like.
sg_luns may be the tool to get the value. But its c
5 matches
Mail list logo
