SlackWiki - User contributions [en]

NVIDIA-Prompted-Kernel-Compile

Merge-delete — Fri, 09 Dec 2011 10:35:06 GMT

Merge-delete:

[[Category:Tutorials]]

=== nVidia Graphics Driver Installation & Kernel Recompile in Slackware 12.0 ===

====Warning!====
----

:Please do all this at your own risk. If you change your kernel and c
ause any damage to your system, you and only you are responsible for it. By providing this tutorial I do not take any responsibility for any damages or losses to your system. This is a disclaimer!

==== Background Info & Rationale for Kernel Recompile ====
----
:I recently bought a used ''Geforce N6200'' video card (nvidia chipset) to replace the ''ATI Radeon 9200SE'' that suddenly died on me. I ran Xorg configuration utility ''xorgconfig'' to set the new card up. Slackware 12.0 ships with a generic ''nv'' driver for nvidia cards, but it does not support graphics acceleration and/or direct rendering. That means no games and no graphic heavy websites. Fortunately, nvidia provides a Linux binary driver for your video card that will do direct rendering and 3D acceleration just fine, although the driver is closed-source. But hey, at least it works.

:Assuming that you're running Slackware 12.0 and using huge generic kernel 2.6.21.5 or newer or the smp version of it, you are going to face some problems compiling the nvidia driver against that kernel. The nvidia installer utility compiles the binary driver to suit your kernel. In Slackware 12.0 the support for Riva framebuffer is enabled by default in the huge-2.6.21.5 and huge-2.6.21.5-smp kernels and it is a problem for the nvidia installer utility. As soon as it notes the riva support enabled in the kernel header files, it quits and the driver module compilation fails. Most people will experience this problem in Slackware 12.0. The solution is to disable riva framebuffer support from the kernel and recompile it.

:At the end of this tutorial you will have a fresh kernel compiled for your system, the nvidia driver compiled against this kernel and installed as kernel module and 3D graphics acceleration as well as direct rendering enabled. So let's begin taking one thing at a time.

==== Back Up Current Kernel & Kernel Modules ====
----

:It is important that you have a backup of your currently working kernel modules so if the new kernel fails, you would still be able to use the old kernel to boot the system. Let's play safe. Important: All steps in this tutorials are done as superuser.

cd /lib/modules
ls
2.6.21.5 2.6.21.5-smp

:Above currently installed kernels on your system are listed. Rename the kernel you're using to something like ''kernel-name''.backup. If you do not know which kernel you're using, do the following. The output of it should list the kernel you're using. Once you find it out, rename it as follows.

uname -a
Linux 2.6.21.5 #1 Sun Mar 16 14:46:57 CDT 2008 i686 AMD Athlon(tm) AuthenticAMD GNU/Linux

mv 2.6.21.5 2.6.21.5-backup
ls
2.6.21.5-smp 2.6.21.5-backup

==== Kernel Configuration and Recompile ====
----

:Now that we have a backup of our current kernel and its modules, its time to proceed with configuration and recompiling the kernel. Change to the kernel source directory and copy the current kernel config file to the kernel source directory

cd /usr/src/linux
cp /boot/config .config #Note that config in /boot has no dot before it, but when we copy it, we include a dot prefix.

This step will copy your current configuration so we can use it as a reference for further steps. Now let's begin kernel configuration

make menuconfig

This should give you a nice ''ncurses'' style detailed graphical menu of kernel configuration.

Select Device Drivers > Graphics Support >

:Scroll down to ''Riva Framebuffer Support'' (not ''nvidia Riva Support'') and press space bar twice. First space bar press will change the <M> to <*> and second will change <*> to < > (blank). Now press ''exit'' three times. The menuconfig will ask you if you want to save the changes. Select ''Yes'' and quit. We have now removed Riva Framebuffer Support from kernel configuration, the culprit for failing nvidia driver module compilation.

:It's time to compile the kernel. Do the following:

make bzImage

:This is a good time to take a break for any of these: Coffee / Tea / Cigarette / Quick run to the grocery store. In short, depending upon how fast your procesor is, this step will take anywhere between 15 minutes to an hour. If everything goes fine, it will compile a new kernel and install newly compiled modules in /lib/modules/. If you get errors, something went wrong and you'll need to get some help from kernel documentation or ask in ##slackware on IRC host ''freenode.net''

:Now that we have a kernel compiled, its time to compile and install kernel modules

make modules && make modules_install

:Again, this step will take some time. But it will be worth the wait. In the basic kernel, there is close to 1000 modules that need to be compiled. Once this step is finished and you did not get any errors, its time to make sure the kernel bzImage was created and the modules were installed to the appropriate location.

pwd
/usr/src/linux
cd arch/i386/boot
pwd
/usr/src/linux/arch/i386/boot
ls
Makefile bootsect.S '''bzImage''' edd.S mtools.conf.in setup.S tools vmlinux.bin
bootsect bootsect.o compressed install.sh setup setup.o video.S

:bzImage is your newly compiled kernel without Riva framebuffer support.

cd /lib/modules
ls
2.6.21.5 2.6.21.5-smp 2.6.21.5-backup

The first entry above is the location of your newly installed kernel modules.

==== Install New Kernel And Update lilo.conf ====
----

:Time to install the new kernel and notify your boot loader of its existence.

cd /usr/src/linux/arch/i386/boot
cp bzImage /boot

:Open your favorite text editor and add following lines to your boot loader (typically /etc/lilo.conf)

cd /etc
emacs -nw lilo.conf

#Linux bootable partition config begins
image = /boot/bzImage
root = /dev/hda2 #or whatever partition your / is located on
label = New-Kernel #You can name it whatever you want. Just don't name it the same as the old kernel
#Linux bootable partition config ends

:Save file, close it and run lilo so the new changes take effect.

lilo
Added *Linux
Added *New-Kernel

:Excellent! It's time to test the new kernel. When you reboot, lilo will now present you with two choices for kernel, use the New-Kernel and boot. If somehow it fails, you can always go back to the old kernel. Just rename the /lib/modules/2.6.21.5-backup as 2.6.21.5 and rename the new kernel modules as something else. You see how important it was for us to backup the kernel as well as kernel modules in the beginning?

:Assuming that your new kernel booted just fine and you had a fully functional system back up, its time to get the nVidia graphics driver from nvidia.com and install it. The current incarnation of nVidia driver is version # 169.12. Either use your favorite browser to download the driver from http://www.nvidia.com/Download/index.aspx?lang=en-us or do the following:

cd /tmp
wget http://us.download.nvidia.com/XFree86/Linux-x86/169.12/NVIDIA-Linux-x86-169.12-pkg1.run

Make the installer utility executable and execute it

chmod 755 NVIDIA-Linux-x86-169.12-pkg1.run
ls -la
-rwxr-xr-x 1 user groupname 17636559 2008-03-17 13:06 NVIDIA-Linux-x86-169.12-pkg1.run

Before we execute it, we need to exit the X server.

telinit 3 #This changes runlevel to 3, shuts down the X server and drops you off at the terminal
sh ./NVIDIA-Linux-x86-169.12-pkg1.run

:This installer utility first tries to find a pre-compiled driver for your kernel which it would not find, then it tries to download it via ftp from nvidia servers which fails too, and finally it proceeds to compile the driver kernel module against your newly installed bzImage kernel. This time, there is no riva framebuffer in the kernel header files and so this step should not fail. Should it fail, ask for help in your local LUG or the highly knowledgeable folks at ##slackware in irc channel freenode.net

==== Updating X.Org Configuration File ====
----

:After the installer utility finishes compiling and installing kernel module for the nvidia driver, it will ask you if you want it to make appropriate changes to your /etc/X11/xorg.conf. I personally chose not to, because I did not want my already customized xorg.conf to be messed with by a third party software. I simply changed the driver name from '''nv''' to '''nvidia''' in the <device> section of /etc/X11/xorg.conf

:That's it folks. You now have a new kernel, new kernel modules and nvidia driver with 3D acceleration and direct rendering. Check direct rendering as follows:

glxinfo | grep dri

:Third line of the output should tell you that Direct Rendering has been enabled. Now its time to fire up X server and check your new driver.

telinit 4

:This should launch X server, you should be seeing a flash of nvidia screen and then back to your favorite window manager. If everything went fine, you should go ahead and check video performance with some game, or a graphics intensive website or such.

==== Acknowledgements ====
----

:This article benefited substantially by input from ##slackware (irc.freenode.net) user '''InspectorCluseau'''

:If you have any questions or if you find a mistake in this tutorial, please contact me at [mailto:crypticlineage@gmail.com]

Kernel-packaging

Merge-delete — Fri, 09 Dec 2011 10:34:52 GMT

Merge-delete:

= 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 pleae 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)

Apache-cgi

Merge-delete — Fri, 09 Dec 2011 10:34:48 GMT

Merge-delete:

[[Category:Tips]]

==To enable a cgi directory for each user==
In order to give each user their own cgi-bin directory, edit the:

:Apache1 (Slackware pre-12.0): <code>/etc/httpd/httpd.conf</code> file 
:Apache2 (Slackware 12.0+): <code>/etc/httpd/extra/httpd-users.conf</code> file 

::...and add:

:<code><Directory /home/*/public_html/cgi-bin/></code>
:<code>Options ExecCGI</code>
:<code>SetHandler cgi-script</code>
:<code></Directory></code>

Then, presuming that UserDir is set to public_html, a cgi program example.cgi could be loaded from that directory as:

::<code>http://example.com/~rbowen/cgi-bin/example.cgi</code>

==To enable a cgi directory for each virtual host==

In the Virtual Host section of your apache config file (<code>/etc/apache/httpd.conf</code>) add the <code>ScriptAlias</code> line below.

:<code><VirtualHost *:80></code>
:::<code>ServerName www.''MyDomain''.org</code>
:::<code>DocumentRoot /home/''MyDomain''/public_html</code>
:::<code>ErrorLog /var/log/''MyDomain''/error.log</code>
:::<code>ScriptAlias /cgi-bin/ "/home/''MyDomain''/public_html/cgi-bin/"</code>
:<code></VirtualHost></code>

Log Correlation

Merge-delete — Fri, 09 Dec 2011 10:34:43 GMT

Merge-delete:

[[Category:Tutorials]]

'''Log Correlation'''
I thought I'd talk about the importance of log correlation. For instance, you've found that someone is continually pinging your server. You want to see if your box is responding to the pings. Usually, you'll know right off, since most people know if their firewall was configured to block pings...I'm just using pings as a quick example, though. Log correlation usually consists of checking, for instance, web server logs against firewall logs, or Snort logs against firewall and web server logs. This helps you understand what suspicious activity is actually doing and if your server/workstation responded (and how it responded, if it did).

I run Snort on a server, along with a web server, which is firewalled with IPTables. I have Snort report what it sees to a MySQL database, although it does record captures to a PCAP file locally. I also run Modsecurity, an application firewall that is designed to sniff and possibly block traffic going to/from web servers, mainly Apache. So, I've a ton of logs that I can correlate: Snort, Apache, IPTables, and Modsecurity logs.

We'll pick something easy. In fact, I'll fabricate some logs by generating some false alerts. I'll use 'wget', to visit my website. Keep in mind that what you see below gives you the advantage...you know what you're doing and looking for when we soon check the logs. This won't be the case when some stranger or worm hits your firewall or web server (or any other application server).

-bash-2.05b$ wget wigglit.ath.cx/root.exe
--23:24:05-- http://wigglit.ath.cx/root.exe
=> `root.exe'
Resolving wigglit.ath.cx... 66.160.141.30
Connecting to wigglit.ath.cx|66.160.141.30|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
23:24:06 ERROR 404: Not Found.

-bash-2.05b$

I used root.exe because there is an old vulnerability was was used to exploit flaws in IIS...the CodeRed worm of old. Now, let's check the web server's logs. I've tail'd my logs:

root@starchild:/var/log/apache# tail -f -n 100 access_log
12.123.12.123 - - [15/Sep/2007:23:34:35 -0400] "GET /root.exe HTTP/1.0" 404 202
12.123.12.123 - - [15/Sep/2007:23:34:35 -0400] "GET /root.exe HTTP/1.0" 404 202 "-" "Wget/1.10.2"

You see that the communcation was accepted. A 404 code, which means 'page not found', was generated. This is usually a good indication, as the server didn't respond favorably to the attack.

Now, let us check the firewall logs. We already know that the firewall allowed the traffic, since the web server responded with a 404...if the traffic was being blocked, there would be no record of the attack in the logs, because the firewall would have intercepted the traffic before it reached the web server. We're checking the firewall logs just to be sure this guy hasn't done anything else that the web server didn't see:

Sep 12 17:28:34 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=34557 DF PROTO=TCP SPT=46656 DPT=10083 WINDOW=5840 RES=0x00 SYN URGP=0
Sep 12 17:28:44 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=18168 DF PROTO=TCP SPT=40091 DPT=449 WINDOW=5840 RES=0x00 SYN URGP=0
Sep 12 17:28:44 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=27053 DF PROTO=TCP SPT=36295 DPT=5060 WINDOW=5840 RES=0x00 SYN URGP=0
Sep 12 17:28:54 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=29291 DF PROTO=TCP SPT=47590 DPT=342 WINDOW=5840 RES=0x00 SYN URGP=0
Sep 12 17:28:54 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=11788 DF PROTO=TCP SPT=43604 DPT=1519 WINDOW=5840 RES=0x00 SYN URGP=0
Sep 12 17:29:04 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=17600 DF PROTO=TCP SPT=32783 DPT=577 WINDOW=5840 RES=0x00 SYN URGP=0
Sep 12 17:29:04 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=51338 DF PROTO=TCP SPT=47879 DPT=18187 WINDOW=5840 RES=0x00 SYN URGP=0
Sep 12 17:29:14 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=58520 DF PROTO=TCP SPT=41983 DPT=517 WINDOW=5840 RES=0x00 SYN URGP=0
Sep 12 17:29:14 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=20255 DF PROTO=TCP SPT=53355 DPT=1986 WINDOW=5840 RES=0x00 SYN URGP=0
Sep 12 17:29:24 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=28213 DF PROTO=TCP SPT=38543 DPT=978 WINDOW=5840 RES=0x00 SYN URGP=0
Sep 12 17:29:24 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=10244 DF PROTO=TCP SPT=45624 DPT=11371 WINDOW=5840 RES=0x00 SYN URGP=0
Sep 12 17:29:37 starchild kernel: ICMP-request: IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=28 TOS=0x00 PREC=0x00 TTL=42 ID=53002 PROTO=ICMP TYPE=8 CODE=0 ID=10683 SEQ=16615
Sep 15 23:21:08 starchild kernel: ICMP-request: IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=84 TOS=0x00 PREC=0x00 TTL=55 ID=40988 PROTO=ICMP TYPE=8 CODE=0 ID=614 SEQ=0

Quite a bit of stuff, huh? This looks to be a port scan! This is something that we didn't see in the Apache logs! Good thing we checked! Looks like this IP needs to be blocked with IPTables (which we won't do in this exercise).

Sadly, nothing shows in the Modsecurity logs, but we've enough information already. What about Snort? Because I've PCAP files, the search becomes a bit more involved. I'll spare the intimate details, but this is what we see:

[**] [1:1256:9] WEB-IIS CodeRed v2 root.exe access [**]
[Classification: Web Application Attack] [Priority: 1]
09/15-23:34:35.708546 0:C:DB:F5:90:0 -> FE:FD:40:3E:E7:DC type:0x800 len:0xB0
12.123.12.123:52753 -> 66.160.141.30:80 TCP TTL:56 TOS:0x0 ID:51589 IpLen:20 DgmLen:162 DF
***AP*** Seq: 0xAF32BB68 Ack: 0x3F319F7A Win: 0xFFFF TcpLen: 32
TCP Options (3) => NOP NOP TS: 288652007 1521931210
[Xref => http://www.cert.org/advisories/CA-2001-19.html]

23:34:35.708546 00:0c:db:f5:90:00 > fe:fd:40:3e:e7:dc, ethertype IPv4 (0x0800), length 176: IP (tos 0x0, ttl 56, id 51589, offset 0, flags [DF], length: 162) 12.123.12.123.52753 > 66.160.141.30.80: P [tcp sum ok] 2939337576:2939337686(110) ack 1060216698 win 65535
0x0000: fefd 403e e7dc 000c dbf5 9000 0800 4500 ..@>..........E.
0x0010: 00a2 c985 4000 3806 56c0 47b2 0aa0 42a0 ....@.8.V.G...B.
0x0020: 8d1e ce11 0050 af32 bb68 3f31 9f7a 8018 .....P.2.h?1.z..
0x0030: ffff e9c5 0000 0101 080a 1134 7ae7 5ab6 ...........4z.Z.
0x0040: d3ca 4745 5420 2f72 6f6f 742e 6578 6520 ..GET./root.exe.
0x0050: 4854 5450 2f31 2e30 0d0a 5573 6572 2d41 HTTP/1.0..User-A
0x0060: 6765 6e74 3a20 5767 6574 2f31 2e31 302e gent:.Wget/1.10.
0x0070: 320d 0a41 6363 6570 743a 202a 2f2a 0d0a 2..Accept:.*/*..
0x0080: 486f 7374 3a20 7769 6767 6c69 742e 6174 Host:.wigglit.at
0x0090: 682e 6378 0d0a 436f 6e6e 6563 7469 6f6e h.cx..Connection
0x00a0: 3a20 4b65 6570 2d41 6c69 7665 0d0a 0d0a :.Keep-Alive....

The first is the Snort alert file...this is a fast alert, with minimal detail (no packet capture). The second section is the full alert, including packet capture. It is also garbled (due to the hex code and the fact that this blog has issues with formatting) Note that my logs show no response. Apparently, my Snort install doesn't have a 404 signature. Again, the fact that we can correlate helps me when my Snort install lacks the data that I may have needed. I was able to look at the Apache logs to see the 404 when my Snort logs didn't show the return traffic.

Well, this concludes our chat about correlating existing logs. Note that any log files can be correlated. Correlation can also assist in tracking down network issues or issues with, for instance, a faulty Snort install (ahem). Although this discussion focused more on security, hopefully this helps someone understand their network or software architecture also.

