Anaconda/Introduction

From FedoraProject

< Anaconda(Difference between revisions)
Jump to: navigation, search
m (1 revision(s))
m
Line 16: Line 16:
  
 
=== Boot process (from a CD-ROM): ===
 
=== Boot process (from a CD-ROM): ===
1. PC initializion phase - BIOS, POST.
+
# PC initializion phase - BIOS, POST.
1. ISOLINUX is invoked from a bootable CD (<code>isolinux.bin</code>).
+
# ISOLINUX is invoked from a bootable CD (<code>isolinux.bin</code>).
1. ISOLINUX loads the kernel from the CD-ROM device (the <code>/isolinux</code> directory on the CD).
+
# ISOLINUX loads the kernel from the CD-ROM device (the <code>/isolinux</code> directory on the CD).
1. ISOLINUX loads the the initrd image (<code>initrd.img</code>).
+
# ISOLINUX loads the the initrd image (<code>initrd.img</code>).
1. The kernel then takes over, and attempts to decompresses the initrd.img into memory (<code>/dev/ram0</code>), and mounts this new filesystem as root (<code>/</code>).
+
# The kernel then takes over, and attempts to decompresses the initrd.img into memory (<code>/dev/ram0</code>), and mounts this new filesystem as root (<code>/</code>).
1. The kernel attempts to run <code>/linuxrc</code> in the newly created root filesystem.
+
# The kernel attempts to run <code>/linuxrc</code> in the newly created root filesystem.
1. The linuxrc program then mounts the CD-ROM (by trial and error), and decompresses a 'true' root filesystem from CD-ROM to <code>/dev/ram1</code>.
+
# The linuxrc program then mounts the CD-ROM (by trial and error), and decompresses a 'true' root filesystem from CD-ROM to <code>/dev/ram1</code>.
1. The kernel takes over and mounts the newly configured root filesystem. The new filesystem is mounted and a softlink for the CD-ROM is added to the <code>/dev</code> directory, so that the system has access to the CD-ROM.
+
# The kernel takes over and mounts the newly configured root filesystem. The new filesystem is mounted and a softlink for the CD-ROM is added to the <code>/dev</code> directory, so that the system has access to the CD-ROM.
1. The kernel runs the <code>/sbin/loader</code> binary which then invokes the anaconda installer.
+
# The kernel runs the <code>/sbin/loader</code> binary which then invokes the anaconda installer.
  
 
=== Anaconda process: ===
 
=== Anaconda process: ===

Revision as of 17:40, 4 June 2014

Contents

I. Introduction to Anaconda

1. Anaconda - the Fedora Core installation program

Anaconda is the installation program for Fedora Core and Red Hat Linux distributions. During installation, the system's hardware is identified and configured, and the appropriate file systems for the system's architecture are created. It then allows for the installation of various software packages. Anaconda can also be used to upgrade existing Fedora Core or Red Hat installations.

Anaconda is able to run in text mode for older machines or graphical mode for most modern machines. It also has the ability to be run in a fully automated mode, through the use of a _kickstart_ file, allowing for the installation to be scripted for unattended operation. Anaconda can also be used to install systems over a network, through any of the common networking protocols (eg. ftp, http, nfs). This makes the process of deploying hundreds, or even thousands of systems very quick, efficient and easy to manage.

The majority of Anaconda is written in Python, with a small initial loader written in C. The code is distributed under the GPL. The graphical frontend is written with pyGtk. Using a scripting language such as Python for the majority of the code allows for a simple distribution of updates and rapid development of new features.

2. The Anaconda installation procedure (from a bootable CD)

Booting from a CD-ROM requires a different boot processes compared to booting from a hard drive. The linux kernel doesn’t really know how to boot from a CD-ROM. When booting from a CD-ROM, an initrd (initial ramdisk) is used as the root filesystem. The initrd is loaded by the _boot loader_ - not the kernel. This makes it possible to boot from any device accessible to the bootloader. ISOLINUX is the boot loader commonly used for booting from a CD-ROM.

Boot process (from a CD-ROM):

  1. PC initializion phase - BIOS, POST.
  2. ISOLINUX is invoked from a bootable CD (isolinux.bin).
  3. ISOLINUX loads the kernel from the CD-ROM device (the /isolinux directory on the CD).
  4. ISOLINUX loads the the initrd image (initrd.img).
  5. The kernel then takes over, and attempts to decompresses the initrd.img into memory (/dev/ram0), and mounts this new filesystem as root (/).
  6. The kernel attempts to run /linuxrc in the newly created root filesystem.
  7. The linuxrc program then mounts the CD-ROM (by trial and error), and decompresses a 'true' root filesystem from CD-ROM to /dev/ram1.
  8. The kernel takes over and mounts the newly configured root filesystem. The new filesystem is mounted and a softlink for the CD-ROM is added to the /dev directory, so that the system has access to the CD-ROM.
  9. The kernel runs the /sbin/loader binary which then invokes the anaconda installer.

Anaconda process:

1. Probe for hardware devices (eg. CD/DVD drives, hard-drives, etc) 1. Prompt to test CD for errors screen 1. Probe for video card 1. Probe for monitor 1. Probe for mouse 1. Welcome to Fedora Core introduction screen 1. Language Selection for the installation screen 1. Keyboard Configuration screen 1. Mouse Configuration screen 1. Monitor Configuration screen 1. Search for existing Fedora Core/Red Hat Linux installations 1. Upgrade existing installation or perform fresh Fedora Core installation screen 1. Installation Type screen [Personal Desktop, Workstation, Server, Custom] 1. Disk Partitioning Setup screen [Automatically Partion, Manually Partition with Disk Druid] 1. Boot Loader Selection screen 1. Network Configuration screen 1. Firewall Configuration screen 1. Default Language Selection for the system and install of additional languages screen 1. Time Zone Selection screen 1. Root Password Selection screen 1. Package Selection screen [Default Packages, Custom Package Selection] 1. Formatting of configured filesystems 1. Transfer of install image to hard drive 1. Installation of Packages 1. Reboot screen. Congratulations, the installation is complete