slackware from scratch: kernel packages
 

I'm trying to build slackware from scratch starting from a centos distribution.

It's the time to build the kernel packages.

I found the slackbuild for kernel-generic, kernel-huge, kernel-headers, kernel-modules, kernel-firmware.

I can't found the slackbuild and the slack-desc for kernel-source.
Whereis?

yes, but I can't found the kernel-source.SlackBuild

slack-desc
basically (supposing $CWD is the slackbuild's folder and you have slack-desc, config, and the linux sources inside it):

You know that I'm able to create a slackware package myself and to create a slackbuild myself, but I'm building slackware from the officials sources.

My think is "why slackware source does not contains kernel-source slackbuild and the slack-desc file"
Pat uses manual commands to create kernel-source package?

There is no need for a SlackBuild because there is nothing to build there ;) If you want to see files slack-desc and doinst.sh just unpack the package with 'explodepkg kernel-source-<version>*txz' then repack it with 'makepkg'

Before you ask, for the same reason there is no separate 'source' for /isolinux/initrd.img: just unpack it to see what's in it.

Also, I wish you good luck but I'm afraid you won't be able to compile some packages. As it has been said in a recent thread (I can't remember which one at the moment) the distribution is not rebuilt from scratch at each release and that would probably be very difficult.

[EDIT]I've found the thread. This post fro Alien Bob explains why it's difficult.

Building Slackware from pure source is a nice little challenge as usually you have to do a lot of rechecking and patching packages to build, though some packages are fairly mainstream and getting a temporary building system up and running is of little consequence to work from as fairly much everything tends to build with only a few headaches here and there, but honestly, it's actually a fun, if not entirely interesting task to see how Slackware works even deeper at the foundations, much like how Gentoo and LFS work as well.

You honestly really have to take the time and build an LFS or LFS-like system to have an honest appreciation of Linux, BSD, and all of UNIX as a whole.

LFS even has tips and an FAQ on how to convert the basic sysvinit scripts to Slackware-like BSD stylized sysvinit scripts.

Best of luck with your build! :D

I have a virtual server centos 6.2 (a minimal system, about 240 rpm) and I'm replacing it compiling slackware.

The first step was install centos gcc, then build then pkgtools and install it on the root filsystem (pkgtools does not conflict with any distribution :) ). Then I rebuilt pkgtools using the installed pkgtools.
Then I built the aaa_base package and installed it. (This operatio DROP the /usr/share/doc, /usr/share/man and some other unfatal file).
pkgtools with the non-slackware "tar" generate bad packages, and installpkg without slackware "du" and "find" command generate warnings, so I built tar, coreutils, diffutils and findutils, then I rebuilt aaa_base and pkgtools using the unbugged pkgtools.
Next I built gcc to replace centos-gcc.

After that I started recompiling all the currently installed rpm.
When a package require another (./configure fails) I build the dependecy.
Sometime ./configure does not fails when the dependency is missing; simply disable some feature; so at the end of process I must to recompile all!!).
Also I must recompile all to use the slackware glibc, but for now I can't build that becouse I need at least kernel 3.2.29, and a very problem will be to change the kernel becouse
1) I must to see if the virtualization software on what the vps is running require some specific kernel module
2) I can access to console of vps, but I cant see the bootloader becouse the console works only when the kernel is loaded. So if there is a problem loading kernel I may need a vps reset recrate (from backup)
3) I dont know if I can substitude grub with lilo

Hello :) Look My threat

Thankyou.

Today I had built nothing :).

For now the best problem is to be sure that the system continue to work even when I overwrite centos libraries. (notice: centos use pam!).
If the system will not boot I cant boot from cd.

linuxdoc-tools uses slacktrack to build the package. During execution it touched the entire filesystem!!!!!!!
Now all files have the same date/time!!!!!!!

"slacktrack: Touching contents of /opt /bin /boot /etc /lib /usr/lib64 /lib64 /sbin /usr /var"

Yes but gnome-doc tools that comes with linuxdoc-tools need ITSTOOL to be build.