Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: William Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] mdev handling
Date: Wed, 08 Sep 2010 15:22:09 +0100	[thread overview]
Message-ID: <4C879C11.3090603@carallon.com> (raw)
In-Reply-To: <AANLkTi=XLJvtakS=nKMYyybTJdtoVvgaA3NFkBSMivHu@mail.gmail.com>

  On 08/09/2010 15:07, Yegor Yefremov wrote:
> AFAIK mdev activation leads only to adding this binary to the rootfs
> tree. What about starting script? Would it make sense to create
> /etc/init.d/S1mdev with the following content:
>
> #!/bin/sh
> #
> # Start the mdev....
> #
>
> case "$1" in
>    start)
>          echo "Starting mdev..."
>          echo /sbin/mdev>  /proc/sys/kernel/hotplug
>          /sbin/mdev -s
>          ;;
>    stop)
> .......

This is what I do on every project I use with mdev, seems like adding an 
option would be good

> echo /sbin/mdev>  /proc/sys/kernel/hotplug - only if such an option
> selected. fstab should be also changed to have
>
> tmpfs           /dev           tmpfs    size=1M          0      0
>
> added. (The size should be much smaller, this is only for testing)

Again these two sound like sensible options.

Regards
Will

> What do you think about this?
>
> Regards,
> Yegor
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Development Manager                      Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

  reply	other threads:[~2010-09-08 14:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 14:07 [Buildroot] mdev handling Yegor Yefremov
2010-09-08 14:22 ` William Wagner [this message]
2010-09-08 14:29 ` Peter Korsgaard
2010-09-08 14:48   ` Yann E. MORIN
2010-09-08 15:07     ` Peter Korsgaard
2010-09-09  9:01   ` Yegor Yefremov
2010-09-09 10:19     ` Thomas Petazzoni
2010-09-09 10:38       ` Yegor Yefremov
2010-09-09 12:00         ` Thomas Petazzoni
2010-09-09 12:48           ` Yegor Yefremov
2010-09-10  7:40       ` Yegor Yefremov
2010-09-10  7:51         ` Peter Korsgaard

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=4C879C11.3090603@carallon.com \
    --to=will_wagner@carallon.com \
    --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