mirror of
git://slackware.nl/current.git
synced 2024-12-28 09:59:53 +01:00
76fc4757ac
Mon Nov 4 17:08:47 UTC 2013 Slackware 14.1 x86_64 stable is released! It's been another interesting release cycle here at Slackware bringing new features like support for UEFI machines, updated compilers and development tools, the switch from MySQL to MariaDB, and many more improvements throughout the system. Thanks to the team, the upstream developers, the dedicated Slackware community, and everyone else who pitched in to help make this release a reality. 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. Have fun! :-) |
||
---|---|---|
.. | ||
config-x86 | ||
config-x86_64 | ||
packaging-x86 | ||
packaging-x86_64 | ||
linux-3.10.17.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.10.17 > /usr/src/linux-3.10.17/.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