mirror of
git://slackware.nl/current.git
synced 2025-01-30 08:38:10 +01:00
d31c50870d
Thu Jun 30 20:26:57 UTC 2016 Slackware 14.2 x86_64 stable is released! The long development cycle (the Linux community has lately been living in "interesting times", as they say) is finally behind us, and we're proud to announce the release of Slackware 14.2. The new release brings many updates and modern tools, has switched from udev to eudev (no systemd), and adds well over a hundred new packages to 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! :-)
40 lines
1.2 KiB
Text
40 lines
1.2 KiB
Text
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 4.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-4.4.14 > /usr/src/linux-4.4.14/.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
|
|
|