> -----Original Message----- > From: Jeremy Katz [mailto:katzj@xxxxxxxxxx] > Sent: Tuesday, June 29, 2004 2:34 PM > To: Kabir, Rezwanul > Cc: Domsch, Matt; anaconda-devel-list@xxxxxxxxxx > Subject: RE: EDD disksigs for disks other than 0x80 > > > On Fri, 2004-06-25 at 14:53 -0500, Rezwanul_Kabir@xxxxxxxx wrote: > > One of the reasons ,I used environment variables is to > access them in > > consistent manner between loader and anaconda. Otherwise I > would have to > > touch more codes to pass them to anaconda in some way, e.g. > as command > > line arguments.. > > 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..? --rez
