Mailinglist Archive: opensuse-autoinstall (99 mails)
| < Previous | Next > |
Re: [opensuse-autoinstall] Overview of autoyast process
- From: Uwe Gansert <ug@xxxxxxx>
- Date: Fri, 4 May 2007 17:13:23 +0200
- Message-id: <200705041713.23993.ug@xxxxxxx>
On Friday 04 May 2007 13:06, Simon Crute wrote:
> [* rules file is downloaded and processed
> * one of more profile fragments are downloaded and merged]
> OR
> [* the full profile is downloaded.]
>
> * any pre scripts are ran
> * Ask commands are ran and user interaction runs.
> * installation confirmation screen is shown.
> * 1st part of the installation starts
> * chroot=false chroot scripts are ran.
> * installer chroots into the new system.
> * chroot=true chroot scripts run.
> * yast configures the system
* reboot
* installation network raises up again (in case of an installation via
network)
* required but missing RPMs are installed
* network_needed=true scripts run
* second stage config from the XML file is done (services, network and
stuff)
* installation network is down (in case of an installation via network)
* network_needed=false scripts run
* SuSEconfig
> At this point, I'm confused. When are post install scripts with
> network_needed=true and network_needed=false ran, what is the difference
> in the environments they run it ?
network_needed=true scripts run more early. If you do network installations,
then the installation network is still up and running when
network_needed=true post-scripts run. With "false" the installation network
is down, while the configured network is still not up and running.
Well, that was true for SLES9. Since 10.2 you can raise the network
via "start_immediately" in the network section so that even
network_needed=false scripts can have a running network.
> * system reboots
no, there is no reboot at that stage. The reboot happens short after
chrooted=true scripts
> * init scripts run
--
ciao, Uwe Gansert
Uwe Gansert, Server Technologies Team
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Business: http://www.suse.de/~ug
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx
> [* rules file is downloaded and processed
> * one of more profile fragments are downloaded and merged]
> OR
> [* the full profile is downloaded.]
>
> * any pre scripts are ran
> * Ask commands are ran and user interaction runs.
> * installation confirmation screen is shown.
> * 1st part of the installation starts
> * chroot=false chroot scripts are ran.
> * installer chroots into the new system.
> * chroot=true chroot scripts run.
> * yast configures the system
* reboot
* installation network raises up again (in case of an installation via
network)
* required but missing RPMs are installed
* network_needed=true scripts run
* second stage config from the XML file is done (services, network and
stuff)
* installation network is down (in case of an installation via network)
* network_needed=false scripts run
* SuSEconfig
> At this point, I'm confused. When are post install scripts with
> network_needed=true and network_needed=false ran, what is the difference
> in the environments they run it ?
network_needed=true scripts run more early. If you do network installations,
then the installation network is still up and running when
network_needed=true post-scripts run. With "false" the installation network
is down, while the configured network is still not up and running.
Well, that was true for SLES9. Since 10.2 you can raise the network
via "start_immediately" in the network section so that even
network_needed=false scripts can have a running network.
> * system reboots
no, there is no reboot at that stage. The reboot happens short after
chrooted=true scripts
> * init scripts run
--
ciao, Uwe Gansert
Uwe Gansert, Server Technologies Team
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Business: http://www.suse.de/~ug
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx
| < Previous | Next > |