Hi,
Once I got things set right, works nice... Sure saves me a lot of time
re-installing the same things for testing or experimenting.
The syslinux.cfg that is generated during the install does not work for me. I
had to change it to the following to get it work (append text is all on one
line):
label linux
kernel vmlinuz
append ramdisk_size=32000 initrd=network.rdz vga=788 kickstart=floppy
automatic=method:nfs,server:linux1,directory:/Cooker/cooker,
network:static,ip:192.168.5.202,netmask:255.255.255.0,
gateway:192.168.5.253,dns:192.168.5.253
Couple observations:
for 'superuser' the 'name' should be set to 'root', the 'pw' should be set to
the md5 value generated during install (it was in 7.1 and 7.2). Probably
goes for users too, but did not add a user at install time to confirm.
I re-ran the autoinstall with a value from /etc/shadow for the 'pw' and the
install ignored it. Until I actually used passwd as root to change, root
access was available to anyone with any password.
for 'mkbootdisk' you might want to force this to undef, especially for those
of us that use a floppy to kickstart things. Imagine my surprise when the
carefully crafted autoinstall disk suddenly becomes a boot disk?
Couple questions:
In the 'partitions', should the field 'hd' => 'hda' be present when you have
multiple disks? Will the installer format disks other than the ones
identified in 'partitions'?
Can the 'configureServices' be controlled from the auto_inst.cfg file? In
the expert install, I get to choose which is started, can I do it with this
file too?
best regards
Dave
