On Sunday 15 April 2001 10:43, you wrote:
> 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?
it was:
label linux
kernel vmlinuz
append 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,
ramdisk_size=32000 initrd=network.rdz vga=788
Note comma after dns ip. I don't know if this was real problem or not? I
can't remember if I tried with out it or not.
>
> [...]
>
> > 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?
>
'mkbootdisk' => 'fd0',
> [...]
>
> > 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'?
I have two disks, hda and hdc. The first disk is partitioned as follows:
'partitions' => [
{
'mntpoint' => '/boot',
'size' => 80292,
'type' => 387
},
{
'mntpoint' => 'swap',
'size' => 497952,
'type' => 130
},
{
'mntpoint' => '/',
'size' => 15502662,
'type' => 387
}
],
and is used to hold all normal files. The second (hdc) is an archive disk
which gets mounted in the root directory (/mass) as follows:
'manualFstab' => [
{
'device' => '/dev/hdc1',
'mntpoint' => '/mass',
'options' => 'default',
'type' => 'reiserfs'
}
],
When I do an autoinstall I do not want the installer to format hdc at all.
The question is: given the above declartions and this one, will it only
format hda?
'partitioning' => {
'clearall' => 1,
'eraseBadPartitions' => 0,
'auto_allocate' => 1
},
regards
Dave
