| To: | Kumba <kumba@gentoo.org> |
|---|---|
| Subject: | Re: [PATCH]: Rewrite of arch/mips/ramdisk/ |
| From: | Christoph Hellwig <hch@lst.de> |
| Date: | Mon, 15 Nov 2004 19:05:07 +0100 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <4197B286.4060503@gentoo.org> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <4196FE7C.9040309@gentoo.org> <20041114085202.GA30480@lst.de> <419794FB.6020104@gentoo.org> <4197B286.4060503@gentoo.org> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.3.28i |
> It looks like this option, which afaict, doesn't seem to have an entry > anywhere in Kconfig, specifies a list of files for inclusion in a cpio > archive that's bundled into the kernel. My question then is, can a > lookback-mountable filesystem image be included in this list, and the > kernel, given /dev/ram0 as root, know to mount and use the loopback image? You could include a loop-back mountable filesystem image. But that's not even nessecary. The kernel will call /init of the files in the initramfs, and you could just store everything you'd store in the loopback filesystem directly in the initramfs image. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH]: Rewrite of arch/mips/ramdisk/, Ralf Baechle |
|---|---|
| Next by Date: | On Sat, 13 Nov 2004, macrohat wrote..., peter fuerst |
| Previous by Thread: | Re: [PATCH]: Rewrite of arch/mips/ramdisk/, Kumba |
| Next by Thread: | Re: [PATCH]: Rewrite of arch/mips/ramdisk/, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |