All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antony Vennard <antony.vennard@macrium.com>
To: buildroot@busybox.net
Subject: [Buildroot] Udev on a live CD system does not appear to populate /dev
Date: Fri, 09 Nov 2012 12:20:08 +0000	[thread overview]
Message-ID: <509CF4F8.6080608@macrium.com> (raw)
In-Reply-To: <509C2166.8050705@mind.be>

On 08/11/2012 21:17, Arnout Vandecappelle wrote:
>  If you build a cpio rootfs, you shouldn't need any additional command line
> parameters because the kernel never gets to mounting the root
> filesystem.  It
> just runs the /init in the initramfs.
> 
>  Using a cpio rootfs should also solve your problems with the device nodes,
> because we provide a /init that mounts devtmpfs explicitly.
> 
>  Regards,
>  Arnout
> 

Yep, I'd come to the conclusion I needed an /init to exist, constructing
the root file system. Manually creating the CD as a test, the kernel
panics (root file system not found) if init doesn't exist. I used the
one from fs/cpio/init as you suggested.

The ram_disk_size parameter does appear to be entirely optional.

I'm now on to the next problem - that script exec's /sbin/init which is
really /bin/busybox... which is exiting straight away or crashing, as
the kernel is now panicking about an exiting init :(

I'm going to have an experiment with this, see if I can understand what
the issue is.

I have also grabbed a copy of buildroot git. Once I've got this working,
I'll have a go at modifying buildroot to build iso9660 targets via this
mechanism. I'm no expert in this kind of thing, but it'll be a good
learning experience.

I may also potentially be looking to integrate EFI boot into our live CD
at some stage - if this is of interest I can have a go at adding this to
buildroot also.

Thanks for your help,

Antony


-- 
________________

Macrium? Software is a trading name of Paramount Software UK Ltd, 
Registered in England and Wales Number 02973414
Registered Office: Kilburn House, Manchester Science Park, Lloyd St. North, 
Manchester M15 6SE United Kingdom

The information contained in this e-mail is confidential, privileged, or 
otherwise protected from disclosure. It is intended only for the use of the 
authorized individual as indicated in the e-mail. Any unauthorized 
disclosure, copying, distribution or taking of any action based on the 
contents of this material is strictly prohibited.

If you have received this e-mail in error, please delete it immediately.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 895 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121109/742b79b0/attachment.asc>

  reply	other threads:[~2012-11-09 12:20 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
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 [this message]
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=509CF4F8.6080608@macrium.com \
    --to=antony.vennard@macrium.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.