From: Wolfgang Denk <wd@denx.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linh Dang <linhd@nortelnetworks.com>,
Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: list of 2.6-related migration issues for embedded programmers?
Date: Mon, 19 Jul 2004 22:58:30 +0200 [thread overview]
Message-ID: <20040719205835.AA851C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 19 Jul 2004 13:51:57 EDT." <Pine.LNX.4.60.0407191350320.23725@dell.enoriver.com>
In message <Pine.LNX.4.60.0407191350320.23725@dell.enoriver.com> you wrote:
>
> > initramfs is convenient. you don't need root access nor special tools
> > to create the root-fs. it very easy when you want to
> > version-controlled you root-fs.
>
> ah, that would be convenient since, as it is, i'm using a hacked
> version of "genext2fs" that allows me to create the initial root fs as
> a regular user. i *definitely* have to look into initramfs, then.
What do you mean with "hacked"? Standard "genext2fs" will do this
just fine.
And as usual, there is two sides to initramfs. It may be convenient
for some cases, where you can use the very same root filesystem image
bundled with the kernel image, but exactly thsi convenience may hurt
you in other cases where it's much better when you have separated
images which can be updated independently of each other.
Speaking for myself: I don't see advantages in it. None.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
I used to be indecisive, now I'm not sure.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-19 20:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 12:15 list of 2.6-related migration issues for embedded programmers? Robert P. J. Day
2004-07-19 17:32 ` Linh Dang
2004-07-19 17:51 ` Robert P. J. Day
2004-07-19 18:14 ` Linh Dang
2004-07-19 19:06 ` Robert P. J. Day
2004-07-19 20:01 ` Robert P. J. Day
2004-07-20 1:29 ` Linh Dang
2004-07-19 20:58 ` Wolfgang Denk [this message]
2004-07-19 21:34 ` Robert P. J. Day
2004-07-19 22:04 ` Wolfgang Denk
2004-07-19 22:12 ` Robert P. J. Day
2004-07-20 1:38 ` Linh Dang
2004-07-20 7:16 ` Wolfgang Denk
2004-07-20 11:29 ` Linh Dang
2004-07-20 12:32 ` Robert P. J. Day
2004-07-20 13:19 ` Linh Dang
2004-07-20 12:40 ` Mark Chambers
2004-07-20 13:42 ` Wolfgang Denk
2004-07-20 16:07 ` Linh Dang
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=20040719205835.AA851C109F@atlas.denx.de \
--to=wd@denx.de \
--cc=linhd@nortelnetworks.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rpjday@mindspring.com \
/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.