On Wed, 2004-06-30 at 10:01 -0500, Rezwanul_Kabir@xxxxxxxx wrote: > > There shouldn't be a need to pass information around, though. Whether > > or not edd is being used should be pretty obvious based on whether or > > not they ask for something in terms of BIOS disks. > > > I must be missing something here...I understood the part(described in > your next email) that you want to populate a struct of some sort ( a > hash table perhaps) with the mapping between BIOS and real device names. > But as I understood the loader/anaconda code, you actually interprete > some of the kickstart directives (e.g. harddrive --partition=<part#> > --dir=/) in loader and some (e.g. part / --size=<size> --ondisk=<disk> ) > in anacoda. If I'm correct, then you'll need to know the BIOS disk > mappings both in loader and in anaconda. How do you propose to propagate > this information from loader to anaconda..? You just reprobe it. As long as the functionality is in libisys, then the code gets shared trivially and there's no need to pass around things that can be probed. Jeremy
