@@ -138,16 +138,16 @@ specific things.
138
138
Building the Disk Image
139
139
-----------------------
140
140
141
- Installing a OS on a file instead of a real disk complicates things but this
141
+ Installing an OS on a file instead of a real disk complicates things but this
142
142
makes development and testing easier.
143
143
144
144
So let's start by allocating a new file of size 100M by doing ``fallocate -l100M
145
145
image`` (some distro's don't have `` fallocate`` so you can do `` dd if=/dev/zero
146
146
of=image bs=1M count=100`` instead). And then we format it like we would format
147
- a disk with `` fdisk image `` . It automatically creates a MBR partition table for
147
+ a disk with `` fdisk image `` . It automatically creates an MBR partition table for
148
148
us and we'll create just one partition filling the whole image by pressing 'n' and
149
149
afterwards just use the default options for everything and keep spamming 'enter'
150
- untill you're done. Finally press 'w' exit and to write the changes to the
150
+ until you're done. Finally press 'w' exit and to write the changes to the
151
151
image.
152
152
``` bash
153
153
$ fdisk image
@@ -192,8 +192,8 @@ my case. Let's make a filesystem on it.
192
192
` ` ` bash
193
193
$ mkfs.ext4 /dev/loop0p1
194
194
` ` `
195
<
8000
td data-grid-cell-id="diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5-195-194-1" data-selected="false" role="gridcell" style="background-color:var(--diffBlob-deletionNum-bgColor, var(--diffBlob-deletion-bgColor-num));text-align:center" tabindex="-1" valign="top" class="focusable-grid-cell diff-line-number position-relative left-side">
- If you want to use something else than ext4, be sure to enable it when
196
- configuring your kernel. Now that we have done that, we can mount it start
195
+ If you want to use something other than ext4, be sure to enable it when
196
+ configuring your kernel. Now that we have done that, we can mount it and start
197
197
putting everything in place.
198
198
` ` ` bash
199
199
$ mkdir image_root
@@ -218,7 +218,7 @@ We'll copy our binaries over.
218
218
$ cp /path/to/busybox usr/bin/busybox
219
219
$ cp /path/to/bzImage boot/bzImage
220
220
```
221
- You can call every busybox utility by supplying the utility as argument, like
221
+ You can call every busybox utility by supplying the utility as an argument, like
222
222
so: ``busybox ls --help``. But busybox also detects by what name it is called
223
223
and then executes that utility. So you can put symlinks for each utility and
224
224
busybox can figure out which utility you want by the symlink' s name.
@@ -232,7 +232,7 @@ These symlinks might be incorrect from outside the system because of the
232
232
absolute path, but they work just fine from within the booted system.
233
233
234
234
Lastly, we' ll copy some files from ``../filesystem`` to the image that will be
235
- some use to us later.
235
+ of some use to us later.
236
236
```bash
237
237
$ cp ../filesystem/{passwd,shadow,group,issue,profile,locale.sh,hosts,fstab} etc
238
238
$ install -Dm755 ../filesystem/simple.script usr/share/udhcpc/default.script
0 commit comments