On Tue, Jul 08, 2008 at 05:52:34PM -0700, David VomLehn wrote: > 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 . That does work fine when packaging the rootfs on the host. It was the reason why we went the ipkg way: you can put device nodes into them. > 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. The only stage we need root privileges in PTXdist is when creating a root filesystem which can be booted via nfsroot (which is common during development). In that case, you *need* /dev/console and /dev/null, which cannot be created by the user. We have solved that by using sudo there: the automatic build asks for the user password, but with a timeout. So in interactive builds, you can just enter the password and have a rootfs ready to be booted, and it still works with automatic overnight builds. rsc -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
