Re: anaconda loader

Is this a snake loader or something?


<ChasW> wrote in message news:0na0p2pqs3lrjof8f9mla3h25v9u29ignk@xxxxxxxxxx
On Mon, 25 Dec 2006 14:41:06 -0500, ChasW <> wrote:

How can I go about using floppy driver disk images instead of actual
floppies for use in a redhat rescue environment?

I cannot seem to get the loader to recognize these images.

Here is what I have done so far:

I have created a bootable dvd-rom which successfully can load the
redhat 9 rescue environment.

I have managed to get the loader to see a kickstart file by placing
the ks.cfg inside the initrd image.

If I type linux rescue dd at the boot prompt, the loader boots and
loads as expected except that I need the floppy driver disk images to
be seen by anaconda and nothing I have tried has made this happen.

I get the prompt for a driver disk, but the only sources it offers are
/dev/fd0 and /dev/hdc which is the dvd-rom drive, but even with the
image there, it doesnt recognize it.

I am wondering if the redhat9 version loader is just not capable of
doing what I want.

Options please?
Technical advice is greatly welcome.

What would be really helpful are tested examples of using the
driverdisk option for the kickstart file with a source being a driver
disk image that resides on the same bootable dvd-rom that booted the
system.

Is it possible to set file sources that are not network sources, but
rather locally mounted paths? if so, please give an example!

Greetings,
Chas

I just wanted to add that the error message I get from kickstart is
"unable to mount driver disk f00" , yet if I go to the rescue shell
prompt I can manually mount the driver disk image and navigate it with
no problems.

So I am suspecting that this may be a syntax error with my usage of
the driverdisk option in the kickstart file.
.