Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
howtos:slackware_admin:kernelbuilding [2012/10/01 17:12 (UTC)] – capitalized the "S" in "source" (title) tommyc | howtos:slackware_admin:kernelbuilding [2018/03/05 20:52 (UTC)] – spelling bifferos |
---|
Changing the "''linux''" symbolic link is safe to do. No applications will break if you let it point to another kernel than the one Slackware installed for you. You will probably notice more linux-* directories in ''/usr/src''. It is common to let the "''linux''" link point to the kernel you are currently working with. It is however no //requirement// to have this symbolic link. Modern software that needs to know the location of the source code of an installed kernel will look at where the symbolic link ''/lib/modules/<kernelversion>/build'' points to instead. | Changing the "''linux''" symbolic link is safe to do. No applications will break if you let it point to another kernel than the one Slackware installed for you. You will probably notice more linux-* directories in ''/usr/src''. It is common to let the "''linux''" link point to the kernel you are currently working with. It is however no //requirement// to have this symbolic link. Modern software that needs to know the location of the source code of an installed kernel will look at where the symbolic link ''/lib/modules/<kernelversion>/build'' points to instead. |
| |
<note>There is a debate whether you should build your kernels in the ''/usr/src'' tree or somewhere entirely else.\\ The cause is an [[http://uwsg.iu.edu/hypermail/linux/kernel/0007.3/0587.html|old post by Linus Torvalds]] (from July 2000) where he advises people to build from within their home directory. I believe this advice is irrelevant for Slackware and the way it has it's kernel headers and glibc package setup. So, **my** advice is to ignore this old post by Linus and install your kernel sources into ''/usr/src'' if you want. The kernel building location is purely a matter of personal preference.</note> | <note>There is a debate whether you should build your kernels in the ''/usr/src'' tree or somewhere entirely else.\\ The cause is an [[http://uwsg.iu.edu/hypermail/linux/kernel/0007.3/0587.html|old post by Linus Torvalds]] (from July 2000) where he advises people to build from within their home directory. I believe this advice is irrelevant for Slackware and the way it has its kernel headers and glibc package setup. So, **my** advice is to ignore this old post by Linus and install your kernel sources into ''/usr/src'' if you want. The kernel building location is purely a matter of personal preference.</note> |
| |
Now, get a Slackware kernel config file for a head start during your own configuring. Pat's config files are pretty generic. By the time you read this, there might be a config for a newer 2.6 release available: | Now, get a Slackware kernel config file for a head start during your own configuring. Pat's config files are pretty generic. By the time you read this, there might be a config for a newer 2.6 release available: |
* Original source: http://alien.slackbook.org/dokuwiki/doku.php?id=linux:kernelbuilding | * Original source: http://alien.slackbook.org/dokuwiki/doku.php?id=linux:kernelbuilding |
* Originally written by [[wiki:user:alienbob | Eric Hameleers]] | * Originally written by [[wiki:user:alienbob | Eric Hameleers]] |
| |
| ====== Also see ====== |
| * If you wish to automate the process, you may want to pull a shell script following the instructions above from [[ https://github.com/jose1711/slackware_stuff/blob/master/build_kernel_slackware.sh | here]] |
| |
<!-- Please do not modify anything below, except adding new tags.--> | <!-- Please do not modify anything below, except adding new tags.--> |
{{tag>howtos software kernel author_alienbob}} | {{tag>howtos software kernel author_alienbob}} |