> Why is it necessary to prevent a user from doing this? Is it just > the presumption that that's not what they really want to do, or is > there a reason why it just can't work? It would benefit many of us > who There are a number of reasons why it might not work, especially when mixing releases as described in the example. Kernel modules come to mind without really thinking it over. > support multiple releases to be able to initiate installs with the > same boot media, and even more so if update level changes also did > not require new media. If it seems a necessary protection for most > users, what about a boot argument that would allow it for those that > care? It is already this way in every case except the one described in the original post (http install w/ stage2.img on local cdrom). The fact that a match is not enforced in this case is an oversight, the fixing of which is the goal of this thread. The current practice of verifying that installation trees match the boot media is intentional, and is not likely to change in the near future. If you want to simplify the deployment of multiple releases you should look into PXE and/or an RHN Satellite. You can even master your own cds with an expanded isolinux.cfg that allows you to select which release's boot media to use. Dave
