On Sun, Dec 05, 2004 at 11:35:42PM -0700, Greg Morgan wrote: > I'd like to see a way of completely decoupling the hard disk imaging in > anaconda. Agreed. > > 2. it still asks for langauge, keyboard settings instead of > > just using the current ones, like any regular X app > > > I would think this is ok. Anaconda still has to understand it's > operating environment. It can do so automatically. Imagine if every program, when started, would ask for the lang and keyboard. That would be silly, the user session already has a default language (BTW, hwo do you get to that, is it just $LANG?). > > 4. It still tries to mess with my disks: > >* moving (1) to step partitionobjinit > >* pv is /dev/hda2 in vg VolGroup00, size is 80866181120 > >* vg VolGroup00, size is 80866181120 > >* lv is VolGroup00/LogVol00, size of 79255568384 > >* lv is VolGroup00/LogVol01, size of 1577058304 > >* running vgchange failed: 1280. disabling lvm > > These may be geared to the Stateless Linux push. It may be, and it's all good, but it should be skipped altogether in --rootpath mode. > Again I'd rather see the disk issue solved. I'd rather put up with this > because it completely separates anaconda from code variations for a > "running system" verses "anaconda for a real install". I see no reason to put up with it, really. Anaconda has an internal variable what holds this info, that can be initialized from a ks file. It should be trivial to simply initialize it from the current running environment (but again, how do we ge to it?). -- Dimi.