On Fri, Dec 05, 2014 at 01:42:29PM -0800, Lee Duncan wrote:
> On 12/05/2014 01:14 PM, Greg KH wrote:
> > On Fri, Dec 05, 2014 at 11:51:16AM -0800, Lee Duncan wrote:
> >> Hi:
> >>
> >> I am trying to figure out how to use libudev to monitor for new iSCSI
> >> boot targets.
> >>
> >> For Emulex CNA c
On 12/05/2014 01:14 PM, Greg KH wrote:
> On Fri, Dec 05, 2014 at 11:51:16AM -0800, Lee Duncan wrote:
>> Hi:
>>
>> I am trying to figure out how to use libudev to monitor for new iSCSI
>> boot targets.
>>
>> For Emulex CNA cards, a new directory gets created of the form
>> /sys/firmware/iscsi_bootN.
On Fri, Dec 05, 2014 at 11:51:16AM -0800, Lee Duncan wrote:
> Hi:
>
> I am trying to figure out how to use libudev to monitor for new iSCSI
> boot targets.
>
> For Emulex CNA cards, a new directory gets created of the form
> /sys/firmware/iscsi_bootN.
Really? That's horrid, what kernel driver i
Hi:
I am trying to figure out how to use libudev to monitor for new iSCSI
boot targets.
For Emulex CNA cards, a new directory gets created of the form
/sys/firmware/iscsi_bootN.
I am new to libudev, but it looks like it's set up to monitor for new
devices. Can I use it to monitor for non-device
