On Sun, Jan 26, 2014 at 07:44:29PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Aug 20, 2013 at 11:30:25AM +0200, Michael Biebl wrote:
> > Am 20.08.2013 01:14, schrieb Andreas Kloeckner:
> > > No idea, up to you. Specifying _netdev for an NFS mount feels a bit
> > > redundant. It's also a regression of sorts, since sysvinit appears to
> > > handle this ok.
> >
> > sysvinit (or rather /etc/init.d/mountnfs.sh) contains a hard-coded list
> > of "network" file systems. I'm not sure if this list is complete and
> > would fail for more exotic ones, too.
> > I'm not sure, if I'd like to maintain such a hard-coded list within
> > systemd as this approach looks like a hack to me.
> Hack or no hack, we maintain such a list :P
>
> bool fstype_is_network(const char *fstype) {
> static const char table[] =
> "cifs\0"
> "smbfs\0"
> "ncpfs\0"
> "ncp\0"
> "nfs\0"
> "nfs4\0"
> "gfs\0"
> "gfs2\0";
>
> return nulstr_contains(table, fstype);
> }
>
> _netdev can be used to tell systemd about fs types in addition to that
> lits. This actually doesn't change all that often, so it's not much of
> a problem.
I see that this was already pointed out in the other subthread.
Zbyszek
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
