hi there
If I understand correctly from an archived post - I should be able to
test my changes to anaconda source files without needing to go through
the entire anaconda rebuild process.
I have created a Fedora tree suitable for NFS installs under
/data/Fedora-Custom/i386/
I have created a directory in this tree - /data/Fedora-Custom/i386/RHupdates
I put any anaconda source files that I have modified into this directory
What I have actually done is that I have previously modified the
anaconda source (actually just the textw/welcome_text.py) and rebuilt it
and run buildinstall and all. My changes cause anaconda to fail due to
my sillyness.
What I want to do now is to use the "original" welcome_text.py as an
"update" file and add it to the RHupdates directory. I'm guessing that
this will get me back to the "original" anaconda setup and all should go
well ... (I know I will need to re-rebuild the anaconda eventually ...)
What is actually happening is that anaconda is still failing at the
welcome screen with the same error as before - so I assume that the
"original" welcome_text.py is not being picked up from the RHupdates
directory ...
here is my boot process:
- I boot with the boot.iso that was re-created after I ran my original
buildinstall (ie modified anaconda)
- I type 'linux updates text' at the boot prompt
- I choose lang, keyboard, and NFS type install
- I setup networking with dhcp
- I give the ip and install directory (/data/Fedora-Custom/i386)
- It prompts me to choose which medium to grab updates from (fd0 or hda)
- I choose hda (fd0 fails btw), confirm, and the install continues ...
but then fails with the same error ...
Any ideas on where I might have gone wrong?
Also - do i need to maintain the anaconda source structure in RHupdates?
(ie. /data/Fedora-Custom/i386/RHupdates/textw/welcome_text.py)
thanks
pantz
--
Before you criticize someone, walk a mile in their shoes, that way when you do criticize them, you're a mile away and you have their shoes!
