All of lore.kernel.org
 help / color / mirror / Atom feed
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 02:04:45 +1100	[thread overview]
Message-ID: <20080329150445.GA27838@cloud.net.au> (raw)
In-Reply-To: <1206802610.3224.180.camel@nigel-x60>

On Sat, Mar 29, 2008 at 02:56:50PM +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?
> > 
> >  Nigel> Not fakeroot itself, but you cannot create a device if you're
> >  Nigel> a non-priv user. So ... nothing fails, makedevs generates
> >  Nigel> lovely zero size files instead of devices & fakeroot appears
> >  Nigel> to hide the errors.
> > 
> > But that's the point of fakeroot. Applications run from within
> > fakeroot believes the trickery and sees the (fake) device nodes. I
> > haven't looked into the initramfs stuff, but why wouldn't that work
> > there as well?
> 
> Does fakeroot keep device-special information if you create devices
> inside its environment? ie. if you create a /dev/hda inside a fakeroot
> using mknod, tar it up, exit fakeroot, untar it with admin privs, is it
> still a device special file?

Yes. The ext2 and jffs2 targets use it for that purpose: they use
makedevs to process the device table, then call genext2fs/mkfs.jffs2
within the fakeroot session to create the image.

You can even have the special devices persist across fakeroot sessions
if you tell it to save/load its session to file.


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  reply	other threads:[~2008-03-29 15:04 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
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 [this message]
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=20080329150445.GA27838@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 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.