All works below as you describe - if you boot the client/build system from 
the local cdrom/PXE. The problem that I have regularly encountered since 2.1
involves using the bootnet.img/boot.img to create a boot floopy, 
and modifying syslinux.cfg for complete hands=off. I had successfully used
this method for both 1.5, Tawie, and 2.0. Since then, I always have
the problem as described below.

For further clarification, the cdrom message splash for interactive install
will appear if the ks.cfg file isn't found on the local floppy. That's not
what is happeneing. The system boots from floppy, loads the kernel, starts
the ks.cfg and goes interactive at the keyboard directive. No errors 
reported on any screen that I can see which leads me to believe that the
problem lies within the floppy image itself. This problem occurs with the
anaconda generated ks.cfg - without my edits. 


Sue Bauer-Lee wrote:
> Please - does someone have a working kickstart (non PXE) for 2.2??
> I've tried to get a working ks for the 02172005 and the most recent iso and
> both failed for boot nfs and cdrom in the same place. I used a ks.cfg from
> an interactive install and they always halt at te keyboard selection
> screen. Purely informaitonal - 2 different hardware systems. I've checked
> the other virtual consoles - no reported errors.

Typically, if the interactive install starts, your ks.cfg was not found. 
  How did you boot the installer?  If your ks.cfg (exactly that file 
name) is on the first floppy drive, then start the install at the boot 
prompt with:

boot:  linux ks=floppy

I place kickstart configs on a web server and use something similar to:

boot:  linux ks=http://1.2.3.4/trustix/cfg/2.2.cfg

Floppy, PXE, nfs, cdrom - all just different ways of bootstrapping the 
installer - pointing anaconda to your kickstart configuration after the 
kernel/initrd are loaded all works the same  ;)

Kind Regards,
Michael Shuler
_______________________________________________
tsl-discuss mailing list
[email protected]
http://lists.trustix.org/mailman/listinfo/tsl-discuss

Reply via email to