SlackWiki - User contributions [en]

Utf-8 linux console

Dive — Fri, 09 May 2014 17:36:30 GMT

Dive: /* A Quick Look at Using UTF-8 in the Linux Console (without X) */

[[Category:Tutorials]]
''by Dive''

== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

A few people have asked about this in ##slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info.

In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
Anyway here we go ...

== The Console ==

The first thing to do is configure the console. There is a kernel parameter we can add to
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.27.7-custom
root = /dev/hda1
label = Linux-custom
append="resume=/dev/hda2 vt.default_utf8=1"
read-only
# Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== LANG environment variable ==

I find that typing multibyte characters like "ä" and erasing them with backspace, I can erase much more than what I wrote. It helps to set the LANG variable, preferably by editing /etc/profile.d/lang.sh (or lang.csh) to set it to en_US.UTF-8 or similar.

== Fonts ==

After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.

== Keyboard ==

Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://home.tiscali.nl/t876506/utf8tbl.html]http://home.tiscali.nl/t876506/utf8tbl.html

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

# key = normal shifted AltGr+e AltGr+shift+e
keycode 18 = e E U+00E8 U+00E9
# prints: e E è é

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/source/uk-utf.map.gz]http://www.unrealize.co.uk/source/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==

By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.

Note: There exists two shell scripts - '''unicode_start''' and '''unicode_stop'''. Typing '''unicode_start [font]''' will load the required font and set up keyboard correctly for unicode input.

Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)

Kernel-packaging

Dive — Fri, 09 Dec 2011 12:15:20 GMT

Dive: /* Creating a Custom Package of Kernel and Modules */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.com/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.com/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.com/Kernel_Checklist Kernel_Checklist]

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(sed "s#^kernel/##" modules.order)
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009-2010 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source ./.config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i486 ;;
arm*) ARCH=arm ;;
*) ARCH=$( uname -m ) ;;
esac
fi
KARCH=$ARCH
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(sed "s#^kernel/##" $MODULELIST)
do
mkdir -p $MODDIR/$(dirname $i)
install -m 644 -v $i $MODDIR/$(dirname $i)
let nummods=$nummods+1
done

mkdir -p $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
EOF

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

mkdir -p $PKG/boot

cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')

cd $PKG

PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}

/sbin/makepkg -l y -c n $PACKAGE

echo -ne '\e[01;34m'
printf "$nummods Modules Built\n"
printf "Kernel Size: $ksize\n"
printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
echo -ne '\e[m\017'

Downloadable version: http://www.dawoodfall.net/slackbuilds/noversion/kernel/

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Fri, 09 Dec 2011 12:14:38 GMT

Dive: /* Creating a Custom Package of Kernel and Modules */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(sed "s#^kernel/##" modules.order)
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009-2010 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source ./.config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i486 ;;
arm*) ARCH=arm ;;
*) ARCH=$( uname -m ) ;;
esac
fi
KARCH=$ARCH
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(sed "s#^kernel/##" $MODULELIST)
do
mkdir -p $MODDIR/$(dirname $i)
install -m 644 -v $i $MODDIR/$(dirname $i)
let nummods=$nummods+1
done

mkdir -p $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
EOF

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

mkdir -p $PKG/boot

cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')

cd $PKG

PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}

/sbin/makepkg -l y -c n $PACKAGE

echo -ne '\e[01;34m'
printf "$nummods Modules Built\n"
printf "Kernel Size: $ksize\n"
printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
echo -ne '\e[m\017'

Downloadable version: http://www.dawoodfall.net/slackbuilds/noversion/kernel/

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Dual Booting With FreeBSD 9

Dive — Tue, 25 Oct 2011 11:08:23 GMT

Dive: /* Custom Rule */

=Introduction=

FreeBSD 9+ differs from older releases by using GPT (GUID Partition Table). This means that lilo and grub version 1 will no longer work. Grub version 2 however does work.

There are two way of doings this - either install grub2 in Slackware, or install it in FreeBSD. Grub2 in Slackware does not seem to be able to pick up the FreeBSD partition and Grub2 in FreeBSD doesn't seem to pick up the Linux partitions. You will need to manually add these to /usr/local/etc/grub.d/40_custom.

To pick up all your Slackware kernels it's probably best to install grub2 in Slackware and add the FreeBSD partition manually. I've shown both methods here though, for completeness.

For this howto we'll assume that Slackware / is on /dev/sda2 (with no separate /boot partition), and that FreeBSD is on /dev/sdb2 (/dev/ada1p2 in FreeBSD-speak). These correspond to (hd0,2) and (hd1,2) in Grub2.

=To install Grub2 in Slackware=

To install Grub2 in Slackware, you can use the slackbuild script here:
http://slackbuilds.org/repository/13.37/system/grub2/ and its dependencies. Once installed, issue:

# grub-install --modules=part_gpt /dev/sda

Edit /etc/grub.d/40_custom to add your FreeBSD partition (see mine below for an example). Once done:

# grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pickup all your Linux partitions and all kernels (hopefully).

=To install in FreeBSD=

To install Grub2 in FreeBSD, you need to use ports.

I won't give an extended howto on using ports but these are the steps:

Fire up your FreeBSD system and navigate your way to /usr/ports/sysutils/grub2 as root

