Re: Installation methods supported by bootdisk.img ...
Bogdan Costescu <bogdan.costescu-hEciA7+sKtudPOQpRHQ53DeJuz7u0hKX@public.gmane.org>
| Newsgroups | gmane.linux.tao.general |
|---|---|
| Message-ID | <Pine.LNX.4.44.0411021140220.32526-100000@kenzo.iwr.uni-heidelberg.de> |
On Mon, 1 Nov 2004, Richard Walsh wrote: > created the boot disk with dd if=./bootdisk.img of=/dev/fd0 bs=1440k, > etc. This image file is advertised to work "for all installation types" If you refer to the README file from the dist/images/ directory, you have stopped reading too soon. Just after that line it also says: ------- A secondary driver disk will be required for most install types other than IDE CDROM and HD based installs. The following driver disks are available: drvblock.img - Supplemental Block Device Drivers drvnet.img - Supplemental Network Drivers pcmciadd.img - PCMCIA Driver Diskette ------- Due to the increasing size of the kernels and modules, they no longer fit on one floppy, therefore the split. One solution is to boot from a CD/DVD which has enough space for the kernel plus any modules. > which should request a fully dhcp driven installation in which my > server supplies the IP address, the location of the kickstart file, > etc., and just runs. You might want to try a PXE installation instead. In dist/images/pxeboot you can find the kernel and initrd image that need to be served by the tftp server. -- Bogdan Costescu IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868 E-mail: Bogdan.Costescu-PDzUyZpvkMP/PDbm/[email protected]