SlackWiki - User contributions [en]

Chromium browser

2012-01-24T07:08:45Z

Klickback: /* Automating the Process */ - added -O option to wget; removed the 'Bugs' section

[[Category:Tutorials]]
== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

Keep in mind that Chromium is the '''testing''' branch of the Chrome web browser, and is not recommended for mission-critical systems. Consider using [http://www.google.com/chrome Google Chrome] or [http://www.mozilla.org/en-US/firefox/ Mozilla Firefox] for production systems.

=== Use Case ===

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. It is aimed at users on a personal desktop or laptop, especially on a single-user system.

While the [http://slackbuilds.org slackbuilds.org] project provides excellent quality build scripts for Chromium, downloading 140MB+ source code and doing compilations that often take more than a couple of hours to complete is generally not feasible for people with laptops, slower computers or slow internet connections.

Therefore, this guide aims on how to automate the process of installing and updating Chromium using daily binary builds that are much smaller in size and take up negligible resources for the install and update process, thus helping the user always run the latest and greatest builds without the hassle of downloading and compiling the source code.

== Getting started ==

Chromium depends on <code>GConf</code> and <code>ORBit2</code>, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
<pre>
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
</pre>

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
<pre>
# sbopkg -i 'ORBit2 GConf'
</pre>

Get the <code>google-chrome-pam-solibs</code> package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bit] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
<pre>
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
</pre>

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the <code>INSTALLDIR</code> variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

<pre>
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i686) ARCH=i686 ;;
*) ARCH=$( uname -m ) ;;
esac
fi

if [ "$ARCH" = "i686" ];then
DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
DIRSUFFIX="_x64"
else
echo "The ARCH should be either i686 or x86_64. Exiting."
exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then # Check to see if `chrome-linux.zip` already exists
mv chrome-linux.zip chrome-linux.zip.old # if it does, rename it to chrome-linux.zip.old as backup
fi # in case the current build has problems
wget -O chrome-linux.zip $CHROMEURL
unzip -u -o ./chrome-linux.zip

</pre>

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
<pre>
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
</pre>
Add the following to your crontab :
<pre>
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1> /dev/null
</pre>
This will run the script at 13:20 every day. See <code>man crontab</code> for more on how to customize your cron jobs.

== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]

Chromium browser

2012-01-16T11:05:58Z

Klickback: Added the article 'category'; Added the 'bugs' section

[[Category:Tutorials]]
== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

Keep in mind that Chromium is the '''testing''' branch of the Chrome web browser, and is not recommended for mission-critical systems. Consider using [http://www.google.com/chrome Google Chrome] or [http://www.mozilla.org/en-US/firefox/ Mozilla Firefox] for production systems.

=== Use Case ===

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. It is aimed at users on a personal desktop or laptop, especially on a single-user system.

While the [http://slackbuilds.org slackbuilds.org] project provides excellent quality build scripts for Chromium, downloading 140MB+ source code and doing compilations that often take more than a couple of hours to complete is generally not feasible for people with laptops, slower computers or slow internet connections.

Therefore, this guide aims on how to automate the process of installing and updating Chromium using daily binary builds that are much smaller in size and take up negligible resources for the install and update process, thus helping the user always run the latest and greatest builds without the hassle of downloading and compiling the source code.

== Getting started ==

Chromium depends on <code>GConf</code> and <code>ORBit2</code>, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
<pre>
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
</pre>

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
<pre>
# sbopkg -i 'ORBit2 GConf'
</pre>

Get the <code>google-chrome-pam-solibs</code> package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bit] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
<pre>
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
</pre>

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the <code>INSTALLDIR</code> variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

<pre>
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i686) ARCH=i686 ;;
*) ARCH=$( uname -m ) ;;
esac
fi

if [ "$ARCH" = "i686" ];then
DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
DIRSUFFIX="_x64"
else
echo "The ARCH should be either i686 or x86_64. Exiting."
exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then # Check to see if `chrome-linux.zip` already exists
mv chrome-linux.zip chrome-linux.zip.old # if it does, rename it to chrome-linux.zip.old as backup
fi # in case the current build has problems
wget $CHROMEURL
unzip -u -o ./chrome-linux.zip