# make install && rm -rf work
# grub-install --modules=part_gpt /dev/ad0

Edit /usr/local/etc/grub.d/40_custom to add your Slackware partition (see mine below for an example). Once done:

# grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pick up FreeBSD automatically.
/usr/local/etc/grub.d/40_custom will contain the extra OS's and FreeBSD boot loader if req'd.

=Custom Rule=
This is my 40_custom:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.

menuentry 'Slackware' --class slackware --class gnu-linux --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,2)'
linux /boot/vmlinuz root=/dev/sdb2 ro
}

menuentry "FreeBSD" --class freebsd --class bsd --class os {
insmod ufs2
set root='(hd1,2)'
kfreebsd /boot/loader
}

(You choose which section you want to add - FreeBSD or Slackware - depending on where you installed Grub2.)

That's pretty much it.

=Notes=

The Slackware partition uses ext4 and the huge kernel with no initrd. For, say, xfs you should use 'insmod xfs'. For an initrd you need to look up the appropriate docs.

Caveat: This was tested on FreeBSD 9.0Beta3. I can't see that it wouldn't work when release is out but you never know.

[[User:Dive|Dive]]

Dual Booting With FreeBSD 9

Dive — Tue, 25 Oct 2011 11:07:51 GMT

Dive: /* Custom Rule */

=Introduction=

FreeBSD 9+ differs from older releases by using GPT (GUID Partition Table). This means that lilo and grub version 1 will no longer work. Grub version 2 however does work.

There are two way of doings this - either install grub2 in Slackware, or install it in FreeBSD. Grub2 in Slackware does not seem to be able to pick up the FreeBSD partition and Grub2 in FreeBSD doesn't seem to pick up the Linux partitions. You will need to manually add these to /usr/local/etc/grub.d/40_custom.

To pick up all your Slackware kernels it's probably best to install grub2 in Slackware and add the FreeBSD partition manually. I've shown both methods here though, for completeness.

For this howto we'll assume that Slackware / is on /dev/sda2 (with no separate /boot partition), and that FreeBSD is on /dev/sdb2 (/dev/ada1p2 in FreeBSD-speak). These correspond to (hd0,2) and (hd1,2) in Grub2.

=To install Grub2 in Slackware=

To install Grub2 in Slackware, you can use the slackbuild script here:
http://slackbuilds.org/repository/13.37/system/grub2/ and its dependencies. Once installed, issue:

# grub-install --modules=part_gpt /dev/sda

Edit /etc/grub.d/40_custom to add your FreeBSD partition (see mine below for an example). Once done:

# grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pickup all your Linux partitions and all kernels (hopefully).

=To install in FreeBSD=

To install Grub2 in FreeBSD, you need to use ports.

I won't give an extended howto on using ports but these are the steps:

Fire up your FreeBSD system and navigate your way to /usr/ports/sysutils/grub2 as root

# make install && rm -rf work
# grub-install --modules=part_gpt /dev/ad0

Edit /usr/local/etc/grub.d/40_custom to add your Slackware partition (see mine below for an example). Once done:

# grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pick up FreeBSD automatically.
/usr/local/etc/grub.d/40_custom will contain the extra OS's and FreeBSD boot loader if req'd.

=Custom Rule=
This is my 40_custom:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.

menuentry 'Slackware' --class slackware --class gnu-linux --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,2)'
linux /boot/vmlinuz root=/dev/sdb2 ro
}

menuentry "FreeBSD --class freebsd --class bsd --class os {
insmod ufs2
set root='(hd1,2)'
kfreebsd /boot/loader
}

(You choose which section you want to add - FreeBSD or Slackware - depending on where you installed Grub2.)

That's pretty much it.

=Notes=

The Slackware partition uses ext4 and the huge kernel with no initrd. For, say, xfs you should use 'insmod xfs'. For an initrd you need to look up the appropriate docs.

Caveat: This was tested on FreeBSD 9.0Beta3. I can't see that it wouldn't work when release is out but you never know.

[[User:Dive|Dive]]

Dual Booting With FreeBSD 9

Dive — Tue, 25 Oct 2011 10:55:53 GMT

Dive:

=Introduction=

FreeBSD 9+ differs from older releases by using GPT (GUID Partition Table). This means that lilo and grub version 1 will no longer work. Grub version 2 however does work.

There are two way of doings this - either install grub2 in Slackware, or install it in FreeBSD. Grub2 in Slackware does not seem to be able to pick up the FreeBSD partition and Grub2 in FreeBSD doesn't seem to pick up the Linux partitions. You will need to manually add these to /usr/local/etc/grub.d/40_custom.

To pick up all your Slackware kernels it's probably best to install grub2 in Slackware and add the FreeBSD partition manually. I've shown both methods here though, for completeness.

For this howto we'll assume that Slackware / is on /dev/sda2 (with no separate /boot partition), and that FreeBSD is on /dev/sdb2 (/dev/ada1p2 in FreeBSD-speak). These correspond to (hd0,2) and (hd1,2) in Grub2.

=To install Grub2 in Slackware=

To install Grub2 in Slackware, you can use the slackbuild script here:
http://slackbuilds.org/repository/13.37/system/grub2/ and its dependencies. Once installed, issue:

