> Under RHEL-5, this process was serial and the user had to click Yes for > each unformatted DASD found, which could take a really long time if > you had thousands of DASDs. > > The idea now is that if the DASD is seen by anaconda, we want to use it > for installation. The stage 1 device initialization routines as well as > the CMS conf file provided at boot time allow the user to restrict the > range of devices we see during installation. If any of the devices we > see are unformatted, run dasdfmt before building the devicetree. I just realized that this is going to need to change when I get my storage filtering patches in. At the least, DASD.startup is going to have to respect storage.exclusiveDisks, or we could be formatting things that the user explicitly said to not use. - Chris _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
