All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Linh Dang" <linhd@nortelnetworks.com>
Cc: "Embedded Linux PPC list" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: list of 2.6-related migration issues for embedded programmers?
Date: Tue, 20 Jul 2004 15:42:16 +0200	[thread overview]
Message-ID: <20040720134221.93224C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 20 Jul 2004 07:29:55 EDT." <wn5vfgi9arw.fsf@linhd-2.ca.nortel.com>


In message <wn5vfgi9arw.fsf@linhd-2.ca.nortel.com> you wrote:
>
> But you don't have to. What ever you can do with the good-old initrd
> image you can do with the new initramfs (really cpio archive)
> image. The main difference is the creation: genext2fs vs cpio.

How do I populate a  initramfs  with  custom  device  nodes?  Without
having root permission, I mean.

And how can I tell a Linux kernel where to find  the  initramfs  data
when they are not linked together?

> I just happen to use zImage.initrd (where ramdisk.image.gz is a cpio
> archive) in our project because it's the most appropriate for our
> situation.

That's OK. Other projects may have different requirements, though.

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
You cannot propel yourself forward by patting yourself on the back.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2004-07-20 13:42 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
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 [this message]
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=20040720134221.93224C109F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=linhd@nortelnetworks.com \
    --cc=linuxppc-embedded@lists.linuxppc.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.