|
2 | 2 |
|
3 | 3 | The Agama installer ships as a Live ISO image generated by [kiwi-ng](https://osinside.github.io/kiwi/index.html).
|
4 | 4 |
|
5 |
| -It can be booted directly from an USB stick, CD/DVD or from the network using the initrd and the kernel extracted from the ISO as it is documented [here](https://osinside.github.io/kiwi/working_with_images/network_live_iso_boot.html#booting-a-live-iso-image-from-network). |
| 5 | +It can be booted directly from an USB stick, CD/DVD or from the network using |
| 6 | +the initrd and the kernel extracted from the ISO as it is documented [here](https://osinside.github.io/kiwi/working_with_images/network_live_iso_boot.html#booting-a-live-iso-image-from-network). |
6 | 7 |
|
7 |
| -**Note:** As the remote boot process of a live ISO image places the ISO file into a ramdisk by default it is recommended to also extract the compressed root file system (squashfs.img). |
| 8 | +:::note |
| 9 | + |
| 10 | +As the remote boot process of a live ISO image places the ISO file into a ramdisk |
| 11 | +by default it is recommended to also extract the compressed root file system |
| 12 | +(squashfs.img). |
| 13 | + |
| 14 | +::: |
8 | 15 |
|
9 | 16 | Once extracted, these files must be copied to an appropriate location accessible via FTP, TFTP, HTTP, HTTPS...
|
10 | 17 |
|
@@ -45,13 +52,29 @@ It already requires network configuration enforcing `rd.neednet=1`.
|
45 | 52 | Sets the repositories to be used by the installer instead of the ones defined
|
46 | 53 | in the product definition.
|
47 | 54 |
|
48 |
| - :::note For an online installation with a registered product does not make sense. |
| 55 | + :::note |
| 56 | + |
| 57 | + For an online installation with a registered product does not make sense. |
| 58 | + |
| 59 | + ::: |
49 | 60 |
|
50 | 61 | ### Network configuration
|
51 | 62 |
|
52 |
| -Network will be configured by dracut only if really required so, kernel boot options like `root=live:<URL>` already requires it but not all the kernel options (e.g., `inst.install_url`) do so, therefore, to ensure the network is configured by dracut set `rd.neednet=1`. |
| 63 | +Network will be configured by dracut only if really required so, there are some |
| 64 | +kernel boot options like `root=live:<URL>` that already requires or enforces the |
| 65 | +network to be configured, but not all the kernel options |
| 66 | +(e.g., `inst.install_url`, `ip`) do so, therefore, to ensure the network is |
| 67 | +configured by dracut set `rd.neednet=1`. |
53 | 68 |
|
54 |
| -:::note If an explicit network configuration is given using the `ip=` parameter Agama will disable the NetworkManager DHCP autosetup when starting the installer and mark the nm-initrd-generator generated connections to be persisted after the installation by default. To disable the copy of network the `inst.copy_network=0` parameter is available. |
| 69 | +:::note |
| 70 | + |
| 71 | +If an explicit network configuration is given using the `ip=` parameter Agama |
| 72 | +will disable the NetworkManager DHCP autosetup when starting the installer |
| 73 | +and mark the nm-initrd-generator generated connections to be persisted after |
| 74 | +the installation by default. To disable the copy of network the |
| 75 | +`inst.copy_network=0` parameter is available. |
| 76 | + |
| 77 | +::: |
55 | 78 |
|
56 | 79 | ### DHCP configuration
|
57 | 80 |
|
@@ -88,10 +111,14 @@ Network will be configured by dracut only if really required so, kernel boot opt
|
88 | 111 |
|
89 | 112 | - `ifname=bootnet:AA:BB:CC:DD:EE:FF ip=bootnet:dhcp rd.neednet=1`
|
90 | 113 |
|
91 |
| -:::note Agama will persist the renamed interface after the installation |
92 |
| -through a systemd network link file. |
| 114 | +:::note |
| 115 | + |
| 116 | +Agama will persist the renamed interface after the installation through a |
| 117 | +systemd network link file. |
| 118 | + |
| 119 | +::: |
93 | 120 |
|
94 | 121 | ## PXE server documentation
|
95 | 122 |
|
96 |
| -For more information about setting up a PXE Boot Server on SUSE Linux Enterprise Server |
97 |
| -16.0 refer to [this guide](https://susedoc.github.io/doc-modular/main/html/SLES-PXE-server/). |
| 123 | +For more information about setting up a PXE Boot Server on SUSE Linux |
| 124 | +Enterprise Server 16.0 refer to [this guide](https://susedoc.github.io/doc-modular/main/html/SLES-PXE-server/). |
0 commit comments