</pre>

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
<pre>
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
</pre>
Add the following to your crontab :
<pre>
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1> /dev/null
</pre>
This will run the script at 13:20 every day. See <code>man crontab</code> for more on how to customize your cron jobs.

==== Bugs / Call for help ====
The script has a bug. Sometimes when running the script, the downloaded file is named something like <code>chrome-linux.zip?ir=1&redirect_counter=</code> instead of <code>chrome-linux.zip</code>. This is noticeable in the download process itself. To fix, press <code>Ctrl + c</code> (to cancel the download) and then rerun the script.

Any inputs for fixing this bug are appreciated.

== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]

Chromium browser

2011-09-23T17:18:33Z

Klickback: /* Use Case */

== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

Keep in mind that Chromium is the '''testing''' branch of the Chrome web browser, and is not recommended for mission-critical systems. Consider using [http://www.google.com/chrome Google Chrome] or [http://www.mozilla.org/en-US/firefox/ Mozilla Firefox] for production systems.

=== Use Case ===

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. It is aimed at users on a personal desktop or laptop, especially on a single-user system.

While the [http://slackbuilds.org slackbuilds.org] project provides excellent quality build scripts for Chromium, downloading 140MB+ source code and doing compilations that often take more than a couple of hours to complete is generally not feasible for people with laptops, slower computers or slow internet connections.

Therefore, this guide aims on how to automate the process of installing and updating Chromium using daily binary builds that are much smaller in size and take up negligible resources for the install and update process, thus helping the user always run the latest and greatest builds without the hassle of downloading and compiling the source code.

== Getting started ==

Chromium depends on <code>GConf</code> and <code>ORBit2</code>, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
<pre>
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
</pre>

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
<pre>
# sbopkg -i 'ORBit2 GConf'
</pre>

Get the <code>google-chrome-pam-solibs</code> package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bit] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
<pre>
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
</pre>

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the <code>INSTALLDIR</code> variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

<pre>
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i686) ARCH=i686 ;;
*) ARCH=$( uname -m ) ;;
esac
fi

if [ "$ARCH" = "i686" ];then
DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
DIRSUFFIX="_x64"
else
echo "The ARCH should be either i686 or x86_64. Exiting."
exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then # Check to see if `chrome-linux.zip` already exists
mv chrome-linux.zip chrome-linux.zip.old # if it does, rename it to chrome-linux.zip.old as backup
fi # in case the current build has problems
wget $CHROMEURL
unzip -u -o ./chrome-linux.zip

</pre>

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
<pre>
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
</pre>
Add the following to your crontab :
<pre>
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1> /dev/null
</pre>
This will run the script at 13:20 every day. See <code>man crontab</code> for more on how to customize your cron jobs.

== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]

Chromium browser

2011-09-23T17:16:18Z

Klickback: added use case

== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

Keep in mind that Chromium is the '''testing''' branch of the Chrome web browser, and is not recommended for mission-critical systems. Consider using [http://www.google.com/chrome Google Chrome] or [http://www.mozilla.org/en-US/firefox/ Mozilla Firefox] for production systems.

=== Use Case ===

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. It is aimed at users on a personal desktop or laptop, especially on a single-user system.

While the [http://slackbuilds.org slackbuilds.org] project provides excellent quality build scripts for Chromium, downloading a 140MB+ source code and doing compilations that often take more than a couple of hours to complete is generally not feasible for people with laptops or slower computers. Therefore, this guide aims on how to automate the process of installing and updating Chromium using daily binary builds that are much smaller in size and take up negligible resources for the install and update process; helping the user always run the latest and greatest builds without the hassle of downloading and compiling the source code.

== Getting started ==

Chromium depends on <code>GConf</code> and <code>ORBit2</code>, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
<pre>
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
</pre>

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
<pre>
# sbopkg -i 'ORBit2 GConf'
</pre>

Get the <code>google-chrome-pam-solibs</code> package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bit] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
<pre>
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
</pre>

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the <code>INSTALLDIR</code> variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

<pre>
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i686) ARCH=i686 ;;
*) ARCH=$( uname -m ) ;;
esac
fi

