<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_1512752942792_28108"><span></span></div><div id="yui_3_16_0_ym19_1_1512752942792_28125"> Michael</div><div class="qtdSeparateBR"><br><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1512752942792_28115" style="display: block;"><div style="font-family: verdana, helvetica, sans-serif; font-size: 10px;" id="yui_3_16_0_ym19_1_1512752942792_28114"><div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1512752942792_28113"><div class="y_msg_container" id="yui_3_16_0_ym19_1_1512752942792_28119"><div id="yiv7387172123"><div id="yui_3_16_0_ym19_1_1512752942792_28128"><div style="color:#000;background-color:#fff;font-family:verdana, helvetica, sans-serif;font-size:10px;" id="yui_3_16_0_ym19_1_1512752942792_28127"><div id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26301"><br clear="none"></div><div dir="ltr" id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26299">u-boot is a bootloader. The u-boot script load the kernel from a server,, constructs the kernel commandline, <br clear="none"></div><div dir="ltr" id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26416">and the u-boot script is complete when the kernel starts, well before these failures. <br clear="none"></div><div id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26297"><br clear="none"></div><div id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26287">In the kernel command line there is a dns server address, 192.168.1.12 passed to the linux kernel on the kernel command line. <br clear="none"></div><div id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26448"><br clear="none"></div><div id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26518">How the DNS server address is passed to resolveconf by the kernal I do not know. That's an interface between the kernel and systemd.</div><div id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26520"><br clear="none"></div><div id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26522">As I wrote, I can define the Ethernet interface as dhcp if that's what is required to populate the files.<br clear="none"></div><div id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26286"><span></span></div><div id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26275">Regards <br clear="none"></div><div class="yiv7387172123signature" id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26253">Duncan Hare<br clear="none"><br clear="none">714 931 7952</div><div class="yiv7387172123qtdSeparateBR" id="yui_3_16_0_ym19_1_1512752942792_28138"><br clear="none"><br clear="none"></div><div class="yiv7387172123yqt3762778052" id="yiv7387172123yqt14650"><div class="yiv7387172123yahoo_quoted" id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26245" style="display:block;"> <div id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26244" style="font-family:verdana, helvetica, sans-serif;font-size:10px;"> <div id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26243" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div dir="ltr" id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26242"> <font id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26241" face="Arial" size="2"> </font><hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Michael Biebl <biebl@debian.org><br clear="none"> <b><span style="font-weight:bold;">To:</span></b> Duncan Hare <dh@synoia.com>; 883829@bugs.debian.org <br clear="none"> <b><span style="font-weight:bold;">Sent:</span></b> Friday, December 8, 2017 10:33 AM<br clear="none"> <b><span style="font-weight:bold;">Subject:</span></b> Re: Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing<br clear="none"> </div> <div class="yiv7387172123y_msg_container" id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26556"><br clear="none"><div dir="ltr" id="yiv7387172123yui_3_16_0_ym19_1_1512752942792_26555">Am 08.12.2017 um 01:44 schrieb Duncan Hare:<br clear="none">> Michael<br clear="none">> <br clear="none">> Full DNS is provided by an MS Windows server 2012R2.<br clear="none">> <br clear="none">> Because it is net boot, the network in enabled before the kernel is<br clear="none">> loaded by u-boot,<br clear="none">> and the kernel starts and mounts the file system over NFS.<br clear="none">> <br clear="none">> Networking parameters, including DNS servers are pass through the kernel<br clear="none">> parameters.<br clear="none">> <br clear="none">> Kernel parms are (these include a lot of raspberry pi stuff), all one<br clear="none">> line no carriage returns<br clear="none">> <br clear="none">> dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs<br clear="none">> rootfstype=nfs nfsrootdebug elevator=deadline rootwait<br clear="none">> nfsroot=192.168.1.10:/nfsroot/r.32.test,tcp,vers=3<br clear="none">> 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<br clear="none">> <br clear="none">> 192,168,1,132 is the raspberry pi machine<br clear="none">> 192.168.1.10 is the linux file server<br clear="none">> 192.168.1.1 is the default gateway<br clear="none">> 255.255.255.0 is the netmask<br clear="none">> abcdef is the hostname in this example<br clear="none">> 192.168.1.12 is one dns server<br clear="none">> 192.168.1.22 is the second dns server<br clear="none">> <br clear="none">> We don't use /dev/nfs in fstab, due to a bug in debian stretch mount<br clear="none">> command (a previous bug report) - which has undergone much change<br clear="none">> because of the<br clear="none">> introduction of fiilesystem ids replacing device names.<br clear="none">> <br clear="none">> the parameters are completed as above by u-boot script.<br clear="none">> <br clear="none">> U-boot does a dhcp command to get the parameters.<br clear="none"><br clear="none">So if I understand you correctly, there is a u-boot script which sets up<br clear="none">/etc/resolv.conf. How exactly does this u-boot script look like and how<br clear="none">is it started. How do you ensure that this script runs before systemd<br clear="none">attempts the NFS network mounts?<br clear="none"><br clear="none">This looks like another case of a misconfiguration.<br clear="none">Systemd can not magically know that it has to wait for a u-boot script<br clear="none">to finish before it attempts any network mounts.<br clear="none">This is for you, the admin, to setup correctly or the u-boot script<br clear="none">(assuming it ships a systemd service) to hook into the correct targets.<br clear="none"><br clear="none"><br clear="none"><br clear="none">> The Linux networking is left as configured in Debian. It can be<br clear="none">> configured as manual or static<br clear="none">> in /etc/networking/interfaces with little or no change in behavior. If<br clear="none">> configure with dhcp Linux<br clear="none">> just get another lease on the same Ethernet address, because the<br clear="none">> mac address is the same for u-boot and linux.<br clear="none">> <br clear="none">> In this configuration networking is the prereq to file systems because<br clear="none">> we are booting a ZFS machine, with as much of the file system ro as possible<br clear="none">> to have a very secure system. At the application layer we plan to run<br clear="none">> Citrix which provides excellent application control.<br clear="none">> <br clear="none"><br clear="none">That's not relevant to this issue.<div class="yiv7387172123yqt5018694463" id="yiv7387172123yqtfd26897"><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?<br clear="none"></div></div><br clear="none"><br clear="none"></div> </div> </div> </div></div></div></div></div><br><br></div> </div> </div> </div></div></body></html>