diff options
| author | David P <megver83@parabola.nu> | 2018-05-18 21:41:48 -0400 |
|---|---|---|
| committer | David P <megver83@parabola.nu> | 2018-05-18 21:41:48 -0400 |
| commit | ba31b0c5c1a7fd41eea1c78dfb63af3d13654f4b (patch) | |
| tree | 5de32bd2617712821158450f366a0e95f8ebde8a | |
Initial import
Just add a README for now
Signed-off-by: David P <megver83@parabola.nu>
| -rw-r--r-- | README.md | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/README.md b/README.md new file mode 100644 index 0000000..430a171 --- /dev/null +++ b/README.md @@ -0,0 +1,16 @@ +## FAQ +### What is this? +A README file + +### No seriously, what's deblob-config? +It is a collection of scripts which edit, using `sed`, a specified kernel configuration file for the version you choose, no matter the architecture. It disables CONFIG lines known to work only with blobs, making the compilation a bit slower and showing annoying "/\*(DEBLOBBED)*/" messages in the kernel log (yes, the kernel log from `dmesg`, **not** the build log). + +### Is it necessary to maintain this? Why does not Parabola manually changes their kernel config files? +We want to diverge as little as possible from Arch kernel configs, which are made for a blobbed Linux kernel. It is easier to "deblob" their configs (I say "deblob" with "" because it's not real deblobbing, just disabling blob's configs) than copy-pasting their changes or even applying them as patches, which may conflict with our changes. + +## Contributing +If you wish to do a request, report a bug, send feedback, etc. you can contact us on our usual channels: + + * https://labs.parabola.nu + * irc://freenode.net/#parabola + * mailto:dev@lists.parabola.nu |