Re: requiring .discinfo in exploded remote trees

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I may have initially misunderstood your response.

> instance.  Yes, we can use tftp/dhcp, but the .discinfo stops  the mixing of 
> kernels with the base distro.

That's only if you insist on including a stage2.img on the cdrom, which
won't work with multiple kernel/initrd pairs anyhow. We don't need to
check for the .discinfo on the boot cd unless you're doing the http with
local stage2. 

So, you cannot have a single boot cd that can boot multiple releases and
do http installs for any/all of the releases using the local stage2.img.
You can, however, have a single cd that can boot multiple kernel/initrd
pairs and use it to do installations of various releases over the
network, as long as your boot media matches your target tree.

HTH


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux