You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* remove some of the more playful language as this is not necessarily a beginners document
* retain the author's voice as much as possible
* remove conjunctions in place of words
* ensure all headings use sentence style capitalization
* replace passive voice phrases
Copy file name to clipboardExpand all lines: docs/guides/migrate2rocky.md
+29-29Lines changed: 29 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,56 +5,56 @@ contributors: tianci li, Steven Spencer
5
5
update: 11-23-2021
6
6
---
7
7
8
-
# How to Migrate to Rocky Linux from CentOS Stream, CentOS, Alma Linux, RHEL, or Oracle Linux
8
+
# How to migrate to Rocky Linux from CentOS Stream, CentOS, Alma Linux, RHEL, or Oracle Linux
9
9
10
-
## Prerequisites & Assumptions
10
+
## Prerequisites and assumptions
11
11
12
12
* CentOS Stream, CentOS, Alma Linux, RHEL, or Oracle Linux running well on a hardware server or VPS. The current supported version for each of these is 8.8 or 9.2.
13
-
* A working knowledge of the command line.
14
-
* A working knowledge of SSH for remote machines.
15
-
* A mildly risk-taking attitude.
16
-
*All commands should be run as root. Either log in as root, or get ready to type "sudo" a lot.
13
+
* A working knowledge of the command line
14
+
* A working knowledge of SSH for remote machines
15
+
* A mildly risk-taking attitude
16
+
*Run commands as root. Either log in as root, or have the ability to elevate privileges with `sudo`.
17
17
18
18
## Introduction
19
19
20
-
In this guide, you'll learn how to convert all of the OSes listed above to fully functional Rocky Linux installs. This is probably one of the most roundabout ways of installing Rocky Linux, but it'll come in handy for people in a variety of situations.
20
+
In this guide, you will learn how to convert all the above OSes to fully functional Rocky Linux installs. This is probably one of the most roundabout ways of installing Rocky Linux, but it will come in handy for people in a variety of situations.
21
21
22
-
For example, some server providers won't support Rocky Linux by default for a while. Or you may have a production server that you want to convert to Rocky Linux without reinstalling everything.
22
+
For example, some server providers will not support Rocky Linux by default for a while. Or you may have a production server that you want to convert to Rocky Linux without reinstalling everything.
23
23
24
-
Well, we've got the tool for you: [migrate2rocky](https://github.com/rocky-linux/rocky-tools/tree/main/migrate2rocky).
24
+
Well, we have the tool for you: [migrate2rocky](https://github.com/rocky-linux/rocky-tools/tree/main/migrate2rocky).
25
25
26
-
It's a script that, when executed, will change out all of your repositories to those of Rocky Linux. Packages will be installed and upgraded/downgraded as necessary, and all of your OS' branding will change too.
26
+
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 OS's branding will also change.
27
27
28
-
Don't worry, if you're new to systems administration, I'll be keeping this as user-friendly as possible. Well, as user friendly as the command line gets.
28
+
Do not worry, if you are new to systems administration, I will be keeping this as userfriendly as possible. Well, as user friendly as the command line gets.
29
29
30
30
### Caveats and warnings
31
31
32
-
1. Do check out migrate2rocky's README page (linked above), because there is a known clash between the script and Katello's repositories. In time, it's probable that we'll discover (and eventually patch) more clashes and incompatibilities, so you'll want to know about those, especially for production servers.
33
-
2. This script is most likely to work without incident on completely fresh installs. _If you want to convert a production server, for the love of all that is holy and good, **make a data backup and system snapshot, or do it in a staging environment first.**_
32
+
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.
33
+
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.**_
34
34
35
-
Okay? We ready? Let's do this.
35
+
Are you ready?
36
36
37
37
## Prepare your server
38
38
39
-
You'll need to grab the actual script file from the repository. This can be done in a number of ways.
39
+
You will need to grab the actual script file from the repository. You can do this several ways.
40
40
41
41
### The manual way
42
42
43
-
Download the compressed files from GitHub and extract the one you need (That'd be *migrate2rocky.sh*). You can find zip files for any GitHub repo on the right-ish side of the repo's main page:
43
+
Download the compressed files from GitHub and extract the one you need (That will be *migrate2rocky.sh*). You can find zip files for any GitHub repository on the right-ish side of the repositorie's main page:
Just, you know, adjust all the file paths and server domains or IP addresses as needed.
53
+
Adjust all the file paths and server domains or IP addresses as needed.
54
54
55
-
### The git way
55
+
### The `git` way
56
56
57
-
Install git on your server with:
57
+
Install `git` on your server with:
58
58
59
59
```
60
60
dnf install git
@@ -70,42 +70,42 @@ Note: this method will download all of the scripts and files in the rocky-tools
70
70
71
71
### The easy way
72
72
73
-
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.
73
+
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.
74
74
75
-
Assuming you have the `curl` utility installed, run this command to download the script into whatever directory you're using:
75
+
Assuming you have the `curl` utility installed, run this command to download the script into whatever directory you are using:
That command will download the file straight to your server, and *only* the file you want. But again, there are security concerns that suggest this isn't necessarily the best practice, so keep that in mind.
81
+
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.
82
82
83
-
## Execution scripts and installation
83
+
## Running the script and installation
84
84
85
-
Use the `cd` command to switch to the directory where the script is located, make sure the file is executable and give the owner of the script file x permissions.
85
+
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.
86
86
87
87
```
88
88
chmod u+x migrate2rocky.sh
89
89
```
90
90
91
-
And now, at long last, execute the script:
91
+
And now, at long last, run the script:
92
92
93
93
```
94
94
./migrate2rocky.sh -r
95
95
```
96
96
97
97
That "-r" option tells the script to just go ahead and install everything.
98
98
99
-
If you've done everything right, your terminal window should look a bit like this:
99
+
If you have done everything right, your terminal window will look a bit like this:
Now, it'll take the script a while to convert everything, depending on the actual machine/server, and the connection it has to the wider internet.
103
+
Now, it will take the script a while to convert everything, depending on the actual machine, and the connection it has to the wider internet.
104
104
105
105
If you see a **Complete!** message at the end, then everything is fine and you can restart the server.
106
106
107
107
108
108
109
-
Give it some time, log back in, and you should have a fancy schmancy new Rocky Linux server to play wi... I mean do very serious work on. Run the `hostnamectl` command to check that your OS was migrated properly, and you're good to go.
109
+
Give it some time, log back in, and you should have a new Rocky Linux server. Run the `hostnamectl` command to check that your OS migrated properly, and you are good.
110
110
111
111
0 commit comments