The biggest blocker for getting this fixed in hardy isn't bug #44194, but rather Debian bug #383073 and Debian bug #383123 that were fixed in a post-hardy merge of sysvinit. Without that fix, there's no way to trigger mounting iscsi devices after they've been made available, which is the problem to be solved: the network interfaces are only *guaranteed* to be up after S40networking, and nothing in hardy will trigger mounting of non-network-filesystem devices after that point.
Fixing 44194 would let us cover all our bases for things such as iSCSI + wpa_supplicant, but that's not actually an interesting use case to the typical iSCSI user and not the problem being discussed here; fixing this bug without 44194 would not be a regression since /usr on iSCSI doesn't work today for anyone in hardy. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-iscsi in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
