linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Linus Walleij" <linus.ml.walleij@gmail.com>
To: linux-embedded@vger.kernel.org
Subject: Re: building Rootfs
Date: Wed, 9 Jul 2008 01:53:46 +0200	[thread overview]
Message-ID: <63386a3d0807081653t5e19cae2vd35c03de4bec7fa8@mail.gmail.com> (raw)
In-Reply-To: <20080708140034.B2B7424681@gemini.denx.de>

2008/7/8 Wolfgang Denk <wd@denx.de>:

>> 3. Getting files into the filesystem when the development
>> system does not allow root access.

> 3. is a non-issue for most common file systems.

The only one thing I ever ran into trouble with was device nodes,
these cannot be reproduced any way, not even with fakeroot
environments, just in scratchbox, which in turn needs you to be root.

initramfs etc can handle it with special description files. But if
you want to cook up say a .tar file of your rootfs, you're pretty
much lost AFAIK.

The good thing is that you don't need the device nodes
if you have udev, I think the kernel wants /dev/console
and a few more at boot but actually it survives just fine
without them.

The rest is possible to create with fakeroot and clever
scripting if I'm not mistaken.

If you know some way of sneaking a device node into a
.tar file created ENTIRELY running as a regular user,
tell me!

Linus

  reply	other threads:[~2008-07-08 23:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BAY131-W252EE4B85EEB3F7A87466FE2940@phx.gbl>
     [not found] ` <4871E98F.8030802@gmail.com>
     [not found]   ` <20080707181018.GG4319@pengutronix.de>
2008-07-07 20:34     ` building Rootfs Linus Walleij
2008-07-07 21:21       ` Robert Schwebel
2008-07-09  0:14         ` Linus Walleij
2008-07-09  7:06           ` Robert Schwebel
2008-07-07 23:24       ` Haller, John H (John)
2008-07-08  6:54         ` Robert Schwebel
2008-07-08 14:00         ` Wolfgang Denk
2008-07-08 23:53           ` Linus Walleij [this message]
2008-07-09  0:52             ` David VomLehn
2008-07-09  7:10               ` Robert Schwebel
2008-07-09  6:21             ` Wolfgang Denk
2008-07-09  6:43             ` Robert Schwebel
2008-07-09  7:22             ` Peter Korsgaard
2008-07-09  8:22         ` Marek Skuczynski

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=63386a3d0807081653t5e19cae2vd35c03de4bec7fa8@mail.gmail.com \
    --to=linus.ml.walleij@gmail.com \
    --cc=linux-embedded@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).