SlackWiki - User contributions [en]

Links

Gabim — Wed, 08 Jul 2009 13:57:13 GMT

Gabim: /* Slackware Links */

[[Category:Information]]

==Slackware Links==
* http://www.slackware.com - the home of Slackware
* http://www.slackwaregallery.org - our ugly mugs :)
* http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ - Slackware FAQ by [[User:juhl|juhl]] (Jesper Juhl)
* http://slackware.wordpress.com - Slackware Blog by [[User:Tyler|Tyler]]
* http://www.slackbook.org - updated version of the slackware book
* http://userlocal.com/ - A focal point for the online Slackware Linux community
* http://www.slackware.com/getslack - Extensive listing of Slackware mirrors
* http://www.slackbasics.org/ - "Slackware Linux Basics" by Daniel de Kok
* http://www.linuxquestions.org/questions/slackware-14/ - Slackware forum
* http://www.kde-look.org/content/show.php?content=23384 - Slack-Track - a superkaramba theme to track the slackware-current changelog on your desktop, created by [[User:omal|omal]]
* http://www.slacklife.com.br - Slackware Brazillian Community - by [[User:Redhate|redhate]]
* http://slackware.linux.or.id - Indonesian Slackware Community - by [[User:Willysr|Willysr]]
* http://open-eslack.org/ - Spanish Slackware community
* http://sbopkg.org - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository
* http://slackbot.sourceforge.net - Buildsystem and buildtools for Slackware

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Free packages==