if [ "$ARCH" = "i686" ];then
DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
DIRSUFFIX="_x64"
else
echo "The ARCH should be either i686 or x86_64. Exiting."
exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then # Check to see if `chrome-linux.zip` already exists
mv chrome-linux.zip chrome-linux.zip.old # if it does, rename it to chrome-linux.zip.old as backup
fi # in case the current build has problems
wget $CHROMEURL
unzip -u -o ./chrome-linux.zip

</pre>

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
<pre>
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
</pre>
Add the following to your crontab :
<pre>
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1> /dev/null
</pre>
This will run the script at 13:20 every day. See <code>man crontab</code> for more on how to customize your cron jobs.

== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]

Chromium browser

2011-09-23T16:07:02Z

Klickback:

== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. A single user system is assumed. However, adapting this tutorial for a multi-user system should be simple enough. Also keep in mind that Chromium is the '''testing''' branch of the Chrome web browser, and is not recommended for mission-critical systems. Consider using [http://www.google.com/chrome Google Chrome] or [http://www.mozilla.org/en-US/firefox/ Mozilla Firefox] for production systems.

== Getting started ==

Chromium depends on <code>GConf</code> and <code>ORBit2</code>, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
<pre>
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
</pre>

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
<pre>
# sbopkg -i 'ORBit2 GConf'
</pre>

Get the <code>google-chrome-pam-solibs</code> package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bit] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
<pre>
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
</pre>

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the <code>INSTALLDIR</code> variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

<pre>
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i686) ARCH=i686 ;;
*) ARCH=$( uname -m ) ;;
esac
fi

if [ "$ARCH" = "i686" ];then
DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
DIRSUFFIX="_x64"
else
echo "The ARCH should be either i686 or x86_64. Exiting."
exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then # Check to see if `chrome-linux.zip` already exists
mv chrome-linux.zip chrome-linux.zip.old # if it does, rename it to chrome-linux.zip.old as backup
fi # in case the current build has problems
wget $CHROMEURL
unzip -u -o ./chrome-linux.zip

</pre>

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
<pre>
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
</pre>
Add the following to your crontab :
<pre>
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1> /dev/null
</pre>
This will run the script at 13:20 every day. See <code>man crontab</code> for more on how to customize your cron jobs.

== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]

Chromium browser

2011-09-23T15:54:53Z

Klickback: Created page with "== Introduction == Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Bro..."

== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. A single user system is assumed, however, modifying it for a multi-user system should be simple enough.

== Getting started ==

Chromium depends on <code>GConf</code> and <code>ORBit2</code>, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
<pre>
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
</pre>

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
<pre>
# sbopkg -i 'ORBit2 GConf'
</pre>

Get the <code>google-chrome-pam-solibs</code> package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bi] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
<pre>
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
</pre>

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the <code>INSTALLDIR</code> variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

<pre>
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i686) ARCH=i686 ;;
*) ARCH=$( uname -m ) ;;
esac
fi

if [ "$ARCH" = "i686" ];then
DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
DIRSUFFIX="_x64"
else
echo "The ARCH should be either i686 or x86_64. Exiting."
exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then # Check to see if `chrome-linux.zip` already exists
mv chrome-linux.zip chrome-linux.zip.old # if it does, rename it to chrome-linux.zip.old as backup
fi # in case the current build has problems
wget $CHROMEURL
unzip -u -o ./chrome-linux.zip

</pre>

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
<pre>
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
</pre>
Add the following to your crontab :
<pre>
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1> /dev/null
</pre>
This will run the script at 13:20 every day. See <code>man crontab</code> for more on how to customize your cron jobs.

== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]

Broadcom Wireless

2011-09-09T14:50:09Z

