This can be done only with an ext2 filesystem type of updates.img. You can also put an updates.img on a block device (either a floppy or a USB key). If you are making your own updates.img, just upload it to a web server you have access to and pass the location as above. All anaconda config options are described elsewhere. ksdevice= can be used to specify a different network device, and the ip= option (along with others for gateway, nameserver, and so forth) can be used for static configuration. If you require other networking configuration, you will need to use various options. It will then attempt to configure this link using DHCP. If you have multiple network interfaces, anaconda will first prompt you to select one (unless you have used the ksdevice= boot parameter). If you're booting via an ISO, to edit the kernel command line, you will need to use the e key in GRUB. To use this method, you will need to edit your kernel command line to include the inst.updates key, like this: This does not require you to modify your installation tree at all. This is how almost all updates images you'll see in bug reports and mailing lists are distributed. The easiest and most popular way to use an updates.img is via the network. There are a number of sources for the updates. The updates.img can be used in a few different ways. These updates are generally distributed as a disk image file (referred to as updates.img from here on out). 1.4.2.1 How to Find Anaconda Version for an Installation ImageĪnaconda has the capability to incorporate updates at runtime to fix any bugs or issues with the installer.1.4.2 Including Updates for an Older Installation Image.1.3 How to Examine an Anaconda Updates Image.1.2 How to Create an Anaconda Updates Image.
0 kommentar(er)
