From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] Udev on a live CD system does not appear to populate /dev
Date: Wed, 07 Nov 2012 19:56:20 +0200 [thread overview]
Message-ID: <509AA0C4.4060506@petroprogram.com> (raw)
In-Reply-To: <5099A14C.5000204@mind.be>
7.11.2012 1:46, Arnout Vandecappelle kirjoitti:
> On 06/11/12 19:37, Stefan Fr?berg wrote:
>> Here's what I have minimally in my own buildroot's fs/skeleton/dev
>> folder (which is copied at the end of the buildroot
>> process into output/target/dev )
>
> Err... That can only work if you have sudo in your post-build script
> - which
> we consider bad practice. We have the device_table to deal with
> device nodes.
> And all of that shouldn't be necessary if you use devtmpfs (or udev or
> mdev,
> which implies devtmpfs). If you use static device nodes, then the
> default
> device_table_dev creates all of those.
>
Nope, no sudo in my live Cd.
Just few pre-made device nodes in fs/skeleton/dev and my special made
init stuff in fs/skeleton/etc/init.d
Well ok, I confess ... I *did* modify /etc/init.d/rcS a little bit for
my needs and also added unionfs mounting to S15mount
and some few other little things
So far I have been very happy with my own personal Live CD Linux distro.
It has 873 MB worth of various userspace utilities in 700 MB CD-R disc.
Feat which would have not been posible without initramfs (XZ
compressed), unionfs and squashfs.
The lowest RAM amount I managed to start it was 192 MB.
With Xorg, Fluxbox and Firefox :-)
Without buildroot and my lil tweakings I could have never made it.
Best regards
Stefan
> If that doesn't work for you, then we should try to fix it in buildroot.
>
> Regards,
> Arnout
next prev parent reply other threads:[~2012-11-07 17:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 14:02 [Buildroot] Udev on a live CD system does not appear to populate /dev Antony Vennard
2012-11-06 18:37 ` Stefan Fröberg
2012-11-06 23:46 ` Arnout Vandecappelle
2012-11-07 17:56 ` Stefan Fröberg [this message]
2012-11-08 9:56 ` Antony Vennard
2012-11-08 12:35 ` Stefan Fröberg
2012-11-08 16:02 ` Antony Vennard
2012-11-08 16:20 ` Stefan Fröberg
2012-11-08 16:29 ` Stefan Fröberg
2012-11-13 6:53 ` Arnout Vandecappelle
2012-11-13 18:07 ` Stefan Fröberg
2012-11-17 22:54 ` Stefan Fröberg
2012-11-18 20:02 ` Arnout Vandecappelle
2012-11-18 20:11 ` Stefan Fröberg
2012-11-20 23:42 ` Stefan Fröberg
2012-11-08 21:17 ` Arnout Vandecappelle
2012-11-09 12:20 ` Antony Vennard
2012-11-09 13:01 ` Arnout Vandecappelle
2012-11-09 13:09 ` Antony Vennard
2012-11-09 15:04 ` Arnout Vandecappelle
2012-11-09 13:11 ` Stefan Fröberg
2012-11-08 15:12 ` Arnout Vandecappelle
2012-11-08 21:09 ` Arnout Vandecappelle
2012-11-06 23:26 ` Arnout Vandecappelle
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=509AA0C4.4060506@petroprogram.com \
--to=stefan.froberg@petroprogram.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 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.