This page is also linked at [http://slackfiles.blogspot.com/2007/09/log-correlation.html my blog]

--[[User:Unixfool|Ron]] 00:35, 16 September 2007 (EDT)

Mount Count

Merge-delete — Fri, 09 Dec 2011 10:33:27 GMT

Merge-delete:

[[Category:Information]]
A count of how many times a filesystem has been mounted. Used to determine whether a [[Forced Fuck]] should be executed.

After a successful fsck (filesystem check), the mount count is reset to zero. When the mount count reaches (or exceeds) the [[Maximum Mount Count]], a Forced Fsck is executed during boot.

Packages

Merge-delete — Fri, 09 Dec 2011 10:33:23 GMT

Merge-delete:

Slackware's package management system utilizes .tgz/.txz tarballs as its standard package format. These tarballs are tar.gz/tar.xz archives which contain Slackware built binaries, support files, a description file and installation script. Although they can be unzipped and untarred like a normal archive, they are (usually) binary-only packages intended to be installed through Slackware's provided package management tools.

Information about a package is stored in two ways, in the filename of the package and a description file inside that package.

==Package Tools==
See the respective manual pages for more information on each of the following commands.

<code>pkgtool</code>

<code>installpkg</code>

<code>removepkg</code>

<code>explodepkg</code>

<code>makepkg</code>

<code>upgradepkg</code>

==Slackware Package Layout==
A typical Slackware package is laid out as such:
./
./install/doinst.sh
./install/slack-desc
[./usr/bin]
[./usr/lib]
[...]

The install directory as well as the files within it will be deleted after the installation of the package to the root install directory (usually '/'). The install directory is not necessarily required for the most basic packages but allows additional functionality: [[slack-desc]] contains the package description, and [[doinst.sh]] contains post-installation instructions such as creating symbolic links.

Every other file within the package is simply untarred (extracted) to the root directory. Most of these files are in standard locations.

There are other special files within packages:

'''usr/doc/<appname><version>'''
All documentation included with the package (such as README, INSTALL, ChangeLog, docs/, etcetera) should be placed in this directory. Some of the files in this directory should be manually copied from the source archive, since Makefiles usually don't copy these documentation files to the package build tree.

==Making Slackware Packages==
See [[Building A Package]]

[[Category: Information]]

Writing A SlackBuild Script

Merge-delete — Fri, 09 Dec 2011 10:32:00 GMT

Merge-delete:

[[Category:Tutorials]]

= Introduction =
Originally written by Florian Mueller jjdm@jjdm.org
Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like linuxpackages.net, or perhaps you just don't like using third-party packages. In this situation, you have several options on how to instll the application:

* ./configure && make && make install
* use checkinstall
* use installwatch
* compile and use makepkg by hand
* write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system. You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly. What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named <build_environment>/latex2html/. Get the most recent source code release of latex2html place it in this directory. Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

$ cd <build_environment>
$ mkdir latex2html
$ cd latex2html
$ wget http://saftsack.fs.uni-bayreuth.de/~latex2ht/current/latex2html-2002-2-1.tar.gz # 05.02.2005

Next, we'll create some other needed files with touch. If you're not familiar with touch, see:
man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

$ touch latex2html.SlackBuild
$ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

$ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step. When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts. Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor. What follows below is a piece by piece walk-through of a working SlackBuild script. You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter. This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability. For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly. The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

#!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

#<your name> revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be <build_environment>/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

#Set initial variables:

CWD=$(pwd)
if [ "$TMP" = "" ]; then
TMP=/tmp
fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.

# The version which appears in the application's filename
VERSION=2002-2-1

# If the version conflicts with the Slackware package standard
# The dash character ("-") is not allowed in the VERSION string
# You can set the PKG_VERSION to something else than VERSION
PKG_VERSION=2002.2.1 # the version which appears in the package name.

ARCH=${ARCH:-i486} # the architecture on which you want to build your package

# First digit is the build number, which specifies how many times it has been built.
# Second string is the short form of the authors name, typical three initials:w
BUILD=${BUILD:-1_rlw}

# The application's name
APP=latex2html

# The installation directory of the package (where its actual directory
# structure will be created)
PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS). If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

if [ "$ARCH" = "i486" ]; then
SLKCFLAGS="-O2 -march=i486 -mtune=i686"
elif [ "$ARCH" = "x86_64" ]; then
SLKCFLAGS="-O2 -fPIC"
fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

# Delete the leftover directories if they exist (due to a previous build)
# and (re)create the packaging directory
rm -rf $PKG
mkdir -p $TMP $PKG
rm -rf $TMP/$APP-$VERSION

# Change to the TMP directory
cd $TMP || exit 1

# Extract the application source in TMP
# Note: if your application comes as a tar.bz2, you need tar -jxvf
tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1

# Change to the application source directory
cd $APP-$VERSION || exit 1

# Change ownership and permissions if necessary
# This may not be needed in some source tarballs, but it never hurts
chown -R root:root .
chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

# Set configure options
# If your app is written in C++, you'll also need to add a line for CXXFLAGS
CFLAGS="$SLKCFLAGS" \
./configure \
--prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var \
--with-perl=/usr/bin/perl \
--enable-eps \
--enable-gif \
--enable-png \
--build=$ARCH-slackware-linux \
--host=$ARCH-slackware-linux

# compile the source, but exit if anything goes wrong
make || exit

# Install everything into the package directory, but exit if anything goes wrong
make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location. See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process. You simply cd into the source directory and run:
./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application. Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
./configure --help | lpr
./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed. This should always be our package directory ($PKG). Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps. A simple line like this:
grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not. If you get some lines of output with $DESTDIR in them, you're in good shape. If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure && make && make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script. There are quite a few applications out there which try to do "funny stuff" during the installation phase.
For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

# Create a directory for documentation
mkdir -p $PKG/usr/doc/$APP-$VERSION

# Copy documentation to the docs directory and fix permissions
cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
cat $CWD/$APP.SlackBuild > $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files. In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

# Create the ./install directory and copy the slack-desc into it
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip. The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and
write the output to a doinst.sh file in the $PKG/install directory.

# Add doinst.sh to package (if it exists)
if [ -e $CWD/doinst.sh.gz ]; then
zcat $CWD/doinst.sh.gz > $PKG/install/doinst.sh
fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

# Strip some libraries and binaries
( cd $PKG
find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
)

# Compress man pages if they exist
if [ -d $PKG/usr/man ]; then
( cd $PKG/usr/man
find . -type f -exec gzip -9 {} \;
for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
)
fi

