8000 Typo seprate,seperate → separate · corenoob/build-linux@a2d802a · GitHub
[go: up one dir, main page]

Skip to content

Commit a2d802a

Browse files
authored
Typo seprate,seperate → separate
1 parent 21b22a4 commit a2d802a

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -43,8 +43,8 @@ editor but it's much better to do it with an interface by doing ``make nconfig``
4343
(this needs ``libncurses5-dev`` on Ubuntu) because it also deals with
4444
dependencies of enabled features. Here you can enable/disable features
4545
and device drivers with the spacebar. ``*`` means that it will be compiled in
46-
your kernel image. ``M`` means it will be compiled inside a seprate kernel
47-
module. This is a part of the kernel that will be put in a seperate file and can
46+
your kernel image. ``M`` means it will be compiled inside a separate kernel
47+
module. This is a part of the kernel that will be put in a separate file and can
4848
be loaded in or out dynamically in the kernel when they are required. The default
4949
config will do just fine for basic stuff like running in a virtual machine. But
5050
in our case, we don't really want to deal with kernel modules so we'll just do
@@ -144,7 +144,7 @@ Installing an OS on a file instead of a real disk complicates things but this
144144
makes development and testing easier.
145145

146146
So let's start by allocating a new file of size 100M by doing ``fallocate -l100M
147-
image``(some distro's don't have ``fallocate`` so you can do ``dd if=/dev/zero
147+
image``(some distros don't have ``fallocate`` so you can do ``dd if=/dev/zero
148148
of=image bs=1M count=100`` instead). And then we format it like we would format
149149
a disk with ``fdisk image``. It automatically creates an MBR partition table for
150150
us and we'll create just one partition filling the whole image by pressing 'n' and
@@ -526,7 +526,7 @@ To make sure that our new service is started at boot we could create a new
526526
``inittab`` entry for it but this isn't very flexible. A better solution is to
527527
use ``runsvdir``. This runs ``runsv`` for every service in a directory. So
528528
running ``runsvdir /etc/init.d`` would do the trick but this way we can't
529-
disable services at boot. To solve this issue we'll create a seperate directory
529+
disable services at boot. To solve this issue we'll create a separate directory
530530
and symlink the enabled services in there.
531531
```bash
532532
$ mkdir -p /etc/rc.d
@@ -553,7 +553,7 @@ kern.* /var/log/kernel.log
553553
$ sv down /etc/init.d/syslogd # restart
554554
$ sv up /etc/init.d/syslogd
555555
```
556-
This will put everything the kernel has to say in a seperate log file
556+
This will put everything the kernel has to say in a separate log file
557557
``/var/log/kernel.log``. But ``syslogd`` doesn't read the kernel logs like
558558
``rsyslog`` does. We need a different service for that.
559559
```bash

0 commit comments

Comments
 (0)
0