From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 2/2] volatiles: Create /var/run/resolv.conf before linking to it
Date: Mon, 15 Dec 2014 07:13:40 -0700 [thread overview]
Message-ID: <548EEC94.4020601@mlbassoc.com> (raw)
In-Reply-To: <1418500650-2156-2-git-send-email-mgloff@emacinc.com>
No commit log?
Also, the order for a symbolic link should not matter, so why make this change?
On 2014-12-13 12:57, Michael Gloff wrote:
> Signed-off-by: Michael Gloff <mgloff@emacinc.com>
> ---
> meta/recipes-core/initscripts/initscripts-1.0/volatiles | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/initscripts/initscripts-1.0/volatiles b/meta/recipes-core/initscripts/initscripts-1.0/volatiles
> index 1fc5816..e6f0695 100644
> --- a/meta/recipes-core/initscripts/initscripts-1.0/volatiles
> +++ b/meta/recipes-core/initscripts/initscripts-1.0/volatiles
> @@ -32,7 +32,7 @@ l root root 1777 /tmp /var/tmp
> d root root 0755 /var/lock/subsys none
> f root root 0664 /var/log/wtmp none
> f root root 0664 /var/run/utmp none
> -l root root 0644 /etc/resolv.conf /var/run/resolv.conf
> f root root 0644 /var/run/resolv.conf none
> +l root root 0644 /etc/resolv.conf /var/run/resolv.conf
> d root root 1777 /run/media none
> l root root 1777 /media /run/media
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-12-15 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 19:57 [PATCH V2 1/2] Link /media to /run/media Michael Gloff
2014-12-13 19:57 ` [PATCH V2 2/2] volatiles: Create /var/run/resolv.conf before linking to it Michael Gloff
2014-12-13 19:59 ` Michael Gloff
2014-12-15 14:13 ` Gary Thomas [this message]
2015-02-07 22:15 ` Michael Gloff
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=548EEC94.4020601@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.