# Compress info pages if they exist (and remove the dir file)
if [ -d $PKG/usr/info ]; then
gzip -9 $PKG/usr/info/*.info
rm -f $PKG/usr/info/dir
fi

=== Build the Package ===

# Build the package
cd $PKG
/sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install. On some applications the DESTDIR Makefile variable has another name. For example, some Qt [http://buyphentermine.herbalweightlossaid.com/ Phen375] applications use the variable INSTALL_ROOT for the same purpose. If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule. Sometimes there will be no DESTDIR equivalent at all. The best thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the [http://www.performer5pills.info/ performer 5] developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that. The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases. In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
./configure --prefix=$PKG/usr
along with your other configure options. This will install *all* of the package contents in that directory. If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move [http://weightlossproductreviews.info/ slimming reviews] them to their correct location within the package directory [http://www.hghadvancedreview.info/ HGH Advanced] tree and everything will be fine. You might also try this along with your other configure options.
./configure --prefix=$PKG/usr \
--sysconfdir=$PKG/etc \
--localstatedir=$PKG/var
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters. In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include [http://www.clearskinmaxreview.info/ clear skin max] instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile. This approach makes it a bit [http://www.hoodiapill.info/ unique hoodia] easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the [http://weightlossproductreviews.info/?page_id=268 slim weight patch] command line. Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make). Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix. For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one [http://www.teethwhitenerguide.com/ teeth whitener reviews] being a template for the "configure" script. Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the [http://www.phen375reviewed.info/ phen375 fat burner] package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here. Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
$ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because [http://www.herbalweightlossaid.com/ slimming pills] developers generally want to conserve space if possible, it's conventional to do this:
$ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your <application>.SlackBuild script so that it applies the patch before it runs configure, make, and make install. To do this, you'll want something like this to run before the configure [http://www.capsiplexreview.info/ capsiplex] script, but after extracting the sources:
zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the [http://proactolpluspills.com/ proactol plus] scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch. You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/
;* http://www2.linuxpackages.net/packages/SlackBuilds/
;* http://www.selkfoster.com.ar/downloads/slackbuilds/
;* http://slack.sarava.org/slackbuilds/

Writing A SlackBuild Script

Merge-delete — Fri, 09 Dec 2011 10:31:03 GMT

Merge-delete:

[[Category:Tutorials]]

= Introduction =

Originally written by Florian Mueller jjdm@jjdm.org
Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like linuxpackages.net, or perhaps you just don't like using third-party packages. In this situation, you have several options on how to instll the application:

* ./configure && make && make install
* use checkinstall
* use installwatch
* compile and use makepkg by hand
* write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system. You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly. What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named <build_environment>/latex2html/. Get the most recent source code release of latex2html place it in this directory. Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

$ cd <build_environment>
$ mkdir latex2html
$ cd latex2html
$ wget http://saftsack.fs.uni-bayreuth.de/~latex2ht/current/latex2html-2002-2-1.tar.gz # 05.02.2005

Next, we'll create some other needed files with touch. If you're not familiar with touch, see:
man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

$ touch latex2html.SlackBuild
$ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

$ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step. When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts. Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor. What follows below is a piece by piece walk-through of a working SlackBuild script. You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter. This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability. For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly. The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

#!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

#<your name> revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be <build_environment>/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

#Set initial variables:

CWD=$(pwd)
if [ "$TMP" = "" ]; then
TMP=/tmp
fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.

# The version which appears in the application's filename
VERSION=2002-2-1

# If the version conflicts with the Slackware package standard
# The dash character ("-") is not allowed in the VERSION string
# You can set the PKG_VERSION to something else than VERSION
PKG_VERSION=2002.2.1 # the version which appears in the package name.

ARCH=${ARCH:-i486} # the architecture on which you want to build your package

# First digit is the build number, which specifies how many times it has been built.
# Second string is the short form of the authors name, typical three initials:w
BUILD=${BUILD:-1_rlw}

# The application's name
APP=latex2html

# The installation directory of the package (where its actual directory
# structure will be created)
PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS). If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

if [ "$ARCH" = "i486" ]; then
SLKCFLAGS="-O2 -march=i486 -mtune=i686"
elif [ "$ARCH" = "x86_64" ]; then
SLKCFLAGS="-O2 -fPIC"
fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

# Delete the leftover directories if they exist (due to a previous build)
# and (re)create the packaging directory
rm -rf $PKG
mkdir -p $TMP $PKG
rm -rf $TMP/$APP-$VERSION

# Change to the TMP directory
cd $TMP || exit 1

# Extract the application source in TMP
# Note: if your application comes as a tar.bz2, you need tar -jxvf
tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1

# Change to the application source directory
cd $APP-$VERSION || exit 1

# Change ownership and permissions if necessary
# This may not be needed in some source tarballs, but it never hurts
chown -R root:root .
chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

# Set configure options
# If your app is written in C++, you'll also need to add a line for CXXFLAGS
CFLAGS="$SLKCFLAGS" \
./configure \
--prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var \
--with-perl=/usr/bin/perl \
--enable-eps \
--enable-gif \
--enable-png \
--build=$ARCH-slackware-linux \
--host=$ARCH-slackware-linux

# compile the source, but exit if anything goes wrong
make || exit

# Install everything into the package directory, but exit if anything goes wrong
make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location. See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process. You simply cd into the source directory and run:
./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application. Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
./configure --help | lpr
./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed. This should always be our package directory ($PKG). Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps. A simple line like this:
grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not. If you get some lines of output with $DESTDIR in them, you're in good shape. If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure && make && make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script. There are quite a few applications out there which try to do "funny stuff" during the installation phase.
For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

# Create a directory for documentation
mkdir -p $PKG/usr/doc/$APP-$VERSION

# Copy documentation to the docs directory and fix permissions
cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
cat $CWD/$APP.SlackBuild > $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files. In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

# Create the ./install directory and copy the slack-desc into it
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip. The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and
write the output to a doinst.sh file in the $PKG/install directory.

# Add doinst.sh to package (if it exists)
if [ -e $CWD/doinst.sh.gz ]; then
zcat $CWD/doinst.sh.gz > $PKG/install/doinst.sh
fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

# Strip some libraries and binaries
( cd $PKG
find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
)

# Compress man pages if they exist
if [ -d $PKG/usr/man ]; then
( cd $PKG/usr/man
find . -type f -exec gzip -9 {} \;
for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
)
fi

# Compress info pages if they exist (and remove the dir file)
if [ -d $PKG/usr/info ]; then
gzip -9 $PKG/usr/info/*.info
rm -f $PKG/usr/info/dir
fi

=== Build the Package ===

# Build the package
cd $PKG
/sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install. On some applications the DESTDIR Makefile variable has another name. For example, some Qt [http://buyphentermine.herbalweightlossaid.com/ Phen375] applications use the variable INSTALL_ROOT for the same purpose. If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule. Sometimes there will be no DESTDIR equivalent at all. The best thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the [http://www.performer5pills.info/ performer 5] developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that. The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases. In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
./configure --prefix=$PKG/usr
along with your other configure options. This will install *all* of the package contents in that directory. If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move [http://weightlossproductreviews.info/ slimming reviews] them to their correct location within the package directory [http://www.hghadvancedreview.info/ HGH Advanced] tree and everything will be fine. You might also try this along with your other configure options.
./configure --prefix=$PKG/usr \
--sysconfdir=$PKG/etc \
--localstatedir=$PKG/var
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters. In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include [http://www.clearskinmaxreview.info/ clear skin max] instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile. This approach makes it a bit [http://www.hoodiapill.info/ unique hoodia] easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the [http://weightlossproductreviews.info/?page_id=268 slim weight patch] command line. Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make). Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix. For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one [http://www.teethwhitenerguide.com/ teeth whitener reviews] being a template for the "configure" script. Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the [http://www.phen375reviewed.info/ phen375 fat burner] package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here. Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
$ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because [http://www.herbalweightlossaid.com/ slimming pills] developers generally want to conserve space if possible, it's conventional to do this:
$ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your <application>.SlackBuild script so that it applies the patch before it runs configure, make, and make install. To do this, you'll want something like this to run before the configure [http://www.capsiplexreview.info/ capsiplex] script, but after extracting the sources:
zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the [http://proactolpluspills.com/ proactol plus] scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch. You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/
;* http://www2.linuxpackages.net/packages/SlackBuilds/
;* http://www.selkfoster.com.ar/downloads/slackbuilds/
;* http://slack.sarava.org/slackbuilds/

Kernel26Compilation

Merge-delete — Fri, 09 Dec 2011 10:29:51 GMT

Merge-delete:

How to build a 2.6.x Kernel on Slackware

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: <code>mkdir pidgin</code>
: <code>cd pidgin</code>
: <code>wget --passive-ftp <nowiki>ftp://slackware.at/slackware-12.1/source/xap/pidgin/*</nowiki></code>
Note: Maybe this replaces the 2.6 part of the kernel compile tutorial already here.

==Warning!==
If you work on your kernel and do something wrong you may destroy your system in a way you have to reinstall it. All actions on your own risk! Noone assures that all actions described here are 100% right and work in any case. We are not responsible for damages caused by following this tutorial!

==Prerequisites==

* Get the kernel sources you want from ftp://ftp.de.kernel.org or from a mirror (http://www.kernel.org/mirrors/).
* Make sure you are able toboot your Slackware original kernel after kernel update (You have to install 2.6.13 from "testing" to do this-slack12 uses 2.6.21.5 by default, no need to install it)

image = /boot/vmlinuz-generic-2.6.13 
root = /dev/ #Your root partition. Get this from another kernel entry or from original /etc/lilo.conf
label = Backup
read-only

Now run "lilo" once as root
* If you want to play safe you may now reboot and try if the kernel boots without errors.
* Uncompress your kernel sources below /usr/src
* The symlink /usr/src/linux has to point to the directory of the new kernel. For example: /usr/src/linux -> /usr/src/linux-2.6.14.4

==Configure the kernel==

* Change to the kernel directory.
cd /usr/src/linux

* Configure your kernel:
** From scratch, then you may choose from

make config (You get prompted for all possible options)
make menuconfig (You get a nice menu where you may navigate with cursor keys. Needs curses-5.x)
make xconfig (You may configure in X, of course needs working X installation)
make gconfig
make qtconfig

:* From old configuration:
Copy the config file of the old kernel to ./.config. If you want to come from orignal Slackware kernel, then:

cp /boot/config .config

After that "make oldconfig" to configure new features (you may acceppt all questions with "Enter" to use the default values) and use "make menuconfig" (or any other of the above list) to change things if you like.

Important! Be sure to compile the alsa modules (or you won't have sound). You have also to do this if you used "make oldconfig" (for example using "make menuconfig") as the original kernel is compiled without alsa.

==Compile and install kernel==

* The real compiling can start:

make (Now, depending on your computer, you may go drinking some coffee, watch a movie or go on your balcony to smoke one ;-) )

If this finished without errors (we assume this) then your kernel and your kernel modules should be compiled.

* Remove symlinks. If you still run your original slackware kernel, then "vmlinuz" and "System.map" are Symlinks to the kernel files. To get sure that we don't override this files, we delete the symlinks

rm /boot/vmlinuz /boot/System.map

* Install the kernel

Install the kernel modules with: 
make modules_install

and the kernel with: 
make install

* If all steps have been done successful you may now use your new (self-made) kernel.

==Troubleshooting==

* Help, the kernel doesn't work!

Choose your backup kernel on lilo, check your kernel configuration and recompile.

* Choose your backup kernel sounds easy, but...

Now you know why you should keep a running kernel before you install a new one. Either your system is as usable as you are able to check the kernel configuration or you may boot from your slackware setup CD, mount your root partition to /mnt, chroot /mnt and recompile your kernel from there or install slackware packages of a running kernel.

[http://www.slackforum.de/wiki/Kernel26Kompilieren german version]

[[Category:Tutorials]]

Windows Partitions

Merge-delete — Fri, 09 Dec 2011 10:29:35 GMT

Merge-delete:

One of the frequent questions on ##slackware is something along the lines of "How can I allow normal users to access my Windows partition?" There are *at least* two different ways of doing this.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: <code>mkdir pidgin</code>
: <code>cd pidgin</code>
: <code>wget --passive-ftp <nowiki>ftp://slackware.at/slackware-12.1/source/xap/pidgin/*</nowiki></code>

For a FAT partition, you *could* add umask=0000 to /etc/fstab's options, but I personally don't recommend doing that. It's *your* computer, so you make the call, but I would do something along these lines:

1. If you want *every* user to be able to read and write to the partition, then you can add dmask=0000 and fmask=0111 to /etc/fstab's options and be done with it - problem solved.

/dev/hda1 /mnt/win98 vfat rw,dmask=0000,fmask=0111 0 0

The reason for dmask/fmask as opposed to umask is quite obvious (though I hadn't thought about it until elohim on ##slackware pointed it out): The FAT and NTFS file systems don't "understand" the executable (-x) bit, so it's automatically present on every file in such a filesystem. There's no need for normal files to be executable (and it can indeed be a security risk), so we use fmask to turn off those permissions.

2. If you only want some users to be able to read and write to the partition, but you want *every* user to have read access, then you'll want something along these lines. First, create a special group called "windows" (change the name if you wish) by adding it to /etc/group using your favorite editor and add to this group the users you want to have write access.

nogroup:x:99:
users:x:100:
console:x:101:
windows:x:102:user1,user2,user3

Next, edit your /etc/fstab line for that partition and specify that it be mounted with group ownership of the "windows" group, and that write access be removed from others.

/dev/hda1 /mnt/win98 vfat rw,gid=102,dmask=0002,fmask=0113 0 0

An NTFS partition will be mounted read-only, so you won't have write access for anyone, but the central idea is the same.

If you don't want everyone else to even have read access to the partition, you can easily do that with the above fstab line modified a bit:

/dev/hda1 /mnt/winXP ntfs ro,gid=102,dmask=0227,fmask=0337 0 0

If you prefer write access to the partition, then you can use ntfs-3g instead and something like this:
All users can read the partition; only members of gid 102 can write:
/dev/hda1 /mnt/win98 ntfs-3g rw,gid=102,dmask=0002,fmask=0113 0 0
Users of gid can read and write; nobody else can do anything:
/dev/hda1 /mnt/winXP ntfs-3g rw,gid=102,dmask=0007,fmask=0117 0 0

For more information, see the [[Permissions and Umasks]] and [[Fstab]] pages.

--rworkman (thanks to Erik for the pointers about dmask and fmask)

[[Category:Tutorials]]

SlackBuild Scripts

Merge-delete — Fri, 09 Dec 2011 10:29:16 GMT

Merge-delete:

SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: <code>mkdir pidgin</code>
: <code>cd pidgin</code>
: <code>wget --passive-ftp <nowiki>ftp://slackware.at/slackware-12.1/source/xap/pidgin/*</nowiki></code>

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: <code>mkdir pidgin</code>
: <code>cd pidgin</code>
: <code>wget --passive-ftp <nowiki>ftp://slackware.at/slackware-12.1/source/xap/pidgin/*</nowiki></code>

This downloads the files needed for Slackware scripts. The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script. For example, in the pidgin source directory, you would need the following files:

: <code>pidgin-2.4.1.tar.bz2 pidgin-encryption-3.0.tar.gz pidgin.SlackBuild* slack-desc </code>

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: <code>VERSION=2.4.1</code>

This is the line we are looking at. Now we can change this to

: <code>VERSION=2.4.2</code>

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: <code>chmod +x pidgin.SlackBuild</code>

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: <code>su -</code>

Now we start the script, and this will compile Pidgin and make a Slackware package. Depending on how the
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: <code>./pidgin.SlackBuild</code>

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]

[[Category:Tutorials]]

Building A Package

Merge-delete — Fri, 09 Dec 2011 10:29:03 GMT

Merge-delete:

[[Category:Tutorials]]

= Intro =

This is a rough outline for building Slackware packages. Some steps may not be neccessary, some steps might be missing. Use the discussion page for side-notes such as using slacktrack (when DESTDIR fails) and other utilities like checkinstall.

== The good and decent way ==

Configure and compile the source as you usually do:
./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc
make

Make a temporary destination directory available:
mkdir /tmp/build

Install into the temporary directory:
make install DESTDIR=/tmp/build

Now strip libs/bins within the temporary directory:
strip -s /tmp/build/usr/lib/* /tmp/build/usr/bin/*

You also want to make sure that anything in <tt>/usr/man</tt> is gzipped before you make the package:
gzip -9 /tmp/build/usr/man/man?/*.?

Create the <tt>install</tt> directory, this is where the description and install script will be stored:
cd /tmp/build
mkdir install
cd install

Using a text editor (or a [http://slack-desc.sourceforge.net/ tool]]), create a file called [[slack-desc]] and fill it with the following contents:

|-----handy-ruler------------------------------------------------------|
app: Application Name
(Short/Brief description)
app:
app: Enter a description of the package you are building.
app: All 11 "app:" lines must be present
app: "app" needs to be your application name.
app: The handy-ruler is there to help you, these lines should not exceed
app: 79 characters.
app:
app:
app:
app:

Create the actual package:
cd /tmp/build
makepkg ../app-version-arch-tag.tgz

''(The dashes should appear as above, so if the version has a subversion like say "1.0 RC2" make sure you use 1.0_RC2 not 1.0-RC2. The arch should be something like "i486" for example. The tag should consist of the build number and your initals, e.g. 1zb for Zaphod Beeblebrox's first build, 2zb for his second build, etc. Official slackware packages have only numbers as tags.)''

When prompted to recreate symbolic links, say <tt>yes</tt> 
When prompted to reset permissions, say <tt>no</tt>

''Note: Using '''makepkg -l y -c n''' will give you the same behaviour as answering yes to the symlinks question, and no to the permissions question.''

If all went well, you can now install the package.
cd ..
installpkg app-version-arch-tag.tgz

# 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 ':'.
== The "i don't have time" way ==

Fortunately, Slackware are pretty flexible too. If you don't mind much about what is the source (beware!) that you're compiling you can burn some stages and do something like this:
./configure --prefix=/usr
make install DESTDIR=$(pwd)/PACKAGE
cd $(pwd)/PACKAGE
makepkg -l y -c n ../app-version-arch-tag.tgz
installpkg ../app-version-arch-tag.tgz

Of course, you will have a package without description, (probably) uncompressed man pages and unstripped binaries.

----
For more information, also see the pages on [[SlackBuild_Scripts]] and [[Different_Approach_To_Buildscripts]].
----

Slack-desc

Merge-delete — Fri, 09 Dec 2011 10:28:05 GMT

Merge-delete:

=Overview=
A proper slack-desc file should be written as follows:

# 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 ':'.

# 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------------------------------------------------------|
appname: appname (Short description of the application)
appname: <this line is generally left blank>
appname: Description of application - this description should be fairly
appname: in-depth; in other words, make it clear what the package does (and
appname: maybe include relevant links and/or instructions if there's room),
appname: but don't get too verbose.
appname: This file can have a maximum of eleven (11) lines of text preceded by
appname: the "appname: " designation.
appname:
appname: It's a good idea to include a link to the application's homepage too.
appname:

The "appname" string must *exactly* match the application name portion of the
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have
a slack-desc file with the <appname> string of "gaim: " rather than "Gaim: " or
"GAIM: " or something else.

The first line ''must'' show the application name followed by a short
description (enclosed in parentheses).

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

The space after the : is needed only when there is text after the :
In the above example lines 9 & 11 should not have a space after the :

=Tools=
1. There is a command-line tool that automates the creation of slack-desc files and helps you generate legal slack-desc files with minimal effort:
http://slack-desc.sourceforge.net/

2. A web-based tool is also available at: http://www.linuxpackages.net/slackcreator.php
=See Also=
man makepkg
man pkgtool

[[Category:Tutorials]]

Slack-desc

Merge-delete — Fri, 09 Dec 2011 10:26:34 GMT

Merge-delete:

=Overview=
A proper slack-desc file should be written as follows:

# 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------------------------------------------------------|
appname: appname (Short description of the application)
appname: <this line is generally left blank>
appname: Description of application - this description should be fairly
appname: in-depth; in other words, make it clear what the package does (and
appname: maybe include relevant links and/or instructions if there's room),
appname: but don't get too verbose.
appname: This file can have a maximum of eleven (11) lines of text preceded by
appname: the "appname: " designation.
appname:
appname: It's a good idea to include a link to the application's homepage too.
appname:

The "appname" string must *exactly* match the application name portion of the
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have
a slack-desc file with the <appname> string of "gaim: " rather than "Gaim: " or
"GAIM: " or something else.

The first line ''must'' show the application name followed by a short
description (enclosed in parentheses).

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

The space after the : is needed only when there is text after the :
In the above example lines 9 & 11 should not have a space after the :

=Tools=
1. There is a command-line tool that automates the creation of slack-desc files and helps you generate legal slack-desc files with minimal effort:
http://slack-desc.sourceforge.net/

2. A web-based tool is also available at: http://www.linuxpackages.net/slackcreator.php
=See Also=
man makepkg
man pkgtool

[[Category:Tutorials]]

Building A Package

Merge-delete — Fri, 09 Dec 2011 10:26:22 GMT

Merge-delete:

[[Category:Tutorials]]

= Intro =

This is a rough outline for building Slackware packages. Some steps may not be neccessary, some steps might be missing. Use the discussion page for side-notes such as using slacktrack (when DESTDIR fails) and other utilities like checkinstall.

== The good and decent way ==

Configure and compile the source as you usually do:
./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc
make

Make a temporary destination directory available:
mkdir /tmp/build

Install into the temporary directory:
make install DESTDIR=/tmp/build

Now strip libs/bins within the temporary directory:
strip -s /tmp/build/usr/lib/* /tmp/build/usr/bin/*

You also want to make sure that anything in <tt>/usr/man</tt> is gzipped before you make the package:
gzip -9 /tmp/build/usr/man/man?/*.?

Create the <tt>install</tt> directory, this is where the description and install script will be stored:
cd /tmp/build
mkdir install
cd install

Using a text editor (or a [http://slack-desc.sourceforge.net/ tool]]), create a file called [[slack-desc]] and fill it with the following contents:

|-----handy-ruler------------------------------------------------------|
app: Application Name
(Short/Brief description)
app:
app: Enter a description of the package you are building.
app: All 11 "app:" lines must be present
app: "app" needs to be your application name.
app: The handy-ruler is there to help you, these lines should not exceed
app: 79 characters.
app:
app:
app:
app:

Create the actual package:
cd /tmp/build
makepkg ../app-version-arch-tag.tgz

''(The dashes should appear as above, so if the version has a subversion like say "1.0 RC2" make sure you use 1.0_RC2 not 1.0-RC2. The arch should be something like "i486" for example. The tag should consist of the build number and your initals, e.g. 1zb for Zaphod Beeblebrox's first build, 2zb for his second build, etc. Official slackware packages have only numbers as tags.)''

When prompted to recreate symbolic links, say <tt>yes</tt> 
When prompted to reset permissions, say <tt>no</tt>

''Note: Using '''makepkg -l y -c n''' will give you the same behaviour as answering yes to the symlinks question, and no to the permissions question.''

If all went well, you can now install the package.
cd ..
installpkg app-version-arch-tag.tgz

== The "i don't have time" way ==

Fortunately, Slackware are pretty flexible too. If you don't mind much about what is the source (beware!) that you're compiling you can burn some stages and do something like this:
./configure --prefix=/usr
make install DESTDIR=$(pwd)/PACKAGE
cd $(pwd)/PACKAGE
makepkg -l y -c n ../app-version-arch-tag.tgz
installpkg ../app-version-arch-tag.tgz

Of course, you will have a package without description, (probably) uncompressed man pages and unstripped binaries.

----
For more information, also see the pages on [[SlackBuild_Scripts]] and [[Different_Approach_To_Buildscripts]].
----

SlackBuild Scripts

Merge-delete — Fri, 09 Dec 2011 10:26:18 GMT

Merge-delete:

SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source.

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: <code>mkdir pidgin</code>
: <code>cd pidgin</code>
: <code>wget --passive-ftp <nowiki>ftp://slackware.at/slackware-12.1/source/xap/pidgin/*</nowiki></code>

This downloads the files needed for Slackware scripts. The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script. For example, in the pidgin source directory, you would need the following files:

: <code>pidgin-2.4.1.tar.bz2 pidgin-encryption-3.0.tar.gz pidgin.SlackBuild* slack-desc </code>

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: <code>VERSION=2.4.1</code>

This is the line we are looking at. Now we can change this to

: <code>VERSION=2.4.2</code>

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: <code>chmod +x pidgin.SlackBuild</code>

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: <code>su -</code>

Now we start the script, and this will compile Pidgin and make a Slackware package. Depending on how the
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: <code>./pidgin.SlackBuild</code>

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]

[[Category:Tutorials]]

Windows Partitions

Merge-delete — Fri, 09 Dec 2011 10:25:36 GMT

Merge-delete:

One of the frequent questions on ##slackware is something along the lines of "How can I allow normal users to access my Windows partition?" There are *at least* two different ways of doing this.

For a FAT partition, you *could* add umask=0000 to /etc/fstab's options, but I personally don't recommend doing that. It's *your* computer, so you make the call, but I would do something along these lines:

1. If you want *every* user to be able to read and write to the partition, then you can add dmask=0000 and fmask=0111 to /etc/fstab's options and be done with it - problem solved.

/dev/hda1 /mnt/win98 vfat rw,dmask=0000,fmask=0111 0 0

The reason for dmask/fmask as opposed to umask is quite obvious (though I hadn't thought about it until elohim on ##slackware pointed it out): The FAT and NTFS file systems don't "understand" the executable (-x) bit, so it's automatically present on every file in such a filesystem. There's no need for normal files to be executable (and it can indeed be a security risk), so we use fmask to turn off those permissions.

2. If you only want some users to be able to read and write to the partition, but you want *every* user to have read access, then you'll want something along these lines. First, create a special group called "windows" (change the name if you wish) by adding it to /etc/group using your favorite editor and add to this group the users you want to have write access.

nogroup:x:99:
users:x:100:
console:x:101:
windows:x:102:user1,user2,user3

Next, edit your /etc/fstab line for that partition and specify that it be mounted with group ownership of the "windows" group, and that write access be removed from others.

/dev/hda1 /mnt/win98 vfat rw,gid=102,dmask=0002,fmask=0113 0 0

An NTFS partition will be mounted read-only, so you won't have write access for anyone, but the central idea is the same.

If you don't want everyone else to even have read access to the partition, you can easily do that with the above fstab line modified a bit:

/dev/hda1 /mnt/winXP ntfs ro,gid=102,dmask=0227,fmask=0337 0 0

If you prefer write access to the partition, then you can use ntfs-3g instead and something like this:
All users can read the partition; only members of gid 102 can write:
/dev/hda1 /mnt/win98 ntfs-3g rw,gid=102,dmask=0002,fmask=0113 0 0
Users of gid can read and write; nobody else can do anything:
/dev/hda1 /mnt/winXP ntfs-3g rw,gid=102,dmask=0007,fmask=0117 0 0

For more information, see the [[Permissions and Umasks]] and [[Fstab]] pages.

--rworkman (thanks to Erik for the pointers about dmask and fmask)

[[Category:Tutorials]]

Writing A SlackBuild Script

Merge-delete — Fri, 09 Dec 2011 10:24:32 GMT

Merge-delete:

[[Category:Tutorials]]

= Introduction =

Originally written by Florian Mueller jjdm@jjdm.org
Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like linuxpackages.net, or perhaps you just don't like using third-party packages. In this situation, you have several options on how to install the application:

* ./configure && make && make install
* use checkinstall
* use installwatch
* compile and use makepkg by hand
* write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system. You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly. What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named <build_environment>/latex2html/. Get the most recent source code release of latex2html place it in this directory. Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

$ cd <build_environment>
$ mkdir latex2html
$ cd latex2html
$ wget http://saftsack.fs.uni-bayreuth.de/~latex2ht/current/latex2html-2002-2-1.tar.gz # 05.02.2005

Next, we'll create some other needed files with touch. If you're not familiar with touch, see:
man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

$ touch latex2html.SlackBuild
$ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

$ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step. When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts. Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor. What follows below is a piece by piece walk-through of a working SlackBuild script. You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter. This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability. For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly. The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

#!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

#<your name> revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be <build_environment>/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

#Set initial variables:

CWD=$(pwd)
if [ "$TMP" = "" ]; then
TMP=/tmp
fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.

# The version which appears in the application's filename
VERSION=2002-2-1

# If the version conflicts with the Slackware package standard
# The dash character ("-") is not allowed in the VERSION string
# You can set the PKG_VERSION to something else than VERSION
PKG_VERSION=2002.2.1 # the version which appears in the package name.

ARCH=${ARCH:-i486} # the architecture on which you want to build your package

# First digit is the build number, which specifies how many times it has been built.
# Second string is the short form of the authors name, typical three initials:w
BUILD=${BUILD:-1_rlw}

# The application's name
APP=latex2html

# The installation directory of the package (where its actual directory
# structure will be created)
PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS). If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

if [ "$ARCH" = "i486" ]; then
SLKCFLAGS="-O2 -march=i486 -mtune=i686"
elif [ "$ARCH" = "x86_64" ]; then
SLKCFLAGS="-O2 -fPIC"
fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

# Delete the leftover directories if they exist (due to a previous build)
# and (re)create the packaging directory
rm -rf $PKG
mkdir -p $TMP $PKG
rm -rf $TMP/$APP-$VERSION

# Change to the TMP directory
cd $TMP || exit 1

# Extract the application source in TMP
# Note: if your application comes as a tar.bz2, you need tar -jxvf
tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1

# Change to the application source directory
cd $APP-$VERSION || exit 1

# Change ownership and permissions if necessary
# This may not be needed in some source tarballs, but it never hurts
chown -R root:root .
chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

# Set configure options
# If your app is written in C++, you'll also need to add a line for CXXFLAGS
CFLAGS="$SLKCFLAGS" \
./configure \
--prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var \
--with-perl=/usr/bin/perl \
--enable-eps \
--enable-gif \
--enable-png \
--build=$ARCH-slackware-linux \
--host=$ARCH-slackware-linux

# compile the source, but exit if anything goes wrong
make || exit

# Install everything into the package directory, but exit if anything goes wrong
make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location. See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process. You simply cd into the source directory and run:
./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application. Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
./configure --help | lpr
./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed. This should always be our package directory ($PKG). Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps. A simple line like this:
grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not. If you get some lines of output with $DESTDIR in them, you're in good shape. If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure && make && make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script. There are quite a few applications out there which try to do "funny stuff" during the installation phase.
For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

# Create a directory for documentation
mkdir -p $PKG/usr/doc/$APP-$VERSION

# Copy documentation to the docs directory and fix permissions
cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
cat $CWD/$APP.SlackBuild > $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files. In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

# Create the ./install directory and copy the slack-desc into it
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip. The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and
write the output to a doinst.sh file in the $PKG/install directory.

# Add doinst.sh to package (if it exists)
if [ -e $CWD/doinst.sh.gz ]; then
zcat $CWD/doinst.sh.gz > $PKG/install/doinst.sh
fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

# Strip some libraries and binaries
( cd $PKG
find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
)

# Compress man pages if they exist
if [ -d $PKG/usr/man ]; then
( cd $PKG/usr/man
find . -type f -exec gzip -9 {} \;
for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
)
fi

# Compress info pages if they exist (and remove the dir file)
if [ -d $PKG/usr/info ]; then
gzip -9 $PKG/usr/info/*.info
rm -f $PKG/usr/info/dir
fi

=== Build the Package ===

# Build the package
cd $PKG
/sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install. On some applications the DESTDIR Makefile variable has another name. For example, some Qt [http://buyphentermine.herbalweightlossaid.com/ Phen375] applications use the variable INSTALL_ROOT for the same purpose. If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule. Sometimes there will be no DESTDIR equivalent at all. The best thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the [http://www.performer5pills.info/ performer 5] developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that. The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases. In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
./configure --prefix=$PKG/usr
along with your other configure options. This will install *all* of the package contents in that directory. If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move [http://weightlossproductreviews.info/ slimming reviews] them to their correct location within the package directory [http://www.hghadvancedreview.info/ HGH Advanced] tree and everything will be fine. You might also try this along with your other configure options.
./configure --prefix=$PKG/usr \
--sysconfdir=$PKG/etc \
--localstatedir=$PKG/var
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters. In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include [http://www.clearskinmaxreview.info/ clear skin max] instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile. This approach makes it a bit [http://www.hoodiapill.info/ unique hoodia] easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the [http://weightlossproductreviews.info/?page_id=268 slim weight patch] command line. Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make). Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix. For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one [http://www.teethwhitenerguide.com/ teeth whitener reviews] being a template for the "configure" script. Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the [http://www.phen375reviewed.info/ phen375 fat burner] package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here. Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
$ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because [http://www.herbalweightlossaid.com/ slimming pills] developers generally want to conserve space if possible, it's conventional to do this:
$ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your <application>.SlackBuild script so that it applies the patch before it runs configure, make, and make install. To do this, you'll want something like this to run before the configure [http://www.capsiplexreview.info/ capsiplex] script, but after extracting the sources:
zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the [http://proactolpluspills.com/ proactol plus] scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch. You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/
;* http://www2.linuxpackages.net/packages/SlackBuilds/
;* http://www.selkfoster.com.ar/downloads/slackbuilds/
;* http://slack.sarava.org/slackbuilds/

Kernel26Compilation

Merge-delete — Fri, 09 Dec 2011 10:20:18 GMT

Merge-delete:

How to build a 2.6.x Kernel on Slackware

Note: Maybe this replaces the 2.6 part of the kernel compile tutorial already here.

==Warning!==
If you work on your kernel and do something wrong you may destroy your system in a way you have to reinstall it. All actions on your own risk! Noone assures that all actions described here are 100% right and work in any case. We are not responsible for damages caused by following this tutorial!

==Prerequisites==

* Get the kernel sources you want from ftp://ftp.de.kernel.org or from a mirror (http://www.kernel.org/mirrors/).
* Make sure you are able toboot your Slackware original kernel after kernel update (You have to install 2.6.13 from "testing" to do this-slack12 uses 2.6.21.5 by default, no need to install it)

image = /boot/vmlinuz-generic-2.6.13 
root = /dev/ #Your root partition. Get this from another kernel entry or from original /etc/lilo.conf
label = Backup
read-only

Now run "lilo" once as root
* If you want to play safe you may now reboot and try if the kernel boots without errors.
* Uncompress your kernel sources below /usr/src
* The symlink /usr/src/linux has to point to the directory of the new kernel. For example: /usr/src/linux -> /usr/src/linux-2.6.14.4

==Configure the kernel==

* Change to the kernel directory.
cd /usr/src/linux

* Configure your kernel:
** From scratch, then you may choose from

make config (You get prompted for all possible options)
make menuconfig (You get a nice menu where you may navigate with cursor keys. Needs curses-5.x)
make xconfig (You may configure in X, of course needs working X installation)
make gconfig
make qtconfig

:* From old configuration:
Copy the config file of the old kernel to ./.config. If you want to come from orignal Slackware kernel, then:

cp /boot/config .config

After that "make oldconfig" to configure new features (you may acceppt all questions with "Enter" to use the default values) and use "make menuconfig" (or any other of the above list) to change things if you like.

Important! Be sure to compile the alsa modules (or you won't have sound). You have also to do this if you used "make oldconfig" (for example using "make menuconfig") as the original kernel is compiled without alsa.

==Compile and install kernel==

* The real compiling can start:

make (Now, depending on your computer, you may go drinking some coffee, watch a movie or go on your balcony to smoke one ;-) )

If this finished without errors (we assume this) then your kernel and your kernel modules should be compiled.

* Remove symlinks. If you still run your original slackware kernel, then "vmlinuz" and "System.map" are Symlinks to the kernel files. To get sure that we don't override this files, we delete the symlinks

rm /boot/vmlinuz /boot/System.map

* Install the kernel

Install the kernel modules with: 
make modules_install

and the kernel with: 
make install

* If all steps have been done successful you may now use your new (self-made) kernel.

==Troubleshooting==

* Help, the kernel doesn't work!

Choose your backup kernel on lilo, check your kernel configuration and recompile.

* Choose your backup kernel sounds easy, but...

Now you know why you should keep a running kernel before you install a new one. Either your system is as usable as you are able to check the kernel configuration or you may boot from your slackware setup CD, mount your root partition to /mnt, chroot /mnt and recompile your kernel from there or install slackware packages of a running kernel.

[http://www.slackforum.de/wiki/Kernel26Kompilieren german version]

[[Category:Tutorials]]

Permissions and Umasks

Merge-delete — Fri, 09 Dec 2011 10:19:48 GMT

Merge-delete:

==Normal Permissions==

On *nix-like systems, traditionally eery file has an owner, an assigned group, and a list of permissions (although POSIX Access Control Lists are getting more popular).

You can change the owner of a file with the "chown" command:

: <code>fred@linux:~> chown someUser foo</code>

You can change the group of a file with the "chgrp" command:

: <code>fred@linux:~> chgrp someGroup foo</code>

Alternatively, you can do both at once:

: fred@linux:~> <code>chown someUser.someGroup foo</code>

or:

: fred@linux:~> <code>chown someUser:someGroup foo</code>

For every file, you can set the following for the User, Group, and Others: r - can read w - can write x - can execute

These are set with the "chmod" command:

: fred@linux:~> <code>chmod u=rwx,g=rx,o=r foo</code>
: fred@linux:~> <code>ls -l foo</code>
: -rwxr-xr-- 1 fred users 0 2004-10-26 11:38 foo

You don't need to set all the permissions - you can just modify them, for example, to make a file executable:

: fred@linux:~> <code>chmod +x foo</code>

You can also change the permissions just for either the User, Group, or Others:

: fred@linux:~> <code>chmod o-x foo</code>

==Octal Permissions==

You can also specify permissions with a number. To find out which numbers, add up the numbers from this table:

r w x
4 2 1

For example, rwxr-xr-- would be:

U G O
4 4 4
+2 +0 +0
+1 +1 +0
=7 =5 =4

So to give a file rwxr-xr-- permissions:

: fred@linux:~> <code>chmod 754 foo</code>

==Umasks==

umasks define which permissions can not be set (in octal). For example, the default umask on slackware is 0022:

: fred@laptop:~$ <code>umask</code>
: 0022

Ignoring the first digit, this means that the owner can do anything, but group and others are unable to write (2 == w). A more secure umask (possibly more suitable for your ~/) is 0077, meaning that group and others have no access to your files.

==More Umask==

The following is based on [[User:Sandman1|Sandman1]]'s Umask tutorial.

Well first this is a pretty boring topic to write about, So im going to get right to the point. When you set a umask you set what permission NOT to set. So when you create a file it uses the umask to set the file permissions. All of this might not make sense now but it will later. Now type:

: <code>umask</code>

Now on slackware you will get "0022", First ignore the first 0. Now we have 022. The first 0 makes sure the owner has ALL the permissions of a file. You can tell that becuase you have no permissions you want to turn off. Now the next two numbers you have a 2 for. The 2 indicates that you NEVER want to set write permissions.

Now that method above of trying to find a umask is a bit confusing. All you do is set the number what you DON'T want the user to have. Now there is an easier way of finding out a umask. You can subtract the permission from 777. Example:

777 - 750 = 027

That is the umask of the 750 permission. Now you may be asking yourself what is this usefull for. Well you can set the umask by typing "umask 027" in bash and when you create a file/directory it goes by umask 027 instead of the 0022.

Now another reason for setting a umask is becuase you want to access a filesystem such as NTFS,VFAT,Samba,etc as a regular user. You can set the umask and allow regular users to write to the filesytem. It is really easy, in the fstab all you add is "umask=027" and remount the filesystem.
See [[Windows_Partitions]] for more information (and a potentially better option than setting umask options).

[[Category:Tutorials]]

Different Approach To Buildscripts

Merge-delete — Fri, 09 Dec 2011 10:18:39 GMT

Merge-delete:

[[Category:Tutorials]]
Pretty much everyone can hanve their own way of writing Slackware buildscripts. I also have mine, which just makes it easier for me to package software.

In here, I'm going to explain mine. To start, let's look at one I wrote this morning while drinking coffee cup #1:

#!/bin/bash

#############################################################################
## Name: jpilot ##
## Version: 0.99.8 ##
## Packager: Martin Lefebvre (dadexter@gmail.com) ##
## Homepage: http://www.jpilot.org ##
#############################################################################

PKGNAME=jpilot
VERSION=0.99.8
LOC="http://jpilot.org/$PKGNAME-$VERSION.tar.gz"
ARCH=`uname -m`

START=`pwd`
PKG=$START/pkg
SRC=$START/work

build() {
mkdir -p $PKG $SRC
cd $SRC
wget $LOC
tar -zxvf $PKGNAME-$VERSION.tar.gz
cd $PKGNAME-$VERSION
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var \
--enable-gtk2 --enable-prometheon

patch -p0 < patch.0.99.8-memory
patch -p0 < patch.jpilot-sync
make
make DESTDIR=$PKG install
mkdir -p $PKG/usr/doc/$PKGNAME-$VERSION
cp -r ABOUT-NLS AUTHORS BUGS COPYING ChangeLog ChangeLog.cvs INSTALL \
NEWS README TODO UPGRADING docs $PKG/usr/doc/$PKGNAME-$VERSION

cp KeyRing/README.txt $PKG/usr/doc/$PKGNAME-$VERSION/README.keyring
cp dialer/README $PKG/usr/doc/$PKGNAME-$VERSION/README.dialer
cp icons/README $PKG/usr/doc/$PKGNAME-$VERSION/README.icons
}

package() {
cd $PKG
find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : \
| xargs strip --strip-unneeded 2> /dev/null
find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : \
| xargs strip --strip-unneeded 2> /dev/null
find . | xargs file | grep "current ar archive" | cut -f 1 -d : | \
xargs strip --strip-debug 2> /dev/null
chown -R root:root usr/bin
gzip -p $PKG/usr/man/man*/*
mkdir $PKG/install
cp $START/slack-desc $PKG/install/slack-desc
cd $PKG
makepkg -l y -c n $START/$PKGNAME-$VERSION-$ARCH-1.tgz
}

