Skip to content

Latest commit

 

History

History

doc

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
features/examples
features/examples
 
 
inst_finish
inst_finish
 
 
inst_images
inst_images
 
 
screenshots
screenshots
 
 
startup
startup
 
 
README.boot
README.boot
 
 
README.doit
README.doit
 
 
README.installer
README.installer
 
 
SELF_UPDATE.md
SELF_UPDATE.md
 
 
UPGRADE.md
UPGRADE.md
 
 
control-file.md
control-file.md
 
 
features.md
features.md
 
 
inst-images.md
inst-images.md
 
 
installation_clients.md
installation_clients.md
 
 
installation_overview.md
installation_overview.md
 
 
installer_extension.md
installer_extension.md
 
 
memory-profile-valgrind-massif.md
memory-profile-valgrind-massif.md
 
 
memsample.md
memsample.md
 
 
memsample.png
memsample.png
 
 
proposal_api.md
proposal_api.md
 
 
release_notes.md
release_notes.md
 
 
snapshots.md
snapshots.md
 
 
system-role-handlers.md
system-role-handlers.md
 
 
url.md
url.md
 
 
vendor.html
vendor.html
 
 
yupdate.md
yupdate.md
 
 

README.boot

In the initial installation system, yast2 perform the following
actions:

- Prepare the target disk (fdisk, mke2fs, ...)
- Install the packages from the first CD
- if the source is remountable, install the other packages

Now the root filesystem is remounted, the new target is
used as root. If yast2 want's to be run again, it has created
the file /var/lib/YaST2/runme_at_boot. YaST2 is then started
as last action of /etc/init.d/boot.