From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Charles-Henri Collin <charlie.collin@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ip=dhcp problem...
Date: Sat, 18 Dec 2004 13:24:11 +0100 [thread overview]
Message-ID: <1103372650.12078.65.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <41C41E2D.3010306@free.fr>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On Sat, 2004-12-18 at 13:10, Charles-Henri Collin wrote:
> >The fix is to make sure you have a nameserver in your /etc/resolv.conf
> >The kernel has no idea how to resolve names into addresses. That's a
> >userspace thing. I'm not sure if you can extract the dhcp info from the
> >kernel after the boot, otherwise you'll just have to run a userspace
> >dhcp client, I use dhclient.
> >
> >
> >
> i should put a /etc/resolv.conf.... but i dont want, for "dark reasons" ;)
> if i have a /etc/resolv.conf, what's the point in querying the dhcp
> server for a nameserver???
> i thought this would set linux a nameserver in case no /etc/resolv.conf
> was find.
> btw, i can't dhclient has i'm nfs-rooting. doing this breaks my
> connection with the nfs server and i lose / !!!!!
> i'm working on it.
> thanks anyway
I use FAI (http://www.informatik.uni-koeln.de/fai/) to install servers
here. They use ip=dhcp in order to have nfs-root, then they run dhclient
in order to get dns and to maintain the lease correctly (not sure the
kernel does this for you). I don't loose contact with the nfs server,
works just fine.
--
/Martin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-12-18 12:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-18 10:15 Charles-Henri Collin
2004-12-18 10:51 ` Andreas Unterkircher
2004-12-18 11:00 ` Jan Engelhardt
2004-12-18 11:52 ` Charles-Henri Collin
2004-12-18 11:59 ` Martin Josefsson
2004-12-18 12:10 ` Charles-Henri Collin
2004-12-18 12:24 ` Martin Josefsson [this message]
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=1103372650.12078.65.camel@tux.rsn.bth.se \
--to=gandalf@wlug.westbo.se \
--cc=charlie.collin@free.fr \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®