From: Paulo Marques <pmarques@grupopie.com>
To: Vadim Lebedev <vadim@mbdsys.com>
Cc: linux-omap-open-source@linux.omap.com,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: PROBLEMS WITH DNS
Date: Fri, 08 Jun 2007 20:05:49 +0100 [thread overview]
Message-ID: <4669A88D.4070008@grupopie.com> (raw)
In-Reply-To: <4669A194.8090108@mbdsys.com>
Vadim Lebedev wrote:
> Paulo Marques wrote:
>
>> Vadim Lebedev wrote:
>>
>>> Eduardo Franceschini wrote:
>>> [...]
>>>
>>>> I can get an IP, but when I go to /etc/resolv.conf , I don't have an
>>>> IP for
>>>> DNS server... somebody know what to do?
>>>
>>> [...]
>>> Maybe one why to do it is to modify kernale mode dhcp client to
>>> create a procfs entry containig info for resolv.conf
>>> and have /etc/resolv.com to be symlink to procfs entry
>>
>>
>> I'd say this is just the opposite direction of where things seem to be
>> going nowadays.
>>
>> AFAICS, the current solution to this problem is to use initrd /
>> initramfs with a user-space dhcp client and nice script to get the DNS
>> information into /etc/resolv.conf.
>>
>> With this in place you can even drop the DHCP / NFS-root support from
>> the kernel and have it all done in user-space.
>>
>> This seems to be the current trend, and I wouldn't be surprised if the
>> options for IP auto config and NFS root were dropped from mainline in
>> the future.
>>
> Kernel mode dhcp client solutions allows muuch faster boot sequences...
> for embedded stuff 15-20 secs boot speed advantage is important....
I can't see why a user space client running from initramfs with
basically the same code as the in-kernel dhcp client would be much
slower. I'd be surprised if the difference is more than a few milliseconds.
So the real problem is to find a dhcp client that is actually as simple
as the in-kernel one. "udhcpc"[1] might just do what you want.
The only other argument I can see for in-kernel dhcp is that it is
easier to configure than it is to setup an initramfs filesystem. As soon
as that problem is somehow solved, I don't see the advantage in keeping
the in-kernel version.
--
Paulo Marques - www.grupopie.com
"Very funny Scotty. Now beam up my clothes."
[1] http://udhcp.busybox.net/
-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
next prev parent reply other threads:[~2007-06-08 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 17:23 PROBLEMS WITH DNS Eduardo Franceschini
2007-06-08 17:33 ` Nishanth Menon
2007-06-08 17:39 ` Vadim Lebedev
2007-06-08 17:54 ` Paulo Marques
2007-06-08 18:36 ` Vadim Lebedev
2007-06-08 19:05 ` Paulo Marques [this message]
2007-06-08 19:32 ` Hans-Jürgen Koch
2007-06-11 11:35 ` Paulo Marques
2007-06-08 19:39 ` Russell King - ARM Linux
2007-06-08 19:38 ` Russell King - ARM Linux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4669A88D.4070008@grupopie.com \
--to=pmarques@grupopie.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap-open-source@linux.omap.com \
--cc=vadim@mbdsys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox