On 11/08/2012 08:36 PM, David Lehman wrote:
On Thu, 2012-11-08 at 20:07 +0000, "Jóhann B. Guðmundsson" wrote:
Can some of you guys enlighten me and explain to me what causes the
dependency in the installer environment with the packages/release it's
about to install and why these have to be tied together ( as in the
installer cannot exist and be run in an isolated environment on it's own
specific bits untied to the release or package set it's about to install )?
Do an install and then look through /tmp/program.log. We run all of
those utilities as part of the installation process. There are a lot of
them, and some change every single release.
But not those that you would have as a part of the "installer OS"
Many of these commands are
run inside the just-installed root, which means the utilities have to be
there (in the installed package set) and they have to behave in the way
we expect them to.
Somehow I doubt that the command used by those utility change that often
so is it really that frequent?
Can you give me any examples when that has happened.
There are also other changes, like how to set the default runlevel pre-
and post-systemd.
Afaik the method to do that is unchanged since the get go ( setting the
default runlevel in systemd ).
Anyway what steps remain to isolate the installer OS from the "installed
OS " so we can have better contingency plan in the future for the
installer ?
JBG
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
