mirror of
git://slackware.nl/current.git
synced 2024-12-26 09:58:59 +01:00
9664bee729
Wed Sep 26 01:10:42 UTC 2012 Slackware 14.0 x86_64 stable is released! We're perfectionists here at Slackware, so this release has been a long time a-brewing. But we think you'll agree that it was worth the wait. Slackware 14.0 combines modern components, ease of use, and flexible configuration... our "KISS" philosophy demands it. The ISOs are off to be replicated, a 6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD. Please consider supporting the Slackware project by picking up a copy from store.slackware.com. We're taking pre-orders now, and offer a discount if you sign up for a subscription. Thanks to everyone who helped make this happen. The Slackware team, the upstream developers, and (of course) the awesome Slackware user community. Have fun! :-) |
||
|---|---|---|
| .. | ||
| config-x86 | ||
| config-x86_64 | ||
| packaging-x86 | ||
| packaging-x86_64 | ||
| linux-3.2.29.tar.sign | ||
| README.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-3.2.29 > /usr/src/linux-3.2.29/.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