mirror of
git://slackware.nl/current.git
synced 2024-12-26 09:58:59 +01:00
5a12e7c134
Wed Aug 26 10:00:38 CDT 2009 Slackware 13.0 x86_64 is released as stable! Thanks to everyone who helped make this release possible -- see the RELEASE_NOTES for the credits. The ISOs are off to the replicator. This time it will be a 6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD. We're taking pre-orders now at store.slackware.com. Please consider picking up a copy to help support the project. Once again, thanks to the entire Slackware community for all the help testing and fixing things and offering suggestions during this development cycle. As always, have fun and enjoy! -P. |
||
---|---|---|
.. | ||
kernel-firmware | ||
kernel-generic | ||
kernel-huge | ||
kernel-modules | ||
2.6.29.x-intel-crash-patch.diff | ||
config-generic-2.6.29.6 | ||
config-huge-2.6.29.6 | ||
config-speakup-2.6.29.6 | ||
linux-2.6.29.6-01-sendpage.diff | ||
linux-2.6.29.6-02-default-mmap_min_addr-4096.diff | ||
linux-2.6.29.6.tar.sign | ||
README.TXT | ||
README_SECURITY.TXT | ||
README_SPEAKUP_PATCH.TXT |
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