Tag Archive : slackware

/ slackware

If you are a students / lecturer / alumnus of Cisco Networking Academy, you can use Packet Tracer for experiment with network especially using Cisco devices. Alternatively we can use dynamips to simulates network. In this article we will discuss about how to install Dynamips and Dynagen to emulates Cisco’s devices on Slackware.

In this article, I use:

  1. Slackware64 14.0 with multilib support.
  2. Dynamips 0.2.8 RC3 for linux
  3. Dynagen

Multilib support is not a must as there are two version of dynamips for Linux, 32-bit and 64-bit.

Dynamips and Dynagen Overview

Dynamips is a software that emulates Cisco IOS on a traditional PC (means our everyday machine). This project started by Christophe Fillot. Initially it emulates Cisco 7200 device and now supports Cisco 3600 series (3620, 3640, and 3660), 2700 series (3725, 2745) and 2600 series (2610 to 2650XM, 2691).

Cristophe Fillot states that this project goals are:

  1. Obtain the Materialsto be used as a training platform, which software used in real world. Allow people to become more familiar with Cisco devices.
  2. Test and experiment the numerous and powerful features of Cisco IOS.
  3. Check quickly configurations to be deployed later on real routers

Note that, this is just an emulator, which can’t replace real router. You can read more from his site on http://www.ipflow.utc.fr/index.php/Cisco_7200_Simulator.

Dynagen is a text-based front end for Dynamips, which use the “Hypervisor” mode for communication with Dynamips. Dynagen is no longer officially maintained, however Dynagen is still updated and developed for used on GNS3.

Dynagen can run on any platform which supports Python.

Obtain the Materials

