Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

Michael Biebl biebl at debian.org
Thu Dec 7 23:48:54 GMT 2017


Control: tags -1 moreinfo
Control: severity -1 normal

Am 08.12.2017 um 00:06 schrieb Duncan Hare:

> browne.danum.local:/nfsroot/b827eb/c23849/home /home   nfs     defaults,rw                    0 0	
> tmpfs                                    /tmp    tmpfs   nodev,nosuid,size=1%,mode=1777 0 0
> 
> After the failed scenario when boot is complete, This fails after mounting the home 
> directory by shell command:
> 
> sudo mkdir /abc
> sudo mount browne:/nfsroot/b827eb/c23849/home /abc
> 
> and normally this works:
>  
> sudo mkdir /abc
> sudo mount browne:/nfsroot/b827eb/c23849/home abc
> 
> and yes, my local domain suffix is .local, becuse it is a Microsoft domain.

How exactly do you configure your network (do you use ifupdown,
network-manager, something else)? Please share those exact configuration.

How exactly do you resolve those local names? Is that really a DNS or a
MDNS name? Do you have a local resolver running?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20171208/7295acc9/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list