On 11/17/2017 4:17 PM, Martin Wilck wrote:
On Fri, 2017-11-17 at 16:09 -0800, si-wei liu wrote:
On 11/17/2017 11:11 AM, Martin Wilck wrote:
Please note that I'm not the author of the patch I linked, and that
this link I sent was also just a starting point:
https://github.com/danimo/dracut/commits/obs_from_git/modules.d/95i
scsi
Note also that this branch is quite a bit behind upstream dracut in
other areas, so porting the iSCSI changes may not be trivial.
Is there a plan to upstream these patches soon?
I don't know. I'll try to find out.
OK. Thanks!
Without getting the divergence into the
upstream it effectively prohibits other folks from contributing bug
fixes to the long standing issue as the nature of the two approaches
(fix iscsid v.s. overhaul with iscsiadm) are in conflict? Is there a
tradeoff in between - we fix the iscsistart issue first then once
you're
ready to upstream you overwrite what we had done?
If you think you're able to fix iscsistart for good, go ahead.
I have my doubts that it'll work in complex situations.
Yeah I understand the current mix use of iscsid and iscsistart is not
quite good. Some may work by chance while some resorts to good timing
thanks to various places of delay (sleep 1) in the script. I like the
proposal of new design of replacing iscsistart, that looks clean indeed.
Thanks,
-Siwei
Martin
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
