Skip to content

Commit 6787787

Browse files
authored
Editing iso_creation.md (#2539)
* create directory "isos" and use git mv to move `iso_creation.md` to the "isos" folder * rm the author created "ISOs" directory * replace passive voice with active throughout * add in fenced code block context descriptions * some other minor corrections
1 parent ef63fe0 commit 6787787

File tree

2 files changed

+31
-15
lines changed

2 files changed

+31
-15
lines changed

docs/guides/.pages

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,3 @@
1-
---
21
nav:
32
- ... | index*.md
43
- ... | installation*.md
@@ -21,8 +20,10 @@ nav:
2120
- File Sharing Services: file_sharing
2221
- Hardware: hardware
2322
- Interoperability: interoperability
23+
- ISOs: isos
2424
- Kernel: kernel
2525
- Mirror Management: mirror_management
2626
- Network: network
2727
- Package Management: package_management
2828
- ...
29+

docs/guides/ISOs/iso_creation.md renamed to docs/guides/isos/iso_creation.md

Lines changed: 29 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Creating a Custom Rocky Linux ISO
33
author: Howard Van Der Wal
4-
contributors:
4+
contributors: Steven Spencer
55
tested with: 9.5
66
tags:
77
- create
@@ -11,7 +11,7 @@ tags:
1111

1212
## Introduction
1313

14-
Creating a custom ISO may be required for a litany of reasons. Perhaps you want to make a change to the boot process, add specific packages or update a configuration file.
14+
You might need to Create a custom ISO for a many reasons. Perhaps you want to make a change to the boot process, add specific packages, or update a configuration file.
1515

1616
This guide will instruct you from start to finish on how to build your own Rocky Linux ISO.
1717

@@ -20,23 +20,27 @@ This guide will instruct you from start to finish on how to build your own Rocky
2020
* A 64 bit machine running Rocky Linux 9 to build the new ISO image.
2121
* A Rocky Linux 9 DVD ISO image.
2222
* A `kickstart` file to apply to the ISO.
23-
* Read the Lorax [Quickstart](https://weldr.io/lorax/lorax.html#quickstart) and [mkksiso](https://weldr.io/lorax/mkksiso.html) documentation to become famililar with how the `Anaconda` `boot.iso` is created.
23+
* Read the Lorax [Quickstart](https://weldr.io/lorax/lorax.html#quickstart) and [mkksiso](https://weldr.io/lorax/mkksiso.html) documentation to become familiar with how to create the `Anaconda` `boot.iso`.
2424

2525
## Package installation and setup
2626

2727
* Install the `lorax` package:
28-
```
28+
29+
```bash
2930
sudo dnf install -y lorax
3031
```
3132

3233
## Building the ISO with a kickstart file
3334

3435
* Run the `mkksiso` command to add a `kickstart` file and then build a new ISO:
35-
```
36+
37+
```bash
3638
mkksiso --ks <PATH_TO_KICKSTART_FILE> <PATH_TO_ISO_TO_MODIFY> <OUTPUT_PATH_FOR_BUILT_ISO>
3739
```
40+
3841
* Below is an example `kickstart` file `example-ks.cfg`, which sets up a Rocky Linux 9.5 `Server With GUI` environment:
39-
```
42+
43+
```bash
4044
lang en_GB
4145
keyboard --xlayouts='us'
4246
timezone Asia/Tokyo --utc
@@ -57,27 +61,36 @@ firewall --enabled
5761

5862
## Adding a repository with its packages to an ISO image
5963

60-
* Make sure the repository you want to add has the `repodata` directory inside of it. If not, this can be created using the `createrepo_c` command and this can be installed with `sudo dnf install -y createrepo_c`
64+
* Make sure the repository you want to add has the `repodata` directory inside of it. If not, you can create this using the `createrepo_c` command and install it with `sudo dnf install -y createrepo_c`
6165
* Add the repository to your `kickstart` file, using the following syntax:
62-
```
66+
67+
```bash
68+
6369
repo --name=extra-repo --baseurl=file:///run/install/repo/<YOUR_REPOSITORY>/
6470
```
71+
6572
* Add your repository using the `--add` flag with the `mkksiso` tool:
66-
```
73+
74+
```bash
6775
mkksiso --add <LINK_TO_YOUR_REPOSITORY> --ks <PATH_TO_KICKSTART_FILE> <PATH_TO_ISO_TO_MODIFY> <OUTPUT_PATH_FOR_BUILT_ISO>
6876
```
6977

70-
* The process is detailed further using the `baseos` repository in the example below:
78+
* You can see additional details of this process using the `baseos` repository in the example below
7179
* The `base os` repository will be locally downloaded along with all of its packages:
72-
```
80+
81+
```bash
7382
dnf reposync -p ~ --download-metadata --repo=baseos
7483
```
84+
7585
* Then add the repository to the `kickstart` file:
76-
```
86+
87+
```bash
7788
repo --name=extra-repo --baseurl=file:///run/install/repo/baseos/
7889
```
90+
7991
* The `kickstart` file would look like the following:
80-
```
92+
93+
```bash
8194
lang en_GB
8295
keyboard --xlayouts='us'
8396
timezone Asia/Tokyo --utc
@@ -96,8 +109,10 @@ firewall --enabled
96109
repo --name=extra-repo --baseurl=file:///run/install/repo/baseos/
97110
%end
98111
```
112+
99113
* Then point the `mkksiso` command directly to the repository directory and build the ISO:
100-
```
114+
115+
```bash
101116
mkksiso --add ~/baseos --ks example-ks.cfg ~/Rocky-9.5-x86_64-dvd.iso ~/Rocky-9.5-x86_64-dvd-new.iso
102117
```
103118

0 commit comments

Comments
 (0)