info/build-linux
1
0
Fork 0
mirror of https://github.com/MichielDerhaeg/build-linux.git synced 2025-09-03 13:12:40 +02:00
Code Issues Releases Wiki Activity

Typo seprate,seperate → separate

Browse Source
This commit is contained in:
Lilian Besson
2017-05-09 19:43:32 +02:00
committed by GitHub
parent 21b22a4b43
commit a2d802a19e
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -43,8 +43,8 @@ editor but it's much better to do it with an interface by doing ``make nconfig``
(this needs ``libncurses5-dev`` on Ubuntu) because it also deals with (this needs ``libncurses5-dev`` on Ubuntu) because it also deals with
dependencies of enabled features. Here you can enable/disable features dependencies of enabled features. Here you can enable/disable features
and device drivers with the spacebar. ``*`` means that it will be compiled in and device drivers with the spacebar. ``*`` means that it will be compiled in
your kernel image. ``M`` means it will be compiled inside a seprate kernel your kernel image. ``M`` means it will be compiled inside a separate kernel
module. This is a part of the kernel that will be put in a seperate file and can module. This is a part of the kernel that will be put in a separate file and can
be loaded in or out dynamically in the kernel when they are required. The default be loaded in or out dynamically in the kernel when they are required. The default
config will do just fine for basic stuff like running in a virtual machine. But config will do just fine for basic stuff like running in a virtual machine. But
in our case, we don't really want to deal with kernel modules so we'll just do 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
makes development and testing easier. makes development and testing easier.
So let's start by allocating a new file of size 100M by doing ``fallocate -l100M So let's start by allocating a new file of size 100M by doing ``fallocate -l100M
image``(some distro's don't have ``fallocate`` so you can do ``dd if=/dev/zero image``(some distros don't have ``fallocate`` so you can do ``dd if=/dev/zero
of=image bs=1M count=100`` instead). And then we format it like we would format of=image bs=1M count=100`` instead). And then we format it like we would format
a disk with ``fdisk image``. It automatically creates an MBR partition table for a disk with ``fdisk image``. It automatically creates an MBR partition table for
us and we'll create just one partition filling the whole image by pressing 'n' and 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
``inittab`` entry for it but this isn't very flexible. A better solution is to ``inittab`` entry for it but this isn't very flexible. A better solution is to
use ``runsvdir``. This runs ``runsv`` for every service in a directory. So use ``runsvdir``. This runs ``runsv`` for every service in a directory. So
running ``runsvdir /etc/init.d`` would do the trick but this way we can't running ``runsvdir /etc/init.d`` would do the trick but this way we can't
disable services at boot. To solve this issue we'll create a seperate directory disable services at boot. To solve this issue we'll create a separate directory
and symlink the enabled services in there. and symlink the enabled services in there.
```bash ```bash
$ mkdir -p /etc/rc.d $ mkdir -p /etc/rc.d
@@ -553,7 +553,7 @@ kern.* /var/log/kernel.log
$ sv down /etc/init.d/syslogd # restart $ sv down /etc/init.d/syslogd # restart
$ sv up /etc/init.d/syslogd $ sv up /etc/init.d/syslogd
``` ```
This will put everything the kernel has to say in a seperate log file This will put everything the kernel has to say in a separate log file
``/var/log/kernel.log``. But ``syslogd`` doesn't read the kernel logs like ``/var/log/kernel.log``. But ``syslogd`` doesn't read the kernel logs like
``rsyslog`` does. We need a different service for that. ``rsyslog`` does. We need a different service for that.
```bash ```bash