From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>, ChenQi <Qi.Chen@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] netbase: add entry to /etc/hosts according to /etc/hostname
Date: Mon, 07 Jan 2019 14:38:06 +0000 [thread overview]
Message-ID: <e8d6a8d1ee7ff0d86ae25c22a09367f0cdb2eeae.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJTo0LaEJ6FTnsbAydx18wKAvHa8dfSAoSo0BpXdVtszAtHn8A@mail.gmail.com>
On Fri, 2018-12-14 at 21:45 +0000, Burton, Ross wrote:
> On Fri, 30 Nov 2018 at 02:18, Chen Qi <Qi.Chen@windriver.com> wrote:
> > We default hostname to ${MACHINE}, but it's not in /etc/hosts,
> > resulting in commands like `hostname -f' failing due to lack
> > of entry.
> >
> > So add entry to /etc/hosts according to /etc/hostname. We do
> > this via pkg_postinst because hostname is set in base-files
> > recipe.
>
> RP and myself are still arguing over this so I thought I'd make my
> argument on the list for debate.
>
> Updating /etc/hosts is being done with a postinst in netbase simply
> because /etc/hostname is contained in the base-files recipe. I
> advocate just moving the creation of /etc/hosts to base-files along
> with /etc/hostname, then base-files can write both files at the same
> time. There's already a dependency on base-files from netbase so
> there will be no change in the rootfs, a file will just move between
> packages.
Coming back to this after the holidays, I agree with Ross, we should
move /etc/hostname to base-files and keep this simple. I'd like to get
this fixed, could you update the patch please?
Cheers,
Richard
next prev parent reply other threads:[~2019-01-07 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 9:37 [PATCH 0/1] netbase: add entry to /etc/hosts according to /etc/hostname Chen Qi
2018-11-29 9:37 ` [PATCH 1/1] " Chen Qi
2018-12-14 21:45 ` Burton, Ross
2019-01-07 14:38 ` Richard Purdie [this message]
2019-01-08 1:57 ` ChenQi
2018-12-26 16:06 ` Jacob Kroon
2018-12-26 17:12 ` Jacob Kroon
-- strict thread matches above, loose matches on Subject: below --
2018-11-26 6:56 [PATCH 0/1] " Chen Qi
2018-11-26 6:56 ` [PATCH 1/1] " Chen Qi
2018-11-28 10:26 ` Burton, Ross
2018-11-28 11:21 ` Richard Purdie
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=e8d6a8d1ee7ff0d86ae25c22a09367f0cdb2eeae.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Qi.Chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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