From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Properly setting up hotplug
Date: Wed, 15 Apr 2009 20:01:47 +0200 [thread overview]
Message-ID: <87eivtx0c4.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090414103327.2fd69516@danhplaptop> (Dan Lyke's message of "Tue\, 14 Apr 2009 10\:33\:27 -0700")
>>>>> "Dan" == Dan Lyke <danlyke@flutterby.com> writes:
Dan> So I know I've gotten a Buildroot install that did this automatically
Dan> once, but through various incremental steps I've gotten a kernel that
Dan> has the hotplug stuff enabled, and if I
Dan> echo /bin/mdev > /proc/sys/kernel/hotplug
Dan> or just run "mdev -s" manually I get my hot-plugged devices created, but
Dan> I'm sure that at some point I had a system where buildroot had created
Dan> the appropriate init script for me.
Dan> Am I hallucinating, or to get this as part of the compile do I need to
Dan> copy my configs across to a fresh buildroot and make again?
The target_busybox does this ("use minimal target skeleton" under the
busybox config).
Dan> And what's the "make" argument for Buildroot that should clean
Dan> everything, but not destroy my configs? "make clean" destroys configs,
Dan> or at least did last time I typed it...
make distclean.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-04-15 18:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 17:33 [Buildroot] Properly setting up hotplug Dan Lyke
2009-04-15 18:01 ` Peter Korsgaard [this message]
2009-04-16 7:10 ` Thomas Petazzoni
2009-04-16 17:59 ` Peter Korsgaard
2009-04-17 0:42 ` Hamish Moffatt
2009-04-17 5:20 ` Peter Korsgaard
2009-04-17 14:19 ` Dan Lyke
-- strict thread matches above, loose matches on Subject: below --
2009-04-17 8:33 Sagaert Johan
2009-04-17 8:52 ` Thiago A. Corrêa
2009-04-17 13:56 ` Peter Korsgaard
2009-04-17 14:19 ` Lloyd Sargent
2009-04-17 13:36 ` Peter Korsgaard
[not found] <E8FBAEC0D1A8452EA1A58E35916B04E6@apexjs>
2009-04-22 8:52 ` 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=87eivtx0c4.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.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.