# grub-install --modules=part_gpt /dev/sda

Edit /etc/grub.d/40_custom to add your FreeBSD partition (see mine below for an example). Once done:

# grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pickup all your Linux partitions and all kernels (hopefully).

=To install in FreeBSD=

To install Grub2 in FreeBSD, you need to use ports.

I won't give an extended howto on using ports but these are the steps:

Fire up your FreeBSD system and navigate your way to /usr/ports/sysutils/grub2 as root

# make install && rm -rf work
# grub-install --modules=part_gpt /dev/ad0

Edit /usr/local/etc/grub.d/40_custom to add your Slackware partition (see mine below for an example). Once done:

# grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pick up FreeBSD automatically.
/usr/local/etc/grub.d/40_custom will contain the extra OS's and FreeBSD boot loader if req'd.

=Custom Rule=
This is my 40_custom:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.

menuentry 'Slackware' --class slackware --class gnu-linux --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,2)'
linux /boot/vmlinuz root=/dev/sdb2 ro
}

menuentry "FreeBSD /boot/loader" --class freebsd --class bsd --class os {
insmod ufs2
set root='(hd1,2)'
kfreebsd /boot/loader
}

(You choose which section you want to add - FreeBSD or Slackware - depending on where you installed Grub2.)

That's pretty much it.

=Notes=

The Slackware partition uses ext4 and the huge kernel with no initrd. For, say, xfs you should use 'insmod xfs'. For an initrd you need to look up the appropriate docs.

Caveat: This was tested on FreeBSD 9.0Beta3. I can't see that it wouldn't work when release is out but you never know.

[[User:Dive|Dive]]

Dual Booting With FreeBSD 9+

Dive — Tue, 25 Oct 2011 09:59:02 GMT

Dive: moved Dual Booting With FreeBSD 9+ to Dual Booting With FreeBSD 9: + messes up the link

#REDIRECT [[Dual Booting With FreeBSD 9]]

Dual Booting With FreeBSD 9

Dive — Tue, 25 Oct 2011 09:59:02 GMT

Dive: moved Dual Booting With FreeBSD 9+ to Dual Booting With FreeBSD 9: + messes up the link

=Introduction=

FreeBSD 9+ differs from older releases by using GPT (GUID Partition Table). This means that lilo and grub version 1 will no longer work. Grub version 2 however does work.

There are two way of doings this - either install grub2 in Slackware, or install it in FreeBSD. Grub2 in Slackware does not seem to be able to pick up the FreeBSD partition and Grub2 in FreeBSD doesn't seem to pick up the Linux partitions. You will need to manually add these to /usr/local/etc/grub.d/40_custom.

To pick up all your Slackware kernels it's probably best to install grub2 in Slackware and add the FreeBSD partition manually. I've shown both methods here though, for completeness.

For this howto we'll assume that Slackware / is on /dev/sda2 (with no separate /boot partition), and that FreeBSD is on /dev/sdb2 (/dev/ada1p2 in FreeBSD-speak). These correspond to (hd0,2) and (hd1,2) in Grub2.

=To install Grub2 in Slackware=

To install Grub2 in Slackware, you can use the slackbuild script here:
http://slackbuilds.org/repository/13.37/system/grub2/ and its dependencies. Once installed, issue:

# grub-install --modules=part_gpt /dev/sda

Edit /etc/grub.d/40_custom to add your FreeBSD partition (see mine below for an example). Once done:

# grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pickup all your Linux partitions and all kernels (hopefully).

=To install in FreeBSD=

To install Grub2 in FreeBSD, you need to use ports.

I won't give an extended howto on using ports but these are the steps:

Fire up your FreeBSD system and navigate your way to /usr/ports/sysutils/grub2 as root

# make install && rm -rf work
# grub-install --modules=part_gpt /dev/ad0

Edit /usr/local/etc/grub.d/40_custom to add your Slackware partition (see mine below for an example). Once done:

# grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pick up FreeBSD automatically.
/usr/local/etc/grub.d/40_custom will contain the extra OS's and FreeBSD boot loader if req'd.

=Custom Rule=
This is my 40_custom:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.

menuentry 'Slackware' --class slackware --class gnu-linux --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,2)'
linux /boot/vmlinuz root=/dev/sdb2 ro
}

menuentry "FreeBSD /boot/loader" --class freebsd --class bsd --class os {
insmod ufs2
set root='(hd1,2)'
kfreebsd /boot/loader
}

(You choose which section you want to add - FreeBSD or Slackware - depending on where you installed Grub2.)

That's pretty much it.

=Notes=

My Slackware uses ext4 and a custom kernel with no initrd. For, say, xfs you should use 'insmod xfs'.

Caveat: This was tested on FreeBSD 9.0Beta3. I can't see that it wouldn't work when release is out but you never know.

[[User:Dive|Dive]]

Dual Booting With FreeBSD 9

Dive — Tue, 25 Oct 2011 09:57:59 GMT

Dive: Created page with "=Introduction= FreeBSD 9+ differs from older releases by using GPT (GUID Partition Table). This means that lilo and grub version 1 will no longer work. Grub version 2 however do..."

=Introduction=

FreeBSD 9+ differs from older releases by using GPT (GUID Partition Table). This means that lilo and grub version 1 will no longer work. Grub version 2 however does work.