* [http://slackware.com/~alien/ http://slackware.com/~alien/] Eric Hameleers' packages
* [http://rlworkman.net/pkgs/ http://rlworkman.net/pkgs/] rworkman's packages
* http://www.linuxpackages.net/
* [http://www.slacky.eu/repository/slackware-11.0/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware
* [http://scxd.info/en/ Slackware Current eXtended Desktop] Packages for Slackware Current

==.SlackBuild Repositories==
* http://slackbuilds.org - The SlackBuilds.org Project
* http://slackbuilds.net - The French SlackBuilds Repository
* http://www.slackware.com/~alien/slackbuilds/ - Eric "Alien" Hameleer's SlackBuilds
* http://slackbuild.strangeworlds.co.uk - cathectic's SlackBuilds
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.
* http://scxd.info/pub/slackbuilds/ - Slackware Current eXtended Desktop's SlackBuilds

==Live CD's based on Slackware==
* [http://www.remote-exploit.org/ BackTrack] The result of the merging of two Innovative Penetration Testing live Linux distributions: Whax and Auditor
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* http://open-eslack.org/wiki/ - Wiki of the Slackware spanish community
* http://slackware.linux.or.id/wiki/ - Indonesian Slackware Wiki

==RSS Feeds==
* http://dev.slackware.it/rss/ - RSS feeds for stable Slackware release and -current ChangeLog
* http://slackbuilds.org/mirror/rss/ - ChangeLog RSS feeds for 8.1 through -current

Dependency Discovery

Gabim — Wed, 08 Jul 2009 13:32:56 GMT

Gabim:

[[Category:Tips]]
== Introduction ==

"Slackware users typically prefer their method of manual dependency resolution, citing the level of system control it grants them." - as the [http://wiki.archlinux.org/index.php/Arch_Compared_To_Other_Distros#Arch_vs_Slackware ArchWiki] says. This total control over the system is one of the main strength of the Slackware distribution.

If the administrator of the system knows every package on the system and ensures their every dependencies, then the system is stable, well usable. If the administrator installs a new, (until now) unknown application, then he/she needs to discover its dependencies via the attached README or documentations, or from starting the application (if something is not installed on the system, then the application won't start).

== Dependency resolution at package installation ==

The dependency resolution can be performed at package installation, if we use a third party package manager, see [[Third_Party_Package_Managers]]. This is very easy, but we should use that third party package manager and maybe we don't want to do it just for a simple package installation. We would like a more Slackware like solution.

== Dependency discovery as a separate task ==

We can discover the dependencies of our system in separate task using the '<code>ldd</code>' command. This is not third party application, it is the part of our system.

We can scan the binaries in our PATH:
#!/bin/bash

ECHO=/usr/bin/echo
SED=/usr/bin/sed
FILE=/usr/bin/file
CUT=/usr/bin/cut
LDD=/usr/bin/ldd
GREP=/usr/bin/grep
AWK=/usr/bin/awk

for p in `$ECHO $PATH | $SED 's/:/ /g'`
do
for f in $p/*
do
if [ 'ELF' == `$FILE -b $f | $CUT -d' ' -f1` ]; then
if $LDD $f | $GREP -q 'not found'; then
$ECHO "$f"
$LDD $f | $GREP 'not found' | $AWK '{print "Not found:", $1}'
fi
fi
done
done

Or, we can print the missing package names instead of the missing library names, so we have to install only the given packages mentioned by this script (I used the concatenated MANIFEST file of '<code>slackpkg</code>' on Slackware64, this file list is more friendlier for scripting):
#!/bin/bash
# This is the concatenated MANIFEST file of slackpkg on Slackware64
MANIFEST=/var/lib/slackpkg/slackware64-filelist.gz

# Do not trust in any command in PATH, shell builtins, etc.
ECHO=/usr/bin/echo
PRINTF=/usr/bin/printf
CUT=/usr/bin/cut
SORT=/usr/bin/sort
GREP=/usr/bin/grep
ZGREP=/usr/bin/zgrep
SED=/usr/bin/sed
AWK=/usr/bin/awk
FILE=/usr/bin/file
LDD=/usr/bin/ldd
NULL=/dev/null

# Check all directories in PATH
for directory in `$ECHO $PATH | $SED 's/:/ /g'`
do
# Check all binaries in PATH directories
for binary in $directory/*
do
# If it is true ELF binary
if [ 'ELF' == `$FILE -b $binary | $CUT -d' ' -f1` ]; then
# Show the progress by printing of actual filename on standard error
$PRINTF "%-70s\r" $binary >&2
# Check the missing shared library dependencies
$LDD $binary 2>$NULL | $GREP 'not found' | $AWK '{print $1}' | while read missing_lib
do
# Print the package name of the missing library
$ZGREP $missing_lib $MANIFEST | $AWK '{print $1}'
done
fi
done
# Clear the progress info
$PRINTF "%-80s\r" "" >&2
# Ignore the duplicated package names
done | $SORT -u

If we would like to scan the binaries of the PATH and the shared libraries of our system, then we need a deeper directory discovery:
#!/bin/bash

# This is the concatenated MANIFEST file of slackpkg on Slackware64
MANIFEST=/var/lib/slackpkg/slackware64-filelist.gz

# Do not trust in any command in PATH, shell builtins, etc.
SYSPATH=$PATH
PATH=/bin:/usr/bin:/usr/sbin
ECHO=/usr/bin/echo
PRINTF=/usr/bin/printf

# Check all directories in PATH and ld.so.conf
# If it is true ELF binary
find `$ECHO $SYSPATH | sed 's/:/ /g'` \
`sed 's/$\/.*\/.*$\/.*/\1/' /etc/ld.so.conf | sort -u` \
-perm -100 -a -type f \
-exec sh -c 'filename="{}"; /usr/bin/echo -n "." >&2; \
[ "ELF" = `file -b $filename | cut -d" " -f1` ] && \
ldd $filename 2>/dev/null | fgrep "not found" \
| cut -d" " -f1' \; | while read missing_lib
do
# Print the missing library and its package name
$ECHO $missing_lib ": `zgrep $missing_lib $MANIFEST | cut -d" " -f1`"
done | sort -u

This small script will browse huge amount of directories and will scan a lot of ELF binaries, so it can run for a long time.
There are more effective ways of the dependency discovery, this is only a very simple solution for a natural system administrator need. It demonstrates that a Slackware user does not need a package manager with dependency resolution, but even so can have a stable, well configured system.

Dependency Discovery

Gabim — Wed, 08 Jul 2009 13:12:27 GMT

Gabim: Created page with 'Category:Information Category:Tutorials == Introduction == "Slackware users typically prefer their method of manual dependency resolution, citing the level of system c...'

[[Category:Information]]
[[Category:Tutorials]]

== Introduction ==

"Slackware users typically prefer their method of manual dependency resolution, citing the level of system control it grants them." - as the [http://wiki.archlinux.org/index.php/Arch_Compared_To_Other_Distros#Arch_vs_Slackware ArchWiki] says. This total control over the system is one of the main strength of the Slackware distribution.

If the administrator of the system knows every package on the system and ensures their every dependencies, then the system is stable, well usable. If the administrator installs a new, (until now) unknown application, then he/she needs to discover its dependencies via the attached README or documentations, or from starting the application (if something is not installed on the system, then the application won't start).

== Dependency resolution at package installation ==

The dependency resolution can be performed at package installation, if we use a third party package manager, see [[Third_Party_Package_Managers]]. This is very easy, but we should use that third party package manager and maybe we don't want to do it just for a simple package installation. We would like a more Slackware like solution.

== Dependency discovery as a separate task ==

We can discover the dependencies of our system in separate task using the '<code>ldd</code>' command. This is not third party application, it is the part of our system.

We can scan the binaries in our PATH:
#!/bin/bash

ECHO=/usr/bin/echo
SED=/usr/bin/sed
FILE=/usr/bin/file
CUT=/usr/bin/cut
LDD=/usr/bin/ldd
GREP=/usr/bin/grep
AWK=/usr/bin/awk

for p in `$ECHO $PATH | $SED 's/:/ /g'`
do
for f in $p/*
do
if [ 'ELF' == `$FILE -b $f | $CUT -d' ' -f1` ]; then
if $LDD $f | $GREP -q 'not found'; then
$ECHO "$f"
$LDD $f | $GREP 'not found' | $AWK '{print "Not found:", $1}'
fi
fi
done
done

Or, we can print the missing package names instead of the missing library names, so we have to install only the given packages mentioned by this script (I used the concatenated MANIFEST file of '<code>slackpkg</code>' on Slackware64, this file list is more friendlier for scripting):
#!/bin/bash
# This is the concatenated MANIFEST file of slackpkg on Slackware64
MANIFEST=/var/lib/slackpkg/slackware64-filelist.gz

# Do not trust in any command in PATH, shell builtins, etc.
ECHO=/usr/bin/echo
PRINTF=/usr/bin/printf
CUT=/usr/bin/cut
SORT=/usr/bin/sort
GREP=/usr/bin/grep
ZGREP=/usr/bin/zgrep
SED=/usr/bin/sed
AWK=/usr/bin/awk
FILE=/usr/bin/file
LDD=/usr/bin/ldd
NULL=/dev/null

# Check all directories in PATH
for directory in `$ECHO $PATH | $SED 's/:/ /g'`
do
# Check all binaries in PATH directories
for binary in $directory/*
do
# If it is true ELF binary
if [ 'ELF' == `$FILE -b $binary | $CUT -d' ' -f1` ]; then
# Show the progress by printing of actual filename on standard error
$PRINTF "%-70s\r" $binary >&2
# Check the missing shared library dependencies
$LDD $binary 2>$NULL | $GREP 'not found' | $AWK '{print $1}' | while read missing_lib
do
# Print the package name of the missing library
$ZGREP $missing_lib $MANIFEST | $AWK '{print $1}'
done
fi
done
# Clear the progress info
$PRINTF "%-80s\r" "" >&2
# Ignore the duplicated package names
done | $SORT -u

If we would like to scan the binaries of the PATH and the shared libraries of our system, then we need a deeper directory discovery:
#!/bin/bash

# This is the concatenated MANIFEST file of slackpkg on Slackware64
MANIFEST=/var/lib/slackpkg/slackware64-filelist.gz

# Do not trust in any command in PATH, shell builtins, etc.
SYSPATH=$PATH
PATH=/bin:/usr/bin:/usr/sbin
ECHO=/usr/bin/echo
PRINTF=/usr/bin/printf

# Check all directories in PATH and ld.so.conf
# If it is true ELF binary
find `$ECHO $SYSPATH | sed 's/:/ /g'` \
`sed 's/$\/.*\/.*$\/.*/\1/' /etc/ld.so.conf | sort -u` \
-perm -100 -a -type f \
-exec sh -c 'filename="{}"; /usr/bin/echo -n "." >&2; \
[ "ELF" = `file -b $filename | cut -d" " -f1` ] && \
ldd $filename 2>/dev/null | fgrep "not found" \
| cut -d" " -f1' \; | while read missing_lib
do
# Print the missing library and its package name
$ECHO $missing_lib ": `zgrep $missing_lib $MANIFEST | cut -d" " -f1`"
done | sort -u

This small script will browse huge amount of directories and will scan a lot of ELF binaries, so it can run for a long time.
There are more effective ways of the dependency discovery, this is only a very simple solution for a natural system administrator need. It demonstrates that a Slackware user does not need a package manager with dependency resolution, but even so can have a stable, well configured system.