David Eastcott <[EMAIL PROTECTED]> writes:
[...]
> 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):
can you tell what you changed?
[...]
> 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'll try.
[...]
> 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?
what was it set to?
[...]
> 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'?
i don't quite understand the question. What do you have 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?
you can. "services" is a list of services that will be run. You can't remove
some though, only give the list of all that you want.
i use:
services => [ qw(syslog xfs network portmap mandrake_firstime) ],
cu Pixel.