Now download the materials. The Dynamips and Dynagen we used are provided by GNS3 (http://www.gns3.net)

If you use Slackware 32-bit, you can download Dynamips 0.2.8-RC3-community for Linux 32-bit. If you use Slackware64, you can download Dynamips 0.2.8-RC3-community for Linux 64-bit. If you use multilib support, you can choose either 32-bit or 64-bit, but I recommended you to use the 64-bit one.

Next, download the source for dynagen. The one we use is dynagen-0.11.0tar.gz. You can obtain it on Sourceforge which located here.

If you have not installed libpcap before, you need to download and install it first.

Installation

Create a new directory /opt/dynamips. The dynamips will be installed to /opt/dynamips and dynagen will be installed to /opt/dynagen (will be created later) respectively.

Now go to /opt.dynamips. Create bin and images directories. Move your dynamips-0.2.8-RC3-community-x86_64.bin (or dynamips-0.2.8-RC3-community-x86.bin) to /opt.dynamips/bin.

Next, copy your dynagen file to /opt. Extract it with the following command:

tar -xf dynagen-0.11.0.tar.gz dynamips-0.2.8-RC3-community-x86_64.bin

You should have a new directory dynagen-0.11.0. Now rename it to dynagen. Thus you now have /opt/dynagen. Then creat a new directory /opt/dynagen/labs.

Remember that you need libpcap if you haven’t install it.

Preparing Cisco IOS Images

Dynamips emulates Cisco devices. Technically speakin, it is running real Cisco IOS images. Thus, to have dynamips run properly (maybe the right word is: to be able to run dynamips), you need to provide Cisco IOS. They can be obtained by dumping the real machines, if you have. Another way is used the images provided by other people. Unfortunately, neither I or dynamips official can not provide you with the images. And yes, you should find it by yourself.

The images supported by dynamips (by current version) are (at least what I have):

  1. 7200
  2. 4000 series
  3. 4500 series
  4. 3600 series (3620, 3640, and 3660)
  5. 2900 series (
  6. 2700 series (3725, 2745)
  7. 2600 series (2610 to 2650XM, 2691)
  8. 1600 series
  9. 1000 series

Place the images on /opt/dynamips/images/.

The Cisco images are compressed. This compressed images will work just fine with Dynamisp, however the boot process is slowed significantly with decompression process. It is recommended to decompress the images beforehand so the emulator doesn’t have to. Do the following if you want:

unzip -p "images file.bin" > "images file.image"

Yes you can substitute with your images filename. Note that for some images, you must uncompressed it first to work with Dynamips.

Usage

Using dynamips and dynagen, we are working with virtual lab. The configuration of all routers, switch, and interconnections that make up the virtual lab are stored on a single “network file”. This file is simply an INI file-like.

Lets start up with a simple virtual lab. Create a new directory /opt/dynagen/labs/simple. Next, create a new file simple1.net write following to it.

# Simple lab
[localhost]
[[7200]]
image = /opt/dynamips/images/c7200-jk9s-mz.124-13b.bin
npe = npe-400
ram = 160
[[ROUTER R1]]
s1/0 = R2 s1/0
[[router R2]]
# Nothing to do

We create a simple net with two routers, R1 and R2. The network is running on localhost, the same machine which run Dynagen. In this network we register a cisco device, router 7200 and specify the images as /opt/dynamips/images/c7200-jk9s-mz.124-13b.bin.  For each instance of 7200 will use an NPE-400 and use 160MB of RAM resource.

Now the topology. R1 has a serial port name S1/0 which is connected to R2’s port of S1/0.  This connection is virtual connection. Dynagen will automatically install a PA-8T adapter in Port 1 on both R1 and R2. On R2, we can omit the adapter as the adapter has been specified before.

In order to run this virtual lab, first start up the dynamips server. Invoke following command:

dynamips -H 7200 &

The 7200 is not the Cisco device, but a port dynamips listening to. Next, load the configuration file to dynagen:

dynagen /opt/dynagen/labs/simple1.net

And there you should see the Cisco IOS is running 😀

Installing Packet Tracer for Slackware

December 5, 2015 | Article | No Comments

Packet Tracer, a wonderful tool for experiment with network, especially for Cisco based device. If you have read previous article about netkit, you will notice that we can only simulate network using linux devices. In this article we will discuss about installation of Packet Tracer Slackware.

In this article I use:

  1. Slackware64 14.0 with multilib enable. Note that for 64-bit, multilib is a must.
  2. Packet Tracer 5.3

Why Packet Tracer?

If you aim for taking Cisco Certified Network certification (either CCNA, CCNP, CCIE, etc), you are strongly need this. Taking Cisco certification required deep understanding of Cisco’s devices as well as networking. Packet Tracer is designed by Cisco to make students learn Cisco’s devices easily.

Another thing I want to emphasize is that Packet Tracer is officially made by Cisco itself. Included with it are some sample projects you can look with various networking scheme, such as simple network with switch, router, etc; A simple VoIP network; network for IP telephone; and much more.

In short, PacketTracer offers following features:

  • Design a physical network
  • Focus on Cisco’s devices.
  • Complete connectivity simulations: perform ping, traceroute, etc.
  • Compatible with HTTP, TCP/IP, Telnet, SSH, TFTP, DHCP and DNS.
  • Rich Cisco device, from analog device (such as analog TV, splitter, etc), to digital device (such as switch, router, PC, etc)
  • Less memory consumption

Acquiring the Materials

Unfortunately, Cisco doesn’t distribute Packet Tracer freely. You must become students, lecturer, or alumnus of Cisco Networking Academy to obtain this tool. In this article, we will only discussing how to install it on Slackware. Therefore, I can’t provide you with some materials. And don’t ask me to provide it, please.

Fortunately, you can search on google. There are many kind people out there provide you with Packet Tracer. Again. I myself search the net to obtain it. The one I use here is Packet Tracer 5.3.3.

You can convert either .deb (package for debian/ubuntu) files or .rpm (for fedore/redhat) files to .tgz using tools such as deb2tgz and rpm2tgz and install it automatically. It is so easy that you can do it by yourself, so we will discuss the more complex one, install from the installer, .bin file. I use PacketTracer533_i386_installer-rpm.bin which include tutorials.

Installation

Now open terminal and go to where you download the file (in this case PacketTracer533_i386_installer-rpm.bin). Our goal now is extracting the package from the installer and later create Slackware package for it.

Now run the installer or initialize setup. You should become root and make sure the installer is executable. Once you run the binary installer file, the content of the “PacketTracer533_i386_installer-rpm.bin” will be extraceted to /tmp folder.

Now view the EULA (End User License Agreement), there you will be asked to press the ENTER key. Don’t do this. Instead, go to /tmp and press CTRL + C combination key to abort the installation. Yes, I’m being serious.

Now go to /tmp/selfextract.XXXXXX folder where XXXXXX is the random string assigned by computer. There should be one. If there are more than one similar directories, you should check any of directories which has Fedore RPM packages. It should not be difficult.

Now go to that directory and convert the .rpm package to .tgz package. Use following command:

rpm2tgz PacketTracer-5.3_3-u.i386.rpm

Then install the converted .tgz file by installpkg tool.

installpkg PacketTracer-5.3_3-u.i386.tgz

The Packet Tracer now should be installed on /usr/local/PacketTracer5 directory. Now, create a symbolic link of Cisco Packet Tracer to /usr/bin directory.

Now, we need to add executable symbolic link of Cisco Packet Tracer to /usr/bin directory to be able to start program from command line interface shortly by packettracer command.

ln -s /usr/local/PacketTracer5/packettracer /usr/bin/packettracer

You can now test whether Packet Tracer is installed completely by invoking packettracer command. Here is the screenshot

pt

What if you want to do some experiment for networking but you don’t have enough resource for it? Not enough PC / switch / router, or maybe don’t have any? You could use Virtual Machine such as VirtualBox and QEMU to emulates hardware. But as you can see, it is painfully and consume lot of resource such as memory and CPU utilization. What if you want to emulates dozens or event hundreds machines? See the point?

So what is the cheapest way to do so? Netkit can answer that. In this article we will installing Netkit to do emulation on Linux (and only linux). In this article I use:

  1. Slackware64 14.0 multilib. If you have Slackware64, you need to enable multilib. Using Slackware 32-bit can proceed.
  2. Netkit version 2.8
  3. Netkit Filesystem
  4. Netkit kernel

The netkit can be downloaded from their official site, here.

What is Netkit

So what is Netkit?

Netkit is an environment for setting up and performing networking experiments at low cost and with little effort. Low cost means you don’t need to setup many computers nor consume many resources on your workstations. It allows to “create” several virtual network devices (full-fledged routers, switches, computers, etc.) that can be easily interconnected in order to form a network on a single PC. Networking equipments are virtual but feature many of the characteristics of the real ones, including the configuration interface.

Emulating a network with Netkit is a matter of writing a simple file describing the link-level topology of the network to be emulated and some configuration files that are identical to those used by real world networking tools. Netkit then takes care of starting (emulated) network devices and of interconnecting them as required. Alternatively, networks can be described by using an XML-based language known as NetML. Starting from a network description in NetML, it is possible to automatically obtain configuration files which can be used with real routers, or Netkit scripts which can be used to emulate the described network.

Unlike Virtual Machine, Netkit use Linux Kernel to emulate device. Therefore, only Linux machine is supported. Netkit exploits open source software and heavily based on the User Mode Linux (UML) variant of the Linux kernel.

Obtaining the Materials

Now, let’s download the required materials. Netkit is composed of three components: the main system, the kernel, and the filesystem. We will download it separately. Again, you can download all of them here.

The main system is the core or the main engine for netkit. The one we use here is Netkit version 2.8 which can be downloaded here.

The filesystem is the “storage” or filesystem used by any of netkit machine. The one we use can be downloaded here.

Last one is the kernel. The kernel is a user process application which emulates linux system. The one we use can be downloaded here.

Install them

In this article we will use /opt directory as the root for installation. Now copy all files we have downloaded to /opt. Use these commands to extract them.

tar -jxf netkit-*

You should notice that we have new directory named netkit. Inside it, you will get some directory such as bin, fs, kernel, check_configuration.d. Netkit doesn’t need to be installed. Thus you can use them directly (but need to be configured, will be described on next section).

Setting the Environment Variable

Before using, we need to set the environment. You need to set following environment variable on your shell. You can set them by using export. These commands must be used on your shell.

export NETKIT_HOME=/opt/netkit
export PATH="${PATH}:${NETKIT_HOME}/bin"
export MANPATH="${MANPATH}:${NETKIT_HOME}/man"

It might be simple, but it will be painful if you want to use netkit on multiple shell, or use netkit multiple times as you need to type them everytime you want to use netkit. The smart way would be save it to some file that will be read by your shell everytime you open terminal. In this case we use bash, and we need to set the configuration locally. Thus we need to modify our .bashrc file. Edit your ~/.bashrc and add following lines.

export NETKIT_HOME=/opt/netkit
export PATH="${PATH}:${NETKIT_HOME}/bin"
export MANPATH="${MANPATH}:${NETKIT_HOME}/man"

When you are done, proceed to next stage.

Checking Configuration

Although I have stated that we can use netkit directly, but we need to check whether netkit can be run or not. At least you have to finish previous stage (setting the environment variables) before proceeding.

Now, open your terminal and go to /opt/netkit. Then invoke following command:

./check_configuration.sh

You should have no problem and will receive message like this:

>  Checking path correctness... passed.
>  Checking environment... passed.
>  Checking for availability of man pages... passed.
>  Checking for proper directories in the PATH... passed.
>  Checking for availability of auxiliary tools:
awk          : ok
basename     : ok
date         : ok
dirname      : ok
find         : ok
getopt       : ok
grep         : ok
head         : ok
id           : ok
kill         : ok
ls           : ok
lsof         : ok
ps           : ok
readlink     : ok
wc           : ok
port-helper  : ok
tunctl       : ok
uml_mconsole : ok
uml_switch   : ok
passed.
>  Checking for availability of terminal emulator applications:
xterm          : found
konsole        : found
gnome-terminal : not found
passed.
>  Checking filesystem type... passed.
>  Checking whether 32-bit executables can run... passed.

[ READY ] Congratulations! Your Netkit setup is now complete!
Enjoy Netkit!

If you don’t get congratulations, you should recheck your installation again. Either way, congratulation! You have installed netkit.

Slackware on Slackware using QEMU

December 5, 2015 | Article | 2 Comments

After successfully install QEMU-KVM on Slackware64 (previous article) and running a Debian for ARM on QEMU article, we will try something more.

In this article, we will discuss about installing Slackware for ARM using QEMU on Slackware64 (Slakwareception?). On this article we will use:

  1. Slackware64 14.0 (as host)
  2. QEMU 14.0 as discussed on this article
  3. Slackware for ARM (as guest)

Obtaining the Materials

If you have not installed QEMU, I suggest you to install it first following this article.

Create a working directory, for example (adjust with yours):

mkdir -p /home/xathrya/SlackARM
cd /home/xathrya/SlackARM

Then we need to download the kernel:

cd /home/xathrya/SlackwareARM
mkdir -p kernels/versatile
cd kernels/versatile
wget -c "ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.0/kernels/versatile/zImage-versatile"

Verify that you have finish download it. Then we will download the initial ramdisk for it, by:

cd /home/xathrya/SlackwareARM
mkdir -p isolinux
cd isolinux
wget -c "ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.0/isolinux/initrd-versatile.img"

Now we will create storage will be sued for our Slackware. Do it by:

cd /home/xathrya/SlackwareARM
mkdir hdd; cd hdd
qemu-img create hdd/arm.qcow 2G

A 2GB is sufficient for our experiments. Then downloads following packages from here . For simplicity, We only need a packages and l packages. But firstly, fo this command:

mkdir -p /home/xathrya/SlackwareARM/slackware
cd /home/xathrya/SlackwareARM/slackware
mkdir a l

Then download these package. The packages on a packages must be downloaded to a directory, while l package must be downloaded to l directory. The list of packages:

“a” packages

  1. aaa_base-14.0-arm-4.tgz
  2. aaa_elflibs-14.0-arm-2.tgz
  3. aaa_terminfo-5.8-arm-1.tgz
  4. bash-4.2.037-arm-1.tgz
  5. bin-11.1-arm-2.tgz
  6. coreutils-8.19-arm-1.tgz
  7. e2fsprogs-1.42.6-arm-1.tgz
  8. etc-14.0-arm-1.tgz
  9. kernel-modules-versatile-3.4.11_versatile-arm-1.tgz
  10. kernel_versatile-3.4.11-arm-1.tgz
  11. pkgtools-14.0-noarch-2.tgz
  12. shadow-4.1.4.3-arm-6.tgz
  13. sysvinit-2.88dsf-arm-2.tgz
  14. sysvinit-functions-8.53-arm-1.tgz
  15. sysvinit-scripts-2.0-noarch-9.tgz
  16. util-linux-2.21.2-arm-3.tgz

“l” packages

  1. glibc-2.15-arm-8.tgz

Then make iso files on /home/xathrya/SlackwareARM (adjust with your path) with content of isolinux, kernels, and slackware. You can do following command:

cd /home/xathrya/SlackwareARM
mkisofs -udf -o /home/xathrya/slackware-arm-14.0.iso -R -J \
-V "Slackware ARM 14.0" -hide-rr-moved -v -d -N -A "Slackware ARM 14.0" .

Notice the dot “.” on the last sentence as part of command. It will create an iso file slackware-arm-14.0.iso on /home/xathrya/.

Running the System

With initrd, kernel, and ISO file, we march to last step which is running the system (and also install it). Do the followings:

cd /home/xathrya/Slackware/ARM
qemu-system-arm -M versatilepb -kernel kernels/versatile/zImage-versatile \
-initrd isolinux/initrd-versatile.img hdd/arm.qcow \
-cdrom /home/xathrya/slackware-arm-14.0.iso

Some error messages might occurred such as

/bin/grep: No such file or directory

But don’t worry, if you follow this article you can able to install Slackware using QEMU.

Emulation with QEMU

December 5, 2015 | Article | 1 Comment

On previous article, we have discuss about how to install QEMU-KVM on Slackware64 and Windows. In this article we will discuss about Virtualization and Emulation using QEMU.

QEMU – Overview

QEMU is an emulator and vitualization tool like VMware, KVM, VirtualBox, and Xen did. It emulates hardware, but with more options available. QEMU is available to emulates some hardware architectures, including embedded system. Processor architecture supported by QEMU are: x86, ARM, MIPS, etc.

QEMU is cross platform, available for many Operating System such including Linux, Microsoft Windows, and any Unix-like as its host operating system.

How it work

QEMU is like any virtualization tools, dividing resource for native OS (the host) and virtual machine (guest). It support virtualization with Xen Hypervisor or Linux KVM modules. With KVM, QEMU can emulate x86, server and embedded PowerPC, and also S390.

As result of resource division, there will be a decreasing in performance both on host and guest system. However, QEMU use dynamic translation to translate machine code of guest to host which makes the performance good enough.

Operating Mode

QEMU has two operating mode, which are:

  1. User Mode Emulation – QEMU can emulate own Linux process which is compiled to a CPU on different CPU.
  2. Full System Emulation – QEMU emulate whole system, including every resource (suh as processor and peripheral). This mode is useful to do some debugging and code testing on virtual machine. Using QEMU we can run some virtual machines simultaneously on a host (of course we should measure the resource needed).

Installation

The installation can be done easily. You can install QEMU by following this article for Linux and this article for Windows.

Running Kernel Image

You can read this article to run a simple Debian for ARM distribution.

Playing with Arguments

Following are arguments that can be used for running a system.

Function Command Notes
 Specifying amount of RAM  -m x  X is the amount of RAM in MB
 Use initial ramdisk  -initrd PATHANDFILENAME
 Add additional disks  -hdb DISK2 -hdc DISK3 -hdd DISK4
 Add cdrom drive  -cdrom FILE  FILE can be ISO or /dev/cdrom on UNIX
 Disable graphic  -nographic  Useful for emulate a headless raspi or to route the output directly to terminal
 Make QEMU exits when the system reboot  -no-reboot
 Pass argument to kernel  -append “KERNEL OPTIONS”  the kernel OPTIONS will be discussed on next section.

Kernel Options

Following are arguments that can be passed to kernel (the one QEMU boot).

Function Command Notes
 Specify what partition of disk will be the root partition  root=DEVICE
 Specify what file to run after kernel is loaded  init=FILE
 Prevent QEMU from simply freeze when the kernel is panic  panic=x  x is the number of seconds before rebooting. Usefule with the -no-reboot option
 Specify default console device for the output.  console=DEVICE

Disk Operation

In this section we will discuss about creating a disk image for QEMU. It is recommended to use Linux. The general syntax for creating a disk is:

qemu-img create <FILENAME> <SIZE>

Where <FILENAME> is filename and path if you don’t want to create the image on current directory. The size is written in numerical value followed by size unit in:

  • k or K for Kilobyte (1024 byte)
  • m or M for Megabyte (1025 kb)
  • g or G for Gygabyte (1024m mb)

The created file contain 0 (zero) and mean nothing to system.

To format a disk, we can use UNIX & Linux utility:

  • EXT2 => mkfs.ext2 <FILENAME>
  • EXT3 => mkfs.ext3 <FILENAME>
  • etc

We can also mounting <FILENAME> to modify it.

Running Kernel Image and RootFS on QEMU

December 5, 2015 | Article | No Comments

On previous article, we have discussed about QEMU installation on Slackware64. In this article we will discuss about how to test QEMU-KVM to run kernel image and rootfs, specifically for ARM embedded system.

In this article, I use:

  1. Slackware64 14.0
  2. Debian ARM

Our goal is to demonstrate QEMU for running kernel image and a rootfs. In specific, we will try to run a Debian installer.

Acquiring the Required Package

As stated before, we will use Debian for ARM. There are two files we need to obtain: the kernel and the initrd.gz. You can download them by using this command:

export SITE=ftp://ftp.debian.org/debian/dists/wheezy/main/installer-armel/current/images/versatile/netboot
wget ${SITE}/vmlinuz-3.2.0-4-versatile
wget ${SITE}/initrd.gz

You may create a directory if you want to keep all the files grouped.

Creating Raw Virtual Hard Disk

Next is creating raw virtual hard disk. At least we need 2GB for storage / image. For that purpose we can create image by:

qemu-img create -f raw hda.img 2G

The -f is for specifying what format of virtual hard drive, which is raw in this case.

Running Virtual Machine with QEMU

Now, the final step. We will running the virtual machine. To do that, invoke this command:

qemu-system-arm -m 256 -M versatilepb -kernel vmlinuz-3.2.0-4-versatile \
-initrd initrd.gz -hda hda.img -append

The command is actually self-explaining. We run machine and gives it 256MB RAM with kernel vmlinuz-3.2.0-4-versatile and initial ramdisk initrd.img, as downloaded.

Now, have fun 😀

On previous article, we have discuss about how to install OpenCV using git and cmake to out Slackware64 14.0 machine. Now on this article we will see how we can use OpenCV with gcc and CMake to build a computer vision application.

On this article we will use:

  1. Slackware64 14.0 (Any Linux is fine)
  2. gcc
  3. CMake
  4. OpenCV

Of course I assume you have successfully install OpenCV. If not, please refer to this. Using CMake gives us advantages such as:

  1. No need to change anything when porting between Linux and Windows
  2. Can be easily combined with other tools by CMake such as Qt, ITK, and VTK.

If you are new to CMake you can visit their website and read their tutorial.

Create An OpenCV Program

Let’s create a simple program. Write a new C++ source file and name it as DisplayImage.cpp:

#include <cv.h>
#include <highgui.h>
using namespace cv;

int main( int argc, char** argv ) {
  Mat image;
  image = imread( argv[1], 1 );
  if( argc != 2 || !image.data ) {
     printf( "No image data \n" );
     return -1;
}

namedWindow( "Display Image", CV_WINDOW_AUTOSIZE );
imshow( "Display Image", image );
waitKey(0);
return 0;
}

 

Create a CMake file

Next create the CMakeLists.txt file which has following text:

project( DisplayImage )
find_package( OpenCV REQUIRED )
add_executable( DisplayImage DisplayImage )
target_link_libraries( DisplayImage ${OpenCV_LIBS} )

Generate the executable

Then execute following:

cd <DisplayImage_directory>
cmake .
make

Result

At this point you will have an executeable file called DisplayImage. Try run it and give it an image location as an argument, such as:

./DisplayImage <some image here>

Now, have you see the image? 😀

Installing OpenCV with Slackware64 14.0

December 5, 2015 | Article | No Comments

OpenCV (Open Source Computer Vision Library) is an open source computer vision and machine learning software library. OpenCV was built to provide a common infrastructure for computer vision applications and to accelerate the use of machine perception in the commercial products. OpenCV is released under BSD-license.

The library itself has more than 2500 optimized algorithms, which includes a comprehensive set of both classic and state-of-the-art computer vision and machine learning algorithms. These algorithms can be used to detect and recognize faces, identify objects, classify human actions in videos, track camera movements, track moving objects, extract 3D models of objects, product 3D point clouds from stereo cameras, etc.

OpenCV has C++, C, Python, and Java interface. In this article we will discuss about how to install OpenCV on linux, specifically Slackware64 14.0. In this article we will use:

  1. Slackware64 14.0
  2. git client
  3. cmake
  4. gcc

Make sure you have them all for this article.

Now download the source from git by using:

git clone https://github.com/Itseez/opencv.git

After that do following:

cd opencv
mkdir release
cd release

cmake -D CMAKE_BUILD_TYPE=RELEASE -D CMAKE_INSTALL_PREFIX=/usr/local ..

Then we compile and install it.

make
make install

At this point we have install OpenCV. Congratulations 😀

Installing TeamViewer 8 on Slackware64

December 5, 2015 | Article | No Comments

TeamViewer is a proprietary application for remote control any computer or Mac over the internet. Teamviewer mainly used for online meeting and currently used by more that 100 million users (as stated by their site). Teamviewer also support linux and the latest version (per February 5th 2013) is 8.0.16675.

In this article we will use Slackware64 14.0 with multilib support. Unfortunately if you are not activating multilib yet, you cannot run teamviewer. It also requires 32 bit packages such as: glibc, zlib, freetype, alsa-lib, GConf. And another thing, Teamviewer is not supporting Slackware officially and the SlackBuild only provide version 7. So to install TeamViewer, we will do a little trick.

First download the TeamViewer on their official site. The one we will use is this one.

Download the files on this url on a single directory. Then do build by invoking the script.

sh teamviewer.SlackBuild

Then copy the rc.teamviewerd to /etc/rc.d directory. Make sure you give execute permission to it.

To run TeamViewer, you must run rc.teamviewerd first by:

/etc/rc.d/rc.teamviewerd start

To start the daemon on every boot sequence, add this line in /etc/rc.d/rc.local:

if [ -x /etc/rc.d/rc.teamviewerd ]; then
  /etc/rc.d/rc.teamviewerd start
fi

And congratulation! We have install TeamViewer. Wanna conference? 🙂

KDE or K Desktop Environment has released their latest version, version 4.9.5, on 1 January 2013. This article will discuss about how to upgrade KDE to 4.95 on Slackware. In this article I use Slackware64 version 14.0. But you can also use Slackware 32 bit to do it.

First of all, copy this article to a text. To upgrade KDE make sure you don’t run X and KDE. You can exit GUI by switch to tty1 (press <CTRL> + <ALT> + <F1>), login with root and invoke this command:

telinit 3

Next we will downloads the required packages on official site. It is more recommended to download from mirror server you know. But at this point we will use the official site as our reference. Now issue this command:

rsync -av rsync://alien.slackbook.org/alien/ktown/14.0/4.9.5 .

The above command will download the whole 4.9.5 directory excluding sources directory into current directory. Beware, pay attention for last “.” (dot) as it is also part of command.

After finish synchronizing, make sure you have minimal three folders: deps, x86, x86_64 under 4.9.5. If you only want to download only 64 bit version, do this instead of last command:

rsync -av --exclude=x86 rsync://alien.slackbook.org/alien/ktown/14.0/4.9.5 .

If you want to download 32 version only, do this:

rsync -av --exclude=x86_64 rsync://alien.slackbook.org/alien/ktown/14.0/4.9.5 .

Now enter directory 4.9.5. Within that directory do these command:

upgradepkg --reinstall --install-new x86_64/deps/*.t?z
upgradepkg --reinstall --install-new x86_64/kde/*.t?z
removepkg kdemultimedia
removepkg ksecrets

If you install 32 bit version, do this instead:

upgradepkg --reinstall --install-new x86/deps/*.t?z
upgradepkg --reinstall --install-new x86/kde/*.t?z
removepkg kdemultimedia
removepkg ksecrets

At this point you are officially has upgrade your KDE to 4.9.5. But if you already have one or more non-english language packs installed, you have to install it to. For you who use 32-bit, you can also do this command:

upgradepkg x86_64/kdei/*.t?z

If you don’t have any but want to install it, you can do this command and substitute XX with language pack you want to install:

upgradepkg --install-new x86_64/kdei/kde-l10n-XX-*.t?z

If you want to know what language packs supported, you can browse the directory by:

ls x86_64/kdei/

Now reboot your system and check to make sure you have install 4.9.5. You can do it by:

kded4-config -v

Did you see 4.9.5 there? 😀

Social media & sharing icons powered by UltimatelySocial