> On Saturday 15 December 2001 10:14, Mike Galbraith wrote:
> > On Thu, 13 Dec 2001, vda wrote:
> > > On Thursday 13 December 2001 06:19, Alexander Viro wrote:
> > > > On Thu, 13 Dec 2001, vda wrote:
> > > > > BTW, don't go for 2.4x, x>10. initrd is broken there and is still
> > > > > unfixed.
> > > >
> > > > Bullshit.
> > >
> > > I have a slackware initrd (minix) which is booting fine with 2.4.10
> > > but fails to boot with 2.4.12 and later (same .config, same bootloader,
> > > same hardware, same AC voltage in the wall outlet, time of day differs by
> > > 1 minute), so it might be true :-)
> >
> > Hmm.. works here with 2.5.1-pre8.
> >
> > -Mike
> > ...
> > RAMDISK driver initialized: 16 RAM disks of 12288K size 1024 blocksize
> > ...
> > RAMDISK: Compressed image found at block 0
> > Freeing initrd memory: 5161k freed
> > MINIX-fs: mounting unchecked file system, running fsck is recommended.
> > VFS: Mounted root (minix filesystem).
> > Freeing unused kernel memory: 236k freed
>
> Have you tried it with minix initrd from
>
> http://port.imtp.ilyichevsk.odessa.ua/linux/vda/minix.gz
No, I converted my 'fire department' initrd to minix and booted that.
-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/