build
package

The top section is just comments identifying the piece of software we're going to build, and the name of the script's author. Then we have the following lines:

PKGNAME=jpilot
VERSION=0.99.8
LOC="http://jpilot.org/$PKGNAME-$VERSION.tar.gz"
ARCH=`uname -m`

START=`pwd`
PKG=$START/pkg
SRC=$START/work

They set the program's name, version, download URL, build and package directories. Since I usually don't specify anything related to the cpu or architecture, it auto detects the architecture. So, the $ARCH variable *should be* accurate.

build() {
mkdir -p $PKG $SRC
cd $SRC
wget $LOC
tar -zxvf $PKGNAME-$VERSION.tar.gz
cd $PKGNAME-$VERSION
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var \
--enable-gtk2 --enable-prometheon

patch -p0 < patch.0.99.8-memory
patch -p0 < patch.jpilot-sync
make
make DESTDIR=$PKG install
mkdir -p $PKG/usr/doc/$PKGNAME-$VERSION
cp -r ABOUT-NLS AUTHORS BUGS COPYING ChangeLog ChangeLog.cvs INSTALL \
NEWS README TODO UPGRADING docs $PKG/usr/doc/$PKGNAME-$VERSION

cp KeyRing/README.txt $PKG/usr/doc/$PKGNAME-$VERSION/README.keyring
cp dialer/README $PKG/usr/doc/$PKGNAME-$VERSION/README.dialer
cp icons/README $PKG/usr/doc/$PKGNAME-$VERSION/README.icons
}

The is the main build function. This contains the code required to build the software. First, we create the build and package directories. The next 3 lines change to the building diirectory, uses wget to fetch the source file and extracts it.

The lines after that are what you would normally type at your command line to build the software:

* Change to the source directory.
* Run ./configure with all the options you want.
* Apply two patches required (in this case) to fix bugs with the software.
* Run make
* Install the software in the package directory defined by $PKG
* Create the standard Slackware Software Documentation directory in the package
* Copy the standard documentation.

The next section is the packaging part:

