From: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>,
initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Please revert commit "There is only one resolv.conf."
Date: Thu, 17 Sep 2009 23:38:32 -0400 [thread overview]
Message-ID: <4AB300B8.4090307@redhat.com> (raw)
In-Reply-To: <4AB254A3.5000302-omB+W0Dpw2o@public.gmane.org>
On 09/17/2009 11:24 AM, Seewer Philippe wrote:
> Having only one resolv.conf is ok for a booted client. That is the
> normal and the usual behaviour is that the first interface to be up and
> ready with data is the one to write the contents.
>
> But inside dracut we really do not want that behaviour. First the
> primary interface (see bootdev cmdline argument) might not be the first
> interface to come up, second if we are in guess-the-interface mode,
> multiple interface might receive different data for resolv.conf and we
> have to use the correct stuff to mount.
>
> So please revert that commit.
Do you agree the one copied ultimately should be the interface that
successfully netbooted?
Warren
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-09-18 3:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 15:24 Please revert commit "There is only one resolv.conf." Seewer Philippe
[not found] ` <4AB254A3.5000302-omB+W0Dpw2o@public.gmane.org>
2009-09-18 3:38 ` Warren Togami [this message]
[not found] ` <4AB300B8.4090307-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-09-18 6:43 ` Seewer Philippe
[not found] ` <4AB32C08.2000406-omB+W0Dpw2o@public.gmane.org>
2009-10-07 21:21 ` Warren Togami
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=4AB300B8.4090307@redhat.com \
--to=wtogami-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=philippe.seewer-omB+W0Dpw2o@public.gmane.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