All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] /run/udev missing ?
Date: Tue, 16 Aug 2011 07:44:44 -0500	[thread overview]
Message-ID: <201108160744.47656.minimod@morethan.org> (raw)
In-Reply-To: <CALR4fELxZAaArCZ9c7SyJzOusP4V6ZBDEtcDhna1yUFFQH7E1A@mail.gmail.com>

On Tue August 16 2011, Diego Iastrubni wrote:
> On Tue, Aug 16, 2011 at 11:40 AM, Sven Neumann <s.neumann@raumfeld.com>wrote:
> 
> >
> > Do you have a suggestion on how to use udev with a kernel that does not
> > yet have this option? We are stuck with 2.6.31 on one of our platforms
> > and I haven't been able to get udev working with recent buildroot on
> > this platform.
> >
> >
> This init.d file woks for me on 2.6.32. I am using tmpfs for mounting udev.
>

Isn't: mount -t ramfs
A ram disk on the older kernels rather than a tmpfs (-t tmpfs) ?

Mike
> 
> Note that for udev 173 you will also need  a patch to compile with older
> toolchains (look for in in the ML or the bugzilla).
> 

      reply	other threads:[~2011-08-16 12:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12  8:29 [Buildroot] /run/udev missing ? Sven Neumann
2011-08-14  6:43 ` Peter Korsgaard
2011-08-15  8:21   ` Sven Neumann
2011-08-15  9:05     ` Peter Korsgaard
2011-08-15  9:34       ` Sven Neumann
2011-08-15 12:10         ` Peter Korsgaard
2011-08-15 14:01           ` Sven Neumann
2011-08-15 14:18             ` Daniel Mack
2011-08-15 14:24             ` Baruch Siach
2011-08-16  8:40   ` Sven Neumann
2011-08-16 11:59     ` Diego Iastrubni
2011-08-16 12:44       ` Michael S. Zick [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=201108160744.47656.minimod@morethan.org \
    --to=minimod@morethan.org \
    --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 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.