Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1141] New: BusyBox based initramfs generation
Date: Fri, 19 Feb 2010 11:44:45 +0000 (UTC)	[thread overview]
Message-ID: <bug-1141-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=1141

           Summary: BusyBox based initramfs generation
           Product: buildroot
           Version: 2009.11
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: serj.kalichev at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=1141)
 --> (https://bugs.busybox.net/attachment.cgi?id=1141)
BusyBox based initramfs generation patch

Sometimes it's necessary to generate not rootfs only but both real rootfs and
initramfs. Initramfs is more simpler and don't need many different packages but
only specially configured busybox and some additional scripts.

There is a makefile initramfs.mk in package/busybox dir for BusyBox based
initramfs generation. But it was unfinished and commented in Config.in. I could
not use it for real project so I try to patch BuildRoot to make it work.

Now BuildRoot can use target dir for generation initramfs. I change
target/initramfs/Config.in file to select the initramfs generation way. They
can choose "none", "initramfs from target dir" and "BusyBox based initramfs".
When you choose "initramfs from target dir" - it's a traditional way to
generate initramfs.

When the choice is "BusyBox based initramfs" BuildRoot can generate two images
- one for initramfs (put it into the bzImage) and the second for real rootfs.
The user can specify the BusyBox config file, the filesystem skeleton and a dir
with customization files for initramfs generation.

The attached patch consist of 
* target/initramfs/Config.in - to configure initramfs generation parameters
* package/busybox/initramfs.mk - to build specially configured BusyBox and
generate the initramfs image. It depends on files in the
package/busybox/initramfs_custom (by default) directory. So user can change
custom files and the initramfs will be rebuild.
* package/busybox/busybox-initramfs.config - it's only the example of
minimalist BusyBox configuration for the initramfs.
* package/busybox/initramfs_custom - it's only the example of simple init
script for the initramfs. It can mount rootfs by the UUID and LABEL.


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2010-02-19 11:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 11:44 bugzilla at busybox.net [this message]
2010-02-21 22:33 ` [Buildroot] [Bug 1141] BusyBox based initramfs generation bugzilla at busybox.net
2010-06-07 14:52 ` bugzilla at busybox.net
2010-06-07 19:44 ` bugzilla at busybox.net
2010-06-07 20:23 ` bugzilla at busybox.net

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=bug-1141-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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