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

typos and stuff

Browse Source
This commit is contained in:
Michiel Derhaeg
2017-04-02 23:40:29 +02:00
parent a5340a48a4
commit cf1b64cbfe
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@@ -35,20 +35,20 @@ some build tools. Installing ``build-essential`` on Ubuntu (or ``base-devel`` on
Arch Linux) will almost give you everything you need. You'll also need to Arch Linux) will almost give you everything you need. You'll also need to
install ``bc`` for some reason. install ``bc`` for some reason.
The next step is configuring you build, inside the untarred directory you do The next step is configuring your build, inside the untarred directory you do
``make defconfig``. This will generate a default config for your currect ``make defconfig``. This will generate a default config for your current cpu
architecture and place it in ``.config``. You can edit it directly with a text architecture and put it in ``.config``. You can edit it directly with a text
editor but it's much better to do it with an interface by doing ``make nconfig`` editor but it's much better to do it with an interface by doing ``make nconfig``
(this needs ``libncurses5-dev`` on Ubuntu). Here you can enable/disable features (this needs ``libncurses5-dev`` on Ubuntu). 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 seprate kernel
module. Which is a part of the kernel that will be put in a seperate file and module. This is a part of the kernel that will be put in a seperate file and can
can be loaded in dynamically in the kernel when they are required. The default be loaded in 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
this: ``sed "s/=m/=y/" -i .config``. Building the kernel is now just running this: ``sed "s/=m/=y/" -i .config``. We're done, so we can simply do ``make`` to
``make``. Don't forget to add ``-jN`` with `N` the number of cores of this might build our kernel. Don't forget to add ``-jN`` with `N` the number of cores
take a while. because this might take a while.
Other useful/interesting ways to configure the kernel are: Other useful/interesting ways to configure the kernel are: