[syslinux] Syslinux with two-disk set (boot+root )

Mike Jones mjj9 at email.byu.edu
Thu Aug 22 21:53:46 PDT 2002


Hmm, you're right.  It's not needed.

Aside from that I still don't understand what you meant here:

> prompt_ramdisk is a kernel option, not a SYSLINUX option.  The kernel
> should support it if suitable configured.

You seemed to imply that if my kernel was configured correctly, I could pass
the ramdisk options to the kernel via syslinux.  Did I misunderstand?

> -----Original Message-----
> From: H. Peter Anvin [mailto:hpa at zytor.com]
> Sent: Thursday, August 22, 2002 8:09 PM
> To: Mike Jones
> Cc: syslinux at zytor.com
> Subject: Re: [syslinux] Syslinux with two-disk set (boot+root )
>
>
> Mike Jones wrote:
> >>You realize that the prompt_ramdisk isn't an initrd, right?  You're
> >>definitely not using the same options, since the initrd= command isn't a
> >>lilo option at all, and you're evidently specifying it.
> >
> >
> > I am, in fact, using initrd in my lilo.conf.  My append line
> for lilo.conf
> > looks like this:
> >
> > append = "ramdisk_size=16384 load_ramdisk=1 prompt_ramdisk=1
> ramdisk_start=0
> > initrd=/mnt/floppy/initrd.gz devfs=mount label=linux"
> >
> > Being somewhat of a Linux novice, I got the above from a how-to on the
> > internet.  I tried a similar line in syslinux.cfg and it
> failed.  Are you
> > saying that it should have worked?
> >
>
> I'm saying that the initrd= in the LILO command line doesn't do jack.
>
> 	-hpa
>
>




More information about the Syslinux mailing list