There are two way of doings this - either install grub2 in Slackware, or install it in FreeBSD. Grub2 in Slackware does not seem to be able to pick up the FreeBSD partition and Grub2 in FreeBSD doesn't seem to pick up the Linux partitions. You will need to manually add these to /usr/local/etc/grub.d/40_custom.

To pick up all your Slackware kernels it's probably best to install grub2 in Slackware and add the FreeBSD partition manually. I've shown both methods here though, for completeness.

For this howto we'll assume that Slackware / is on /dev/sda2 (with no separate /boot partition), and that FreeBSD is on /dev/sdb2 (/dev/ada1p2 in FreeBSD-speak). These correspond to (hd0,2) and (hd1,2) in Grub2.

=To install Grub2 in Slackware=

To install Grub2 in Slackware, you can use the slackbuild script here:
http://slackbuilds.org/repository/13.37/system/grub2/ and its dependencies. Once installed, issue:

# grub-install --modules=part_gpt /dev/sda

Edit /etc/grub.d/40_custom to add your FreeBSD partition (see mine below for an example). Once done:

# grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pickup all your Linux partitions and all kernels (hopefully).

=To install in FreeBSD=

To install Grub2 in FreeBSD, you need to use ports.

I won't give an extended howto on using ports but these are the steps:

Fire up your FreeBSD system and navigate your way to /usr/ports/sysutils/grub2 as root

# make install && rm -rf work
# grub-install --modules=part_gpt /dev/ad0

Edit /usr/local/etc/grub.d/40_custom to add your Slackware partition (see mine below for an example). Once done:

# grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pick up FreeBSD automatically.
/usr/local/etc/grub.d/40_custom will contain the extra OS's and FreeBSD boot loader if req'd.

=Custom Rule=
This is my 40_custom:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.

menuentry 'Slackware' --class slackware --class gnu-linux --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,2)'
linux /boot/vmlinuz root=/dev/sdb2 ro
}

menuentry "FreeBSD /boot/loader" --class freebsd --class bsd --class os {
insmod ufs2
set root='(hd1,2)'
kfreebsd /boot/loader
}

(You choose which section you want to add - FreeBSD or Slackware - depending on where you installed Grub2.)

That's pretty much it.

=Notes=

My Slackware uses ext4 and a custom kernel with no initrd. For, say, xfs you should use 'insmod xfs'.

Caveat: This was tested on FreeBSD 9.0Beta3. I can't see that it wouldn't work when release is out but you never know.

[[User:Dive|Dive]]

User:Dive

Dive — Mon, 04 Oct 2010 14:36:47 GMT

Dive: Created page with 'Homepage: http://dawoodfall.net Email: dave@dawoodfall.net'

Homepage: http://dawoodfall.net
Email: dave@dawoodfall.net

Utf-8 linux console

Dive — Mon, 27 Sep 2010 10:20:05 GMT

Dive: /* Keyboard */

[[Category:Tutorials]]
''by Dive''

== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info.

In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
Anyway here we go ...

== The Console ==

The first thing to do is configure the console. There is a kernel parameter we can add to
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.27.7-custom
root = /dev/hda1
label = Linux-custom
append="resume=/dev/hda2 vt.default_utf8=1"
read-only
# Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== LANG environment variable ==

I find that typing multibyte characters like "ä" and erasing them with backspace, I can erase much more than what I wrote. It helps to set the LANG variable, preferably by editing /etc/profile.d/lang.sh (or lang.csh) to set it to en_US.UTF-8 or similar.

== Fonts ==

After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.

== Keyboard ==

Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://home.tiscali.nl/t876506/utf8tbl.html]http://home.tiscali.nl/t876506/utf8tbl.html

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

# key = normal shifted AltGr+e AltGr+shift+e
keycode 18 = e E U+00E8 U+00E9
# prints: e E è é

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/source/uk-utf.map.gz]http://www.unrealize.co.uk/source/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==

By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.

Note: There exists two shell scripts - '''unicode_start''' and '''unicode_stop'''. Typing '''unicode_start [font]''' will load the required font and set up keyboard correctly for unicode input.

Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)

Kernel-packaging

Dive — Mon, 16 Aug 2010 22:04:03 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(sed "s#^kernel/##" modules.order)
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009-2010 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source ./.config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i486 ;;
arm*) ARCH=arm ;;
*) ARCH=$( uname -m ) ;;
esac
fi
KARCH=$ARCH
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(sed "s#^kernel/##" $MODULELIST)
do
mkdir -p $MODDIR/$(dirname $i)
install -m 644 -v $i $MODDIR/$(dirname $i)
let nummods=$nummods+1
done

mkdir -p $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
EOF

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

mkdir -p $PKG/boot

cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')

cd $PKG

PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}

/sbin/makepkg -l y -c n $PACKAGE

echo -ne '\e[01;34m'
printf "$nummods Modules Built\n"
printf "Kernel Size: $ksize\n"
printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
echo -ne '\e[m\017'

Downloadable version: http://www.dawoodfall.net/slackbuilds/noversion/kernel/

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Mon, 16 Aug 2010 22:01:10 GMT

