Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Kukard <nkukard@lbsd.net>
To: buildroot@busybox.net
Subject: [Buildroot] initramfs doesn't need root to create an image
Date: Sat, 29 Mar 2008 06:59:01 +0000	[thread overview]
Message-ID: <1206773941.3224.126.camel@nigel-x60> (raw)

Attached a patch which removes the requirement on fakeroot & makedevs
and prevents files from being created in /dev instead of devices when
one builds buildroot as a non-priv user.

Initramfs doesn't require a priv user to create the image. A perl script
merges the devices.txt into the initramfs list, fixes the permissions,
fixes ownership, orders directories to be created first and spits out a
clean list.

-N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: initramfs-rework-noroot.patch
Type: text/x-patch
Size: 8028 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080329/ca2de3e9/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://busybox.net/lists/buildroot/attachments/20080329/ca2de3e9/attachment.pgp 

             reply	other threads:[~2008-03-29  6:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29  6:59 Nigel Kukard [this message]
2008-03-29 14:00 ` [Buildroot] initramfs doesn't need root to create an image Hamish Moffatt
2008-03-29 14:12   ` Nigel Kukard
2008-03-29 14:33     ` Peter Korsgaard
2008-03-29 14:56       ` Nigel Kukard
2008-03-29 15:04         ` Hamish Moffatt
2008-03-29 16:02           ` Nigel Kukard
2008-03-29 16:13         ` Peter Korsgaard
2008-03-29 16:32           ` Nigel Kukard

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=1206773941.3224.126.camel@nigel-x60 \
    --to=nkukard@lbsd.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