From: Donald White <dbwhite@asu.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Create initrd tool without being root?
Date: Fri, 28 Mar 2003 07:16:39 -0700 [thread overview]
Message-ID: <3E845947.3050802@asu.edu> (raw)
In-Reply-To: 20030328082536.C0A8CC6E0D@atlas.denx.de
Thanks.
Wolfgang Denk wrote:
> In message <3E83EF1D.4050509@asu.edu> you wrote:
>
>>I thought someone on this list recently mentioned a tool dor creating initrd without
>> being root. I couldn't find it i the archives. Can someone help me?
>
>
> The ELDK (in current versions) uses the genext2fs to build the SELF
> ramdisk images. For example, you can check out the "spec" file for
> the SELF RPM from our ELDK build environment und manually go through
> the tsteps. Or just follow the usgae message:
>
> -> genext2fs
> Usage: genext2fs [options] image
> Create an ext2 filesystem image from directories/files
>
> -x image Use this image as a starting point
> -d directory Add this directory as source
> -f file Add nodes (e.g. devices) from this spec file
> -b blocks Size in blocks
> -i inodes Number of inodes
> -r reserved Number of reserved blocks
> -g path Generate a block map file for this path
> -e value Fill unallocated blocks with value
> -z Make files with holes
> -v Print resulting filesystem structure
> -h Show this help
>
> Example of spec file:
> drwx /dev
> crw- 10,190 /dev/lcd
> brw- 1,0 /dev/ram0
>
> Report bugs to xavier.bestel at free.fr
>
>
> Best regards,
>
> Wolfgang Denk
>
prev parent reply other threads:[~2003-03-28 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 6:43 [U-Boot-Users] Create initrd tool without being root? Donald White
2003-03-28 7:59 ` Stephan Linz
2003-03-28 14:16 ` Donald White
2003-03-28 8:25 ` Wolfgang Denk
2003-03-28 14:16 ` Donald White [this message]
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=3E845947.3050802@asu.edu \
--to=dbwhite@asu.edu \
--cc=u-boot@lists.denx.de \
/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