LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-02-2013, 01:50 PM   #1
zerouno
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 272

Rep: Reputation: 82
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?
 
Old 08-02-2013, 02:25 PM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,593

Rep: Reputation: 434Reputation: 434Reputation: 434Reputation: 434Reputation: 434
http://slackware.osuosl.org/slackwar...packaging-x86/
 
Old 08-02-2013, 02:27 PM   #3
zerouno
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 272

Original Poster
Rep: Reputation: 82
yes, but I can't found the kernel-source.SlackBuild
 
Old 08-02-2013, 04:25 PM   #4
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,474

Rep: Reputation: 901Reputation: 901Reputation: 901Reputation: 901Reputation: 901Reputation: 901Reputation: 901Reputation: 901
slack-desc
Code:
kernel-source: kernel-source (Linux kernel source)
kernel-source:
kernel-source: Source code for Linus Torvalds' Linux kernel.
kernel-source:
kernel-source: This is the complete and unmodified source code for the Linux kernel.
kernel-source:
kernel-source:
kernel-source:
kernel-source:
kernel-source:
kernel-source:
basically (supposing $CWD is the slackbuild's folder and you have slack-desc, config, and the linux sources inside it):
Code:
mkdir -p $PKG/usr/src $PKG/install
cd $PKG/usr/src
tar xf $CWD/linux-$VERSION.tar.xz # the pristine sources
ln -s linux-$VERSION linux
cat $CWD/config > linux-$VERSION/.config
cat $CWD/slack-desc > $PKG/install/slack-desc
cd $PKG
makepkg $OUTPUT/kernel-source-$VERSION-noarch-1.txz

Last edited by ponce; 08-02-2013 at 04:34 PM.
 
3 members found this post helpful.
Old 08-02-2013, 06:38 PM   #5
zerouno
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 272

Original Poster
Rep: Reputation: 82
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?
 
Old 08-03-2013, 03:36 PM   #6
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,519

Rep: Reputation: 1183Reputation: 1183Reputation: 1183Reputation: 1183Reputation: 1183Reputation: 1183Reputation: 1183Reputation: 1183Reputation: 1183
Quote:
Originally Posted by zerouno View Post
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.

Last edited by Didier Spaier; 08-03-2013 at 04:34 PM. Reason: [EDIT] added.
 
Old 08-03-2013, 06:38 PM   #7
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,631
Blog Entries: 15

Rep: Reputation: 1103Reputation: 1103Reputation: 1103Reputation: 1103Reputation: 1103Reputation: 1103Reputation: 1103Reputation: 1103Reputation: 1103
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!
 
Old 08-03-2013, 08:23 PM   #8
zerouno
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 272

Original Poster
Rep: Reputation: 82
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
 
Old 08-04-2013, 06:46 AM   #9
tuxbg
Member
 
Registered: Sep 2012
Location: Bulgaria,Varna
Distribution: Slackware64
Posts: 249

Rep: Reputation: Disabled
Hello Look My threat
 
1 members found this post helpful.
Old 08-04-2013, 04:59 PM   #10
zerouno
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 272

Original Poster
Rep: Reputation: 82
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.
 
Old 08-05-2013, 11:50 AM   #11
zerouno
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 272

Original Poster
Rep: Reputation: 82
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"
 
Old 08-05-2013, 01:02 PM   #12
tuxbg
Member
 
Registered: Sep 2012
Location: Bulgaria,Varna
Distribution: Slackware64
Posts: 249

Rep: Reputation: Disabled
Quote:
Originally Posted by zerouno View Post
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Packages for Linux from scratch 6.5 mahaju Linux From Scratch 7 06-21-2012 11:09 AM
Kernel - basic Slackware packages hua Slackware 8 03-31-2011 04:24 AM
Removing Slackware kernel packages camphor Slackware 4 12-21-2009 03:49 AM
SMP Kernel Packages for Slackware ? Grunthos Slackware 15 04-03-2005 12:56 AM
Kernel 2.6.7 installation from Slackware 10 packages? plm Slackware 8 06-28-2004 01:33 PM


All times are GMT -5. The time now is 08:18 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration