Mkinitcpio: Unterschied zwischen den Versionen

Aus wiki.archlinux.de
← Zum vorherigen Versionsunterschied
erste Teil-Übersetzung
Tuxnix (Diskussion | Beiträge)
1.687 Bearbeitungen
Hook micrcode ergänzt
 
(66 dazwischenliegende Versionen von 17 Benutzern werden nicht angezeigt)
Zeile 1: Zeile 1:
= Einleitung =
{{SEITENTITEL:mkinitcpio}}{{righttoc}}


'''mkinitcpio''' ist die nächste Generation der '''initramfs'''-Erstellung. Es hat viele Vorteile gegenüber der alten '''mkinitrd''' und '''mkinitramfs''' Scripte.
'''mkinitcpio''' ist die nächste Generation der '''initramfs'''-Erstellung. Es hat viele Vorteile gegenüber den alten Skripten '''mkinitrd''' und '''mkinitramfs'''.


* Es nutzt '''klibc''' und '''kinit''' der Linux-Entwicklern welches eine kleine und leichtgewichtige Basis bereitstellt, um Programme sehr früh im ''userspace'' laufen zu lassen.  
* Es nutzt '''klibc''' und '''kinit''' der Linux-Entwickler, welches eine kleine und leichtgewichtige Basis bereitstellt, um Programme sehr früh im ''userspace'' laufen zu lassen.  
* Es kann mittels '''udev''' die Hardware zur Laufzeit erkennen, so daß nur die wirklich nötigen Module geladen werden.
* Es kann mittels '''udev''' die Hardware zur Laufzeit erkennen, so dass nur die wirklich nötigen Module geladen werden.
* Die hook-basierenden init Scripte sind leicht erweiterbar und können auch durch externe Pakete genutzt werden.
* Die hook-basierenden init-Scripte sind leicht erweiterbar und können auch durch externe Pakete genutzt werden.
* Es unterstützt bereits '''lvm2''', '''dm-crypt''' (legacy und luks volumes), '''raid''', '''swsusp''' und '''suspend2''' Fortsetzen und Starten vob '''usb''' Datenträgern.
* Es unterstützt bereits '''lvm2''', '''dm-crypt''' (legacy und luks volumes), '''raid''', '''swsusp''' und '''suspend2''' Fortsetzen und Starten von '''usb''' Datenträgern.
* Viele Funktionen können von der Kernel-Kommandozeile konfiguriert werden ohne das Image neu erstellen zu müssen.
* Viele Funktionen können von der Kernel-Kommandozeile konfiguriert werden ohne das Image neu erstellen zu müssen.
* Mit dem '''mkinitcpio''' Skript ist es möglich, das Image in den Kernel zu integrieren.
* Mit dem '''mkinitcpio'''-Skript ist es möglich, das Image in den Kernel zu integrieren.


'''mkinitcpio''' wurde von '''phrakture''' und '''tpowa''' mit einiger Hilfe von der Community entwickelt.
'''mkinitcpio''' wurde von '''phrakture''' und '''tpowa''' mit Hilfe aus der Community entwickelt.


= Installation von mkinitcpio =
{{installation|paket=mkinitcpio|repo=core}}
== Aus dem current Repository ==


Das '''mkinitcpio''' Script ist im current Repository verfügbar. Du kannst es mit pacman installieren:
mkinitcpio ist Bestandteil jeder Arch Linux Installation.
# pacman -Sy mkinitcpio


== Aus dem svn ==
== Konfiguration ==


Die aktuelle Entwickler-Version von '''mkinitcpio''' kannst Du aus  phraktures svn Repository laden:
Die Konfigurationsdatei lautet {{ic|/etc/mkinitcpio.conf}}.
# svn co http://phraktured.net/initramfs
Die neuesten Scripte befinden sich nun im '''initramfs/mkinitcpio''' Verzeichnis.


= Aktivierung für Kernel ab 2.6.17 =
=== MODULES ===
Es werden zwei Images während der Installation des Kernels erstellt:


- '''kernel26'''
Mit dem MODULES-Eintrag können Module explizit dem Image hinzugefügt werden.
/boot/kernel26.img --> enhält nur die automatisch erkannten Module
/boot/kernel26-fallback.img --> enthält alle Module
- '''kernel26beyond'''
/boot/kernel26beyond.img --> enhält nur die automatisch erkannten Module
/boot/kernel26beyond-fallback.img --> enthält alle Module
Ändere Deine Bootloader-Konfiguration Deinen Bedürfnissen entsprechend.
== Achtung => '''lvm2''', '''raid''' and '''encrypt''' werden standardmäßig '''nicht''' aktiviert! ==
Zur Konfiguration dieser System lese bitte die entsprechenden Anleitungen im Wiki.


= Anpassung der Konfigurations-Dateien =
Beispiel: Bei Verwendung des nouveau Treiber wird bereits die Konsole beim Starten diesen verwenden.


== '''Änderung es Haupt-Image''' ==
MODULES=(nouveau)
Um die Standard-Einstellungen des Haupt-Image zu ändern, nutze folgende Datei:


/etc/mkinitcpio.conf
=== BINARIES und FILES ===


mkinitcpio benutzt standardmäßig diese Datei.
Mit diesen Optionen können Dateien dem Abbild hinzugefügt werden. Der einzige Unterschied zwischen BINARIES und FILES ist, dass BINARIES die Bibliotheken nach Abhängigkeiten durchsucht, während FILES nur Dateien hinzufügt.


