home     open source
PHP and modifications
RPM Building
SuSE Linux RPMs
Linux Installation
Privacy Statement

Bootnet-PLIP disk for RedHat 7.0

(This information is mostly relevant to other releases as well.)

This disk is an edited bootnet disk for RedHat 7.0. I added the modules parport.o, parport_pc.o and plip.o to the original bootnet.img, as well as entries for parport_pc and plip in module-info. Since there was enough space left on the disk I did not have to remove any of the available modules. This means you can use this disk image as if it were a normal bootnet.img. There is no need for multiple bootnet disks, you can use this one in any case.

When using this disk for a PLIP connection, a few things should be kept in mind:
The parport module should be loaded before the PLIP module. Specify i/o address and irq parameters for the parallel port when inserting the parallel port module. No parameters need to be specified when inserting the PLIP module.
After inserting the parport_pc module the installer will show the "Installation method" screen a second time. This is expected behaviour.
When specifying network parameters, do not use a netmask of If you do this by accident you will have to reboot to be able to mount the installation directory succesfully. Going back and respecifying the parameters will not help you out.

When doing an NFS install with RedHat 7.0 make sure all files from the RedHat directories from both CD's are copied to the NFS mount point (cp -a RedHat for both CD's). (This behaviour has changed for 7.1 or 7.2. See the Red Hat docs for details.)

This bootnet-plip disk was inspired on the one made for RedHat 6.2 by Tilmann Bubeck. His bootnet-plip disk for RedHat 6.2 can no longer be found at http://www-ti.informatik.uni-tuebingen.de/˜bubeck/bootnet-plip-62.img.
See the PLIP-Install-HOWTO for a brief description on how to make such a disk yourself. Note that the HOWTO does not mention the addition of the parport.o and the plip.o modules to the disk. It is not necessary to compile your own modules. Make sure you use the modules contained in the kernel-BOOT rpm instead of the default modules.

d62b5c9539f8fca437df31b40297a711 bootnet-plip-62.img
215b946e86b072df3b502f4b0d2b8930 bootnet-plip-rh7.img
6218e7df5ba3e9d7d3edf8ee2d54b2d9 bootnet-plip-rh71.img