On Thu, Oct 01, 2015 at 04:56:55PM -0400, Ian Stakenvicius wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 01/10/15 04:16 PM, William Hubbs wrote: > > On Thu, Oct 01, 2015 at 02:42:15PM -0400, Ian Stakenvicius > > wrote: > >> -----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 > >>> 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. > > > > The original plan was to move to a point where everyone puts > > _netdev in their fstab for network mounts on Linux so that we > > don't have to track file system types like we do in OpenRC right > > now. On Linux, > > > > mount -a -O _netdev > > > > would mount all network file systems and > > > > umount -a -O _netdev > > > > would unmount them. On busybox, the last time I checked, umount > > -a doesn't support -O at all. > > > > (putting aside the removal of the openrc net-fs list and the need to > require -all- network mounts to need _netdev in /etc/fstab for a while > ) > > When did you last check busybox? Indications seem to be that > busybox has received this support a few versions ago. My quick > 'busybox mount -v -a -O _netdev ; busybox mount -v -a -O no_netdev' > seems to indicate it's supported fine with current stable busybox. > So i think this removal can just be rolled back as it's based on > obsolete knowledge. Please read my statement above again; I said umount not mount. ;-) William