Dive: /* Installing Modules and Kernel to our Package Directory */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(sed "s#^kernel/##" modules.order)
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009-2010 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source ./.config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i486 ;;
arm*) ARCH=arm ;;
*) ARCH=$( uname -m ) ;;
esac
fi
KARCH=$ARCH
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##" )
do
mkdir -p $MODDIR/$(dirname $i)
install -m 644 -v $i $MODDIR/$(dirname $i)
let nummods=$nummods+1
done

mkdir -p $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
EOF

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

mkdir -p $PKG/boot

cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')

cd $PKG

PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}

/sbin/makepkg -l y -c n $PACKAGE

echo -ne '\e[01;34m'
printf "$nummods Modules Built\n"
printf "Kernel Size: $ksize\n"
printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
echo -ne '\e[m\017'

Downloadable version: http://www.dawoodfall.net/slackbuilds/noversion/kernel/

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 25 Jul 2010 20:08:30 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009-2010 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source ./.config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i486 ;;
arm*) ARCH=arm ;;
*) ARCH=$( uname -m ) ;;
esac
fi
KARCH=$ARCH
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##" )
do
mkdir -p $MODDIR/$(dirname $i)
install -m 644 -v $i $MODDIR/$(dirname $i)
let nummods=$nummods+1
done

mkdir -p $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
EOF

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

mkdir -p $PKG/boot

cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')

cd $PKG

PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}

/sbin/makepkg -l y -c n $PACKAGE

echo -ne '\e[01;34m'
printf "$nummods Modules Built\n"
printf "Kernel Size: $ksize\n"
printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
echo -ne '\e[m\017'

Downloadable version: http://www.dawoodfall.net/slackbuilds/noversion/kernel/

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 25 Jul 2010 20:07:37 GMT

Dive: /* Creating a Custom Package of Kernel and Modules */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009-2010 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source ./.config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i486 ;;
arm*) ARCH=arm ;;
*) ARCH=$( uname -m ) ;;
esac
fi
KARCH=$ARCH
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##" )
do
mkdir -p $MODDIR/$(dirname $i)
install -m 644 -v $i $MODDIR/$(dirname $i)
let nummods=$nummods+1
done

mkdir -p $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
EOF

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

mkdir -p $PKG/boot

cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')

cd $PKG

PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}

/sbin/makepkg -l y -c n $PACKAGE

echo -ne '\e[01;34m'
printf "$nummods Modules Built\n"
printf "Kernel Size: $ksize\n"
printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
echo -ne '\e[m\017'

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 25 Jul 2010 20:03:57 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009-2010 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source ./.config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i486 ;;
arm*) ARCH=arm ;;
*) ARCH=$( uname -m ) ;;
esac
fi
KARCH=$ARCH
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##" )
do
mkdir -p $MODDIR/$(dirname $i)
install -m 644 -v $i $MODDIR/$(dirname $i)
let nummods=$nummods+1
done

mkdir -p $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
EOF

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

mkdir -p $PKG/boot

cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')

cd $PKG

PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}

/sbin/makepkg -l y -c n $PACKAGE

echo -ne '\e[01;34m'
printf "$nummods Modules Built\n"
printf "Kernel Size: $ksize\n"
printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
echo -ne '\e[m\017'

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 25 Jul 2010 19:52:39 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009-2010 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source ./.config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##" )
do
mkdir -p $MODDIR/$(dirname $i)
install -m 644 -v $i $MODDIR/$(dirname $i)
let nummods=$nummods+1
done

mkdir -p $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
EOF

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

mkdir -p $PKG/boot

cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')

cd $PKG

PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}

/sbin/makepkg -l y -c n $PACKAGE

echo -ne '\e[01;34m'
printf "$nummods Modules Built\n"
printf "Kernel Size: $ksize\n"
printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
echo -ne '\e[m\017'

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 25 Jul 2010 19:44:11 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source ./.config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##" )
do
mkdir -p $MODDIR/$(dirname $i)
install -m 644 -v $i $MODDIR/$(dirname $i)
let nummods=$nummods+1
done

mkdir -p $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
EOF

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

mkdir -p $PKG/boot

cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')

cd $PKG

PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}

/sbin/makepkg -l y -c n $PACKAGE

echo -ne '\e[01;34m'
printf "$nummods Modules Built\n"
printf "Kernel Size: $ksize\n"
printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
echo -ne '\e[m\017'

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 25 Jul 2010 19:42:37 GMT

Dive: /* Making the Package */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source .config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
EOF

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 14 Mar 2010 16:22:55 GMT

Dive: /* Conclusion */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source .config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
EOF

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 14 Mar 2010 16:21:47 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source .config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
EOF

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 14 Mar 2010 16:19:48 GMT

Dive: /* Installing Modules and Kernel to our Package Directory */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source .config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 14 Mar 2010 16:19:26 GMT

Dive: /* Installing Modules and Kernel to our Package Directory */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir -p /tmp/kernel-package/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source .config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 14 Mar 2010 16:16:58 GMT

Dive: /* Installing Modules and Kernel to our Package Directory */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir $PKG/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source .config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 14 Mar 2010 16:16:27 GMT

Dive: /* Installing Modules and Kernel to our Package Directory */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir $PKG/install

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source .config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 14 Mar 2010 16:15:43 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Notes:
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will
# have problems.
# Do not omit setting localname in .config.

