From mboxrd@z Thu Jan 1 00:00:00 1970 To: "Wolfgang Denk" Cc: "Embedded Linux PPC list" Subject: Re: list of 2.6-related migration issues for embedded programmers? References: <20040720134221.93224C109F@atlas.denx.de> From: "Linh Dang" Date: Tue, 20 Jul 2004 12:07:28 -0400 In-Reply-To: <20040720134221.93224C109F@atlas.denx.de> (Wolfgang Denk's message of "Tue, 20 Jul 2004 09:42:16 -0400") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linuxppc-embedded@lists.linuxppc.org List-Id: On 20 Jul 2004, wd@denx.de wrote: > In message 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. You have a point here, I guess with initramfs you have to: - use devfs (which was deprecated in 2.6) - use udev - grok-sysfs-yourself (which is pretty easy) > > And how can I tell a Linux kernel where to find the initramfs data > when they are not linked together? Well, the same way as with the good old-initrd. the initramfs root-fs IS an INITRD in compressed-cpio format (instead of fs format such as ext2). me think I'm still missing something about initrd. Regards -- L.D. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/