From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] initramfs doesn't need root to create an image
Date: Sun, 30 Mar 2008 01:00:04 +1100 [thread overview]
Message-ID: <20080329140004.GA25949@cloud.net.au> (raw)
In-Reply-To: <1206773941.3224.126.camel@nigel-x60>
On Sat, Mar 29, 2008 at 06:59:01AM +0000, Nigel Kukard wrote:
> 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.
Why? Was there a problem with fakeroot?
The ext2 and jffs2 targets both use fakeroot, although the generator
tools can do privilege squashing and handle device tables themselves.
Next week I need to add ubifs support, and currently the generator tool
does not have device table support fwiw.
Thanks,
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-03-29 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 6:59 [Buildroot] initramfs doesn't need root to create an image Nigel Kukard
2008-03-29 14:00 ` Hamish Moffatt [this message]
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=20080329140004.GA25949@cloud.net.au \
--to=hamish@cloud.net.au \
--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