source .config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install

cat << EOF > $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 14 Mar 2010 16:13:25 GMT

Dive: /* Installing Modules and Kernel to our Package Directory */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a 2.6.29.6-jabberwok > /dev/null 2> /dev/null
fi

( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

source .config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Sun, 14 Mar 2010 16:11:56 GMT

Dive: /* Installing Modules and Kernel to our Package Directory */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

doinst.sh:

## Taken from stock modules package
if [ -x sbin/depmod ]; then
chroot . /sbin/depmod -a $VERSION-$LOCALNAME > /dev/null 2> /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

source .config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 19:24:44 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

source .config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 15:07:11 GMT

Dive: /* Building */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
LOCALNAME=${LOCALNAME:-jabberwok}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 14:17:42 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install' as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
LOCALNAME=${LOCALNAME:-jabberwok}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 13:35:27 GMT

Dive: /* Kernel Output Target Option */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install' as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
LOCALNAME=${LOCALNAME:-jabberwok}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make menuconfig
make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Talk:Kernel-packaging

Dive — Thu, 11 Mar 2010 12:52:41 GMT

Dive: Created page with 'Originally I used the O= switch to build in a separate build directory. This isn't really necesary, but if you prefer to do this have a look at the README file in top directory a…'

Originally I used the O= switch to build in a separate build directory. This isn't really necesary, but if you prefer to do this have a look at the README file in top directory about the O= switch.

Kernel-packaging

Dive — Thu, 11 Mar 2010 12:49:02 GMT

Dive: /* Building */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect.

== Building ==

Copy your .config into the source directory and do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install' as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
LOCALNAME=${LOCALNAME:-jabberwok}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make menuconfig
make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 12:44:12 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect.

== Building ==

From your kernel source directory do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install' as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
LOCALNAME=${LOCALNAME:-jabberwok}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG

make menuconfig
make

for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 12:41:43 GMT

Dive: /* Output Into a Build Directory */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect.

== Building ==

From your kernel source directory do

make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

make

*Note: Do not use 'make install' or 'make modules_install' as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

#!/bin/sh
# Slackware build script for kernel and modules
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
LOCALNAME=${LOCALNAME:-jabberwok}
OUTPUT=${TMP:-/tmp}
KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
set -e

rm -rf $KOUTPUT
rm -rf $PKG
mkdir -p $KOUTPUT

cd $SOURCE
make O=$KOUTPUT menuconfig
make mrproper
make O=$KOUTPUT
make O=$KOUTPUT modules_install

cd $KOUTPUT
for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 12:37:35 GMT

Dive: /* Kernel Output Target Option */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect.

== Output Into a Build Directory ==

From your kernel source directory do

make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

make O=/tmp/kernel-build
make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

#!/bin/sh
# Slackware build script for kernel and modules
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
LOCALNAME=${LOCALNAME:-jabberwok}
OUTPUT=${TMP:-/tmp}
KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
set -e

rm -rf $KOUTPUT
rm -rf $PKG
mkdir -p $KOUTPUT

cd $SOURCE
make O=$KOUTPUT menuconfig
make mrproper
make O=$KOUTPUT
make O=$KOUTPUT modules_install

cd $KOUTPUT
for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 08:42:34 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.

The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==

From your kernel source directory do

make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

make O=/tmp/kernel-build
make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

#!/bin/sh
# Slackware build script for kernel and modules
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
LOCALNAME=${LOCALNAME:-jabberwok}
OUTPUT=${TMP:-/tmp}
KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
set -e

rm -rf $KOUTPUT
rm -rf $PKG
mkdir -p $KOUTPUT

cd $SOURCE
make O=$KOUTPUT menuconfig
make mrproper
make O=$KOUTPUT
make O=$KOUTPUT modules_install

cd $KOUTPUT
for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 08:42:07 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.

The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==

From your kernel source directory do

make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

make O=/tmp/kernel-build
make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

#!/bin/sh
# Slackware build script for kernel and modules
# Copyright 2009 David Woodfall <dave@dawoodfall.net>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
LOCALNAME=${LOCALNAME:-jabberwok}
OUTPUT=${TMP:-/tmp}
KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
set -e

rm -rf $KOUTPUT
rm -rf $PKG
mkdir -p $KOUTPUT

cd $SOURCE
make O=$KOUTPUT menuconfig
make mrproper
make O=$KOUTPUT
make O=$KOUTPUT modules_install

cd $KOUTPUT
for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 08:34:43 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.

The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==

From your kernel source directory do

make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

make O=/tmp/kernel-build
make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

#!/bin/bash

KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
LOCALNAME=${LOCALNAME:-jabberwok}
OUTPUT=${TMP:-/tmp}
KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
set -e

rm -rf $KOUTPUT
rm -rf $PKG
mkdir -p $KOUTPUT

cd $SOURCE
make O=$KOUTPUT menuconfig
make mrproper
make O=$KOUTPUT
make O=$KOUTPUT modules_install

cd $KOUTPUT
for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir -p $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 05:22:44 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.

The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==

From your kernel source directory do

make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

make O=/tmp/kernel-build
make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

#!/bin/bash

KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
LOCALNAME=${LOCALNAME:-jabberwok}
OUTPUT=${TMP:-/tmp}
KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
set -e

rm -rf $KOUTPUT
rm -rf $PKG
mkdir -p $KOUTPUT

cd $SOURCE
make O=$KOUTPUT menuconfig
make mrproper
make O=$KOUTPUT
make O=$KOUTPUT modules_install

cd $KOUTPUT
for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

|-----handy-ruler------------------------------------------------------|
kernel-jabberwok: kernel and modules 2.6.29.6-jabberwok
kernel-jabberwok:
kernel-jabberwok: Jabberwokky type kernel!
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 05:02:29 GMT

Dive: /* A Little Automation */

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.

The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==

From your kernel source directory do

make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

make O=/tmp/kernel-build
make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

#!/bin/bash

SOURCE=/usr/src/linux-2.6.29.6-jabberwok
ARCH=i386
KARCH=i686
MODULELIST=modules.order
PRGNAM=kernel
VERSION=2.6.29.6
BUILD=1
TAG=_daw
LOCALNAME=jabberwok
OUTPUT=/tmp
KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
set -e

rm -rf $KOUTPUT
rm -rf $PKG
mkdir -p $KOUTPUT

cd $SOURCE
make O=$KOUTPUT menuconfig
make mrproper
make O=$KOUTPUT
make O=$KOUTPUT modules_install

cd $KOUTPUT
for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $MODDDIR/$(dirname $i)
install -m 644 -v $i $MODDDIR/$(dirname $i)
done

mkdir $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

|-----handy-ruler------------------------------------------------------|
kernel-jabberwok: kernel and modules 2.6.29.6-jabberwok
kernel-jabberwok:
kernel-jabberwok: Jabberwokky type kernel!
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 04:32:58 GMT

Dive:

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.

The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==

From your kernel source directory do

make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

make O=/tmp/kernel-build
make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot
cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

#!/bin/bash

SOURCE=/usr/src/linux-2.6.29.6-jabberwok
ARCH=i386
KARCH=i686
MODULELIST=modules.order
PRGNAM=kernel
VERSION=2.6.29.6
BUILD=1
TAG=_daw
LOCALNAME=jabberwok
OUTPUT=/tmp
KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
BUILDDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
set -e

rm -rf $KOUTPUT
rm -rf $PKG
mkdir -p $BUILDDIR
mkdir -p $KOUTPUT

cd $SOURCE
make O=$KOUTPUT menuconfig
make mrproper
make O=$KOUTPUT
make O=$KOUTPUT modules_install

cd $KOUTPUT
for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $BUILDDIR/$(dirname $i)
install -m 644 -v $i $BUILDDIR/$(dirname $i)
done

mkdir $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

|-----handy-ruler------------------------------------------------------|
kernel-jabberwok: kernel and modules 2.6.29.6-jabberwok
kernel-jabberwok:
kernel-jabberwok: Jabberwokky type kernel!
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Kernel-packaging

Dive — Thu, 11 Mar 2010 04:31:55 GMT

Dive: Created page with '= Creating a Custom Package of Kernel and Modules = *Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and …'

= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.

The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==

From your kernel source directory do

make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

make O=/tmp/kernel-build
make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:

for i in $(cat modules.order | sed "s#^kernel/##")
do
mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
done

Now we need the kernel and associated files.

mkdir /tmp/kernel-package/boot

cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

mkdir /tmp/kernel-package/install
echo "/sbin/depmod -a" > /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

cd /tmp/kernel-package
/sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

#!/bin/bash

SOURCE=/usr/src/linux-2.6.29.6-jabberwok
ARCH=i386
KARCH=i686
MODULELIST=modules.order
PRGNAM=kernel
VERSION=2.6.29.6
BUILD=1
TAG=_daw
LOCALNAME=jabberwok
OUTPUT=/tmp
KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
BUILDDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
set -e

rm -rf $KOUTPUT
rm -rf $PKG
mkdir -p $BUILDDIR
mkdir -p $KOUTPUT

cd $SOURCE
make O=$KOUTPUT menuconfig
make mrproper
make O=$KOUTPUT
make O=$KOUTPUT modules_install

cd $KOUTPUT
for i in $(cat $MODULELIST | sed "s#^kernel/##")
do
mkdir -p $BUILDDIR/$(dirname $i)
install -m 644 -v $i $BUILDDIR/$(dirname $i)
done

mkdir $PKG/boot
cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

mkdir $PKG/install
echo "/sbin/depmod -a" > $PKG/install/doinst.sh

cat << EOF > $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.

|-----handy-ruler------------------------------------------------------|
kernel-jabberwok: kernel and modules 2.6.29.6-jabberwok
kernel-jabberwok:
kernel-jabberwok: Jabberwokky type kernel!
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
kernel-jabberwok:
EOF

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)

