From: Marek Skuczynski <mareksk@easymail.pl>
To: "Haller, John H (John)" <jhaller@alcatel-lucent.com>
Cc: Linus Walleij <linus.ml.walleij@gmail.com>,
linux-embedded@vger.kernel.org
Subject: Re: building Rootfs
Date: Wed, 09 Jul 2008 10:22:20 +0200 [thread overview]
Message-ID: <4874753C.4010601@easymail.pl> (raw)
In-Reply-To: <B78930B8E34A824993912C39C24569E60141D874@ILEXC3U01.ndc.lucent.com>
Haller, John H (John) pisze:
>> What else is there out there for rootfs, really? A hack
>> from every embedded company there is? I'm more after
>> what people actually *use* and what is community driven
>> here, not so much opinions on what is best (which will
>> probably be the unwanted side effect of this mail
>> anyway...)
>>
>> Linus
>
> There are three issues in building an embedded cross-filesystem:
[--CUT--]
> 3. Getting files into the filesystem when the development
> system does not allow root access.
Couple years ago, I found a simple solution for this issue. The
filesystem image is described in the initramfs_list file format. That is
easy to modify (adding new nodes, fixing paths, etc).
The final image building scenario is as follows:
cat initramfs_list | check_fs_integrity | mk<fs>image > image_file
Of course the initramfs_list file is cooked up dynamically basis on
configuration of kernel, drivers and etc.
mareksk
prev parent reply other threads:[~2008-07-09 8:22 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
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 [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=4874753C.4010601@easymail.pl \
--to=mareksk@easymail.pl \
--cc=jhaller@alcatel-lucent.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 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.