forked from rocky-linux/documentation
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
rocky-linux#1867 fix markdown violation on custome-linux-kernal.md,mi…
…grate2rocky.md
- Loading branch information
1 parent
59d2fe7
commit 4f43991
Showing
2 changed files
with
26 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,11 +9,11 @@ update: 11-23-2021 | |
|
||
## Prerequisites and assumptions | ||
|
||
* CentOS Stream, CentOS, AlmaLinux, RHEL, or Oracle Linux running on a hardware server or VPS. Non-Stream CentOS is frozen at version 8.5. The current supported version of the other systems is 8.9 or 9.3. | ||
* A working knowledge of the command line | ||
* A working knowledge of SSH for remote machines | ||
* A mildly risk-taking attitude | ||
* Run commands as root. Either log in as root, or have the ability to elevate privileges with `sudo` | ||
- CentOS Stream, CentOS, AlmaLinux, RHEL, or Oracle Linux running on a hardware server or VPS. Non-Stream CentOS is frozen at version 8.5. The current supported version of the other systems is 8.9 or 9.3. | ||
- A working knowledge of the command line | ||
- A working knowledge of SSH for remote machines | ||
- A mildly risk-taking attitude | ||
- Run commands as root. Either log in as root, or have the ability to elevate privileges with `sudo` | ||
|
||
## Introduction | ||
|
||
|
@@ -23,13 +23,13 @@ For example, some server providers will not support Rocky Linux by default for a | |
|
||
Well, we have the tool for you: [migrate2rocky](https://github.com/rocky-linux/rocky-tools/tree/main/migrate2rocky). | ||
|
||
It is a script that, when run, will change out all of your repositories to those of Rocky Linux. Packages will install and upgrade or down-grade as necessary, and your operating system's branding will also change. | ||
It is a script that, when run, will change out all of your repositories to those of Rocky Linux. Packages will install and upgrade or down-grade as necessary, and your operating system's branding will also change. | ||
|
||
Do not worry, if you are new to systems administration, I will be keeping this as user friendly as possible. Well, as user friendly as the command line gets. | ||
|
||
### Caveats and warnings | ||
|
||
1. Do check out migrate2rocky's README page (linked above), because known clashes between the script and Katello's repositories exist. In time, we will probably discover (and eventually patch) more clashes and incompatibilities, so you will want to know about those, especially for production servers. | ||
1. Do check out migrate2rocky's README page (linked above), because known clashes between the script and Katello's repositories exist. In time, we will probably discover (and eventually patch) more clashes and incompatibilities, so you will want to know about those, especially for production servers. | ||
2. This script is most likely to work without incident on completely fresh installs. _If you want to convert a production server, **make a data backup and system snapshot, or do it in a staging environment first.**_ | ||
|
||
Are you ready? | ||
|
@@ -44,9 +44,12 @@ Download the compressed files from GitHub and extract the one you need (That wil | |
|
||
![The "Download Zip" button](images/migrate2rocky-github-zip.png) | ||
|
||
Then, upload the executable to your server with SSH by running this command on your local machine (note: if you're running a 9.x system, add a 9 before the `.sh`): | ||
Then, upload the executable to your server with SSH by running this command on your local machine: | ||
|
||
``` | ||
!!! Note | ||
If you're running a 9.x system, add a 9 before the `.sh` | ||
|
||
```bash | ||
scp PATH/TO/FILE/migrate2rocky.sh [email protected]:/home/ | ||
``` | ||
|
||
|
@@ -56,13 +59,13 @@ Adjust all the file paths and server domains or IP addresses as needed. | |
|
||
Install `git` on your server with: | ||
|
||
``` | ||
```bash | ||
dnf install git | ||
``` | ||
|
||
Then clone the rocky-tools repository with: | ||
|
||
``` | ||
```git | ||
git clone https://github.com/rocky-linux/rocky-tools.git | ||
``` | ||
|
||
|
@@ -72,25 +75,31 @@ Note: this method will download all of the scripts and files in the rocky-tools | |
|
||
This is probably the easiest way to obtain the script. You only need a suitable HTTP client (`curl`, `wget`, `lynx` and so on) installed on the server. | ||
|
||
Assuming you have the `curl` utility installed, run this command to download the script into whatever directory you are using (note: if you're running a 9.x system, add a 9 before the `.sh`): | ||
Assuming you have the `curl` utility installed, run this command to download the script into whatever directory you are using | ||
|
||
``` | ||
!!! Note | ||
If you're running a 9.x system, add a 9 before the `.sh` | ||
|
||
```bash | ||
curl https://raw.githubusercontent.com/rocky-linux/rocky-tools/main/migrate2rocky/migrate2rocky.sh -o migrate2rocky.sh | ||
``` | ||
|
||
That command will download the file straight to your server, and *only* the file you want. But again, security concerns suggest this is not necessarily the best practice, so keep that in mind. | ||
|
||
## Running the script and installation | ||
|
||
Use the `cd` command to switch to the directory where the script is, ensure the file is executable, and give the owner of the script file x permissions (note: iin the below commands, if you're running a 9.x system, add a 9 before the `.sh`). | ||
Use the `cd` command to switch to the directory where the script is, ensure the file is executable, and give the owner of the script file x permissions | ||
|
||
``` | ||
!!! Note | ||
In the below commands, if you're running a 9.x system, add a 9 before the `.sh` | ||
|
||
```bash | ||
chmod u+x migrate2rocky.sh | ||
``` | ||
|
||
And now, at long last, run the script: | ||
|
||
``` | ||
```bash | ||
./migrate2rocky.sh -r | ||
``` | ||
|
||
|