Auto Install for Mandrake Linux | ||
---|---|---|
Prev | Next |
As with all things, the Automated Installation facility has its problems. This section will attempt to identify them and illustrate, if possible, work a rounds for them.
These problems and issues are common to all releases of the current distributions' Version.
1. |
Missing RAID and LVM definitions. |
|
Unfortunately when the auto_inst.cfg file is generated, the RAID and LVM declarations are NOT. You will have to manually add them your self. |
2. |
Enabling passno, freq and toFormatCheck with partitions. |
|
To enable these features requires that you make a modification to the Stage2 perl scripts as follows: a) Uncompress the file using: gunzip Mandrake/mdkinst/usr/bin/perl-install/fsedit.pm.gz b) Adjust the lines (about 481) from: sub suggest_part {
...
foreach ('options', 'lv_name', 'encrypt_key') { $part->{$_} = $best->{$_} if $best->{$_}; } 1; }
|
|
to: sub suggest_part {
...
foreach ('options', 'lv_name', 'encrypt_key', 'passno', 'freq', 'toFormatCheck') { $part->{$_} = $best->{$_} if exists $best->{$_}; } 1; }
c) Compress the file using: gzip Mandrake/mdkinst/usr/bin/perl-install/fsedit.pm.gz
|
These ones are specific to the Community Release.
1. |
Usability Problems with replay*.img files. |
|
CD-ROM Installs: the replay_install.img's file syslinux.cfg has the automatic=method:disk on the append line twice, usable but not correct. Also, you can only install from the first CD. GRUB: the replay_install.img file is usable, although it has an empty syslinux.cfg file that is not used. Network: the replay_install.img file is usable, but the syslinux.cfg file it contains does not have any of the network information that it should. The replay_install_drivers.img file is usable, but it has an empty syslinux.cfg file. You can use these images, but you might want to correct them, before using, to ensure nothing odd occurs. Or you can use the procedures in Scratch Built Auto Install Diskette to to create your own.
|
|
You may also find that the floppy disk(s) that you generated during the manual install exhibit similar problems. |
|
|
|
|
These ones are specific to the Final Release.
|
|
|
|
These ones are here because cooker is where it all starts. Unfortunately, these issues are only valid at the time this document is released, and they may already be resolved by the time you read this.
1. |
Services missing from the auto_inst.cfg file. (Community Release) |
|
To get the 'services' => ... included in the generated configuration file (on floppy, in the images, or /root/drakx/auto_inst.cfg.pl), you have to click on the Configure button associated with Configure Services on the Summary screen during the initial GUI installation. Alternately, you can look in the directory /etc/rc.d/rc5.d and create the entry by examining the files listed with “S??<name of service>” where <name of service> also appears in the /etc/rc.d/init.d directory. |
2. |
Generated Replay / Automated Floppy have error. (Cooker after the Community Release) |
|
If you are using the
Grub Hard Disk method to auto install, you will find that the
generated floppy and the It contains: kernel /cooker/isolinux/alt0/vmlinuz ramdisk_size=128000 root=/dev/ram3 acpi=ht vga=788 automatic=method:disk kickstart=floppy automatic=met:disk,dis:hde,par:hde7,dir:/cooker,
and should be: kernel /cooker/isolinux/alt0/vmlinuz ramdisk_size=128000 root=/dev/ram3 acpi=ht vga=788 kickstart=floppy automatic=met:disk,dis:hde,par:hde7,dir:/cooker,
|
Prev | Home | Next |
Network and Connection Examples | GNU Free Documentation License |