== '''Änderung des Fallback-Image''' ==
=== HOOKS ===
Um die Standard-Einstellungen des Fallback-Image zu ändern, nutze folgende Dateien:
kernel26 --> '/boot/mkinitcpio-kernel26.conf'
kernel26beyond --> '/boot/mkinitcpio-kernel26beyond.conf
und füge die Dateien der Zeile '''NoUpgrade =''' der '/etc/pacman.conf' hinzu. Dies ist nur bei speziellen Konfigurationen mit lvm oder raid nötig.


Dies ist der wichtigste Teil der mkinitcpio Konfiguration. Diese Zeile enthält alle HOOKS, welche während der Imageerstellung oder zur Laufzeit ausgeführt werden. Hierbei muss die Reihenfolge beachtet werden:


== Konfiguration der HOOKS ==
HOOKS=(foo1 foo2 bar1 bar2)


This is the most important part of mkinitcpio configuration. The HOOKS line contains the hooks that are executed on image creation and on runtime in the exact order they are executed. The format is like this:
Am besten man prüft anhand des eigenen Systems, welche HOOKS aktuell verfügbar sind. Zusätzlich wird angezeigt, welche als veraltet gelten, und welche zukünftig verwendet werden sollen.


  HOOKS="foo1 foo2 foo3 bar1 bar2"
  mkinitcpio -L


=== Available hooks ===
Für jeden gelisteten HOOK gibt es eine Zusatzinfo.


