From ed0b7e0494a8a491240b450af2b69c15909755d0 Mon Sep 17 00:00:00 2001
From: toloveru <mdr1996@live.be>
Date: Wed, 5 Apr 2017 21:11:23 +0200
Subject: [PATCH] Add instructions to create config file

---
 .install.swp | Bin 12288 -> 0 bytes
 README.md    |  16 +++++++++++++++-
 2 files changed, 15 insertions(+), 1 deletion(-)
 delete mode 100644 .install.swp

diff --git a/.install.swp b/.install.swp
deleted file mode 100644
index 1e135853c3953615fbdfc68eec20338dd250a69e..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001

literal 12288
zcmeI&&ubJh6bJCslL)J#|G?|)p)Kf4wHLvQqM|MJsCW=$HuKgAn@NTwqYU`t9}qA8
z8U97$P5L*8N0Z&zx^AJ;W91uoge5P@%Ln$b?3?U9-+xMX@?8<fRUx)M{dkdG{5<-$
zCxo=7vMw#0J}UOJVB6D^;_8RRfyF~ByM|5h#bXtU89T#T)+}d*GCq`A|MMgyKmY<~
z7Z{1X+qdRl^>MaI*RMT0`w`dy0SG_<0uX=z1Rwwb2%KAi&~Av2vHA<c3oZ@w#@al5
z!~_8dKmY;|fB*y_009U<00Izzz&R8sD<O_XLTq1-#mE2um%smiUJ>GZjIS}?$9NLs
zSIqem!^Sv>k@jrGz<>Y*AOHafKmY;|fB*y_0D=EUpmoZGDP{YM4(&21Ye?Fr)f_l~
zX)@uv%98JW;6?^bY|4pdlFk~%xo7uANnTHi-QF&&=Pa*!lul6Q^{`Gp_J~)VW|yb?
zXiSG3s9~BJ`<B#{dfQRwnY?W{)M+DY&o`(v)v}tVG+pd3?{l#|FE>>e$_d@ncZp?f
zDZ5wO&gq_t&bvZeS?a=1lv(Xk&uE9<(ck;UvgrF&m2MtR8J<nS&L6S%goTD|$=IN#
q{i|5niF^Mn9cQmJ%%4bKSvxN2fo=O#(^P5pb2~BKEYhQVEq((kchBPh

diff --git a/README.md b/README.md
index d545a63..d7ba02d 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,21 @@ Ever thought of compiling a custom kernel, but held back because of the need for
 
 ### Installation
 1. Clone and navigate to the repository, then run `./install`
-2. Copy your existing kernel .config file to `/root/.config/kernel/.config`. If you don't know how to create this file, this tool probably isn't for you.
+2. Copy your existing kernel .config file to `/root/.config/kernel/.config`.
+
+### Gee, I don't have my own .config file. How can I create one?
+The easiest approach (and the one that I used as well), is using the assistance of the [Arch Wiki](https://wiki.archlinux.org/index.php/Kernels/Traditional_compilation).
+So, in a nutshell:
+1. Grab the kernel source from [kernel.org](https://kernel.org) and its signature, and put it in a kernel build directory.
+2. Unpack the archive using `unxz linux-*.*.*.tar.xz` (replace the wildcards with the version number). This will return you a .tar file.
+3. Verify the tarball by running `gpg2 --verify linux-*.*.*.tar.sign`
+4. Receive the keys if required with `gpg2 --recv-keys KEY_ID` (for more info check on [kernel.org](https://www.kernel.org/category/signatures.html)) and verify again.
+5. Unpack the tarball using `tar xf linux-*.*.*.tar`
+6. Change directory to linux-*.*.*
+7. Clean up the kernel directory using `make clean && make mrproper`.
+8. Run `make localmodconfig` to get a basic configuration file.
+9. You can add more features like NTFS support, AppArmor, kernel hardening etc. using `make nconfig` and navigating to the respective configuration menus.
+10. Don't forget to copy the config file to /root/.config/kernel/.config!
 
 ### This script runs as root. Isn't that unsafe?
 In a non-interactive script, it's much easier to run priveleged by default and drop priveleges as needed, instead of requiring authentication every time. If you know of a fully non-interactive way of achieving on-the-fly enhanced priveleges though, feel free to open a pull request.