Utf-8 linux console

Dive — Mon, 01 Mar 2010 13:37:50 GMT

Dive:

[[Category:Tutorials]]
''by Dive''

== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info.

In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
Anyway here we go ...

== The Console ==

The first thing to do is configure the console. There is a kernel parameter we can add to
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.27.7-custom
root = /dev/hda1
label = Linux-custom
append="resume=/dev/hda2 vt.default_utf8=1"
read-only
# Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== Fonts ==

After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.

== Keyboard ==

Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://home.tiscali.nl/t876506/utf8tbl.html]http://home.tiscali.nl/t876506/utf8tbl.html

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

# key = normal shifted AltGr+e AltGr+shift+e
keycode 18 = e E U+00E8 U+00E9
# prints: e E è é

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==

By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.

Note: There exists two shell scripts - '''unicode_start''' and '''unicode_stop'''. Typing '''unicode_start [font]''' will load the required font and set up keyboard correctly for unicode input.

Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)

Utf-8 linux console

Dive — Sat, 08 Aug 2009 18:33:56 GMT

Dive: /* A Quick Look at Using UTF-8 in the Linux Console (without X) */

[[Category:Tutorials]]
''by Dive''

== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info.

In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
Anyway here we go ...

== The Console ==

The first thing to do is configure the console. There is a kernel parameter we can add to
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.27.7-custom
root = /dev/hda1
label = Linux-custom
append="resume=/dev/hda2 vt.default_utf8=1"
read-only
# Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== Fonts ==