mkinitcpio -H base
==== Verfügbare HOOKS ====
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border-style:solid; border-width:1px; border-collapse:collapse; empty-cells:show"
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border-style:solid; border-width:1px; border-collapse:collapse; empty-cells:show"
|-
|-
! Hook || Installation || Runtime
! Hook || Information
|-
| '''base''' || This hook provides crucial runtime necessities for booting. DO NOT remove this hook unless you know what you're doing.
|-
| '''udev''' || This hook will use udev to create your root device node and detect the needed modules for your root device. It is also required for firmware loading in initramfs. It is recommended to use this hook.
|-
|'''microcode''' || This hook adds early microcode update files for Intel and AMD processors. If /boot/amd-ucode.img or /boot/intel-ucode.img exist, they are included in the initcpio. If not, the individual microcode files in /lib/firmware/ are included if they exist. If the autodetect hook runs before this hook, it will only add early microcode update files for the processor of the system the image is built on.
|-
|-
| '''base''' || Sets up all initial directories and installs base klibc utilities and libraries. Always add this hook unless you know what you are doing. ||
| '''systemd''' || This will install a basic systemd setup in your initramfs, and is meant to replace the 'base', 'usr', 'udev' and 'timestamp' hooks. Other hooks with runtime components will need to be ported, and will not work as intended. You also may wish to still include the 'base' hook (before this hook) to ensure that a rescue shell exists on your initramfs.  
|-
|-
| '''udev''' || Adds udev to your image || Udev will be used to create your root device node and detect the needed modules for your root device. As it simplifies things, using the udev hook is recommended.
| '''modconf''' || This hook installs modprobe configuration files from /etc/modprobe.d and /usr/lib/modprobe.d.  
|-
|-
| '''modload''' || || An alternative autodetecion method which is much slower than udev. Using this hook is discouraged. Use udev instead.
| '''usr''' || This provides a support for mounting /usr via a late running hook. No configuration is needed, as the mount options will be pulled directly from the fstab on the real root device.  
|-
|-
| '''autodetect''' || Shrinks your initramfs to a smaller size by autodetecting your needed modules. Be sure to verify included modules are correct and none are missing. This hook must be run before other subsystem hooks in order to take advantage of auto-detection. Any hooks placed before 'autodetect' will be installed in full. ||
| '''autodetect''' || This hook shrinks your initramfs to a smaller size by autodetecting the needed modules. Be sure to verify included modules are correct and none are missing. This hook must be run before other subsystem hooks in order to take advantage of auto-detection. Any hooks placed before 'autodetect' will be installed in full.  
|-
|-
| '''ide''' || Adds IDE modules to the image. Use this if your root device is on a IDE disk. Also use the '''autodetect''' hook if you want to minimize your image size || Loads IDE modules. You will need the '''udev''' or '''modload''' hook unless you specify the needed modules manually (see MODULES section below).
| '''sata''' || This hook is deprecated in favor of 'block'  
|-
|-
| '''sata''' || Adds serial ATA modules to the image. Use this if your root device is on a SATA disk. Also use the '''autodetect''' hook if you want to minimize your image size. || Loads SATA modules. You will need the '''udev''' or '''modload''' hook unless you specify the needed modules manually (see MODULES section below).
| '''scsi''' || This hook is deprecated in favor of 'block'  
|-
|-
| '''scsi''' || Adds SCSI modules to the image. Use this if your root device is on a SCSI disk. Also use the '''autodetect''' hook if you want to minimize your image size. || Loads SCSI modules. You will need the '''udev''' or '''modload''' hook unless you specify the needed modules manually (see MODULES section below).
| '''usb''' || This hook is deprecated in favor of 'block'  
|-
|-
| '''usb''' || Adds USB modules to the image. Use this if your root device is on a USB mass storage device. || Loads USB modules. You will need the '''udev''' or '''modload''' hook unless you specify the needed modules manually (see MODULES section below).
| '''fw''' || This hook is deprecated in favor of 'block'  
|-
|-
| '''usbinput''' || Adds USB HID modules to the image. Use this if you have an USB keyboard and need it in early userspace (either for entering encryption passphrases or for failsafe mode) || Loads USB HID modules. You will need the '''udev''' or '''modload''' hook unless you specify the needed modules manually (see MODULES section below).
| '''block''' || This hook loads the necessary modules for most block devices using pata, sata, scsi, firewire, usb, or mmc. Detection will take place at runtime. To minimize the modules in the image, add the autodetect hook too.  
|-
|-
| '''fw''' || Adds Firewire modules to the image. Use this if your root device is on a FW mass storage device. || Loads FW modules. You will need the '''udev''' or '''modload''' hook unless you specify the needed modules manually (see MODULES section below).
| '''usbinput''' || This hook is deprecated in favor of 'keyboard'  
|-
|-
| '''net''' || Adds the necessary modules for a network device. For pcmcia net devices please add pcmcia hook too. ||  Loads network modules. You will need the '''udev''' or '''modload''' hook unless you specify the needed modules manually (see MODULES section below).  See the section [[Configuring_mkinitcpio#Customizing_the_kernel_command_line|Customizing the kernel command line]] for further configuration.
| '''keyboard''' || This hook loads the necessary modules for keyboard devices. As a side-effect modules for some non-keyboard input devices might be added to, but this should not be relied on. Detection will take place at runtime. To minimize the modules in the image, add the autodetect hook too.  
|-
|-
| '''pcmcia''' || Adds the necessary modules for pcmcia devices. You need to have pcmciautils installed to use this.||  Loads pcmcia modules. You will need the '''udev''' or '''modload''' hook unless you specify the needed modules manually (see MODULES section below).
| '''filesystems''' || This hook adds filesystems modules to the image. If you would like to minimize the modules installed in the image, add the autodetect hook too.  
|-
|-
| '''dsdt''' || Loads a custom acpi dsdt file during boot. Place your custom dsdt file for inclusion at /lib/initcpio/custom.dsdt || The custom dsdt file is automatically used by the kernel if it is present in initramfs.
| '''lvm2''' || This hook enables LVM2 volumes in initramfs. Do pacman -S lvm2 before.  
|-
|-
| '''filesystems''' || This includes necessary filesystem modules into your image. This hook is necessary if you want to be able to boot || This will detect the filesystem type at runtime, load the module and pass it to kinit. NOTE: it will NOT detect reiser4, it must be added to modules list.
| '''sd-lvm2''' || This hook enables LVM2 volumes in systemd-based initramfs. Do pacman -S lvm2 before.  
|-
|-
| '''lvm2''' || Adds the device mapper kernel module and the lvm tool to the image. You need to have the lvm2 package installed to use this. || Enables all lvm2 volume groups. This is necessary if you have your root filesystem on lvm.
| '''mdadm''' || This hook loads the necessary modules for any raid root device, and assembles the raid device when run. If arrays are defined in /etc/mdadm.conf, the file will be used instead of command line assembling. Do pacman -S mdadm before. Please see mkinitcpio -H mdadm
|-
|-
| '''raid''' || Adds the modules and mdassamble for a software raid setup. You need to have mdadm installed to use this.|| Loads the necessary modules for software raid devices, and assembles the raid devices when run. See the section [[Configuring_mkinitcpio#Customizing_the_kernel_command_line|Customizing the kernel command line]] for further configuration.
| '''dmraid''' || This hook loads the necessary modules for a dmraid root device. Do pacman -S dmraid before.  
|-
|-
| '''encrypt''' || Adds the dm-crypt kernel module and the cryptsetup tool to the image. You need to have the cryptsetup package installed to use this. || Detects and unlocks an encrypted root partition. See the section [[Configuring_mkinitcpio#Customizing_the_kernel_command_line|Customizing the kernel command line]] for further configuration.
| '''encrypt''' || This hook allows for an encrypted root device. Users should specify the device to be unlocked using 'cryptdevice=device:dmname' on the kernel command line, where 'device' is the path to the raw device, and 'dmname' is the name given to the device after unlocking, and will be available as /dev/mapper/dmname. Do pacman -S cryptsetup before. Please see mkinitcpio -H encrypt
|-
|-
| '''resume''' ||  || This tries to resume from "suspend to disk" state. Works with both swsusp and [[Suspend to Disk|suspend2]]. See the section [[Configuring_mkinitcpio#Customizing_the_kernel_command_line|Customizing the kernel command line]] for further configuration.
| '''sd-encrypt''' || This hook allows for an encrypted root device. Users should specify the device to be unlocked using 'cryptdevice=device:dmname' on the kernel command line, where 'device' is the path to the raw device, and 'dmname' is the name given to the device after unlocking, and will be available as /dev/mapper/dmname. Do pacman -S cryptsetup before. Please see mkinitcpio -H sd-encrypt
|-
|-
| '''firmware''' || Adds /lib/firmware files. || Loads firmware. You will need the '''udev''' hook to get firmware loaded.  
| '''resume''' || This hook initializes support for resuming from Disk. Supports swsusp and suspend2.  
|-
|-
| '''keymap''' || Adds keymap and consolefonts from rc.conf. || Loads the specified keymap and consolefont from rc.conf during early userspace.
| '''fschk''' || This hook provides fsck and filesystem specific helpers to perform an fsck operation on the root device prior to mounting. If the autodetect hook is used, only the fsck helper specific to your filesystem will be added to the image. It is highly recommended that if you include this hook that you also include any necessary modules to ensure your keyboard will work in early userspace. Please see mkinitcpio -H fsck
|-
| '''consolefont''' || This hook loads consolefont specified in vconsole.conf during early userspace.  
|-
| '''sd-vconsole''' || This hook adds the keymap(s) and font specified in vconsole.conf to the image and loads them during early userspace.  
|}
|}


=== Examples ===
Beispiele:


This configuration will work for most users with a standard setup:
Diese Konfiguration sollte für die meisten Benutzer funktionieren:


  HOOKS="base udev autodetect ide scsi sata filesystems"
  HOOKS=(base systemd autodetect modconf block filesystems sd-vconsole fsck)


If you want to use the image on more than one machine, use this configuration:
Du kannst verschlüsselte Dateisysteme innerhalb von lvm nutzen:


  HOOKS="base udev ide scsi sata filesystems"
  HOOKS=(base autodetect modconf block lvm2 encrypt filesystems keyboard consolefont fsck)


You can use encrypted volumes on top of lvm2 volume groups:
Du kannst verschlüsselte Dateisysteme innerhalb von lvm nutzen, wenn systemd im Einsatz ist:


  HOOKS="base udev autodetect ide scsi sata lvm2 encrypt filesystems"
  HOOKS=(base systemd autodetect modconf block sd-lvm2 sd-encrypt filesystems sd-vconsole fsck)


== Configuring the MODULES ==
=== COMPRESSION ===
# Use this to compress the initramfs image. By default, gzip compression is used. Use 'cat' to create an uncompressed image.
COMPRESSION=(xz)
=== COMPRESSION_OPTIONS ===
# Additional options for the compressor
COMPRESSION_OPTIONS=(-9)


You can use the MODULES in the configuration file to load a module before anything else is done. For example, if you don't want to use '''udev''' or '''modload''', you can add all necessary modules manually and make booting faster:
== Erstellen des Images ==


MODULES="piix ide_disk reiserfs"
Erstelle das Image mit folgendem Befehl:
HOOKS="base autodetect ide filesystems"


NOTE: if you're using '''reiser4''', you MUST add it to the modules list.
# mkinitcpio -p linux


== Configuring the BINARIES and FILES ==
== Extrahieren des Images ==


These options allow you to add files to the image. The only difference is that BINARIES checks binaries and libraries for dependencies, while FILES simply adds the file.
Wenn du wissen möchtest, was sich innerhalb des initrd-Abbildes befindet, kann du es auspacken und in den enthaltenen Dateien herumstöbern.


Examples:
Das initrd-Abbild ist ein 'SVR4 CPIO'-Archiv, das durch die Befehle ''find'' und ''bsdcpio'' erstellt wurde und optional durch ein vom Kernel verstandenes Komprimierungsschema komprimiert wurde: genauer gesagt gzip, bzip2, lzma, lzo oder xz.


FILES="/etc/modprobe.conf"
mkinitcpio beinhaltet ein Werkzeug namens lsinitcpio, welches die Inhalte des initramfs-Abbildes anzeigt und extrahiert.


BINARIES="/usr/bin/somefile"
Das Anzeigen der Dateien im Abbild geschieht durch:


= Creating the image =
# lsinitcpio /boot/initramfs-linux.img


Create the image with the following command:
Man kann sich auch eine Auflistung der wichtigen Teile des Abbildes anzeigen lassn:


  mkinitcpio -g /boot/kernel26.img
  # lsinitcpio -a /boot/initramfs-linux.img


This will generate the image for the currently running kernel and save it at '''/boot/kernel26.img''', which is the location for '''kernel26''' package. Users of '''kernel26beyond''' should use the following instead:
Das Extrahieren aller Dateien in das aktuelle Verzeichnis:


  mkinitcpio -g /boot/kernel26beyond.img
  # lsinitcpio -x /boot/initramfs-linux.img


If you are creating an image for a kernel other than the one you are currently running, add the kernel version to the command line:
== Kernelzeile anpassen ==


mkinitcpio -g /boot/kernel26.img -k 2.6.16-ARCH
Einige Optionen müssen in der Kernelzeile angegeben werden. Einige Mkinitcpio Hooks haben spezielle Optionen. Um diese soll es in diesem Abschnitt gehen.


Wenn du nicht weißt was die Kernelzeile ist, schau in die Dokumentationen von [[GRUB]] oder [[Syslinux]].


''NOTE:'' The following may confuse some people. It is only intended to help create fallback images for people already running the current kernel. To create images for any kernel that is not currently running, you MUST use the -k parameter.
=== Failsafe Modus ===


A fallback image should have been created when you installed '''kernel26''' or '''kernel26beyond''' but in case you want to re-generate it
Wenn du


  mkinitcpio -c /boot/mkinitcpio-kernel26.conf -g /boot/kernel26.img
  break=y
for beyond
mkinitcpio -c /boot/mkinitcpio-kernel26beyond.conf -g /boot/kernel26beyond.img


See '''mkinitcpio -h''' for more options.
zur Kernelzeile hinzufügst, dann stoppt Init nach dem das Setup vollständig ist und du landest in einer ''dash'' shell. Diese kann genutzt werden um sich über den Erfolg des Vorgangs zu versichern. Wenn du dich ausloggst geht der normale Bootvorgang weiter.


Don't forget to add a new bootloader entry. Just make a copy of your old one and change the initrd to your new image. As long as mkinitcpio is beta, please always leave the old one intact, so that you can boot it if something goes wrong. You can use mkinitcpio with any kernel, so kernel26 and kernel26-beyond users are encouraged to try it.
=== Hooks deaktivieren ===


= Customizing the kernel command line =
Du kannst hooks deaktivieren indem du ''disablehooks'' zur Kernelzeile hinzufügst:
 
Just like without initramfs, some options need to be passed on the kernel command line to configure your kernel, like the root device. Some of the mkinitcpio hooks have special options. These are discussed below.
 
If you don't know what a kernel command line is, please refer to the [[GRUB]] or [[Lilo]] documentation.
 
== Entering failsafe mode ==
 
If you add the option
break=y
to the kernel command line, init stops after the setup is completed and you are left with a ''dash'' shell. This can be used to verify that everything went fine. If you logout, normal boot continues.
 
== Disabling hooks ==
 
You can disable a hook at runtime by adding the ''disablehooks'' option to the kernel command line like this:


  disablehooks=hook1,hook2,hook2
  disablehooks=hook1,hook2,hook2


for example
zum Beispiel


  disablehooks=resume
  disablehooks=resume


== Blacklisting modules ==
=== Module blacklisten ===


You can blacklist modules by adding the ''disablemodules'' option to the kernel command line like this:
Du kannst Module blacklisten indem du ''disablemodules'' zur Kernelzeile hinzufügst:


  disablemodules=mod1,mod2,mod3
  disablemodules=mod1,mod2,mod3


for example
zum Beispiel


  disablemodules=ata_piix
  disablemodules=ata_piix


'''THIS FEATURE IS AVAILABLE SINCE MKINITCPIO 0.5.1'''
[[Kategorie:Konfiguration]]
 
== Using raid ==
First add the raid hook to the HOOKS list in /etc/mkinitcpio.conf
 
'''Kernel Parameters: '''
Specify all your md arrays with md= parameter: (only adding the raid array you're booting from is enough)


add the following to the kernel line in grub/menu.lst:
[[en:mkinitcpio]]
  Example: md=0,/dev/sda3,/dev/sda4 md=1,/dev/hda1,/dev/hdb1
  working example: kernel /vmlinuz26beyond root=/dev/md0 ro md=0,/dev/sda1,/dev/sdb1
This will setup 2 md arrays with persistent superblocks
 
'''Setup:'''
  - for old raid arrays without persistent superblocks:
    md=<md device no.>,<raid level>,<chunk size factor>,<fault level>,dev0,dev1
  - for raid arrays with persistent superblocks:
    md=<md device no.>,dev0,dev1,...,devn
  - for, to assemble a partitionable array:
    md=d<md device no.>,dev0,dev1,...,devn
 
'''Parameters:'''
  - <md device no.> = the number of the md device:
    0 means md0, 1 means md1, ...
  - <raid level> = -1 linear mode, 0 striped mode
    other modes are only supported with persistent super block
  - <chunk size factor> = (raid-0 and raid-1 only):
    Set  the chunk size as 4k << n.
  - <fault level> = totally ignored
  - <dev0-devn>: e.g. /dev/hda1,/dev/hdc1,/dev/sda1,/dev/sdb1
 
== Using net ==
 
'''Kernel Parameters:'''
 
'''ip='''
 
An interface spec can be either short form, which is just the name of
an interface (eth0 or whatever), or long form.  The long form consists
of up to seven elements, separated by colons:
 
  ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
  nfsaddrs= is an alias to ip= and can be used too.
 
''Parameter explanation:''
  <client-ip>  IP address of the client. If empty, the address will
                either be determined by RARP/BOOTP/DHCP. What protocol
                is used de- pends on the <autoconf> parameter. If this
                parameter is not empty, autoconf will be used.
 
  <server-ip>  IP address of the NFS server. If RARP is used to
                determine the client address and this parameter is NOT
                empty only replies from the specified server are
                accepted. To use different RARP and NFS server,
                specify your RARP server here (or leave it blank), and
                specify your NFS server in the `nfsroot' parameter
                (see above). If this entry is blank the address of the
                server is used which answered the RARP/BOOTP/DHCP
                request.
 
  <gw-ip>      IP address of a gateway if the server is on a different
                subnet. If this entry is empty no gateway is used and the
                server is assumed to be on the local network, unless a
                value has been received by BOOTP/DHCP.
 
  <netmask>    Netmask for local network interface. If this is empty,
                the netmask is derived from the client IP address assuming
                classful addressing, unless overridden in BOOTP/DHCP reply.
 
  <hostname>    Name of the client. If empty, the client IP address is
                used in ASCII notation, or the value received by
                BOOTP/DHCP.
 
  <device>      Name of network device to use. If this is empty, all
                devices are used for RARP/BOOTP/DHCP requests, and the
                first one we receive a reply on is configured. If you
                have only one device, you can safely leave this blank.
 
  <autoconf> Method to use for autoconfiguration. If this is either
                'rarp', 'bootp', or 'dhcp' the specified protocol is
                used.  If the value is 'both', 'all' or empty, all
                protocols are used.  'off', 'static' or 'none' means
                no autoconfiguration.
''Examples:''
  ip=127.0.0.1:::::lo:none  --> Enable the loopback interface.
  ip=192.168.1.1:::::eth2:none --> Enable static eth2 interface.
  ip=:::::eth0:dhcp --> Enable dhcp protcol for eth0 configuration.
'''nfsroot='''
 
If the 'nfsroot' parameter is NOT given on the command line, the default
"/tftpboot/%s" will be used.
 
  nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]
 
''Parameter explanation:''
 
  <server-ip>  Specifies the IP address of the NFS server. If this field
                is not given, the default address as determined by the
                `ip' variable (see below) is used. One use of this
                parameter is for example to allow using different servers
                for RARP and NFS. Usually you can leave this blank.
 
  <root-dir>    Name of the directory on the server to mount as root. If
                there is a "%s" token in the string, the token will be
                replaced by the ASCII-representation of the client's IP
                address.
 
  <nfs-options> Standard NFS options. All options are separated by commas.
                If the options field is not given, the following defaults
                will be used:
                        port            = as given by server portmap daemon
                        rsize          = 1024
                        wsize          = 1024
                        timeo          = 7
                        retrans        = 3
                        acregmin        = 3
                        acregmax        = 60
                        acdirmin        = 30
                        acdirmax        = 60
                        flags          = hard, nointr, noposix, cto, ac
 
'''root=/dev/nfs'''
  If you don't use nfsroot= parameter you need to set root=/dev/nfs
  to boot from a nfs root by autoconfiguration.
 
== Using lvm ==
 
If your root device is on lvm, you have to add the '''lvm2''' hook. You have to pass your root device on the kernel command line in the format
 
root=/dev/mapper/<volume group name>-<logical volume name>
 
for exmaple
 
root=/dev/mapper/myvg-root
 
== Using encrypted root ==
 
If your root volume is encrypted, you need to add the '''encrypt''' hook. Then specify your root device on the kernel command line, just as if it was unencrypted, for example
 
root=/dev/sda5
 
for an encrypted partition on an sata or scsi disk or
 
root=/dev/mapper/myvg-root
 
for an encrypted lvm volume. The root device will be automatically changed to ''/dev/mapper/root''.
 
=== Using LUKS volumes ===
 
If you use LUKS for hard disk encryption, the init script will detect the encryption automatically if the '''encrypt''' hook is enabled. It will then ask for a passphrase and try to unlock the volume.
 
=== Using legacy cryptsetup volumes ===
 
If you are using a legacy cryptsetup volume, you have to specify all cryptsetup options necessary to unlock it on the kernel command line. The option format is
 
crypto=hash:cipher:keysize:offset:skip
 
representing cryptsetup's --hash, --cipher, --keysize, --offset and --skip options. If you omit an option, cryptsetup's default value is used, so you can just specify
 
crypto=::::
 
if you created your volume with the default settings.
 
'''NOTE:''' For technical reasons, it is not possible to verify the correctness of your passphrase with legacy cryptsetup volumes. If you typed it wrong, mounting will simply fail. It is recommended that you use LUKS instead.
 
=== Using loop-aes volumes ===
 
'''mkinitcpio''' does not support loop-aes yet.
 
== Using Suspend to Disk ==
 
If you want to use suspend to disk, you have to add the '''resume''' hook.
 
=== swsusp ===
 
''TODO''
 
=== µswsusp ===
 
µswsusp is not supported yet.
 
=== suspend2 ===
 
If you are using [[Suspend to Disk|suspend2]], you have to specify the ''resume2'' kernel commandline option. If you are using the swap writer, use
 
resume2=swap:/dev/hda3
 
where ''/dev/hda3'' is your swap partition. If you want to use the filewriter, use
 
resume2=file:/dev/hda2:0x123456
 
where ''/dev/hda2'' is the partition where the suspend2 image is stored (most likely the root partition) and ''0x123456'' is the file offset. You can get the exact value with the commands
 
echo "/suspend2_file" > /proc/suspend2/filewriter_target
cat /proc/suspend2/resume2
 
where /suspend2_file is the path to your suspend image file. This - of course - works for lvm volumes as well. You can also use a suspend file on an encrypted root partition with the option
 
resume2=file:/dev/mapper/root:0x123456
 
where ''0x123456'' is the offset again. Resuming from an encrypted swap partition is not supported.
 
== Example bootloader configuration files ==
 
If you use the beyond kernel, the filenames are ''kernel26beyond.img'' and ''kernel26beyond-fallback.img'' instead of ''kernel26.img'' and ''kernel26-fallback.img'', respectively. Also, change "vmlinuz26" to "vmlinuz26beyond".
 
=== GRUB ===
 
For those who have /boot on a separate partition:
 
# (0) Arch Linux
title Arch Linux
root  (hd0,3)
kernel /vmlinuz26 root=/dev/hda4 vga=791 ro
initrd /kernel26.img
title Arch Linux Fallback
root  (hd0,3)
kernel /vmlinuz26 root=/dev/hda4 vga=791 ro
initrd /kernel26-fallback.img
 
For those who do _not_ have /boot on a separate partition:
 
# (0) Arch Linux
title Arch Linux
root  (hd0,3)
kernel /boot/vmlinuz26 root=/dev/hda4 vga=791 ro
initrd /boot/kernel26.img
title Arch Linux Fallback
root  (hd0,3)
kernel /boot/vmlinuz26 root=/dev/hda4 vga=791 ro
initrd /boot/kernel26-fallback.img
 
=== LILO ===
 
If you use LILO, it is recommended that you use ''append="root=/dev/XYZ"'' instead of ''root=/dev/XYZ''. If you already have a global ''append'' option, then use ''addappend''.
 
boot=/dev/hdX
default = <Label of default image>
timeout=50
vga=791
lba32
prompt
# for the hardware-autodetecting image
image=/boot/vmlinuz26
label=ArchLinux
append="root=/dev/hdXY"
initrd=/boot/kernel26.img
read-only
# fallback image if the other doesnt work (Will most prob. never be used)
image=/boot/vmlinuz26
label=ArchLinuxFallBack
append="root=/dev/hdXY"
initrd=/boot/kernel26-fallback.img
read-only
 
= Troubleshooting =
== piix ide controllers and beyond kernel ==
=== Problem ===
If you are having problems getting mkinitcpio to detect your hard drive giving errors akin to "Can't find device dev(0,0)" when switching to kinit, then this could be because of a conflict that the ata_piix and piix drivers have.  The beyond kernel has some libata patches that cause ata_piix to *conflict* with piix.
 
=== Solution ===
Edit /etc/mkinitcpio.conf to only have ide or sata or scsi depending on what your system actually needs to boot.
 
[[Kategorie:Installation]]
[[Kategorie:Konfiguration]]
[[Kategorie:Unvollständig]]

Aktuelle Version vom 5. März 2024, 23:49 Uhr

mkinitcpio ist die nächste Generation der initramfs-Erstellung. Es hat viele Vorteile gegenüber den alten Skripten mkinitrd und mkinitramfs.

  • Es nutzt klibc und kinit der Linux-Entwickler, welches eine kleine und leichtgewichtige Basis bereitstellt, um Programme sehr früh im userspace laufen zu lassen.
  • Es kann mittels udev die Hardware zur Laufzeit erkennen, so dass nur die wirklich nötigen Module geladen werden.
  • Die hook-basierenden init-Scripte sind leicht erweiterbar und können auch durch externe Pakete genutzt werden.
  • Es unterstützt bereits lvm2, dm-crypt (legacy und luks volumes), raid, swsusp und suspend2 Fortsetzen und Starten von usb Datenträgern.
  • Viele Funktionen können von der Kernel-Kommandozeile konfiguriert werden ohne das Image neu erstellen zu müssen.
  • Mit dem mkinitcpio-Skript ist es möglich, das Image in den Kernel zu integrieren.

mkinitcpio wurde von phrakture und tpowa mit Hilfe aus der Community entwickelt.

Installation

Das Programm ist als mkinitcpio in core verfügbar, und kann von dort mittels Pacman installiert werden.

pacman -S mkinitcpio

mkinitcpio ist Bestandteil jeder Arch Linux Installation.

Konfiguration

Die Konfigurationsdatei lautet /etc/mkinitcpio.conf.

MODULES

Mit dem MODULES-Eintrag können Module explizit dem Image hinzugefügt werden.

Beispiel: Bei Verwendung des nouveau Treiber wird bereits die Konsole beim Starten diesen verwenden. 

MODULES=(nouveau)

BINARIES und FILES

Mit diesen Optionen können Dateien dem Abbild hinzugefügt werden. Der einzige Unterschied zwischen BINARIES und FILES ist, dass BINARIES die Bibliotheken nach Abhängigkeiten durchsucht, während FILES nur Dateien hinzufügt.

HOOKS

Dies ist der wichtigste Teil der mkinitcpio Konfiguration. Diese Zeile enthält alle HOOKS, welche während der Imageerstellung oder zur Laufzeit ausgeführt werden. Hierbei muss die Reihenfolge beachtet werden: 

HOOKS=(foo1 foo2 bar1 bar2)

Am besten man prüft anhand des eigenen Systems, welche HOOKS aktuell verfügbar sind. Zusätzlich wird angezeigt, welche als veraltet gelten, und welche zukünftig verwendet werden sollen. 

mkinitcpio -L

Für jeden gelisteten HOOK gibt es eine Zusatzinfo. 

mkinitcpio -H base

Verfügbare HOOKS

Hook Information
base This hook provides crucial runtime necessities for booting. DO NOT remove this hook unless you know what you're doing.
udev This hook will use udev to create your root device node and detect the needed modules for your root device. It is also required for firmware loading in initramfs. It is recommended to use this hook.
microcode This hook adds early microcode update files for Intel and AMD processors. If /boot/amd-ucode.img or /boot/intel-ucode.img exist, they are included in the initcpio. If not, the individual microcode files in /lib/firmware/ are included if they exist. If the autodetect hook runs before this hook, it will only add early microcode update files for the processor of the system the image is built on.
systemd This will install a basic systemd setup in your initramfs, and is meant to replace the 'base', 'usr', 'udev' and 'timestamp' hooks. Other hooks with runtime components will need to be ported, and will not work as intended. You also may wish to still include the 'base' hook (before this hook) to ensure that a rescue shell exists on your initramfs.
modconf This hook installs modprobe configuration files from /etc/modprobe.d and /usr/lib/modprobe.d.
usr This provides a support for mounting /usr via a late running hook. No configuration is needed, as the mount options will be pulled directly from the fstab on the real root device.
autodetect This hook shrinks your initramfs to a smaller size by autodetecting the needed modules. Be sure to verify included modules are correct and none are missing. This hook must be run before other subsystem hooks in order to take advantage of auto-detection. Any hooks placed before 'autodetect' will be installed in full.
sata This hook is deprecated in favor of 'block'
scsi This hook is deprecated in favor of 'block'
usb This hook is deprecated in favor of 'block'
fw This hook is deprecated in favor of 'block'
block This hook loads the necessary modules for most block devices using pata, sata, scsi, firewire, usb, or mmc. Detection will take place at runtime. To minimize the modules in the image, add the autodetect hook too.
usbinput This hook is deprecated in favor of 'keyboard'
keyboard This hook loads the necessary modules for keyboard devices. As a side-effect modules for some non-keyboard input devices might be added to, but this should not be relied on. Detection will take place at runtime. To minimize the modules in the image, add the autodetect hook too.
filesystems This hook adds filesystems modules to the image. If you would like to minimize the modules installed in the image, add the autodetect hook too.
lvm2 This hook enables LVM2 volumes in initramfs. Do pacman -S lvm2 before.
sd-lvm2 This hook enables LVM2 volumes in systemd-based initramfs. Do pacman -S lvm2 before.
mdadm This hook loads the necessary modules for any raid root device, and assembles the raid device when run. If arrays are defined in /etc/mdadm.conf, the file will be used instead of command line assembling. Do pacman -S mdadm before. Please see mkinitcpio -H mdadm
dmraid This hook loads the necessary modules for a dmraid root device. Do pacman -S dmraid before.
encrypt This hook allows for an encrypted root device. Users should specify the device to be unlocked using 'cryptdevice=device:dmname' on the kernel command line, where 'device' is the path to the raw device, and 'dmname' is the name given to the device after unlocking, and will be available as /dev/mapper/dmname. Do pacman -S cryptsetup before. Please see mkinitcpio -H encrypt
sd-encrypt This hook allows for an encrypted root device. Users should specify the device to be unlocked using 'cryptdevice=device:dmname' on the kernel command line, where 'device' is the path to the raw device, and 'dmname' is the name given to the device after unlocking, and will be available as /dev/mapper/dmname. Do pacman -S cryptsetup before. Please see mkinitcpio -H sd-encrypt
resume This hook initializes support for resuming from Disk. Supports swsusp and suspend2.
fschk This hook provides fsck and filesystem specific helpers to perform an fsck operation on the root device prior to mounting. If the autodetect hook is used, only the fsck helper specific to your filesystem will be added to the image. It is highly recommended that if you include this hook that you also include any necessary modules to ensure your keyboard will work in early userspace. Please see mkinitcpio -H fsck
consolefont This hook loads consolefont specified in vconsole.conf during early userspace.
sd-vconsole This hook adds the keymap(s) and font specified in vconsole.conf to the image and loads them during early userspace.

Beispiele:

Diese Konfiguration sollte für die meisten Benutzer funktionieren: 

HOOKS=(base systemd autodetect modconf block filesystems sd-vconsole fsck)

Du kannst verschlüsselte Dateisysteme innerhalb von lvm nutzen: 

HOOKS=(base autodetect modconf block lvm2 encrypt filesystems keyboard consolefont fsck)

Du kannst verschlüsselte Dateisysteme innerhalb von lvm nutzen, wenn systemd im Einsatz ist: 

HOOKS=(base systemd autodetect modconf block sd-lvm2 sd-encrypt filesystems sd-vconsole fsck)

COMPRESSION

# Use this to compress the initramfs image. By default, gzip compression is used. Use 'cat' to create an uncompressed image.
COMPRESSION=(xz)

COMPRESSION_OPTIONS

# Additional options for the compressor
COMPRESSION_OPTIONS=(-9)

Erstellen des Images

Erstelle das Image mit folgendem Befehl: 

# mkinitcpio -p linux

Extrahieren des Images

Wenn du wissen möchtest, was sich innerhalb des initrd-Abbildes befindet, kann du es auspacken und in den enthaltenen Dateien herumstöbern.

Das initrd-Abbild ist ein 'SVR4 CPIO'-Archiv, das durch die Befehle find und bsdcpio erstellt wurde und optional durch ein vom Kernel verstandenes Komprimierungsschema komprimiert wurde: genauer gesagt gzip, bzip2, lzma, lzo oder xz.

mkinitcpio beinhaltet ein Werkzeug namens lsinitcpio, welches die Inhalte des initramfs-Abbildes anzeigt und extrahiert.

Das Anzeigen der Dateien im Abbild geschieht durch: 

# lsinitcpio /boot/initramfs-linux.img

Man kann sich auch eine Auflistung der wichtigen Teile des Abbildes anzeigen lassn: 

# lsinitcpio -a /boot/initramfs-linux.img

Das Extrahieren aller Dateien in das aktuelle Verzeichnis: 

# lsinitcpio -x /boot/initramfs-linux.img

Kernelzeile anpassen

Einige Optionen müssen in der Kernelzeile angegeben werden. Einige Mkinitcpio Hooks haben spezielle Optionen. Um diese soll es in diesem Abschnitt gehen.

Wenn du nicht weißt was die Kernelzeile ist, schau in die Dokumentationen von GRUB oder Syslinux.

Failsafe Modus

Wenn du 

break=y

zur Kernelzeile hinzufügst, dann stoppt Init nach dem das Setup vollständig ist und du landest in einer dash shell. Diese kann genutzt werden um sich über den Erfolg des Vorgangs zu versichern. Wenn du dich ausloggst geht der normale Bootvorgang weiter.

Hooks deaktivieren

Du kannst hooks deaktivieren indem du disablehooks zur Kernelzeile hinzufügst: 

disablehooks=hook1,hook2,hook2

zum Beispiel 

disablehooks=resume

Module blacklisten

Du kannst Module blacklisten indem du disablemodules zur Kernelzeile hinzufügst: 

disablemodules=mod1,mod2,mod3

zum Beispiel 

disablemodules=ata_piix
Abgerufen von „https://wiki.archlinux.de/index.php?title=Mkinitcpio&oldid=23999“