| To: | linux-mips@oss.sgi.com |
|---|---|
| Subject: | Re: emebedded ramdisk vs initrd |
| From: | Guido Guenther <agx@sigxcpu.org> |
| Date: | Fri, 23 Nov 2001 14:22:10 +0100 |
| In-reply-to: | <20011123135518.A12210@gandalf.physik.uni-konstanz.de>; from agx@sigxcpu.org on Fri, Nov 23, 2001 at 01:55:18PM +0100 |
| Mail-followup-to: | linux-mips@oss.sgi.com |
| References: | <20011123135518.A12210@gandalf.physik.uni-konstanz.de> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
On Fri, Nov 23, 2001 at 01:55:18PM +0100, Guido Guenther wrote: > Trying to link in arch/mips/ramdisk/ramdisk.o whenever > CONFIG_BLK_DEV_INITRD is defined is a bad idea, since there are other ...and therefore makes the compilation fail, I should add. -- Guido |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | emebedded ramdisk vs initrd, Guido Guenther |
|---|---|
| Next by Date: | Re: FPU test on RedHat7.1, Carsten Langgaard |
| Previous by Thread: | emebedded ramdisk vs initrd, Guido Guenther |
| Next by Thread: | Re: emebedded ramdisk vs initrd, Pete Popov |
| Indexes: | [Date] [Thread] [Top] [All Lists] |