package() {
cd $PKG
find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : \
| xargs strip --strip-unneeded 2> /dev/null
find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : \
| xargs strip --strip-unneeded 2> /dev/null
find . | xargs file | grep "current ar archive" | cut -f 1 -d : | \
xargs strip --strip-debug 2> /dev/null
chown -R root:root usr/bin
gzip -p $PKG/usr/man/man*/*
mkdir $PKG/install
cp $START/slack-desc $PKG/install/slack-desc
cd $PKG
makepkg -l y -c n $START/$PKGNAME-$VERSION-$ARCH-1.tgz
}

* We change to the package directory
* Strip executables and libraries in order to decrease size.
* As a Slackware standard, we change the ownership of the executables to root:root (to be done for every bin/ and sbin/ directory)
* We compress the manpages
* Create install/ and copy the slack-desc file from the start directory
* Finally, change back to the package folder and create the package tarball.

In this example, the slack-desc and some patch files are distributed with the SlackBuild. This also makes it easier to ship the build script with patches that might be required for the software to work on Slackware (patch to remove PAM stuff).

The slack-desc file format is described here: [http://www.linuxpackages.net/howto.php?page=slack-desc&title=Slackware+Desc+Files LinuxPackages.net]

Additional files:

Some people use slapt-get (like me). slapt-get supports additional features such as
* Dependencies
* Conflicts
* Suggestions

Not everyone wants those features, so building a package with those files will not interfere with the normal pkgtools process. For more info on these optional files, go here: [http://www.linuxpackages.net/howto.php?page=perfect-package&title=Perfect+Package#Optional LinuxPackages.net]

If you decide to use those files, you will then have to repeat these lines:

cp $START/slack-desc $PKG/install/slack-desc

for slack-required, slack-conflicts, and slack-suggests.

----
See also [[SlackBuild_Scripts]] and [[Writing A SlackBuild Script]]
----

User talk:Merge-delete

Merge-delete — Sun, 27 Nov 2011 13:14:08 GMT

Merge-delete: Planning a trip to lonavala?Visit our site for more information on hotels in lonavala.

Boutique Hotels In India

Indulge yourself in sheer luxury throughout your remain in boutique hotels in India.[http://hotelslonavala.net/ hotels in lonavala] These are the places where one can live like rajas and maharajas. They're simply unique within their architecture and hang up where one can get highly personalized services inside a distinctive manner. They are heritage hotels that supply you with a unique connection with living existence.[http://hotelslonavala.net/ hotels in lonavala] Just opposite to western style hotels, these places permit you to know and have the wealthy culture and history of India.

On a trip from the beaten tracks in India, you might find several boutique hotels where one can unwind yourself and also have home-cooked food. With enchanting folk music, amazing architecture, peace and exceptional hospitality, these hotels can bring alive the times of rajas and maharajas of older occasions. Their architecture, gardens, food and luxuries echo from the glorious past of India. Although you will find several hotels in India but when youre searching for best hotels, then certainly Rajasthan may be the condition that you need to visit whenever you arrived at India.

You will find several havelis-converted-hotels in Rajasthan where you can unwind yourself and dip your senses in luxury. Remaining during these hotels is definitely an entirely different experience. Youll feel like you aren't nowadays. For experience a completely different lifestyle, you have to visit these hotels and spend your trip. Trust, youll possess a lifetime experience. The deserted great thing about Rajasthan and wealthy tradition enables you to definitely go through the luxury in simplicity. You no more have to pretend as possible be genuine and do what youve always loved.

The best hotels in Rajasthan are Rawla Narlai, Raas Hotel, The Serai, Udai Kothi, Bhainsrorgarh and Devigarh. From the sights of those hotels, regal inside and grass to authentic antiques, lodging and fooding may be worth admiring. You seem like wandering within the deserts, going through the wonder, studying wealthy tradition, listening folk music and gorging on local meals. Several companies offer vacation packages to Rajasthan. Whenever you arrived at India, you just cant manage to miss these places. They feature glorious past of India.

Hibernate

Merge-delete — Tue, 18 Oct 2011 13:12:49 GMT

Merge-delete: /* Generic kernel + initrd */

In Slackware, hibernation works out-of-the-box and can be easily done from KDE's menu. Resuming from hibernation, however, is not set up, so when you turn on your computer again, it starts as normal. That is, if your hardware supports it and if you've set up a swap space larger than your RAM.

== Huge kernel ==

To tell your kernel where to resume from, you need to write the info to ''lilo.conf'':

append=" resume=/dev/sda6"

Replace ''/dev/sda6'' with your actual swap space. Swap partitions are perfect, I think swap files should work too. If you don't know where your swap lies, look at ''/proc/swaps''.

== Generic kernel + initrd ==

If you're using generic or your own kernel, you need to adjust initrd image as well. Append

-h /dev/sdx

to mkinitrd command so it may look like this:

mkinitrd -c -k <kernel-version> -f <fs_type> -m <fs_type> -r /dev/sdx -h /dev/sdy

Replace ''/dev/sdx'' with your actual root partition and ''/dev/sdy'' with your actual swap space.

If you're using LVM, don't forget to append '''-L''' to mkinitrd command

mkinitrd -c -k <kernel-version> -f <fs_type> -m <fs_type> -r /dev/sdx -h /dev/volumegroup/swap -L

Afterwards, run lilo.

== Further reading ==

* [http://www.linuxquestions.org/linux/answers/Hardware/Mini_HOW_TO_Hibernate_and_resume_0 Mini_HOW_TO_Hibernate_and_resume_0]
* Hibernate to encrypted swap - [http://slackware.osuosl.org/slackware-13.1/README_CRYPT.TXT REAME_CRYPT.TXT]

[[Category:Tutorials]]

Acer Aspire 502x(WLMi)

Merge-delete — Sun, 16 Oct 2011 11:19:00 GMT

Merge-delete: Remove out of date information and some of the references to pre-historic kernels

[[Category:Hardware]]
==Slackware on an Acer Aspire 5020 series==

This article is based on an Aspire 5021WLMi. The 5021WLMi is an an AMD Turion 64 based laptop - it mainly differs from other laptops of the 5020 series only in the specific processor model and some other models come with built in bluetooth - the 5021 has an ML-28 and no bluetooth, I believe the 5024 uses an ML-34 and does have built in bluetooth, so most of this should apply to the 502x series as well. (This is a work in progress, and therefore far from finished).

I have installed my own bluetooth module into the 5021 - this is not very difficult to do (just rather fiddly), but the instructions for operating the bluetooth apply to any 5020 series laptop with bluetooth installed.

==Hardware==
Output of lspci:<pre>
00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01)
00:02.0 PCI bridge: ATI Technologies Inc RS480 PCI-X Root Port
00:07.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 11)
00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge
00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller (rev 02)
00:14.6 Modem: ATI Technologies Inc ATI SB400 - AC'97 Modem Controller (rev 02)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X700 (PCIE)
06:05.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
06:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
06:06.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
06:06.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller
06:06.4 Class 0805: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller
06:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
</pre>

===Overview===

* AMD Turion 64 ML-28 at 1.6 GHz with 128 KB L1 cache and 512 KB L2 cache
* 512 MB of DDR333 memory
* 15.4" Samsung LTN154X3-L01 WXGA LCD panel (1280 x 800)
* ATi Mobility Radeon X700 (128MB dedicated memory)
* 80GB (4200 RPM) (P)ATA Hard Drive ([http://www.seagate.com/cda/products/discsales/marketing/detail/0,1081,638,00.html Seagate Momentus 4200.2 - ST9808210A])
* Slot DVD Writer (DVD-R/RW, DVD+R/RW, DVD+R Dual Layer)
* Texas Instruments (TI7421) 6-in-1 card reader
* Gigabit Ethernet (Realtek RTL-8169 chipset?)
* 802.11 b/g Wireless LAN (Broadcom AirForce One 54g (BCM4318))
* ATi SB400 AC'97 Soundcard + Modem
* 1 x IR port
* 1 x IEEE-1394 (Firewire) port
* 4 x USB ports
* 1 x S-Video port
* 1 x VGA port
* 1 x PCMCIA slot

===Working===

* Video Card: ATI Mobility X700 (1280x800 - fglrx and radeon & r300)
* Broadcom Wireless LAN Card (acer_acpi + ndiswrapper with bcmwl564.sys driver, available as 80211g.zip from Acer driver download area. Slamd64 - need Windows XP 64 driver).
* Soundcard (snd-atiixp as of alsa-driver-1.0.9b or kernel)
* Function/Hot Keys (have not tried all though; extra configuration required for 'multimedia' keys)
* Touchpad (Doesn't need a driver for basic functions)
* USB
* CD/RW, DVD+/-RW
* Ethernet card (works with Realtek 8169 driver)
* Battery Status
* PCMCIA
* 6-in-1 card reader (SD/ MMC & MemoryStick/ Pro only at the moment - [http://tifmxx.berlios.de/ driver in progress])
* Bluetooth

===Not Tested, but probably works===

* Firewire
* Infra Red
* VGA out

==Kernel Configuration==

You will need to use a 2.6.19 or newer kernel to get this laptop to work properly in Linux without any extra kernel patching (see Troubleshooting for more information).

I would *strongly* recommend you always use the latest stable 2.6.x kernel with this laptop, since there are a lot of fixes going in that relate to this laptop (ATI chipset, apic, yenta socket, wireless drivers (b43), etc).

This should be very similar to any other AMD64 laptop with an ATi chipset (like the Acer Ferrari 4000 series- enable anything with 'ATI IXP', plus the relevant ACPI options. I'll put up more here about any necessary specific options later. However, I have *disabled* the framebuffer, as it doesn't play well with the X video drivers.

When building a new kernel make sure that you use the following options, if you want to use the ATI/fglrx driver: 
use '/dev/agpgart' as module 
turn off, the 'Direct Render Manager' 
(so you dont select 'radeon'..) 

==Hardware Package and Software Dependencies==
===Graphics===

Follow the instructions here [http://slackwiki.org/ATI_Graphics] to install and set up your video driver, using the radeon & r300 Mesa drivers. fglrx is no longer supported on this hardware.

===Mouse===

To get advanced features, you will need to install the [http://web.telia.com/~u89404340/touchpad/ Synaptics Mousepad driver for X] and change your mouse driver in xorg.conf to use 'synaptics'. (I use the Synaptics driver mostly to disable 'Tap-to-Click')

To ensure the touchpad always has the same device name, create /etc/udev/rules.d/local.rules (if it doesn't exist) and add the following:

BUS=="serio", SYSFS{description}=="i8042 Aux-3 Port", KERNEL=="mouse*", NAME="input/%k",SYMLINK+="input/touchpad"

You can now point xorg.conf towards /dev/input/touchpad for the touchpad (/dev/input/touchpad will always be a symlink to whichever device the touchpad is - this can vary depending on whether you plug another mouse into the system before or after booting).

===Modem===

This is a Conexant HSF modem - it is incompatible with slmodemd (you therefore do _not_ need snd-atiixp-modem). The only drivers available for this modem are from [http://www.linuxant.com Linuxant] (the free-of-charge drivers are limited to 14.4K, you will need to pay if you want full 56.6K speeds and fax).

===Wireless===

To use the built in wireless, you need to firstly switch on the wireless, then load the b43 driver. You will also need to obtain the firmware for this card - see [http://linuxwireless.org/en/users/Drivers/b43#devicefirmware Linux Wireless] on where to get it from.

1. Enable Wireless

'''2.6.24:'''

* Download, build and install [http://code.google.com/p/aceracpi acer_acpi]
* Load acer_acpi: modprobe acer_acpi wireless=1

'''2.6.25 or newer:'''

* echo 1 > /sys/devices/platform/acer-wmi/wireless
* Or create /etc/modprobe.d/acer-wmi and add "options acer-wmi wireless=1" to do this at boot time

2. Install b43 firmware

* Download, build and install b43-fwcutter - use the [http://www.slackbuilds.org SlackBuilds.org] Slackbuild for thos
* Follow the instructions on [http://linuxwireless.org/en/users/Drivers/b43#devicefirmware Linux Wireless] for your kernel version to extract the firmware and install it to /lib/firmware

(The orange light for the wireless at the front should turn on now)

3. Configure the wireless in /etc/rc.d/rc.inet1.conf

Note: I deleted rc.wireless.conf as it is unecessary and keeps trying to override rc.inet1.conf (besides, configuring wireless in rc.inet1.conf is the future).

===Bluetooth===

The bluetooth is an internal USB dongle. To turn it on:

* echo 1 > /sys/devices/platform/acer-wmi/bluetooth
* Or create /etc/modprobe.d/acer-wmi and add "options acer-wmi bluetooth=1" to do this at boot time

The bluetooth device can now be seen with lsusb (it is not visible when bluetooth if you don't enable it through acer_acpi/ acer-wmi).

===Special Keys===

There is a keymap for the special keys available [http://www.fwconsult.com/acer-install/index.html here].

However, I have had problems with it on my UK layout keyboard so would not recommend using it at the moment.

===Special Keys with X===

====HAL====

You will need, at a minimum, HAL 0.5.10 and hal-info 20070725. The Aspire 5020 has been submitted to HAL as part of their keyboard quirk project, so the extra keys which generated dmesg messages, will now generate proper keycodes.

====X====

There is now a generic acer_laptop keyboard layout in upstream xkeyboard-config (which works in tandem with HAL to map the extra keys). This will be in the next xkeyboard-config release after 1.0 (it is therefore unlikely to make the next X.Org release).

You can also use the evdev layout instead.

===Hardware Monitoring===

Unfortunately, the extent of 'hardware monitoring' on this system comes through 3 thermal zones provided by ACPI.

You can play around with using I2C to access the SMBus, but the hardware on the other end of it appears to be a National Semiconductors chip of sorts that is not supported under Linux (and based on comments on the lm_sensors mailing list, due to various problems, is not very likely to be either).

===Suspend===

Suspend does work on this laptop (assuming you don't have any funny PCMCIA, USB or Firewire devices attached that will break it).

'''In a terminal'''

You will need either vbetool or a 2.6.17-rc (or newer) kernel with s2ram (found in [http://suspend.sourceforge.net suspend]).

Using s2ram:
s2ram -f -p

Using swusp (run this command after resuming):
vbetool post

'''In X'''

Works with either radeon or fglrx (you don't need to run s2ram if you suspend from X).

===Card Reader===

This card reader is not fully supported in Linux yet. There is an in development driver, [http://tifmxx.berlios.de tifmxx], that currently supports MMC/ SD, and Memory Stick/ Pro. If you want to help out the project, hardware donations are welcome for unsupported hardware (be aware that the developer's card reader can not physically support SmartMedia cards).

==Troubleshooting==

===HPET===

Not available on this laptop - locks hard with hpet=force (I suspect HPET's are only available on the newer SB480 chipsets).

===DVDs will not play back===

You need to set the DVD region before you can play any DVDs. The 'regionset' tool for Linux will let you do this (otherwise you will have lots of strange error messages in dmesg).

===Suspend/ Resume does not work===

Please be aware that kernel updates can break this. If that's the case, I will try and update this page to reflect that.

Otherwise, go back and make sure you have applied the necessary patch specified earlier in "Suspend" to your kernel. Also, try unplugging any devices attached to the laptop, rebooting (some drivers can be a bit funny otherwise) and then try suspend/ resume. If it now works, then one of your devices or a driver somewhere is breaking suspend - in which case, you should report the bug to the relevant person/ place.

==Contributors==

*[http://slackwiki.org/User:Ccorbacho Carlos Corbacho (aka cathectic)]
*[http://slackwiki.org/User:Funmain Funmain]

==External Links/ References==
* [http://forums.slamd64.com/viewtopic.php?t=27 fglrx on Slamd64]
* [http://www.fwconsult.com/acer-install/index.html Installing Gentoo (2005.0) on an Acer 5021NWLCi]
* [http://gentoo-wiki.com/HARDWARE_Gentoo_Acer_Ferrari_4005WLMi_Manual Gentoo Acer Ferrari 4005WLMi Manual]
* [http://website.lineone.net/~bryanrpoole/atiixp-modem.html ATI-IXP MC97 Modem Development / Configuration Information]
* [http://bugzilla.kernel.org/show_bug.cgi?id=3927 Kernel Bugzilla entry for AMD64/ ATi timer running fast problem]
* [http://doube.net/3023wlmi.html Linux and Windows on an Acer Aspire 3023WLMi]

Upgrade Using Slapt-get

Merge-delete — Sun, 26 Jun 2011 10:37:24 GMT

Merge-delete:

[[Category:Tutorials]]
= Introduction =

See the [[Slapt-get]] page for an introduction to slapt-get and its functionality.

Prior to using slapt-get, you should really be familiar with proper usage of the native Slackware package management tools:
man pkgtool
man installpkg
man upgradepkg
man removepkg
As indicated in the link above, slapt-get is *not* a replacement for those utilities - it *uses* those utilities. As such, any inherent "limitations" (yes, I use that term loosely) in the pkgtool suite will also apply to slapt-get.

= Installation and Configuration =

Get the [[slapt-get]] package for your version of Slackware.

Once it's installed, configure it to point to your favourite
mirror (edit '''/etc/slapt-get/slaptgetrc''')

# See /usr/doc/slapt-get-0.10.1/example.slapt-getrc
# for example source entries and configuration hints.
WORKINGDIR=/var/slapt-get
EXCLUDE=^kernel-.*,^alsa-.*,^glibc.*,.*-[0-9]dl$,^devs$,^udev$,aaa_elflibs,x86_64
SOURCE=http://slackware.osuosl.org/slackware-12.2/:OFFICIAL
SOURCE=http://software.jaos.org/slackpacks/12.2/:OFFICIAL

= Usage Hints =

Depending upon your individual goals of using slapt-get, the usage hints will vary. An individual wishing to upgrade from one release of Slackware to another will have more issues with which to contend than another individual who simply wants to keep up-to-date with official security/stability patches.

The biggest piece of advice I can give to *anyone* regardless of how/why you're using slapt-get is this: READ THE CHANGELOG! The pertinent portions of the changelog are also viewable for each package using --show option. You'll be okay most of the time if you ignore this advice, but don't come crying to ##slackware if you do... :)

From '''man slapt-get''':
UPGRADE.TXT and ChangeLog.txt is still required reading, the latter is especially true when running -current.

By the way, don't even consider trying to follow the Slackware -current development using slapt-get; that's just *asking* for a problem (for reasons which will hopefully be clear later).
Official ChangeLog is at ftp://ftp.slackware.com/pub/slackware/slackware-12.2/ChangeLog.txt
Replace the "12.2" with the release version you're using.
Rather than using the official ChangeLog (and Slackware.com bandwidth), it's better to use one of the official Slackware mirrors (you'll notice faster connections with the mirrors):
<SlackwareMirror>/slackware-<version>/ChangeLog.txt
See the Slackware site [[http://slackware.com/getslack/]] to find an official mirror site.

== Usage Hint #1: Security and Stability Patches ==

If your only goal is to stay up-to-date with official security and stability patches for your version of Slackware, then the default configuration of slapt-get should work fine for you. While I'm not the author of slapt-get (Jason, feel free to jump in here), it seems to me that this was the original intent of slapt-get (and it works *extremely* well for that task, might I add).

The only exception of which I can think is kernel upgrades; thankfully, those haven't happened *too* often in official releases in recent memory, but they do occur frequently enough to be worth considering. The default configuration of slapt-get will ignore kernel upgrades, so the only way you'll know about those is by reading the official ChangeLog. Anyway, every time you upgrade your kernel, you'll need to make sure the paths in '''/etc/lilo.conf''' point to a valid kernel, and then run '''/sbin/lilo''' to reinstall LILO. If you use some other boot loader, then I'm going to assume you know enough about its usage to perform the corresponding operation (if required) after upgrading your kernel.

I would recommend that you keep your old kernel around when installing a new one; it's always good to have a known-good kernel lying around just in case the new one doesn't boot. However, you'll notice that by default, running this command:
slapt-get --install kernel-$VERSION
will *upgrade* the kernel; in other words, it will *remove* the old kernel package and *install* the new one. This is not desirable if you wanted to keep your old kernel, so you can run this command instead:
slapt-get --install --no-upgrade kernel-$VERSION
From '''man slapt-get''':
--no-upgrade
Install the package rather than attempting to detect if a previous version is
installed and upgrading it. This is useful for installing kernel packages. This
option is only valid for --install targets.
You might also find this option useful for installing multiple versions of the alsa-* packages; if you're running both 2.4.x and 2.6.x kernels, you'll need the alsa-driver packages for both kernels, so an *upgrade* of the 2.4.x version to 2.6.x will remove the 2.4.x version.

== Usage Hint #2: Upgrade From One Release To Another ==

Every Slackware release includes a file named UPGRADE.TXT - it was included for a reason, so READ IT! Once you are familiar with its contents, the rationale behind the information below will make more sense.

=== Step 1: Edit your /etc/slapt-get/slaptgetrc ===

Edit your '''/etc/slapt-get/slaptgetrc''' file to reflect the new Slackware version

This:
SOURCE=http://slackware.osuosl.org/slackware-12.1/
SOURCE=http://software.jaos.org/slackpacks/12.1/
becomes this:
SOURCE=http://slackware.osuosl.org/slackware-12.2/:OFFICIAL
SOURCE=http://software.jaos.org/slackpacks/12.2/:OFFICIAL

=== Step 2: Download all updated packages ===

Download all updated packages to slapt-get's working directory; by default, this is '''/var/slapt-get'''
slapt-get --dist-upgrade --ignore-excludes --download-only

=== Step 3: Put your machine in single-user mode ===

Make sure you have already performed step 2, because the network will not be available in runlevel 1.
telinit 1

=== Step 4: Upgrade main packages ===

Versions >= 0.9.11 upgrade glibc-solibs, pkgtools, and sed first , and then upgrade the remainder of the packages. If you have read the UPGRADE.TXT file, you already know why this is needed. (hint, hint)

* '''Step 4a:''' If you are using slapt-get version earlier than 0.9.11, do:
slapt-get --install kernel --no-upgrade
slapt-get --install glibc-solibs pkgtools sed
slapt-get --dist-upgrade

* '''Step 4b:''' If you are using slapt-get version 0.9.11 or later, do:
slapt-get --install kernel --no-upgrade
slapt-get --dist-upgrade --ignore-excludes

The '''--dist-upgrade''' option will prompt you to install all *new* packages in the ./a series, and you should say "yes" to ensure that you have a working system after the upgrade. See step 8 below for more information on installing new packages.

=== Step 5: Update LILO and config files ===
* Make sure the paths in '''/etc/lilo.conf''' point to a valid kernel image, and then run '''/sbin/lilo'''
* Fix your config files in '''/etc'''; the new ones are named with a *.new suffix. You should be able to use '''diff -u file file.new''' to show the differences between file and file.new. You'll have to decide whether to completely replace the old files with the new ones or merge your changes into the new ones first, but you *must* use the new files.

=== Step 6: Go back to multi-user mode ===

Sometimes the screen stays blank when you return to runlevel 3, and you might be worried that something went wrong. Before you panic, type '''clear''' and press Enter - you'll probably get your root prompt back :)
telinit 3

=== Step 7: Remove obsolete packages ===

There is an option to do this automatically with slapt-get:
slapt-get [--remove|--dist-upgrade] --remove-obsolete
From '''man slapt-get'''
--remove-obsolete
Remove installed packages that are no longer available. This works for dist-upgrade
only. This removes packages that are no longer available from any current package
sources, but are currently installed. Be careful as this will also remove custom
built packages.
As you see, this option will be fine ''if you don't have any custom-compiled packages'' installed (such as with [[checkinstall]] or using [[SlackBuild_Scripts]]). Read through the official ChangeLog to find all packages that were removed from Slackware during the development phase; you might be able use something like this to make the process go a bit more quickly:
grep -i removed ChangeLog.txt OR grep Removed ChangeLog.txt

=== Step 8: Add new packages ===

Similar to removing obsolete packages, there is an option to do this automatically with slapt-get using the '''--install-set''' option:
slapt-get --upgrade --install-set a ap d f k kde l n t tcl x xap y

From '''man slapt-get''':
--install-set [disk set(s)]
Install specified disk set(s). example: --install-set xap n l

This option will upgrade (or install, if not already installed) every package in every disk set. For reasons already detailed (kernel/alsa versions), this may not be desirable; additionally, if you don't have a full installation of Slackware for whatever reason, this will not be desirable.

The safest option is to read through the official ChangeLog.txt, make a note of new packages added during the release cycle, and install them now with this command:
slapt-get --install <newpackage1> <newpackage2> <...>
You might be able to use something like this to make the process go a bit more quickly, but it will return quite a few extraneous results.
grep -i added ChangeLog.txt

=== Step 9: Admire the Results :) ===
At this point, you should be running the latest version of Slackware.

== Usage Hint #3: Keep Up With Slackware -current Development ==

After modifying your <code>/etc/slapt-get/slaptgetrc</code> file to reflect -current sources, the most important advice you should hear is: READ THE CHANGELOG

Seriously, always read the ChangeLog.txt file associated with the -current tree; so long as you read it prior to running the <code>slapt-get --upgrade</code> command, you should be familiar with any issues that might be encountered.

One idea you might consider is to use slapt-get as a "double checking" tool to ensure you haven't accidentally overlooked any packages. While the concerns detailed earlier in this article apply here (you won't be informed of any new packages added to -current), you can use the following lines to see if you missed anything that needed to be upgraded:

slapt-get --update
slapt-get --upgrade --simulate

= Related Links =

* [[Release_Changes|Changes in Slackware Release Versions]]

Slapt-get

Merge-delete — Sat, 25 Jun 2011 17:03:12 GMT

Merge-delete: /* Distributions */

'''slapt-get''' is an [[APT]]-like system for [http://en.wikipedia.org/wiki/Slackware Slackware] [[package management]].

It tries to emulate the features of [[Debian]]'s [[apt-get]] as closely as possible.

==Features==

* uses native [http://en.wikipedia.org/wiki/Slackware Slackware] tools (installpkg, upgradepkg, and removepkg)
* supports multiple package sources (including http://linuxpackages.net)
* cache data concerning packages and updates from package sources
* supports sources from ftp, ftps, http, https, file:/// and more (libcurl)
* resumes broken downloads and will verify package integrity with [http://en.wikipedia.org/wiki/Md5 MD5] checksum
* show packages that are available (from cached data) and installed
* search package listing using [http://en.wikipedia.org/wiki/POSIX POSIX] and extended [http://en.wikipedia.org/wiki/Regular_expressions regular expressions] by package name, location, and description
* retrieve, install, and remove packages by name or by specific version
* retrieve and apply updates
* upgrade from one Slackware release to another in a few simple steps - see [[Upgrade_Using_Slapt-get]]
* show description of packages, including mirror location, version, size, dependencies (where available, see [http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ10 FAQ]), conflicts (where available, see [http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ31 FAQ]), suggestions (where available, see [http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ44 FAQ]), description, and installation status
* exclude (hold) packages from upgrades, by name or by regular expression
* transaction engine for install, remove, and upgrades, reporting concise information on what is to be done, ensuring each step happens correctly
* "compare package version" algorithm to prevent downgrades
* recursive dependency resolution using slack-required meta-data ([http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ10 see FAQ]) supporting hard, soft, and conditional dependencies
* package conflict resolution using slack-conflicts meta-data ([http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ31 see FAQ])
* package suggestion support for complimentary packages ([http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ44 see FAQ])
* Package data download robustness, only writing changes if all sources download successfully as well as only downloading those sources that have changed since the last download
* [http://en.wikipedia.org/wiki/I18n i18n] support via [http://en.wikipedia.org/wiki/GNU GNU] gettext with over 20 language translations
* extremely fast and easy to script with

==Dependencies==

slapt-get does not provide dependency resolution for packages included within the Slackware distribution. It does, however, provide a framework for dependency resolution in Slackware compatible packages similar in fashion to the hand-tuned method [http://en.wikipedia.org/wiki/Advanced_Packaging_Tool Advanced Packaging Tool|APT] utilizes. Several package sources and Slackware based distributions take advantage of this functionality.

Adding dependency information requires no modification to the packages themselves. Rather, the package listing file, PACKAGES.TXT, is used to specify these relationships. This file is provided by [http://en.wikipedia.org/wiki/Patrick_Volkerding Patrick Volkerding] and is similar to the Packages.gz file in use by [http://en.wikipedia.org/wiki/Debian Debian]. Several scripts are available to generate the PACKAGES.TXT file from a group of packages (See [http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ17 FAQ #17]). The file format used by [http://en.wikipedia.org/wiki/Patrick_Volkerding Patrick Volkerding] is extended by adding a few extra lines per package. slapt-get then parses this file during source downloads. Typically, third party packages store the dependency information within the package itself for later extraction into the PACKAGES.TXT ([http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ19 See FAQ #19]). The inclusion of this information within the Slackware package format does not inhibit the ability for Slackware pkgtools to install these packages. This information is silently ignored and discarded after the package is installed.

[http://www.stabellini.net/depslack.html Other methods] exist for adding dependency information for official Slackware packages without altering the packages themselves.

==Package Sources==

slapt-get works with official Slackware mirrors and third party package repositories. slapt-get looks for support files, PACKAGES.TXT and CHECKSUMS.md5, in the repository for package information. These files provide package names, versions, sizes (both compressed and uncompressed), checksums, as well as a package description. These files can be extended, as discussed in the previous section, to add dependency listings, conflict information, and package suggestions. These files can also proxy for other remote sources by specifying a MIRROR declaration for each package.

==libslapt==

slapt-get exports a [http://en.wikipedia.org/wiki/C_programming_language C] [http://en.wikipedia.org/wiki/Library_(computer_science) library] that is used by [http://en.wikipedia.org/wiki/gslapt gslapt] to provide similar functionality through a [http://en.wikipedia.org/wiki/GTK+ GTK+] frontend.

==Distributions==

Besides Slackware, slapt-get may be used with or included by the following distributions:

* [http://www.vectorlinux.com Vector Linux]
* [http://www.mutagenix.org Mutagenix]
* [http://slax.linux-live.org SLAX]
* [http://www.slamd64.com/ Slamd64]
* [http://gsb.sourceforge.net/ Freerock GNOME]
* [http://www.gware.org/ GWARE GNOME]
* [http://slampp.abangadek.com/ SLAMPP]
* [http://getopenlab.com/ OpenLab GNU/Linux]
* [http://ocsid.spaghettilinux.org/ Open Community Slackware Install DVD]
* [http://floyd-linux.pappapc.com/ Floyd GNU/Linux]
* [http://www.stibs.cc/stx/ STX GNU/Linux]
* [http://www.nnlinux.com/ Nonux GNU/Linux]
* [http://wolvix.org/ Wolvix LiveCD]
* [http://www.collegelinux.org College Linux]
* [http://www.zenwalk.org/ Zenwalk Linux]
* [http://www.truvalinux.org.tr Truva Linux]
* [http://sms.it-ccs.com SMS(Superb Mini Server)]

==Examples==

$ slapt-get --update
Retrieving package data http://www.slackware.at/data/slackware-10.0/ ...Done
Retrieving patch list http://www.slackware.at/data/slackware-10.0/ ...Done
Retrieving checksum list http://www.slackware.at/data/slackware-10.0/ ...Done
Reading Package Lists...Done
Retrieving package data http://software.jaos.org/slackpacks/10.0/ ...Cached
Retrieving patch list http://software.jaos.org/slackpacks/10.0/ ...Cached
Retrieving checksum list http://software.jaos.org/slackpacks/10.0/ ...Cached
Reading Package Lists...Done

$ slapt-get --upgrade
Reading Package Lists... Done
The following packages have been EXCLUDED:
devs kernel-headers
The following packages will be upgraded:
binutils bash bin bind cdrtools bzip2 kbd cups cxxlibs e2fsprogs etc gawk gcc gdb inetd infozip less links
logrotate lynx man man-pages openssh openssl openssl-solibs pidentd pkgtools procps sed shadow slocate
sysklogd sysvinit tar tcpip util-linux vim wget zlib
39 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 36710K of archives.
After unpacking 17880K of additional disk space will be used.
Do you want to continue? [y/N]

$ slapt-get --show slapt-get
Package Name: slapt-get
Package Mirror: http://software.jaos.org/slackpacks/10.0/
Package Location: .
Package Version: 0.9.9f-i386-1
Package Size: 147 K
Package Installed Size: 530 K
Package Required: curl >= 7.12.0-i486-1,glibc-solibs >= 2.3.2-i486-7,binutils,openssl >= 0.9.7d-i486-1,pkgtools,zlib
Package Conflicts:
Package Suggests:
Package MD5 Sum: cb4b44cbb4efee4e993109231b107828
Package Description:
slapt-get: slapt-get (APT like system for Slackware)
slapt-get: slapt-get is an APT like system for Slackware package management.
slapt-get:
slapt-get: * See /usr/doc/slapt-get-0.9.9f/ for complete documentation.
slapt-get: * You will also want to customize /etc/slapt-get/slapt-getrc,
slapt-get: using a local mirror. www.slackware.com may be very busy.
slapt-get: * Support:
slapt-get: http://software.jaos.org/cgi-bin/mailman/listinfo/slapt-get-user
slapt-get: * Please translate
slapt-get: http://software.jaos.org/BUILD/slapt-get/po/slapt-get.pot
slapt-get: then send to slapt-get-devel@software.jaos.org
slapt-get:
Package Installed: yes

==External links==
*[http://software.jaos.org/#slapt-get Homepage]

[[Category:Information]]

Install Slackware Using A USB Flash Drive

Merge-delete — Tue, 07 Jun 2011 11:08:05 GMT

Merge-delete: Installation quirks

[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Syslinux >= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk

Make it hybrid:

isohybrid slackware-13.1-install-dvd.iso

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

The following command will overwrite all the files currently present on the USB drive so prior backups are highly advisable:

dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is, and mount the device to some location:

mkdir flash && mount /dev/sdX1 flash

When installing, choose "Install from a hard drive partition", with the USB drive as source partition.

Other than that, installation process should be no different than when installing from a DVD.

Building A Package

Merge-delete — Thu, 12 May 2011 20:39:39 GMT

Merge-delete: Added link to slack-desc section and link to slack-desc generation tool

[[Category:Tutorials]]

= Intro =

This is a rough outline for building Slackware packages. Some steps may not be neccessary, some steps might be missing. Use the discussion page for side-notes such as using slacktrack (when DESTDIR fails) and other utilities like checkinstall.

== The good and decent way ==

Configure and compile the source as you usually do:
./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc
make

Make a temporary destination directory available:
mkdir /tmp/build

Install into the temporary directory:
make install DESTDIR=/tmp/build

Now strip libs/bins within the temporary directory:
strip -s /tmp/build/usr/lib/* /tmp/build/usr/bin/*

You also want to make sure that anything in <tt>/usr/man</tt> is gzipped before you make the package:
gzip -9 /tmp/build/usr/man/man?/*.?

Create the <tt>install</tt> directory, this is where the description and install script will be stored:
cd /tmp/build
mkdir install
cd install

Using a text editor (or a [http://slack-desc.sourceforge.net/ tool]]), create a file called [[slack-desc]] and fill it with the following contents:

|-----handy-ruler------------------------------------------------------|
app: Application Name (Short/Brief description)
app:
app: Enter a description of the package you are building.
app: All 11 "app:" lines must be present
app: "app" needs to be your application name.
app: The handy-ruler is there to help you, these lines should not exceed
app: 79 characters.
app:
app:
app:
app:

Create the actual package:
cd /tmp/build
makepkg ../app-version-arch-tag.tgz

''(The dashes should appear as above, so if the version has a subversion like say "1.0 RC2" make sure you use 1.0_RC2 not 1.0-RC2. The arch should be something like "i486" for example. The tag should consist of the build number and your initals, e.g. 1zb for Zaphod Beeblebrox's first build, 2zb for his second build, etc. Official slackware packages have only numbers as tags.)''

When prompted to recreate symbolic links, say <tt>yes</tt> 
When prompted to reset permissions, say <tt>no</tt>

''Note: Using '''makepkg -l y -c n''' will give you the same behaviour as answering yes to the symlinks question, and no to the permissions question.''

If all went well, you can now install the package.
cd ..
installpkg app-version-arch-tag.tgz

== The "i don't have time" way ==

Fortunately, Slackware are pretty flexible too. If you don't mind much about what is the source (beware!) that you're compiling you can burn some stages and do something like this:
./configure --prefix=/usr
make install DESTDIR=$(pwd)/PACKAGE
cd $(pwd)/PACKAGE
makepkg -l y -c n ../app-version-arch-tag.tgz
installpkg ../app-version-arch-tag.tgz

Of course, you will have a package without description, (probably) uncompressed man pages and unstripped binaries.

----
For more information, also see the pages on [[SlackBuild_Scripts]] and [[Different_Approach_To_Buildscripts]].
----

Slack-desc

Merge-delete — Thu, 12 May 2011 19:37:41 GMT

Merge-delete: Added Tools section, with links to tools that generate slack-desc files

=Overview=
A proper slack-desc file should be written as follows:

# 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------------------------------------------------------|
appname: appname (Short description of the application)
appname: <this line is generally left blank>
appname: Description of application - this description should be fairly
appname: in-depth; in other words, make it clear what the package does (and
appname: maybe include relevant links and/or instructions if there's room),
appname: but don't get too verbose.
appname: This file can have a maximum of eleven (11) lines of text preceded by
appname: the "appname: " designation.
appname:
appname: It's a good idea to include a link to the application's homepage too.
appname:

The "appname" string must *exactly* match the application name portion of the
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have
a slack-desc file with the <appname> string of "gaim: " rather than "Gaim: " or
"GAIM: " or something else.

The first line ''must'' show the application name followed by a short
description (enclosed in parentheses).

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

The space after the : is needed only when there is text after the :
In the above example lines 9 & 11 should not have a space after the :

=Tools=
1. There is a command-line tool that automates the creation of slack-desc files and helps you generate legal slack-desc files with minimal effort:
http://slack-desc.sourceforge.net/

2. A web-based tool is also available at: http://www.linuxpackages.net/slackcreator.php
=See Also=
man makepkg
man pkgtool

[[Category:Tutorials]]

Fstab

Merge-delete — Tue, 19 Apr 2011 23:16:06 GMT

Merge-delete: /* Useful Examples */

The /etc/fstab file tells the system how and where to mount filesystems by default.

==Syntax==
The syntax of the file is this:

<table cellspacing="10">
<tr>
<td align="right">MAN PAGE-ese:</td>
<td align="center">FS_SPEC</td>
<td align="center">FS_FILE</td>
<td align="center">FS_VFSTYPE</td>
<td align="center">FS_MNTOPS</td>
<td align="center">FS_FREQ</td>
<td align="center">FS_PASSNO</td>
</tr><tr>
<td align="right">IN ENGLISH:</td>
<td align="center">DEVICE</td>
<td align="center">MOUNT_POINT</td>
<td align="center">FILESYSTEM</td>
<td align="center">OPTIONS</td>
<td align="center">DUMP</td>
<td align="center">FSCK_ORDER</td>
</tr><tr>
<td align="right">EXAMPLE:</td>
<td align="center">/dev/hdb1</td>
<td align="center">/mnt/windows</td>
<td align="center">vfat</td>
<td align="center">default</td>
<td align="center">0</td>
<td align="center">1</td>
</tr>
</table>

==Field Descriptions==
FS_SPEC (DEVICE) - the device or remote filesystem to be mounted.

FS_FILE (MOUNT_POINT) - the mount point for the filesystem. NOTE: For swap partitions, this field should be specified as `none'. If the name of the mount point contains spaces these can be escaped as `\040'.

FS_VFSTYPE (FILESYSTEM)- the type of the filesystem. As of Slackware 10.2, the FILE_SYSTEM choices are:
:auto, adfs, affs, autofs, coda, cramfs, devpts, efs, ext2, ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs, nfs, nfs4, ntfs, proc, qnx4, reiserfs, romfs, smbfs, sysv, tmpfs, udf, ufs, umsdos, vfat, xfs, xiafs and possibly others.
NOTE: for swap-able and portable devices (e.g. memory sticks and CDROMs), <code>auto</code> is the best choice because it allows the computer to determine the correct filesystem.

FS_MNTOPS (OPTION) - the (comma seperated) mount options. See the MOUNT command's MAN PAGE for the options because there are MANY!
The most commonly used options are: 
:noauto - do not mount this device/partition automatically on boot-up.
:ro - mount this device/partition READ-ONLY (e.g. CDROM).
:owner - Only allow the owner to mount and un-mount this device/partition.
:users - Allow any user to mount or unmount this device/partition.

FS_FREQ (DUMP) - used for these filesystems by the dump command to determine which filesystems need to be dumped. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be dumped. For the most part, this should be "0" (zero).

FS_PASSNO (FSCK_ORDER) - used by the fsck program to determine the order in which filesystem checks are done at reboot time. The root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked.

==Benefits Of fstab Entries==
Once you have a device in the fstab, mounting become VERY easy. Instead of having to:
:<code>mount -t iso9660 /dev/hdb1 /mnt/cdrom</code>
every time you want to use the CDROM, you can just type:
:<code>mount /mnt/cdrom</code>
IF you have the entry in your fstab.

==Useful Examples==
CDROM: 
:/dev/hdc1 /mnt/cdrom auto noauto,ro,owner,users 0 0

[[USB Memory Stick]]: 
:/dev/sda1 /mnt/memstick auto noauto,owner,users 0 0 
(make sure to <code>mkdir /mnt/memstick</code> after changing your /etc/fstab).

[[External USB Drive / NTFS partition]]
:/dev/sdd1 /media/1T ntfs-3g auto 0 0
(/dev/sdd1 is your external USB hard drive and /media/1T is destination folder)

Note: For changing who can access the filesystem on NON-Native linux formats see [[Permissions and Umasks]] and [[Windows Partitions]]

[[Category:Tutorials]]

Fstab

Merge-delete — Tue, 19 Apr 2011 23:08:37 GMT

Merge-delete: /* Useful Examples */

The /etc/fstab file tells the system how and where to mount filesystems by default.

==Syntax==
The syntax of the file is this:

<table cellspacing="10">
<tr>
<td align="right">MAN PAGE-ese:</td>
<td align="center">FS_SPEC</td>
<td align="center">FS_FILE</td>
<td align="center">FS_VFSTYPE</td>
<td align="center">FS_MNTOPS</td>
<td align="center">FS_FREQ</td>
<td align="center">FS_PASSNO</td>
</tr><tr>
<td align="right">IN ENGLISH:</td>
<td align="center">DEVICE</td>
<td align="center">MOUNT_POINT</td>
<td align="center">FILESYSTEM</td>
<td align="center">OPTIONS</td>
<td align="center">DUMP</td>
<td align="center">FSCK_ORDER</td>
</tr><tr>
<td align="right">EXAMPLE:</td>
<td align="center">/dev/hdb1</td>
<td align="center">/mnt/windows</td>
<td align="center">vfat</td>
<td align="center">default</td>
<td align="center">0</td>
<td align="center">1</td>
</tr>
</table>

==Field Descriptions==
FS_SPEC (DEVICE) - the device or remote filesystem to be mounted.

FS_FILE (MOUNT_POINT) - the mount point for the filesystem. NOTE: For swap partitions, this field should be specified as `none'. If the name of the mount point contains spaces these can be escaped as `\040'.

FS_VFSTYPE (FILESYSTEM)- the type of the filesystem. As of Slackware 10.2, the FILE_SYSTEM choices are:
:auto, adfs, affs, autofs, coda, cramfs, devpts, efs, ext2, ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs, nfs, nfs4, ntfs, proc, qnx4, reiserfs, romfs, smbfs, sysv, tmpfs, udf, ufs, umsdos, vfat, xfs, xiafs and possibly others.
NOTE: for swap-able and portable devices (e.g. memory sticks and CDROMs), <code>auto</code> is the best choice because it allows the computer to determine the correct filesystem.

FS_MNTOPS (OPTION) - the (comma seperated) mount options. See the MOUNT command's MAN PAGE for the options because there are MANY!
The most commonly used options are: 
:noauto - do not mount this device/partition automatically on boot-up.
:ro - mount this device/partition READ-ONLY (e.g. CDROM).
:owner - Only allow the owner to mount and un-mount this device/partition.
:users - Allow any user to mount or unmount this device/partition.

FS_FREQ (DUMP) - used for these filesystems by the dump command to determine which filesystems need to be dumped. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be dumped. For the most part, this should be "0" (zero).

FS_PASSNO (FSCK_ORDER) - used by the fsck program to determine the order in which filesystem checks are done at reboot time. The root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked.

==Benefits Of fstab Entries==
Once you have a device in the fstab, mounting become VERY easy. Instead of having to:
:<code>mount -t iso9660 /dev/hdb1 /mnt/cdrom</code>
every time you want to use the CDROM, you can just type:
:<code>mount /mnt/cdrom</code>
IF you have the entry in your fstab.

==Useful Examples==
CDROM: 
:/dev/hdc1 /mnt/cdrom auto noauto,ro,owner,users 0 0

[[USB Memory Stick]]: 
:/dev/sda1 /mnt/memstick auto noauto,owner,users 0 0 
(make sure to <code>mkdir /mnt/memstick</code> after changing your /etc/fstab).

[[External USB Drive / NTFS partition]]
:/dev/sdd1 /media/1T ntfs-3g defaults 2 0
(/dev/sdd1 is your external USB hard drive and /media/1T is destination folder)

Note: For changing who can access the filesystem on NON-Native linux formats see [[Permissions and Umasks]] and [[Windows Partitions]]

[[Category:Tutorials]]

Hibernate

Merge-delete — Wed, 13 Apr 2011 11:39:54 GMT

Merge-delete:

In Slackware, hibernation works out-of-the-box and can be easily done from KDE's menu. Resuming from hibernation, however, is not set up, so when you turn on your computer again, it starts as normal. That is, if your hardware supports it and if you've set up a swap space larger than your RAM.

== Huge kernel ==

To tell your kernel where to resume from, you need to write the info to ''lilo.conf'':

append=" resume=/dev/sda6"

Replace ''/dev/sda6'' with your actual swap space. Swap partitions are perfect, I think swap files should work too. If you don't know where your swap lies, look at ''/proc/swaps''.

== Generic kernel + initrd ==

If you're using generic or your own kernel, you need to adjust initrd image as well. Append

-h /dev/sdx

to mkinitrd command so it may look like this:

mkinitrd -c -k 2.6.33.4 -f <fs_type> -m <fs_type> -r /dev/sdx -h /dev/sdy

Replace ''/dev/sdx'' with your actual root partition and ''/dev/sdy'' with your actual swap space.

If you're using LVM, don't forget to append '''-L''' to mkinitrd command

mkinitrd -c -k 2.6.33.4 -f <fs_type> -m <fs_type> -r /dev/sdx -h /dev/volumegroup/swap -L

Afterwards, run lilo.

== Further reading ==

* [http://www.linuxquestions.org/linux/answers/Hardware/Mini_HOW_TO_Hibernate_and_resume_0 Mini_HOW_TO_Hibernate_and_resume_0]
* Hibernate to encrypted swap - [http://slackware.osuosl.org/slackware-13.1/README_CRYPT.TXT REAME_CRYPT.TXT]

[[Category:Tutorials]]

VirtualBox Compilation

Merge-delete — Sun, 10 Apr 2011 13:33:04 GMT

Merge-delete: /* Source packages */

[[category:tutorials]]
'''VirtualBox''' is a general-purpose full virtualizer for x86 hardware, targeted at server, desktop and embedded use. It comes in two editions
* Open Source Edition (OSE) - open-source licensed under GPLv2
* Personal Use and Evaluation License (PUEL) - closed-source with additional features (USB support, Remote desktop support, ...)

== Disclaimer ==
This tutorial applies to slackware-''current'' (-current after stable versions 13.1) and VirtualBox 4.0.x OSE

== Prerequisites ==
See this [http://www.virtualbox.org/wiki/Linux%20build%20instructions list]

Below lies additional, not obvious or not mentioned prerequisites.

=== Source packages ===
* VirtualBox - get it here: [http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-4.0.2.tar.bz2 http://download.virtualbox.org/virtualbox/x.y.z/VirtualBox-x.y.z.tar.bz2] where x.y.z stands for version numbers (eg. 4.0.2)
* PulseAudio - no SlackBuild available (note: applies to 09-01-2010); download sources from [http://www.pulseaudio.org http://www.pulseaudio.org]
* makeself - get it here: [http://megastep.org/makeself/ http://megastep.org/makeself/]

=== Slackware packages ===
* jdk
* gcc-java

=== SlackBuilds ===
* iasl - contained in SlackBuild [http://slackbuilds.org/repository/13.1/development/acpica/ acpica]

== Compilation ==
Unpack sources somewhere
<pre>
tar xjvf VirtualBox-x.y.z.tar.bz2 -C build/
cd build/VirtualBox-x.y.z_OSE/
</pre>

Run configure script which will generate Makefile.kmk and env.sh scripts
<pre>
$ ./configure --nofatal --disable-hardening --disable-docs
</pre>
<code>--nofatal</code> configure won't stop on non-fatal errors; it usually fails on <code>makeself</code> variable

<code>--disable-hardening</code> - automatically set few symbolic links so you can run VirtualBox binaries from bin/ directory of your build environment; '''don't''' use this switch if you're building package for redistribution

<code>--disable-docs</code> - for some reason, build fails when building documentation. If you don't mind using online documentation it's safe to disable building it

Update build environment variables with auto-generated script
<pre>
$ source ./env.sh
</pre>

Now it's time to compile sources, but there are few pitfalls

=== Troubleshooting & Pitfalls ===
==== PAM ====
Slackware doesn't ship PAM, so you have to change one line in Config.kmk to disable it
<pre>
if1of ($(KBUILD_TARGET), linux solaris)
# VBOX_WITH_PAM = 1
VBOX_WITH_PAM =
endif
</pre>

Note: It's really blank space, 0 doesn't work as logical False

==== Java path ====
Inside Config.kmk there is block with few possible locations of JDK binaries. Unfortunately, JDK in Slackware has different path, so you have to add right path.
<pre>
ifeq ($(KBUILD_TARGET),linux)
ifeq ($(origin VBOX_JAVA_HOME),undefined)
# Add correct detection for you distro after the /usr/../java-6-sun line.
# Slackware JDK resides in /usr/lib/jdk1.6.0_23 (JDK 1.6 update 23; type what version suits you)
VBOX_JAVA_HOME := $(firstword $(wildcard \
$(PATH_DEVTOOLS)/linux.x86/jdk1.6.0_21 \
/usr/lib/jvm/java-6-sun \
/usr/lib/jvm/java-6-openjdk \
/usr/lib/jdk1.6.0_23 \
/usr/lib/jvm/sun-jdk-1.6 \
) /usr/lib/jvm/java-6-sun)
endif
endif
</pre>

=== Build ===
Everything should be prepared by now. Type following command to build VirtualBox
<pre>
$ kmk
</pre>

Build VirtualBox kernel module
<pre>
$ cd out/linux.x86/release/bin/src
$ make
$ su
<password>
$ make install
$ cd ..
</pre>

Load kernel module (as root)
<pre>
$ modprobe vboxdrv
</pre>

Now you can start VirtualBox front-end from local bin/ directory
<pre>
$ ./VirtualBox
</pre>

Hibernate

Merge-delete — Sun, 10 Apr 2011 13:20:31 GMT

Merge-delete:

In Slackware, hibernation works out-of-the-box and can be easily done from KDE's menu. Resuming from hibernation, however, is not set up, so when you turn on your computer again, it starts as normal. That is, if your hardware supports it and if you've set up a swap space larger than your RAM.

To tell your kernel where to resume from, you need to write the info to ''lilo.conf'':

append=" resume=/dev/sda6"

Replace ''/dev/sda6'' with your actual swap space. Swap partitions are perfect, I think swap files should work too. If you don't know where your swap lies, look at ''/proc/swaps''.

If you're using generic or your own kernel, you need to adjust initrd image as well. Append

-h /dev/sdx

to mkinitrd command so it may look like this:

mkinitrd -c -k 2.6.33.4 -r /dev/sdx -f <fs_type> -m <fs_type> -h /dev/sdy

Replace ''/dev/sdx'' with your actual root partition and ''/dev/sdy'' with your actual swap space.

Afterwards, run lilo.

----

The above is everything I needed to do with my Slackware64 13.1 on a new laptop. I hope that works for you as well, but there are many requirements and intricacies not mentioned above. Google might help you. Please edit this document accordingly if you find out more.

Some more info at [http://www.linuxquestions.org/linux/answers/Hardware/Mini_HOW_TO_Hibernate_and_resume_0]

[[Category:Tutorials]]

VirtualBox Compilation

Merge-delete — Sun, 27 Feb 2011 01:15:12 GMT

Merge-delete: little update; not complete yet

[[category:tutorials]]
'''VirtualBox''' is a general-purpose full virtualizer for x86 hardware, targeted at server, desktop and embedded use. It comes in two editions
* Open Source Edition (OSE) - open-source licensed under GPLv2
* Personal Use and Evaluation License (PUEL) - closed-source with additional features (USB support, Remote desktop support, ...)

== Disclaimer ==
This tutorial applies to slackware-''current'' (-current after stable versions 13.1) and VirtualBox 4.0.x OSE

== Prerequisites ==
See this [http://www.virtualbox.org/wiki/Linux%20build%20instructions list]

Below lies additional, not obvious or not mentioned prerequisites.

=== Source packages ===
* VirtualBox - get it here: [http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-4.0.2.tar.bz2 http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-x.y.z.tar.bz2] where x.y.z stands for version numbers (eg. 4.0.2)
* PulseAudio - no SlackBuild available (note: applies to 09-01-2010); download sources from [http://www.pulseaudio.org http://www.pulseaudio.org]
* makeself - get it here: [http://megastep.org/makeself/ http://megastep.org/makeself/]

=== Slackware packages ===
* jdk
* gcc-java

=== SlackBuilds ===
* iasl - contained in SlackBuild [http://slackbuilds.org/repository/13.1/development/acpica/ acpica]

== Compilation ==
Unpack sources somewhere
<pre>
tar xjvf VirtualBox-x.y.z.tar.bz2 -C build/
cd build/VirtualBox-x.y.z_OSE/
</pre>

Run configure script which will generate Makefile.kmk and env.sh scripts
<pre>
$ ./configure --nofatal --disable-hardening --disable-docs
</pre>
<code>--nofatal</code> configure won't stop on non-fatal errors; it usually fails on <code>makeself</code> variable

<code>--disable-hardening</code> - automatically set few symbolic links so you can run VirtualBox binaries from bin/ directory of your build environment; '''don't''' use this switch if you're building package for redistribution

<code>--disable-docs</code> - for some reason, build fails when building documentation. If you don't mind using online documentation it's safe to disable building it

Update build environment variables with auto-generated script
<pre>
$ source ./env.sh
</pre>

Now it's time to compile sources, but there are few pitfalls

=== Troubleshooting & Pitfalls ===
==== PAM ====
Slackware doesn't ship PAM, so you have to change one line in Config.kmk to disable it
<pre>
if1of ($(KBUILD_TARGET), linux solaris)
# VBOX_WITH_PAM = 1
VBOX_WITH_PAM =
endif
</pre>

Note: It's really blank space, 0 doesn't work as logical False

==== Java path ====
Inside Config.kmk there is block with few possible locations of JDK binaries. Unfortunately, JDK in Slackware has different path, so you have to add right path.
<pre>
ifeq ($(KBUILD_TARGET),linux)
ifeq ($(origin VBOX_JAVA_HOME),undefined)
# Add correct detection for you distro after the /usr/../java-6-sun line.
# Slackware JDK resides in /usr/lib/jdk1.6.0_23 (JDK 1.6 update 23; type what version suits you)
VBOX_JAVA_HOME := $(firstword $(wildcard \
$(PATH_DEVTOOLS)/linux.x86/jdk1.6.0_21 \
/usr/lib/jvm/java-6-sun \
/usr/lib/jvm/java-6-openjdk \
/usr/lib/jdk1.6.0_23 \
/usr/lib/jvm/sun-jdk-1.6 \
) /usr/lib/jvm/java-6-sun)
endif
endif
</pre>

=== Build ===
Everything should be prepared by now. Type following command to build VirtualBox
<pre>
$ kmk
</pre>

Build VirtualBox kernel module
<pre>
$ cd out/linux.x86/release/bin/src
$ make
$ su
<password>
$ make install
$ cd ..
</pre>

Load kernel module (as root)
<pre>
$ modprobe vboxdrv
</pre>

Now you can start VirtualBox front-end from local bin/ directory
<pre>
$ ./VirtualBox
</pre>

The Regulars

Merge-delete — Fri, 18 Feb 2011 08:40:05 GMT

Merge-delete: /* Others */

==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:cpunches|cpunches]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:robert-brown|robert-brown]]
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]
* [[User:natex|natex]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.

VirtualBox Compilation

Merge-delete — Wed, 09 Feb 2011 03:16:01 GMT

Merge-delete: add missing step + few minor changes

[[category:tutorials]]
'''VirtualBox''' is a general-purpose full virtualizer for x86 hardware, targeted at server, desktop and embedded use. It comes in two editions
* Open Source Edition (OSE) - open-source licensed under GPLv2
* Personal Use and Evaluation License (PUEL) - closed-source with additional features (USB support, Remote desktop support, ...)

== Disclaimer ==
This tutorial applies to slackware-''current'' (-current after stable versions 13.1) and VirtualBox 4.0.x OSE

== Prerequisites ==
See this [http://www.virtualbox.org/wiki/Linux%20build%20instructions list]

Below lies additional, not obvious or not mentioned prerequisites.

=== Source packages ===
* VirtualBox - get it here: [http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-4.0.2.tar.bz2 http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-x.y.z.tar.bz2] where x.y.z stands for version numbers (eg. 4.0.2)
* PulseAudio - no SlackBuild available (note: applies to 09-01-2010); download sources from [http://www.pulseaudio.org http://www.pulseaudio.org]
* makeself - get it here: [http://megastep.org/makeself/ http://megastep.org/makeself/]

=== Slackware packages ===
* jdk
* gcc-java

=== SlackBuilds ===
* iasl - contained in SlackBuild [http://slackbuilds.org/repository/13.1/development/acpica/ acpica]

== Compilation ==
Unpack sources somewhere
<pre>
tar xjvf VirtualBox-x.y.z.tar.bz2 -C build/
cd build/VirtualBox-x.y.z_OSE/
</pre>

Run configure script which will generate Makefile.kmk and env.sh scripts
<pre>
$ ./configure --nofatal --disable-hardening --disable-docs
</pre>
<code>--nofatal</code> configure won't stop on non-fatal errors; it usually fails on <code>makeself variable</code>

<code>--disable-hardening</code> - set some environment variable; use when you don't want to build package

<code>--disable-docs</code> - for some reason, build fails when building documentation. If you don't mind using online documentation it's safe to disable building it

Update build environment variables with auto-generated script
<pre>
$ source ./env.sh
</pre>

Now it's time to compile sources, but there are few pitfalls

=== Troubleshooting & Pitfalls ===
==== PAM ====
Slackware doesn't ship PAM, so you have to change one line in Config.kmk to disable it
<pre>
if1of ($(KBUILD_TARGET), linux solaris)
# VBOX_WITH_PAM = 1
VBOX_WITH_PAM =
endif
</pre>

Note: It's really blank space, 0 doesn't work as logical False

==== Java path ====
Inside Config.kmk there is block with few possible locations of JDK binaries. Unfortunately, JDK in Slackware has different path, so you have to add right path.
<pre>
ifeq ($(KBUILD_TARGET),linux)
ifeq ($(origin VBOX_JAVA_HOME),undefined)
# Add correct detection for you distro after the /usr/../java-6-sun line.
# Slackware JDK resides in /usr/lib/jdk1.6.0_23 (JDK 1.6 update 23; type what version suits you)
VBOX_JAVA_HOME := $(firstword $(wildcard \
$(PATH_DEVTOOLS)/linux.x86/jdk1.6.0_21 \
/usr/lib/jvm/java-6-sun \
/usr/lib/jvm/java-6-openjdk \
/usr/lib/jdk1.6.0_23 \
/usr/lib/jvm/sun-jdk-1.6 \
) /usr/lib/jvm/java-6-sun)
endif
endif
</pre>

=== Build ===
Everything should be prepared by now. Type following command to build VirtualBox
<pre>
$ kmk
</pre>

VirtualBox Compilation

Merge-delete — Wed, 09 Feb 2011 03:11:01 GMT

Merge-delete: Created page with "category:tutorials '''VirtualBox''' is a general-purpose full virtualizer for x86 hardware, targeted at server, desktop and embedded use. It comes in two editions * Open Sour..."

[[category:tutorials]]
'''VirtualBox''' is a general-purpose full virtualizer for x86 hardware, targeted at server, desktop and embedded use. It comes in two editions
* Open Source Edition (OSE) - open-source licensed under GPLv2
* Personal Use and Evaluation License (PUEL) - closed-source with additional features (USB support, Remote desktop support, ...)

== Disclaimer ==
This tutorial applies to slackware-''current'' (-current after stable versions 13.1) and VirtualBox 4.0.x OSE

== Prerequisites ==
See this [http://www.virtualbox.org/wiki/Linux%20build%20instructions list]

Below lies additional, not obvious or not mentioned prerequisites.

=== Source packages ===
* VirtualBox - get it here: [http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-4.0.2.tar.bz2 http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-x.y.z.tar.bz2] where x.y.z stands for version numbers (eg. 4.0.2)
* PulseAudio - no SlackBuild available (note: applies to 09-01-2010); download sources from [http://www.pulseaudio.org http://www.pulseaudio.org]
* makeself - get it here: [http://megastep.org/makeself/ http://megastep.org/makeself/]

=== Slackware packages ===
* jdk
* gcc-java

=== SlackBuilds ===
* iasl - contained in SlackBuild [http://slackbuilds.org/repository/13.1/development/acpica/ acpica]

== Compilation ==
Unpack sources somewhere
<pre>
tar xjvf VirtualBox-x.y.z.tar.bz2 -C build/
cd build/VirtualBox-x.y.z_OSE/
</pre>

Run configure script which will generate Makefile.kmk and env.sh scripts
<pre>
$ ./configure --nofatal --disable-hardening --disable-docs
</pre>
<code>--nofatal</code> configure won't stop on non-fatal errors; it usually fails on <code>makeself variable</code>

<code>--disable-hardening</code> - set some environment variable; use when you don't want to build package

<code>--disable-docs</code> - for some reason, build fails when building documentation. If you don't mind using online documentation it's safe to disable building it

Update build environment variables with auto-generated script
<pre>
$ source ./env.sh
</pre>

Now it's time to compile sources, but there are few pitfalls
==== PAM ====
Slackware doesn't ship PAM, so you have to change one line in Config.kmk to disable it
<pre>
if1of ($(KBUILD_TARGET), linux solaris)
# VBOX_WITH_PAM = 1
VBOX_WITH_PAM =
endif
</pre>

Note: It's really blank space, 0 doesn't work as logical False

==== Java path ====
Inside Config.kmk there is block with few possible locations of JDK binaries. Unfortunately, JDK in Slackware has different path, so you have to add right path.
<pre>
ifeq ($(KBUILD_TARGET),linux)
ifeq ($(origin VBOX_JAVA_HOME),undefined)
# Add correct detection for you distro after the /usr/../java-6-sun line.
# Slackware JDK resides in /usr/lib/jdk1.6.0_23 (JDK 1.6 update 23; type what version suits you)
VBOX_JAVA_HOME := $(firstword $(wildcard \
$(PATH_DEVTOOLS)/linux.x86/jdk1.6.0_21 \
/usr/lib/jvm/java-6-sun \
/usr/lib/jvm/java-6-openjdk \
/usr/lib/jdk1.6.0_23 \
/usr/lib/jvm/sun-jdk-1.6 \
) /usr/lib/jvm/java-6-sun)
endif
endif
</pre>

Dhcp renewal after wakeup

Merge-delete — Sun, 28 Nov 2010 15:39:39 GMT

Merge-delete:

[[Category:Tips]]

Sometimes you need a new IP address after waking up from sleep/standby/hibernate modes. Network managers like Wicd can do this and are recommended for laptops, but you can use the pm-utils triggers yourself without installing and running more software too. The following script works for me:

<pre>
#!/bin/sh
#
# put this to: /usr/lib64/pm-utils/sleep.d/05DhcpcdRenew
# /usr/lib/pm-utils/ .. on 32-bit systems

case "$1" in
hibernate|suspend)
dhcpcd -k eth0
;;
thaw|resume)
dhcpcd eth0
;;
*) exit $NA
;;
esac
</pre>

The script probably needs to be executable.

Dhcp renewal after wakeup

Merge-delete — Sat, 27 Nov 2010 14:08:58 GMT

Merge-delete: dhcp renew after sleep tip

[[Category:Tips]]

Sometimes you need a new IP address after waking up from sleep/standby/hibernate modes. Network managers like Wicd can do this and are recommended for laptops, but you can use the pm-utils triggers yourself without installing and running more software too. The following script works for me:

<pre>
#!/bin/sh
#
# put this to: /usr/lib64/pm-utils/sleep.d/05DhcpcdRenew
# /usr/lib/pm-utils/ .. on 32-bit systems

case "$1" in
hibernate|suspend)
;;
thaw|resume)
dhcpcd -n
;;
*) exit $NA
;;
esac
</pre>

The script probably needs to be executable.

Multilib

Merge-delete — Thu, 05 Aug 2010 21:03:37 GMT

Merge-delete: Link to alienBOB's multilib tutorial and a detail about not using SBo packages for display drivers.

There's a good tutorial (and packages) on how to set up multilib support (32-bit programs on Slackware64) at
[http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib AlienBOB's site]. You'd do well to go there next.

''However'', as that's not complete and clear on all points, here are some details:

==Binary display drivers==

You need to reinstall binary drivers. ATI and Nvidia driver packages contain both 64bit and 32bit libraries to be maximally useful on a 64bit multilib OS. However, the slackbuild scripts available at slackbuilds.org are not up to this task, so if you already installed 64-bit binary drivers from slackbuilds.org, you should remove these and then use ATI's or Nvidia's driver installer.

[[Category:Tutorials]]

Kernel Checklist

Merge-delete — Wed, 28 Jul 2010 00:45:20 GMT

Merge-delete: just fixed a couple of spelling typos

# [√] Make sure the filesystem type of your root partition is compiled into the kernel. To check what your root filesystem is type "mount".
# [√] Check that your networking card is compiled as a module or compiled into the kernel.
# [√] If you are using NVIDIA video card make sure you compile the AGP as a module
# [√] The sound card is important for listening to music; module it, or compile it in.
# [√] Another important thing that people miss out is the IDE chipset. This is important because you want to enable DMA on drives, and other important speed enhancements.
# [√] If you are going to use a camera that requires usb mass storage compile in SCSI Generic and USB-Mass storage.
# [√] Compile the sysfs feature in the kernel as that is an important for /sys. It is important for the 2.6 kernel.
# [√] If you must have framebuffer make sure you compile it in with the appropriate things. If you get a black screen set lilo.conf to vga = normal, then mess with it later. Also for nvidia users the rivafb is broken on many cards, so do not compile it in because it effects the nvidia driver for X. So use the vesafb instead.
# [√] Another useful tool that i use is the .config in /proc (A must have I think)
# [√] ATA/ATAPI settings are also useful for people, might want to make sure your kernel has that.
# [√] SATA/SCSI Make SURE YOU COMPILE it into the kernel and make sure you actually compile it in. If you have a SATA or SCSI hardware.
# [√] Iptables modules if you are going to use iptables or make a firewall. I use modules:)
# [√] I always recommend that in ALSA you compile or module OSS Emulation API
# [√] APM or ACPI is always something you might want to enable. This is not a feature needed by the kernel but, some people might need its features.

Just a reminder that the root filesystem (SCSI/SATA/etc) should be compiled into the kernel for obvious reasons.

[[Category:Tips]]

SlackRoll Tutorial

Merge-delete — Fri, 23 Jul 2010 10:50:35 GMT

Merge-delete:

SlackRoll is a package or update manager for Slackware Linux. Part of this tutorial has been taken from its [http://rg3.github.com/slackroll/ official webpage] and FAQ. SlackRoll's defining points:

* Its internal mechanism based on package states.
* Like slackpkg, SlackRoll only works with official mirrors, meaning that to keep third party packages up to date you need to perform the task by hand (recommended practice, using SlackBuild scripts) or use a second different tool.
* It does not try to compare package version numbers to decide if a package should be upgraded or not.
* Partly as a consequence of the previous point, it has no known flaws detecting package updates (including reverts), new packages, removed packages, third party packages getting an official version and blacklisted packages (frozen in its terminology) being removed.
* It has a broad range of operations and features.
* It attempts to be fast. Most internal operations like listing available upgrades usually take less than one second on a modern computer.

= Installation =

== Requirements ==

* Python 2.4 or later (provided by package python starting with Slackware 10.1).
* GnuPG (provided by package gnupg or gnupg2).
* Vim (provided by package vim).
* A pager which is less by default (provided by package less).

== Procedure ==

Download the SlackRoll package from the [http://github.com/rg3/slackroll/downloads project download page] and install it in your system using <tt>installpkg</tt>.

= Background Information =

The majority of SlackRoll commands that receive a list of packages expect only the package names (foo as opposed to foo-1.1-i486-3.tgz). Some of them also allow using a specific version, but they are the exception.

SlackRoll creates a persistent database of packages in your hard drive. Each package is in one of several possible states. Part of the initial configuration consists in deciding which states some of your packages will have. There are two types of states: states to avoid (temporary states) and normal states. When the remote Slackware official tree is updated, SlackRoll may put some packages in temporary states. By upgrading, installing, removing and marking packages your objective is to correct those packages and put them in a normal state.

== States to Avoid ==

=== New ===

New packages are packages present in the remote tree that weren't present before. You should decide if you want to install them or mark them as not installed.

=== Outdated ===

Outdated packages are present in your system, but the version you have does not match any relevant one in the remote tree. You should upgrade these packages.

=== Unavailable ===

Unavailable packages are packages present in your system. Previously, they probably existed in the remote tree, but now they do not seem to be available for downloading and installing. You should decide if you want to remove them or mark them as foreign.

== Normal States ==

=== Installed ===

Installed packages are very common. They are present in your system and in the remote tree, and both versions match.

=== Not Installed ===

Not installed packages are also very common. They are present in the remote tree but not in your system. They can be downloaded and installed if you want.

=== Foreign ===

Foreign packages are packages present in your system but not in the remote tree. However, unlike unavailable packages, they are supposed to be present in your system. No package will enter this state automatically. Only the ones you mark. It's usually reserved for third party packages and packages you build yourself. It's worth noting that if a foreign package ever appears in the remote official tree, it will be marked as installed or, probably, outdated. Thus, SlackRoll will give priority to the new official package over yours. If you still want to use your own build, mark it as frozen.

=== Frozen ===

Frozen packages are present in your system and in the remote tree. Your version may or may not match the ones from the remote tree, but SlackRoll will not tell you they need to be upgraded. No package will enter this state automatically. It's usually reserved for packages that shouldn't be upgraded automatically or ever (aaa_elflibs, kernels, etc) and sometimes for customized versions of official packages. It's also worth mentioning that a frozen package will be moved to unavailable if it disappears from the remote tree. It that happens and you want to continue using it, you'll need to mark it as foreign.

= Initial Configuration =

Word of warning: it's highly recommended to do the initial configuration from an up-to-date and controlled system. This will avoid confusion and helps preventing mistakes setting the initial package states.

== Preparing Your System ==

Choose a Slackware mirror for your Slackware version. Use the set-mirror operation to select one mirror. SlackRoll can work with stable trees as well as the current tree. Example:

# slackroll set-mirror 'http://slackware.example.org/slackware-current/'

Do not forget to include the trailing slash in the mirror URL. Import, to your keyring, the GnuPG key used to sign the official Slackware packages. This key can be found in Slackware CDs and DVDs as the file GPG-KEY, and you can import the key to your keyring using the command gpg --import, but SlackRoll is able to download the key from the mirror and importing it automatically, if you trust the mirror.

# slackroll import-key

Finally, retrieve the mirror information for the first time. This will download a few metadata files, and this is what you need to do when you're going to handle a new round of updates.

# slackroll update

== Going Over Package States for The First Time ==

When you run SlackRoll for the first times, it will put every remote package not present in your system in the state New. When your system is up to date and under control, you can blindly mark every new package as not installed with the following command:

# slackroll new-not-installed

Any third party package present in your system will be put in the state Unavailable. When your system is up to date and under control you can blindly mark all unavailable packages as foreign. However, the number of foreign packages is usually not very high and forgetting to remove from your system a package that was removed from the remote tree is a common mistake. The Book of Best Practices would suggest that you review the list of unavailable packages once and carefully in order to detect packages that should not be present in your system. To print the list run:

# slackroll list-unavailable

If you locate any package that needs to be removed, you can remove them using removepkg or the remove operation. The later has additional functionality so it's recommended:

# slackroll remove foo bar

Now you can mark the rest as foreign packages.

# slackroll unavailable-foreign

Finally, you probably want to mark some packages as frozen. It's usually a good idea to do this with aaa_elflibs, kernel packages and others.

# slackroll frozen aaa_elflibs foo bar

= Day to Day Usage =

Apart from the operations listed here, you can run the help operation to get the full list of supported operations, along with a brief description of each one. A more detailed description can be found in the [http://wiki.github.com/rg3/slackroll/operations-guide operations guide].

== New Round of Updates ==

What to do when there is a new round of updates? The Book of Best Practices suggests taking care of different events in a specific order:

* Updates to glibc-solibs, sed and pkgtools need to be handled first, in that order.
* If there are new packages, handle them second.
* Then, it's time to upgrade outdated packages.
* If packages have been deleted from the remote tree, handle them last.

This is the correct order in 99% of the cases. SlackRoll will attempt to warn you and ask for confirmation if it detects you may be breaking this order. However, you have the last word on what to do, so proceed with caution and don't break your system.

First, update the remote mirror information with the update operation we mentioned before. New changelog entries will be saved to your hard drive. It's recommended that you take a look at the changelog at this point, using the changelog operation. Then, get an overview of the events using the list-transient operation, which will list the new, outdated and unavailable packages along with a big fat warning message if activity in key system packages is detected.

The best way to deal with glibc-solibs, sed and pkgtool updates is to use the upgrade-key-packages operation.

# slackroll upgrade-key-packages

You could also use the install operation. Despite its name, it can be used to both install and upgrade individual packages. Let's suppose packages glibc-solibs and sed where updated:

# slackroll install glibc-solibs sed

The install operation is one of the few operations allowing you to pass specific package versions. It will proceed in the order you indicate, so remember to give the packages in the correct order if you use this method.

Second, you should handle new packages. You can clearly get a list of new packages with the list-new operation. New packages can be installed with the install operation as we just showed. When installing a remote package, SlackRoll will give you the opportunity of selecting the version to install if there are several available in the remote tree. Or, if you are not interested in installing a new package, mark it as not installed:

# slackroll not-installed foo bar

If the package names are not enough for you to decide if you want to install it or not, you can always use the info operation and SlackRoll will download and display the package info file (small txt files in the remote tree). And, of course, be carefull with new libraries as they may have been included to extend the functionality of an existing package you may have installed.

The third step is taking care of outdated packages. For that, a few operations are available. list-upgrades lets you see a summary of the available upgrades. You can download and install them with upgrade or download them with download-upgrades or even print their URLs with urls-upgrades.

And, finally, review the list of unavailable packages. Be careful with unavailable packages. Sometimes you install a foreign package but forget to mark it as such in SlackRoll. To avoid that problem, it's better to install them with the install-foreign operation. Individual unavailable packages can be removed with the remove operation as we showed before, and also all of them at the same time with the remove-unavailable operation.

== Installing and Removing Individual Packages ==

There are a few operations related to installing and getting some information about individual packages. The most common ones are install to upgrade or install packages, info to maybe download and display package info files, urls to get a list of URLs and remove to remove individual packages.

Operations that install packages let you manage .new files after the installation is completed, in a similar way to slackpkg. You can view the differences between the .new file and its counterparts with vimdiff (which provides a nice and colorized way of spotting the differences and maybe porting the old configuration to the new file), you can overwrite the old file with the .new file, delete the .new file directly, etc.

Additionally, removal operations also track pairs of .new files and give you the opportunity of deleting configuration files that have been left behind. You are not forced to remove the files left behind, of course.

Upgrade operations will perform both tasks. First, they will let you review the .new files and then they will give you the opportunity of deleting obsolete configuration files left behind.

While using vimdiff, turning off syntax highlighting is recommended. Vim uses colors to highlight file differences and those can interfere with syntax highlighting colors, making text invisible or hard to read. Syntax highlighting can be turned off temporarily by using "<tt>:syntax off</tt>" in command mode, or you can disable it permanently putting "<tt>syntax off</tt>" in your <tt>~/.vimrc</tt> file (noting that usually you run SlackRoll as the superuser).

== Managing Customized Versions of Official Packages ==

There are at least three ways of dealing with customized versions of official packages. These are custom versions or compilations of packages present in the remote official tree. They are normally used to add or remove features, or activate or apply patches that are disabled by default. For example, if you want to activate the freetype bytecode interpreter, you need to rebuild that package.

The simplest way of dealing with these packages is to give them the same name and version as the official packages. When they are upgraded in the remote tree, however, SlackRoll will want to upgrade them. You can mark them as frozen before upgrading and only unfreeze them after you have rebuilt the new version, if you want to avoid SlackRoll replacing them with the new official version.

Second, you can give them the same name and version as the official package, but keep them frozen all the time. How would you know then if they need to be rebuilt? With the list-outdated-frozen operation. Take into account the information given by list-outdated-frozen is not reflected by any other command. Specifically, it's not reflected as part of list-transient and friends.

Third, you can give them a name or version different to the official package. Typically this means adding a custom build suffix and marking the package as frozen. How would you know if you need to rebuild it? Paying attention to the changelog specifically searching for upgrades in those packages and also using the list-versions operation, that lets you view the different known versions of a package, including local and remote ones.

== Maintenance ==

SlackRoll barely requires maintenance. It keeps all downloaded packages in its package cache, located in the /var/slackroll/packages directory. When downloading files, it keeps them in a temporary directory until they're fully downloaded. If you want to remove every downloaded package, you can simply perform <code>slackroll erase-cache</code>. There is, however, a clean-cache operation which does not remove every downloaded package, but only those that are no longer present in the remote tree. Running that operation from time to time keeps your package cache sane and controlled. It may also be a good idea to delete the temporary directory contents from time to time, with <code>slackroll erase-tmp</code>, but it should be empty unless you interrupt SlackRoll while downloading stuff and never attempt to complete the download.

== Other Operations ==

If you run the help operation you will see SlackRoll has many other operations, including operations to list packages by state, list local packages, list remote packages and list all known packages. It has operations to put packages in specific states and checking the state of packages. You can also download, install, display info or remove new or unavailable packages or packages with a matching path (like /slackware/kde/). Finally, there are search operations, to search for packages by name or path, search for files in your local system (like running grep on the contents of /var/log/packages), query the Slackware Package Browser, and finally a few very slow but sometimes useful operations to search for broken symlinks under a specific hierarchy and the same for orphan files (files not belonging to any package), as well as searching for missing files.

As a general rule, every operation either does not accept arguments or allows a list of them. Operations accepting packages as arguments expect the package name only unless the help text mentions that they also accept specific package versions. Some operations need regular expressions. For the most part they have the same syntax as they have in grep or Perl, but you can read the [http://docs.python.org/lib/re-syntax.html Python regular expressions syntax reference] if you want to perform an unusually complex search.

[[Category:Tutorials]]

==Related Links==

[http://www.cellulite.co.uk/ '''cellulite''']

ACPI Modules

Merge-delete — Thu, 22 Jul 2010 07:14:18 GMT

Merge-delete:

[[Category:Tips]]

These are the kernel modules that need to be loaded in order to use some of the features of ACPI.

* ac - AC adapter information
* battery - Battery information
* fan
* button - Enables accesing info about ACPI-controlled buttons (like the Power button and the LID button)
* video
* thermal - Driver for the Thermal Zone (/proc/acpi/thermal_zone)
* processor - Loads the ACPI processor driver (/proc/acpi/processor)
* container - Loads the ACPI container driver
* vendor-specific drivers (eg acer_acpi, [http://www.thinkwiki.org/wiki/Thinkpad-acpi thinkpad-acpi])
* [http://www.college-paper.org/custom-essay.html college essays]

Console-Only Communication

Merge-delete — Wed, 14 Jul 2010 09:18:55 GMT

Merge-delete:

HOWTO: access on-line resorces on the internet using only console-based tools.

== Overview ==
Many times, particularly when things aren't working as expected, you may find yourself restricted to a console-only (non-X or non-graphical) session. If you have networking running, you can still access on-line support tools through your console. This tutorial shows you how to:

* Use virtual consoles to increase the number of consoles you can use simultaneously;
* Use the <tt>screen</tt> to create sessions that are persistant even after you close the console;
* Use <tt>irssi</tt> to access the irc network and ##slackware on irc.freenode.org;
* Use <tt>lynx</tt> and <tt>wget</tt> to access HTTP (web) server information;
* Use <tt>lynx</tt> to pastebin a file when you need to send configuration information to an IRC channel, and;
* Use <tt>wget</tt> to download a pastebin file to your local machine.

== Prerequisites ==
This tutorial will assume you are comfortable with the following concepts:
* Basic file management operations (<tt>cp</tt>,<tt>rm</tt>,etc);
* Using a console-based file editor (<tt>pico</tt>,<tt>vi</tt>,etc);
* [http://www.casino-spielen.biz online casino spiele]

== Virtual Consoles ==
One of the handiest features if you're relegated to working from a console is the use of virtual consoles. This allows you to start multiple login sessions from the same console keyboard, mouse, and monitor. That way, you can have one virtual console logged into IRC so you can talk to ##slackware, one that you can use for web access, and another that you can use to test commands.

Using virtual consoles is easy. Simply hold the ALT key while hitting the F2 key (ALT+F2) to switch to the second console. To switch back to the first console, use ALT+F1. You have virtual consoles available on F1 through F6.

If you're using X, you can still access one of the virtual consoles, which is useful if X is hung up for some reason (especially if X won't restart using ctrl+alt+backspace). To access this virtual console, hold CTRL *and* ALT while pressing the F6 key (CTRL+ALT+F6). To switch back to your X session, press CTRL+ALT+F7.

== Using <tt>screen</tt> ==
The <tt>screen</tt> utility allows you to start a console session which is persistent across login and logout. This is useful, for example, if you're using IRC -- perhaps you want to stay logged into your IRC channel even after you have logged out of your console session. The concept is straightforward: when you run screen, it gives you a bash prompt "inside of" the screen session. At this new bash prompt you can start your IRC session. When you wish to log out, you can detach from screen and log out -- but screen continues to run in the background. When you log back in, you can re-attach to your screen session and resume your IRC session.

Visit [[Screen|this page]] for the specifics on attaching and detaching sessions using <tt>screen</tt>.

== Using <tt>irssi</tt> ==
The <tt>irssi</tt> program is a console-based IRC client. Using irssi, you can access the ##slackware IRC channel on irc.freenode.net.

*WARNING*: Whenever you are using any type of IRC client on any type of machine, make sure that you are not doing so as the superuser (root). Doing so is a security risk, since if for some reason an attacker is able to successfully attack your IRC client, the attacker will have root access to your machine.

To access the ##slackware channel on irc.freenode.org using <tt>irssi</tt>, perform the following steps:

* Start irssi:
user@slackbox:~$ irssi
* At the (status) prompt, connect to irc.freenode.org:
[(status)] /connect irc.freenode.org
* Once connected, set your nick:
[(status)] /nick Myl33tNick
* Join the ##slackware channel:
[(status)] /join ##slackware
* To exit irssi:
[(status)] /quit
Visit [[Irssi|this page]] for more information on using irssi.

== Using <tt>lynx</tt> and <tt>wget</tt> ==
You can use <tt>lynx</tt> and <tt>wget</tt> to access http (web) servers from your console session. Lynx allows you to access a web site interactively, much like using a graphical browser such as Firefox, but through a text-only console session. <tt>Wget</tt> allows you to retrieve documents from web servers non-interactively, which is handy when you need to retrieve a certain document (say a tarball or a script file) from a web server in a very quick way.

To start using lynx, from a bash prompt simply type:
user@slackbox:~$ lynx "http://www.slackware.com"
to visit Slackware's official website. To exit lynx, use CTRL+C. In the example above, the double-quotes are not strictly required. However, many URLs contain characters which have special meaning to the bash interpreter (such as the ampersand), and the double-quotes stop bash from trying to interpret those characters.

Although wget has a wide array of options (visit man wget sometime), its basic use is very simple. For example, to download the latest kernel patch (as of this writing) from kernel.org, simply do:
user@slackbox:~$ wget "http://www.kernel.org/pub/linux/kernel/v2.6/patch-2.6.20.3.bz2"
Again, the quotes here are not strictly required for this URL, but are required for certain URLs. It's good to get in the habit of always double-quoting URLs from a bash prompt.

== Using <tt>lynx</tt> in conjuction with pastebin ==
You may find yourself on ##slackware and another channel member may ask you to "pastebin" information to them. The purpose of pastebin is so that you can share technical information (for example, the contents of a configuration file) with the other channel members, without pasting that information directly into IRC itself (which is generally disliked by other IRC members and will get you banned if you try it). "Pastebin" is a generic term for a web site which offers this sort of service. There are many pastebin sites out there; for simplicity's sake, this tutorial uses [http://pastebin.ca pastebin.ca].

You can use lynx to access the pastebin site, but what if you need to pastebin the contents of an entire file? You can do this using the <tt>lynx</tt> program:
* use <tt>lynx</tt> to access pastebin.ca:
user@slackbox:~$ lynx "http://pastebin.ca"
* Page down until you see the large textbox area, move your cursor to the first line (where you see the X below):
Create a New Pastebin Post

Welcome to the Pastebin. For information on what this is, take a look
at the What is This? page. You may also want to see the most recent
post to the pastebin.

Please enter your new post below (or upload a file instead):

paste below

X_____________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
(NORMAL LINK) Use right-arrow or <return> to activate.
Arrow keys: Up and Down to move. Right to follow a link; Left to go back.
H)elp O)ptions P)rint G)o M)ain screen Q)uit /=search [delete]=history list
* Press Ctrl+X, then i, and enter the location of the file you wish to pastebin.
Enter a filename: /etc/ssh/sshd_config
* Page down until you see the "Submit Post" link, select it (it will turn yellow), and press the enter key.
* On the next page, scroll down until you find the URL to your pastebin file. It will look something like this:
paste added to database

Your paste has been accepted an added to the database. You will be
redirected to it momentarily. The URL for it is:

http://pastebin.ca/398871

You may use that URL for referencing your submission from now on.
* Give this URL to the person who requested the information on IRC.

== Using <tt>wget</tt> in conjunction with pastebin ==
Every pastebin site should have a way to request any pastebin file in "raw" format, meaning without the added HTML code so that the pastebin information displays properly in a browser. Accessing the "raw" format means you can access exactly what was pastebinned, with nothing else added. This is useful if you want to download a configuration file from pastebin. If you know the raw URL of the pastebin page you need, you can use wget to retrieve the file.
* Find the raw URL associated with the pastebin page. For pastebin.ca, this is just the regular URL with an extra "raw" directory inserted. For example, if your regular pastebin url is http://pastebin.ca/398871, then the raw version is at http://pastebin.ca/raw/398871.
* use wget to retrieve the file, but rename it so that it's not named 398871 (in this example, the output is named "this.cfg"):
user@slackbox:~$ wget "http://pastebin.ca/raw/398871" -O this.cfg
You'll find you'll use commands like wget over and over again this way, even when you have access to a fully graphical web browser.
[[Category:Tutorials]]

SlackWiki:Community Portal

Merge-delete — Wed, 16 Jun 2010 20:10:07 GMT

Merge-delete:

====[http://www.slackwarebrasil.org GUS-BR]====
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil) 
[http://www.slackwarebrasil.org www.slackwarebrasil.org ]
 
====[http://slacky.eu/ Slacky.eu]====
The Italian Slackware Community 
[http://slacky.eu/ http://slacky.eu]
 
====[http://slackware.linux.or.id Indonesian Slackware Community]====
[http://slackware.linux.or.id http://slackware.linux.or.id]

SlackWiki:Community Portal

Merge-delete — Wed, 16 Jun 2010 20:00:45 GMT

Merge-delete: Created page with '===BRASIL=== ====[http://www.slackwarebrasil.org GUS-BR]==== Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil) [http://www.slackwarebrasil.org www.slackwar…'

===BRASIL===
====[http://www.slackwarebrasil.org GUS-BR]====
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil) 
[http://www.slackwarebrasil.org www.slackwarebrasil.org ]

===ITALY===
====[http://slacky.eu/ Slacky.eu]====
The Italian Slackware Community 
[http://slacky.eu/ http://slacky.eu]

Hibernate

Merge-delete — Wed, 02 Jun 2010 13:42:09 GMT

Merge-delete: fix + link

In Slackware, hibernation works out-of-the-box and can be easily done from KDE's menu. Resuming from hibernation, however, is not set up, so when you turn on your computer again, it starts as normal. That is, if your hardware supports it and if you've set up a swap space larger than your RAM.

To tell your kernel where to resume from, you need to write the info to ''lilo.conf'':

append=" resume=/dev/sda6"

Replace ''/dev/sda6'' with your actual swap space. Swap partitions are perfect, I think swap files should work too. If you don't know where your swap lies, look at ''/proc/swaps''. Afterwards, run lilo.

----

The above is everything I needed to do with my Slackware64 13.1 on a new laptop. I hope that works for you as well, but there are many requirements and intricacies not mentioned above. Google might help you. Please edit this document accordingly if you find out more.

Some more info at [http://www.linuxquestions.org/linux/answers/Hardware/Mini_HOW_TO_Hibernate_and_resume_0]

[[Category:Tutorials]]

Hibernate

Merge-delete — Wed, 02 Jun 2010 13:32:35 GMT

Merge-delete: Crude and minimal (but to the point) hibernation help

Utf-8 linux console

Merge-delete — Wed, 02 Jun 2010 13:04:39 GMT

Merge-delete: Added setting LANG in /etc/profile.d/lang.sh

[[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/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)