<html><head></head><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:10px"><div id="yui_3_16_0_ym19_1_1512664885613_61568">Michael</div><div id="yui_3_16_0_ym19_1_1512664885613_61570"><br></div><div id="yui_3_16_0_ym19_1_1512664885613_61572">Full DNS is provided by an MS Windows server 2012R2.</div><div id="yui_3_16_0_ym19_1_1512664885613_61364"><br></div><div id="yui_3_16_0_ym19_1_1512664885613_61362">Because it is net boot, the network in enabled before the kernel is loaded by u-boot,</div><div id="yui_3_16_0_ym19_1_1512664885613_61366" dir="ltr">and the kernel starts and mounts the file system over NFS.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61399"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61424">Networking parameters, including DNS servers are pass through the kernel parameters.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61553"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61588">Kernel parms are (these include a lot of raspberry pi stuff), all one line no carriage returns<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61640"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61652">dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs rootfstype=nfs nfsrootdebug elevator=deadline rootwait nfsroot=192.168.1.10:/nfsroot/r.32.test,tcp,vers=3 ip=192.168.1.132:192.168.1.10:192.168.1.1:255.255.255.0:abcdef::off:192.168.1.12:192.168.1.22</div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61700"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61720">192,168,1,132 is the raspberry pi machine<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61701">192.168.1.10 is the linux file server</div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61756">192.168.1.1 is the default gateway</div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61758">255.255.255.0 is the netmask</div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61760">abcdef is the hostname in this example<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61762">192.168.1.12 is one dns server</div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61768">192.168.1.22 is the second dns server</div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61833"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61834">We don't use /dev/nfs in fstab, due to a bug in debian stretch mount command (a previous bug report) - which has undergone much change because of the <br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_62005">introduction of fiilesystem ids replacing device names.<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61817"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61832">the parameters are completed as above by u-boot script.<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61775"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61542">U-boot does a dhcp command to get the parameters.<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61456"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61479">The Linux networking is left as configured in Debian. It can be configured as manual or static</div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61507">in /etc/networking/interfaces with little or no change in behavior. If configure with dhcp Linux <br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61528">just get another lease on the same Ethernet address, because the <br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61948">mac address is the same for u-boot and linux.<br></div><div id="yui_3_16_0_ym19_1_1512664885613_61361"><span><br></span></div><div id="yui_3_16_0_ym19_1_1512664885613_61951"><span id="yui_3_16_0_ym19_1_1512664885613_61950">In this configuration networking is the prereq to file systems because we are booting a ZFS machine, with as much of the file system ro as possible</span></div><div id="yui_3_16_0_ym19_1_1512664885613_61971" dir="ltr"><span id="yui_3_16_0_ym19_1_1512664885613_61950">to have a very secure system. At the application layer we plan to run Citrix which provides excellent application control.</span></div><div id="yui_3_16_0_ym19_1_1512664885613_61342"> </div><div class="signature" id="yui_3_16_0_ym19_1_1512664885613_61311">Duncan Hare<br><br>714 931 7952</div><div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1512664885613_61307"><br><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1512664885613_61299" style="display: block;"> <div style="font-family: verdana, helvetica, sans-serif; font-size: 10px;" id="yui_3_16_0_ym19_1_1512664885613_61298"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1512664885613_61297"> <div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61305"> <font id="yui_3_16_0_ym19_1_1512664885613_61386" face="Arial" size="2"> <hr id="yui_3_16_0_ym19_1_1512664885613_61388" size="1"> <b><span style="font-weight:bold;">From:</span></b> Michael Biebl <biebl@debian.org><br> <b><span style="font-weight: bold;">To:</span></b> Duncan Hare <dh@synoia.com>; 883829@bugs.debian.org <br> <b><span style="font-weight: bold;">Sent:</span></b> Thursday, December 7, 2017 3:49 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_ym19_1_1512664885613_61296"><br><div dir="ltr" id="yui_3_16_0_ym19_1_1512664885613_61295">Control: tags -1 moreinfo<br clear="none">Control: severity -1 normal<br clear="none"><div class="yqt9090020745" id="yqtfd84526"><br clear="none">Am 08.12.2017 um 00:06 schrieb Duncan Hare:<br clear="none"><br clear="none">> browne.danum.local:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0 <br clear="none">> tmpfs /tmp tmpfs nodev,nosuid,size=1%,mode=1777 0 0<br clear="none">> <br clear="none">> After the failed scenario when boot is complete, This fails after mounting the home <br clear="none">> directory by shell command:<br clear="none">> <br clear="none">> sudo mkdir /abc<br clear="none">> sudo mount browne:/nfsroot/b827eb/c23849/home /abc<br clear="none">> <br clear="none">> and normally this works:<br clear="none">> <br clear="none">> sudo mkdir /abc<br clear="none">> sudo mount browne:/nfsroot/b827eb/c23849/home abc<br clear="none">> <br clear="none">> and yes, my local domain suffix is .local, becuse it is a Microsoft domain.</div><br clear="none"><br clear="none">How exactly do you configure your network (do you use ifupdown,<br clear="none">network-manager, something else)? Please share those exact configuration.<br clear="none"><br clear="none">How exactly do you resolve those local names? Is that really a DNS or a<br clear="none">MDNS name? Do you have a local resolver running?<br clear="none"><br clear="none"><br clear="none">-- <br clear="none">Why is it that all of the instruments seeking intelligent life in the<br clear="none">universe are pointed away from Earth?<div class="yqt9090020745" id="yqtfd25382"><br clear="none"></div></div><br><br></div> </div> </div> </div></div></body></html>