Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] eth0 missing ? [SOLVED]
Date: Fri, 27 Feb 2015 16:33:25 -0300	[thread overview]
Message-ID: <54F0C685.2010107@zacarias.com.ar> (raw)
In-Reply-To: <297D02207CF04F1EBF5136C4CA389165@JohanW7>

On 02/27/2015 04:28 PM, Sagaert Johan wrote:

> Hi 
> 
> In 2015.02-rc1 /run was introduced in the skeleton and an tmpfs entry was added in fstab.
> 
> There was an fstab file in my overlay file system that had overwritten the one from the skeleton
> so that /run existed on the real filesystem instead of been mounted as tmpfs.
> This caused the different pid files to remain between boots and confused eudev.
> 
> Best regards,
> Johan

Hi.
Buildroot assumes /run is volatile hence doesn't do any cleanup tasks on
it at boot time.
Regards.

      reply	other threads:[~2015-02-27 19:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25  9:57 [Buildroot] eth0 missing ? Sagaert Johan
2015-02-25 14:03 ` Gustavo Zacarias
2015-02-25 14:31   ` Sagaert Johan
2015-02-27 19:28   ` [Buildroot] eth0 missing ? [SOLVED] Sagaert Johan
2015-02-27 19:33     ` Gustavo Zacarias [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=54F0C685.2010107@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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