All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] initramfs doesn't need root to create an image
Date: Sat, 29 Mar 2008 17:13:51 +0100	[thread overview]
Message-ID: <87wsnl7bk0.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1206802610.3224.180.camel@nigel-x60> (Nigel Kukard's message of "Sat\, 29 Mar 2008 14\:56\:50 +0000")

>>>>> "Nigel" == Nigel Kukard <nkukard@lbsd.net> writes:

 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?

 Nigel> Does fakeroot keep device-special information if you create
 Nigel> devices inside its environment? ie. if you create a /dev/hda
 Nigel> inside a fakeroot using mknod, tar it up, exit fakeroot, untar
 Nigel> it with admin privs, is it still a device special file?

Yes, that's the point of fakeroot.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2008-03-29 16:13 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
2008-03-29 16:02           ` Nigel Kukard
2008-03-29 16:13         ` Peter Korsgaard [this message]
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=87wsnl7bk0.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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.