-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Since this conversation is now technical rather than news-item related, I've changed to a new thread.
On 01/10/15 02:17 PM, J. Roeleveld wrote: > On 1 October 2015 17:49:15 CEST, Mike Gilbert > <flop...@gentoo.org> wrote: >>>>>>>> On 28/09/15 06:58 PM, William Hubbs wrote: >>>>>>>>> Also, we are dropping the use of the -O switch >>>>>>>>> for mount/umount -a. This is being dropped >>>>>>>>> because it is util-linux specific and not >>>>>>>>> compatible with busybox. >>>>>>>> >> >> The _netdev option is really there to support things like >> iSCSI, where you are mounting a filesystem like ext4 from a >> block device which requires network connectivity. >> >> I think some changes are needed here, because this change to >> localmount is quite like to break this usage. > > All, > > I had a thought. Not sure if this is possible and if it is, it > would mean a change to the fstab for people using iSCSI. > > 1) Add an udev rule to name iSCSI devices differently. (Currently > sd×, maybe to something like scs×) 2) Have 'localmount' ignore > those entries in fstab. 3) Have 'netmount' (or similar) mount > those entries. > > I haven't looked into the current scripts yet, so if this doesn't > make any sense at all, let me know. I will investigate this more > over the weekend. > At this point, we need to verify the whole reason for its removal is actually accurate -- it seems it was dropped due to bug 468600, which is about -O [no]_netdev not being recognized by busybox mount. However, there are comments in the bug and notes in busybox documentation which seems to indicate that -O support has been in busybox since 1.20.2, and current stable is 1.23.1-r1.. If the issue is still confirmed, then we can look into alternative methods of handling iscsi. Unfortunately, filtering out targets for 'mount -a' based on their /dev name is entirely not supported by any mount that I know of, so the method listed above will likely be harder rather than easier to implement, so I don't think renaming them will be of much use (not to mention that it would entirely remove the possibility of mounting based on UUID and similar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlYNfocACgkQAJxUfCtlWe3BzwEA1g4oaAP0EITKy0GC0Giq9NAS XLKHTFNuEObUJNGI38gA/2Xl17ucnvN1TyCd5QZEQ132fOm1jd/e/f9NHDfwNlri =LOFf -----END PGP SIGNATURE-----
