summaryrefslogtreecommitdiffstats
path: root/source/k/README.TXT
diff options
context:
space:
mode:
Diffstat (limited to 'source/k/README.TXT')
-rw-r--r--source/k/README.TXT40
1 files changed, 40 insertions, 0 deletions
diff --git a/source/k/README.TXT b/source/k/README.TXT
new file mode 100644
index 000000000..13cdcb71d
--- /dev/null
+++ b/source/k/README.TXT
@@ -0,0 +1,40 @@
+Since I should document this somewhere, here's the procedure
+for building the Slackware kernel package. I do not patch the official
+kernel sources, but it's not exactly a virgin either.
+
+=============================================================
+Version specific notes (if any):
+=============================================================
+
+For a 2.6.x kernel (much easier):
+
+ Untar Linus' source in /usr/src.
+ Make all files owned by root:root with reasonable perms.
+ Install a suitable .config, or use make menuconfig, etc.
+
+ An example would be to use one of the config files here:
+ # cat config-generic-2.6.29.6 > /usr/src/linux-2.6.29.6/.config
+
+ Then run the build programs:
+
+ make oldconfig
+ make bzImage
+ make clean
+ make prepare
+ rm .version
+
+That's it! You now have a clean Slackware-configured Linux source
+tree.
+
+The kernel in Slackware supports SMP. With as common as
+multicore CPUs and SMP boards have become, this seemed like the
+obvious choice. The kernels are probably better for single CPU
+machines, too, if they will run them.
+
+At this point if you are running huge.s or generic.s, you should have
+no problems building kernel modules.
+
+Have fun! :-)
+
+Pat
+