linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David VomLehn <dvomlehn@cisco.com>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: linux-embedded@vger.kernel.org
Subject: Re: building Rootfs
Date: Tue, 08 Jul 2008 17:52:34 -0700	[thread overview]
Message-ID: <48740BD2.6090000@cisco.com> (raw)
In-Reply-To: <63386a3d0807081653t5e19cae2vd35c03de4bec7fa8@mail.gmail.com>

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

We do this all the time. We have a very minimal root filesystem and aren't 
currently using any of the frameworks for building root filesystems, so 
everything is done with make. In general, we create tar files for each piece. The 
piece that has device nodes has a make file with something like:

	all:
		fakeroot make fakeroot-package

	fakeroot-package:
		mkdir -p image
		mknod image/dev/null c 1 3
		mknod image/dev/random c 1 8
		tar -C image -czf image.tgz .

We ran into some issues when we separated running mknod and tar into separate 
fakeroot invocations because there is a bug in fakeroot with exporting and 
importing its state. Fortunately, doing all of this under a single fakeroot 
command works just fine. When we untar the tar files for all of the pieces to 
create a root filesystem image and then run mkcramfs to create a CRAMFS image, we 
do all commands under a single invocation of fakeroot.

No stage of the build requires running as root.
-- 
David VomLehn, dvomlehn@cisco.com




     - - - - -                              Cisco                            - - - - -         
This e-mail and any attachments may contain information which is confidential, 
proprietary, privileged or otherwise protected by law. The information is solely 
intended for the named addressee (or a person responsible for delivering it to 
the addressee). If you are not the intended recipient of this message, you are 
not authorized to read, print, retain, copy or disseminate this message or any 
part of it. If you have received this e-mail in error, please notify the sender 
immediately by return e-mail and delete it from your computer.

  reply	other threads:[~2008-07-09  0:52 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
2008-07-09  0:52             ` David VomLehn [this message]
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=48740BD2.6090000@cisco.com \
    --to=dvomlehn@cisco.com \
    --cc=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).