Re: Problem installing Slink on UDB/Multia
-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 13 May 1999, Nikita Schmidt wrote:
> On Tuesday, 11 May, Dang Hoang Nguyen wrote:
> > Hello,
> > I'm setting up a Multia box for home use. However, when I try to boot up
> > Slink with the rescue disk I get the following error. This is after I've
> > gotten Milo to load.
> > MILO>> boot fd0:linux root=/dev/fd0 load_ramdisk=1 prompt_ramdisk=1
> > VFS: Disk change detected on device 2/0
> > [MS-DOS FS Rel. 12,FAT]
> > [me=0xf0,cs=1,#f=2,fs=1,fl=9,ds=19,de=112,data=26,se=2880,ts=0,ls=512]
> > Transaction block size = 512
> > Not enough memory
> > Hit a key to reboot
> Get a newer MILO from ftp://genie.ucd.ie/pub/alpha/milo/milo-latest/Noname.
> It was unfortunately too late to make its way into Slink.
Or better yet, use aboot. With the ARC/Milo scheme I had problems almost
every time I booted. And it's slow. SRM and aboot is much faster, and it's
the easiest boot loader to reconfigure I've seen for Linux. To change
kernels, you can just copy the file and reboot. I love it!
There are just a couple of catches:
1. you have to partition your disk BSD-style (use fdisk, not cfdisk)
2. aboot doesn't seem to like compressed kernels (easy fix for that)
3. it's not the best documented setup I've seen... (see the SRM-HOWTO)
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----