diff --git a/.github/workflows/docbook.yml b/.github/workflows/docbook.yml index 956b3d2471..31830f2fc6 100644 --- a/.github/workflows/docbook.yml +++ b/.github/workflows/docbook.yml @@ -21,7 +21,7 @@ jobs: allow-build: ${{ steps.select-dc-build.outputs.allow-build }} relevant-branches: ${{ steps.select-dc-build.outputs.relevant-branches }} steps: - - uses: actions/checkout@v3 + - uses: actions/checkout@v4 - name: Checking basic soundness of DC files uses: openSUSE/doc-ci@gha-select-dcs @@ -50,7 +50,7 @@ jobs: matrix: dc-files: ${{ fromJson(needs.select-dc-files.outputs.validate-list) }} steps: - - uses: actions/checkout@v3 + - uses: actions/checkout@v4 - name: Validating DC file(s) ${{ matrix.dc-files }} uses: openSUSE/doc-ci@gha-validate with: @@ -68,14 +68,14 @@ jobs: matrix: dc-files: ${{ fromJson(needs.select-dc-files.outputs.build-list) }} steps: - - uses: actions/checkout@v3 + - uses: actions/checkout@v4 - name: Building DC file(s) ${{ matrix.dc-files }} id: build-dc uses: openSUSE/doc-ci@gha-build with: dc-files: ${{ matrix.dc-files }} - name: Uploading builds as artifact - uses: actions/upload-artifact@v3 + uses: actions/upload-artifact@v4 with: name: ${{ steps.build-dc.outputs.artifact-name }} path: ${{ steps.build-dc.outputs.artifact-dir }}/* @@ -89,7 +89,7 @@ jobs: continue-on-error: true steps: - name: Downloading all build artifacts - uses: actions/download-artifact@v3 + uses: actions/download-artifact@v4 with: path: artifact-dir - name: Publishing builds on susedoc.github.io diff --git a/xml/aarch64_inst_problem.xml b/xml/aarch64_inst_problem.xml index 272a85b502..3d02bafb02 100644 --- a/xml/aarch64_inst_problem.xml +++ b/xml/aarch64_inst_problem.xml @@ -104,6 +104,35 @@ + + Remote installation using an IPMI console + + When installing remotely using an IPMI console, you may face problems with the installation. + To fix the problems and install &productnameshort;, proceed as follows: + + + + + Press e during the start of the installer to enter the GRUB menu. + + + + + Replace splash=silent with ConsoleDevice=/dev/tty1. + + + + + Continue to boot with x or F10. Press F1 to launch the installer in a terminal window. + + + + + When installing &productnameshort; using &pxename; network boot, add the following parameter + to the kernel parameter list: + + console=tty + diff --git a/xml/ay_erb_templates.xml b/xml/ay_erb_templates.xml index f944229698..e2c5819eb0 100644 --- a/xml/ay_erb_templates.xml +++ b/xml/ay_erb_templates.xml @@ -404,14 +404,14 @@ Configure the connected network cards <interfaces t="list"> - <% with_link = netword_cards.sort_by { |n| n[:name] }.find { |n| n[:link] } %> + <% with_link = network_cards.sort_by { |n| n[:name] }.find { |n| n[:link] } %> <% if with_link %> <interface> <device><%= with_link[:device] %></device> <startmode>auto</startmode> <bootproto>dhcp</bootproto> </interface> - <% end > + <% end %> </interfaces> diff --git a/xml/bootconcept.xml b/xml/bootconcept.xml index c91d642ae5..2daae22774 100644 --- a/xml/bootconcept.xml +++ b/xml/bootconcept.xml @@ -278,41 +278,13 @@ when you need to regenerate an initramfs manually: - - - - - - - - - - - - - - - - - - - - - - - - - - Adding drivers because of hardware changes - If you need to change hardware (for example, hard disks), and this + If you need to change hardware, for example, hard disks, and this hardware requires different drivers to be in the kernel at boot time, you must update the initramfs file. @@ -383,6 +355,21 @@ + + Adding or removing swap devices, re-creating swap area + + + Whenever you add or remove a swap device, or re-create a swap area + with a different UUID, update the initramfs as + outlined in . You may also + need to update variables that + include the option in + /etc/default/grub, and then regenerate + /boot/grub2/grub.cfg as outlined in . + + + diff --git a/xml/deployment_images_ignition.xml b/xml/deployment_images_ignition.xml index 9f44dbc519..80382ffb27 100644 --- a/xml/deployment_images_ignition.xml +++ b/xml/deployment_images_ignition.xml @@ -141,8 +141,7 @@ The storage attribute is used to configure partitions, RAID, define file systems, create files, etc. To define partitions, use the disks attribute. The - filesystem attribute is used to format partitions - and define mount points of particular partitions. The + filesystem attribute is used to format partitions. The files attribute can be used to create files in the file system. Each of the mentioned attributes is described in the following sections. @@ -286,6 +285,13 @@ storage: The <literal>filesystem</literal> attribute + + &ignition; does not perform modifications to mount units + + The file system attribute does not modify mount units. If you add a new partition or remove an + existing partition, you must manually adjust the mount units. + + filesystem must contain the following attributes: diff --git a/xml/storage_filesystems.xml b/xml/storage_filesystems.xml index b9b36d86c8..969335c69f 100644 --- a/xml/storage_filesystems.xml +++ b/xml/storage_filesystems.xml @@ -2109,12 +2109,12 @@ The file system has the following characteristics: - - - ufs + + + ufs - + Used by BSD, SunOS and NextStep. Only supported in read-only mode. @@ -2166,36 +2166,7 @@ The file system has the following characteristics: mount: /mnt/mx: unknown filesystem type 'minix' (hint: possibly blacklisted, see mount(8)). - - To enable the mounting of the file system, you need to remove the particular - file system from the blocklist. Each blocked file system has its own - configuration file, for example, for efs it is - /lib/modules.d/60-blacklist_fs-efs.conf. However, do - not edit these files, as they are overwritten whenever the package - suse-module-tools is updated. To allow automatic mounting - of the blocked file system, you have the following options: - - - - - - Create a symbolic link to /dev/null, for example, for - the efs file system: - -&prompt.sudo;ln -s /dev/null /etc/modules.d/60-blacklist_fs-efs.conf - - - - Copy the configuration file to /etc/modprobe.d: - -&prompt.sudo;cp /lib/modules.d/60-blacklist_fs-efs.conf /etc/modprobe.d/60-blacklist_fs-efs.conf - - And comment the following statement in the configuration file: - -# blacklist omfs - - - + Even though a file system cannot be mounted automatically, you can load the corresponding kernel module for the file system directly using @@ -2213,13 +2184,55 @@ The file system has the following characteristics: unblacklist: loading cramfs file system module unblacklist: Do you want to un-blacklist cramfs permanently (<y>es/<n>o/n<e>ver)? y unblacklist: cramfs un-blacklisted by creating /etc/modprobe.d/60-blacklist_fs-cramfs.conf - - - If you select yes, the modprobe - command calls a script that creates a symbolic link from the configuration - file of the provided file system to /dev/null. Thus, - the file system is removed from the blocklist. - + + Here you have the following options: + + + + yes + + + The module will be loaded and removed from the blacklist. Therefore, the module will be + loaded automatically in future without any other prompt. + + + The configuration file /etc/modprobe.d/60-blacklist_fs-${MODULE}.conf is + created. Remove the file to undo the changes you performed. + + + + + no + + + The module will be loaded, but it is not removed from the blacklist. Therefore, on a next + module loading + you will see the prompt above again. + + + + + ever + + + The module will be loaded, but autoloading is disabled even for future use, and the prompt + will no longer be displayed. + + + The configuration file /etc/modprobe.d/60-blacklist_fs-${MODULE}.conf is + created. Remove the file to undo the changes you performed. + + + + + c + + + This option is used to interrupt the module loading. + + + + Large file support in Linux