Controls/gitea-pages
0
2
Fork 0
Code Pull Requests Actions Activity

cleanup broken links

Browse Source
This commit is contained in:
ebner
2024-08-08 17:47:02 +02:00
parent b2ea60f678
commit dd00c21e41
4 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
admin-guide/deployment/rhel9/installation.md
+1 -1
View File
@@ -6,7 +6,7 @@
## Network Installation
The machine you want to install needs to be [registered in `sysdb`](../admin-guide/deployment/sample). If you don't have the bob command installed locally you can login to __lxsup.psi.ch__ to use it. Remember that you need a valid Kerberos ticket before modifying a sysdb entry via `bob`.
The machine you want to install needs to be [registered in `sysdb`](../basic_installation.md). If you don't have the bob command installed locally you can login to __lxsup.psi.ch__ to use it. Remember that you need a valid Kerberos ticket before modifying a sysdb entry via `bob`.
More details regaring `bob` can be found [here](https://git.psi.ch/linux-infra/bob).
Optional you can set `netboot` and RHEL 9 installer but that can also be selected manually in be boot menu:
admin-guide/guidelines.md
+3 -3
View File
@@ -39,7 +39,7 @@ It is in the responsibilty of the owner/administrator of a system to care about
By default once a week (in the night from Sunday to Monday) security updates are automatically applied. Other updates, including Kernel updates, need to be installed manually.
This is [configurable](configuration/package_updates), you may switch it off completely, make it run daily or make it install all updates.
This is [configurable](configuration/package_updates.md), you may switch it off completely, make it run daily or make it install all updates.
Reboots are never done automatically.
@@ -47,8 +47,8 @@ Also for software which have been installed from other sources than RPM package
### Snapshots
On specially protected systems where stability is more important than being up-to-date, there is the option to freeze the provided RPM package version to a specified date. Also this can be [configured in Hiera](configuration/package_repositories)(chapter "Using Specific Package Repository Snapshot"). If such a system is set by such a "Repo Tag" to a specific snapshot, the update procedure cannot get newer than the given state.
On specially protected systems where stability is more important than being up-to-date, there is the option to freeze the provided RPM package version to a specified date. Also this can be [configured in Hiera](configuration/package_repositories.md)(chapter "Using Specific Package Repository Snapshot"). If such a system is set by such a "Repo Tag" to a specific snapshot, the update procedure cannot get newer than the given state.
Again, this should only be done for nodes in protected networks, e.g. with access restrictions through an [ssh gateway](../services-admin-guide/ssh_gateways) and requires consent with IT Security.
Again, this should only be done for nodes in protected networks, e.g. with access restrictions through an [ssh gateway](../services/admin-guide/ssh_gateways.md) and requires consent with IT Security.