After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.

== Keyboard ==

Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://www.tony-franks.co.uk/UTF-8.htm]http://www.tony-franks.co.uk/UTF-8.htm

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

# key = normal shifted AltGr+e AltGr+shift+e
keycode 18 = e E U+00E8 U+00E9
# prints: e E è é

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==

By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.

Note: There exists two shell scripts - '''unicode_start''' and '''unicode_stop'''. Typing '''unicode_start [font]''' will load the required font and set up keyboard correctly for unicode input.

Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)

Utf-8 linux console

Dive — Mon, 27 Jul 2009 20:15:47 GMT

Dive: /* Conclusion */

[[Category:Tutorials]]
== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info.

In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
Anyway here we go ...

== The Console ==

The first thing to do is configure the console. There is a kernel parameter we can add to
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.27.7-custom
root = /dev/hda1
label = Linux-custom
append="resume=/dev/hda2 vt.default_utf8=1"
read-only
# Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== Fonts ==

After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.

== Keyboard ==

Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://www.tony-franks.co.uk/UTF-8.htm]http://www.tony-franks.co.uk/UTF-8.htm

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

# key = normal shifted AltGr+e AltGr+shift+e
keycode 18 = e E U+00E8 U+00E9
# prints: e E è é

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==

By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.

Note: There exists two shell scripts - '''unicode_start''' and '''unicode_stop'''. Typing '''unicode_start [font]''' will load the required font and set up keyboard correctly for unicode input.

Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)

Utf-8 linux console

Dive — Mon, 27 Jul 2009 20:15:19 GMT

Dive: /* Conclusion */

[[Category:Tutorials]]
== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info.

In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
Anyway here we go ...

== The Console ==

The first thing to do is configure the console. There is a kernel parameter we can add to
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.27.7-custom
root = /dev/hda1
label = Linux-custom
append="resume=/dev/hda2 vt.default_utf8=1"
read-only
# Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== Fonts ==

After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.

== Keyboard ==

Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://www.tony-franks.co.uk/UTF-8.htm]http://www.tony-franks.co.uk/UTF-8.htm

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

# key = normal shifted AltGr+e AltGr+shift+e
keycode 18 = e E U+00E8 U+00E9
# prints: e E è é

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==

By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.

Note: There exists two shell scripts - '''unicode_start''' and '''unicode_stop'''. Typing unicode_start [font] will load the required font and set up keyboard correctly for unicode input.

Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)

Utf-8 linux console

Dive — Mon, 27 Jul 2009 20:14:35 GMT

Dive: /* Conclusion */

[[Category:Tutorials]]
== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info.

In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
Anyway here we go ...

== The Console ==

The first thing to do is configure the console. There is a kernel parameter we can add to
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.27.7-custom
root = /dev/hda1
label = Linux-custom
append="resume=/dev/hda2 vt.default_utf8=1"
read-only
# Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== Fonts ==

After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.

== Keyboard ==

Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://www.tony-franks.co.uk/UTF-8.htm]http://www.tony-franks.co.uk/UTF-8.htm

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

# key = normal shifted AltGr+e AltGr+shift+e
keycode 18 = e E U+00E8 U+00E9
# prints: e E è é

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==

By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.

Note: There exists two applications - '''unicode_start''' and '''unicode_stop'''. Typing unicode_start [font] will load the required font and set up keyboard correctly for unicode input.

Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)

Utf-8 linux console

Dive — Mon, 27 Jul 2009 20:13:53 GMT

Dive: /* Conclusion */

[[Category:Tutorials]]
== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info.

In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
Anyway here we go ...

== The Console ==

The first thing to do is configure the console. There is a kernel parameter we can add to
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.27.7-custom
root = /dev/hda1
label = Linux-custom
append="resume=/dev/hda2 vt.default_utf8=1"
read-only
# Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== Fonts ==

After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.

== Keyboard ==

Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://www.tony-franks.co.uk/UTF-8.htm]http://www.tony-franks.co.uk/UTF-8.htm

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

# key = normal shifted AltGr+e AltGr+shift+e
keycode 18 = e E U+00E8 U+00E9
# prints: e E è é

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==

By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.

Note: There exists two applications - '''unicode_start''' and '''unicode_stop'''. Typing unicode_start <font> will load the required font and set up keyboard correctly for unicode input.

Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)