From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20110414/003985.html | 71 +++++++++++++++++++++++++++++++++ 1 file changed, 71 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110414/003985.html (limited to 'zarb-ml/mageia-dev/20110414/003985.html') diff --git a/zarb-ml/mageia-dev/20110414/003985.html b/zarb-ml/mageia-dev/20110414/003985.html new file mode 100644 index 000000000..20c6fc6a8 --- /dev/null +++ b/zarb-ml/mageia-dev/20110414/003985.html @@ -0,0 +1,71 @@ + + + + [Mageia-dev] dhcp-client is borked as of today + + + + + + + + + +

[Mageia-dev] dhcp-client is borked as of today

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Apr 14 19:07:14 CEST 2011 +

+
+ +
On 14 April 2011 01:46, Frank Griffin <ftg at roadrunner.com> wrote:
+>> It writes a "search" line to /etc/resolv.conf of the not-fully-qualified
+>> hostname rather than the domain names returned by the DHCP server.
+>>
+>> For instance, if the hostname is "ftglap" and the domain names returned by
+>> the server are "x.y.z y.z", you get "search ftglap" rather than  "search
+>> x.y.z y.z" as you used to get prior to the last update.
+>>
+>> Ring a bell with anyone ?  I'm not sure if this is worth a bug report,
+>> unless it was a conscious decision that needs to be contested.
+>>
+> This was for an NM-controlled wireless NIC.  On a desktop host for a wired
+> NIC not controlled by NM, there is now no "search" line at all.
+
+A NM issue then?
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1