Klickback: Added sbopkg instructions

[[Category:Tutorials]]
== Introduction ==

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

== Prerequisites ==

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

== Getting Started ==

The first thing is to check if the user is part of the ''netdev'' group :

<pre>groups</pre>

If the output does not contain <code>netdev</code>, then as <code>root</code>, enter the following command :

<pre>usermod -a -G netdev username</pre>

where <code>username</code> is the name of your user account.

== Installing the driver ==

=== Sbopkg method ===
If a working internet connection is available on the laptop (say a wired connection), use [http://sbopkg.org sbopkg] to install the drivers :
<pre>sbopkg -i broadcom-sta</pre>

=== Manual method ===
Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

== Blacklisting the b43 and ssb modules ==

The Broadcom's <code>wl</code> driver conflicts with the kernel's <code>b43</code> driver, so open up the <code>/etc/modprobe.d/blacklist.conf</code> using the text editor of your choice as <code>root</code> and add the following lines to it :

<pre>
blacklist ssb
blacklist b43
</pre>

== Final steps ==

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the <code>iwconfig</code> command. you should see an output like this :

<pre>
$ iwconfig
lo no wireless extensions.

eth1 IEEE 802.11 Nickname:"lapto"
Access Point: Not-Associated
Link Quality:5 Signal level:217 Noise level:199
Rx invalid nwid:0 invalid crypt:31 invalid misc:0

eth0 no wireless extensions.
</pre>

This output suggests that the drivers installed right and your wireless card is recognized as <code>eth1</code> by the kernel. Hooray!

You can now either use the <code>iwconfig</code> tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

== Installing Wicd ==

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If a working internet connection is available on the laptop (say a wired connection), simply use <code>slackpkg</code> to install wicd :
<pre>slackpkg install wicd</pre>

=== Using package tarball ===

Download the <code>Wicd</code> package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using <code>installpkg</code>. For example, on a 32-bit system, as root :
<pre>
wget http://slackware.osuosl.org/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
installpkg ./wicd-1.7.0-i486-2.txz
</pre>

== Wicd usage ==
Start the Wicd daemon :

<pre>
/etc/rc.d/rc.wicd start
</pre>

Once its started, run <code>wicd-client</code> and configure the network to your liking.

=== Caveat ===
Wicd by default treats <code>wlan0</code> as the default wireless interface. Since the interface is <code>eth1</code> in our case, you might want to correct this in Wicd's Preferences.

Links

2011-09-09T12:32:09Z

Klickback: Added new links, Improved formatting, and removed obsolete links

[[Category:Information]]

==Slackware Links==
* http://www.slackware.com - the home of Slackware
* [http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ Slackware FAQ by] [[User:juhl|juhl]] (Jesper Juhl)
* [http://www.nielshorn.net/slackware/slack_versions.php A complete overview of all Slackware versions] by Niels Horn
* [http://www.slackbook.org Updated version of the slackware book]
* [http://www.slackware.com/getslack Extensive listing of Slackware mirrors]
* [http://www.linuxquestions.org/questions/slackware-14/ Slackware forum] on LinuxQuestions.org
* [http://slackbuilds.org/ slackbuilds.org - Build scripts for additional software]
* [http://sbopkg.org sbopkg.org] - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository
* [http://gitorious.org/sbopkg-slackware-queues Build queues for all Slackware packages from SlackBuilds.org]
* [http://slackworld.berlios.de/ The Slack World page on berlios]
* [http://slacky.eu European Slackware community]
* [http://slackware.linux.or.id Indonesian Slackware Community] - by [[User:Willysr|Willysr]]
* [http://open-eslack.org/ Spanish Slackware community]
* [http://www.slack-world.com Iranian Slackware Community]
* http://jtgzmanager.sf.net/ A new frontend to pkgtools built with Qt4 C++ libs - by Alexandre Arnt
* http://slackbot.sourceforge.net - Buildsystem and buildtools for Slackware
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.

==Free packages==
* [http://connie.slackware.com/~alien/slackbuilds/ Eric Hameleers' packages] [http://slackware.org.uk/people/alien/slackbuilds/ mirror]
* [http://rlworkman.net/pkgs/ rworkman's packages] [http://slackware.org.uk/people/rlworkman/ mirror]
* [http://www.nielshorn.net/slackware/slack_pkg.php Niels Horn's packages]
* http://www.linuxpackages.net/
* [http://repository.slacky.eu/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware

==SlackBuild Repositories==
* [http://slackbuilds.org The SlackBuilds.org Project]
* [http://www.slackware.com/~alien/slackbuilds/ Eric "Alien" Hameleer's SlackBuilds]
* [http://slackware.org.uk/people/rlworkman/sources/ rworkman's SlackBuilds]

==Live CD's based on Slackware==
* [http://porteus.org/ Porteus] - A fast, portable and modular live CD/USB, originally started as a community remix of Slax
* [http://www.imagineos.com.br/ ImagineOS] (formerly GoblinX)
* [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://alien.slackbook.org/ Alien Bob's Wiki]
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://open-eslack.org/wiki/ A Spanish 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 stable and current

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

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

Broadcom Wireless

2011-09-09T11:27:27Z

Klickback: Fixed formatting

[[Category:Tutorials]]
== Introduction ==

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

== Prerequisites ==

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

== Getting Started ==

The first thing is to check if the user is part of the ''netdev'' group :

<pre>groups</pre>

If the output does not contain <code>netdev</code>, then as <code>root</code>, enter the following command :

<pre>usermod -a -G netdev username</pre>

where <code>username</code> is the name of your user account.

== Installing the driver ==

Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

== Blacklisting the b43 and ssb modules ==

The Broadcom's <code>wl</code> driver conflicts with the kernel's <code>b43</code> driver, so open up the <code>/etc/modprobe.d/blacklist.conf</code> using the text editor of your choice as <code>root</code> and add the following lines to it :

<pre>
blacklist ssb
blacklist b43
</pre>

== Final steps ==

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the <code>iwconfig</code> command. you should see an output like this :

<pre>
$ iwconfig
lo no wireless extensions.

eth1 IEEE 802.11 Nickname:"lapto"
Access Point: Not-Associated
Link Quality:5 Signal level:217 Noise level:199
Rx invalid nwid:0 invalid crypt:31 invalid misc:0

eth0 no wireless extensions.
</pre>

This output suggests that the drivers installed right and your wireless card is recognized as <code>eth1</code> by the kernel. Hooray!

You can now either use the <code>iwconfig</code> tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

== Installing Wicd ==

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If you already have a working internet connection on the laptop (say a wired connection), simply use <code>slackpkg</code> to install wicd :
<pre>slackpkg install wicd</pre>

=== Using package tarball ===

Download the <code>Wicd</code> package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using <code>installpkg</code>. For example, on a 32-bit system, as root :
<pre>
wget http://slackware.osuosl.org/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
installpkg ./wicd-1.7.0-i486-2.txz
</pre>

== Wicd usage ==
Start the Wicd daemon :

<pre>
/etc/rc.d/rc.wicd start
</pre>

Once its started, run <code>wicd-client</code> and configure the network to your liking.

=== Caveat ===
Wicd by default treats <code>wlan0</code> as the default wireless interface. Since the interface is <code>eth1</code> in our case, you might want to correct this in Wicd's Preferences.

Broadcom Wireless

2011-09-09T11:26:49Z

Klickback:

[[Category:Tutorials]]
= Introduction =

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

== Prerequisites ==

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

== Getting Started ==

The first thing is to check if the user is part of the ''netdev'' group :

<pre>groups</pre>

If the output does not contain <code>netdev</code>, then as <code>root</code>, enter the following command :

<pre>usermod -a -G netdev username</pre>

where <code>username</code> is the name of your user account.

== Installing the driver ==

Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

== Blacklisting the b43 and ssb modules ==

The Broadcom's <code>wl</code> driver conflicts with the kernel's <code>b43</code> driver, so open up the <code>/etc/modprobe.d/blacklist.conf</code> using the text editor of your choice as <code>root</code> and add the following lines to it :

<pre>
blacklist ssb
blacklist b43
</pre>

== Final steps ==

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the <code>iwconfig</code> command. you should see an output like this :

<pre>
$ iwconfig
lo no wireless extensions.

eth1 IEEE 802.11 Nickname:"lapto"
Access Point: Not-Associated
Link Quality:5 Signal level:217 Noise level:199
Rx invalid nwid:0 invalid crypt:31 invalid misc:0

eth0 no wireless extensions.
</pre>

This output suggests that the drivers installed right and your wireless card is recognized as <code>eth1</code> by the kernel. Hooray!

You can now either use the <code>iwconfig</code> tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

== Installing Wicd ==

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If you already have a working internet connection on the laptop (say a wired connection), simply use <code>slackpkg</code> to install wicd :
<pre>slackpkg install wicd</pre>

=== Using package tarball ===

Download the <code>Wicd</code> package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using <code>installpkg</code>. For example, on a 32-bit system, as root :
<pre>
wget http://slackware.osuosl.org/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
installpkg ./wicd-1.7.0-i486-2.txz
</pre>

== Wicd usage ==
Start the Wicd daemon :

<pre>
/etc/rc.d/rc.wicd start
</pre>

Once its started, run <code>wicd-client</code> and configure the network to your liking.

=== Caveat ===
Wicd by default treats <code>wlan0</code> as the default wireless interface. Since the interface is <code>eth1</code> in our case, you might want to correct this in Wicd's Preferences.

User:Klickback

2011-09-09T11:17:24Z

Klickback: User page

User klickback on ##slackware at freenode

Broadcom Wireless

2011-09-09T11:14:47Z

Klickback: A HowTo for installing and configuring Broadcom wireless cards on Slackware

[[Category:Tutorials]]
= Introduction =

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

= Prerequisites =

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

= Getting Started =

The first thing is to check if the user is part of the ''netdev'' group :

<pre>groups</pre>

If the output does not contain <code>netdev</code>, then as <code>root</code>, enter the following command :

<pre>usermod -a -G netdev username</pre>

where <code>username</code> is the name of your user account.

= Installing the driver =

Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

= Blacklisting the b43 and ssb modules =

The Broadcom's <code>wl</code> driver conflicts with the kernel's <code>b43</code> driver, so open up the <code>/etc/modprobe.d/blacklist.conf</code> using the text editor of your choice as <code>root</code> and add the following lines to it :

<pre>
blacklist ssb
blacklist b43
</pre>

= Final steps =

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the <code>iwconfig</code> command. you should see an output like this :

<pre>
$ iwconfig
lo no wireless extensions.

eth1 IEEE 802.11 Nickname:"lapto"
Access Point: Not-Associated
Link Quality:5 Signal level:217 Noise level:199
Rx invalid nwid:0 invalid crypt:31 invalid misc:0

eth0 no wireless extensions.
</pre>

This output suggests that the drivers installed right and your wireless card is recognized as <code>eth1</code> by the kernel. Hooray!

You can now either use the <code>iwconfig</code> tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

= Installing Wicd =

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If you already have a working internet connection on the laptop (say a wired connection), simply use <code>slackpkg</code> to install wicd :
<pre>slackpkg install wicd</pre>

=== Using package tarball ===

Download the <code>Wicd</code> package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using <code>installpkg</code>. For example, on a 32-bit system, as root :
<pre>
wget http://slackware.osuosl.org/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
installpkg ./wicd-1.7.0-i486-2.txz
</pre>

= Wicd usage =
Start the Wicd daemon :

<pre>
/etc/rc.d/rc.wicd start
</pre>

Once its started, run <code>wicd-client</code> and configure the network to your liking.

=== Caveat ===
Wicd by default treats <code>wlan0</code> as the default wireless interface. Since the interface is <code>eth1</code> in our case, you might want to correct this in Wicd's Preferences.