Re: [systemd-devel] Help: Local and Remote targets

2019-08-27 Thread Lennart Poettering
On Di, 20.08.19 15:26, Tony Rodriguez (unixpro1...@gmail.com) wrote: > I modified systemd-219 functionality to meet a custom requirement for > detecting filesystems/devices that use iscsi without using the _netdev > keyword in /etc/fstab.  It is a strict requirement regarding not using > _netdev

Re: [systemd-devel] Help: Local and Remote targets

2019-08-20 Thread Tony Rodriguez
Understood but I don't have to worry about iscsi offloading for now.   Some theories I have to attack the problem but each has a problem and may be complex. 1) Since I can obtain udev/disk information when the system is in a multi-user already booted stated.  Check for "iscsi" devices and

Re: [systemd-devel] Help: Local and Remote targets

2019-08-20 Thread Rick Beldin
This might be problematic. What will you do with iscsi devices that support iscsi offload? Those are typically completely invisible to the OS and just appear as another HBA. On 8/20/19 3:26 PM, Tony Rodriguez wrote: > I modified systemd-219 functionality to meet a custom requirement for >

[systemd-devel] Help: Local and Remote targets

2019-08-20 Thread Tony Rodriguez
I modified systemd-219 functionality to meet a custom requirement for detecting filesystems/devices that use iscsi without using the _netdev keyword in /etc/fstab.  It is a strict requirement regarding not using _netdev that I have no control over.   However,  I am stuck. From my