README.rst 4.87 KB
Newer Older
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
=======
archiso
=======

The archiso project features scripts and configuration templates to build installation media (*.iso* images) for BIOS
and UEFI based systems on the x86_64 architecture.
Currently creating the images is only supported on Arch Linux.

Requirements
============

The following packages need to be installed to be able to create an image with the included scripts:

* arch-install-scripts
* dosfstools
* e2fsprogs
* libisoburn
18
* mtools
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
* squashfs-tools

For running the images in a virtualized test environment the following packages are required:

* edk2-ovmf
* qemu

For linting the shell scripts the following package is required:

* shellcheck

Profiles
========

Archiso comes with two profiles: **baseline** and **releng**. While both can serve as starting points for creating
custom live media, **releng** is used to create the monthly installation medium.
They can be found below `configs/baseline/ <configs/baseline/>`_  and `configs/releng/ <configs/releng/>`_
36
(respectively). Both profiles are defined by files to be placed into overlays (e.g. *airootfs* -> *the image's /*).
37

38
39
Read `README.profile.rst <README.profile.rst>`_ to learn more about how to create profiles.

40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
Create images
=============

Usually the archiso tools are installed as a package. However, it is also possible to clone this repository and create
images without installing archiso system-wide.

As filesystems are created and various mount actions have to be done when creating an image, **root** is required to run
the scripts.

When archiso is installed system-wide and the modification of a profile is desired, it is necessary to copy it to a
writeable location, as */usr/share/archiso* is tracked by the package manager and only writeable by root (changes will
be lost on update).

The examples below will assume an unmodified profile in a system location (unless noted otherwise).

55
It is advised to consult the help output of **mkarchiso**:
56
57
58

  .. code:: bash

59
    mkarchiso -h
60
61
62
63
64
65

Create images with packaged archiso
-----------------------------------

  .. code:: bash

66
    mkarchiso -w path/to/work_dir -o path/to/out_dir path/to/profile
67
68
69
70

Create images with local clone
------------------------------

71
Clone this repository and run:
72
73
74

  .. code:: bash

75
    ./archiso/mkarchiso -w path/to/work_dir -o path/to/out_dir path/to/profile
76
77
78
79
80

Testing
=======

The convenience script **run_archiso** is provided to boot into the medium using qemu.
81
It is advised to consult its help output:
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96

  .. code:: bash

    run_archiso -h

Run the following to boot the iso using BIOS:

  .. code:: bash

    run_archiso -i path/to/an/arch.iso

Run the following to boot the iso using UEFI:

  .. code:: bash

97
    run_archiso -u -i path/to/an/arch.iso
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114

The script can of course also be executed from this repository:


  .. code:: bash

    ./scripts/run_archiso.sh -i path/to/an/arch.iso

Installation
============

To install archiso system-wide use the included **Makefile**:

  .. code:: bash

    make install

115
116
117
118
119
120
Optionally install archiso's mkinitcpio hooks:

  .. code:: bash

    make install-initcpio

121
122
123
Optional Features
=================

124
125
The iso image contains a grub environment block holding the iso name and version. This allows to
boot the iso image from grub with a version specific cow directory to mitigate overlay clashes.
126
127
128
129
130

  .. code:: grub
      loopback loop archlinux.iso
      load_env -f (loop)/arch/grubenv
      linux (loop)/arch/boot/x86_64/vmlinuz-linux ... \
131
          cow_directory=${NAME}/${VERSION} ...
132
133
      initrd (loop)/arch/boot/x86_64/initramfs-linux-lts.img

David Runge's avatar
David Runge committed
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
Contribute
==========

Development of archiso takes place on Arch Linux' Gitlab: https://gitlab.archlinux.org/archlinux/archiso

Please read our distribution-wide `Code of Conduct <https://wiki.archlinux.org/index.php/Code_of_conduct>`_ before
contributing, to understand what actions will and will not be tolerated.

Read our `contributing guide <CONTRIBUTING.rst>`_ to learn more about how to provide fixes or improvements for the code
base.

Discussion around archiso takes place on the `arch-releng mailing list
<https://lists.archlinux.org/listinfo/arch-releng>`_ and in `#archlinux-releng
<ircs://chat.freenode.net/archlinux-releng>`_ on `freenode.net <https://freenode.net/>`_.

All past and present authors of archiso are listed in `AUTHORS <AUTHORS.rst>`_.

151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
Releases
========

`Releases of archiso <https://gitlab.archlinux.org/archlinux/archiso/-/tags>`_ are created by its current maintainer
`David Runge <https://gitlab.archlinux.org/dvzrv>`_. Tags are signed using the PGP key with the ID
`C7E7849466FE2358343588377258734B41C31549`.

To verify a tag, first import the relevant PGP key:

  .. code:: bash

    gpg --auto-key-locate wkd --search-keys dvzrv@archlinux.org


Afterwards a tag can be verified from a clone of this repository:

  .. code:: bash

    git verify-tag <tag>

171
172
173
174
License
=======

Archiso is licensed under the terms of the **GPL-3.0-or-later** (see `LICENSE <LICENSE>`_).