Building Inkscape (v0.47) Binary Package in Slackware 13.0 using SBo (SlackBuild.org) SlackBuild Script and SBOPKG Tool

Diagram on the left side shows the build dependency order to compile Inkscape (v0.47) source in Slackware 13.0. "graphviz", "lxml" and "numpy" are optional, but for better functionality it is strongly recommended to install them also. You can find information about dependencies for any package in README file in SlackBuild archive file. Here is the ftp repository of SBo (SlackBuilds.org). Tracking dependency order for the package you wish to install and checking over each of README files of tracked dependencies to explore whether any other dependencies exist or not, you can easily make a complete dependency diagram for compilation of intended package as on the left side. Synchronize your Sbopkg package list with the SBo repository and place all dependencies and intended package in correct order in SBOPKG build queue before begining to compilation process and then start to build programs and libraries in the list. Here is the docs/help page of SBOPKG.

aMSN 0.98.1 is released!

http://www.amsn-project.net/ Most of the people around me use Microsoft's "MSN" for instant messaging and MSN is indispensable part of their computer culture. Up to now, I made many of my close friends migrate to GNU/Linux and ordinarily exposed to many questions about this OS. One of the questions requested to me is that whether Microsoft's MSN works on GNU/Linux operating systems or not. There is a number of MSN client software for GNU/Linux, but most of them do not satisfy the new migrants. At that point, "aMSN" becomes prominent, because in the view of functionality and visual appearance, it resembles to Microsoft's "MSN" most. Now let us build aMSN native "Slackware 13" binary package using SBo SlackBuild script. Today 27th of November 2009 and there is no SlackBuild script for aMSN 0.98.1 on SBo homepage :(. But do not worry :), it is possible to build aMSN 0.98.1 binary using previous (0.97.2) SBo SlackBuild script. Just replacing source tarball with latest source tarball (0.98.1) and editing SlackBuild script for the new source version and archive type, you can easily build aMSN 0.98.1 binary package for "Slackware 13". "aMSN 0.98.1 Source", "aMSN 0.97.2 SBo SlackBuild", "aMSN 0.97.2 SBo CPG Signature" $ wget http://topraksuenerji.org/open_source/amsn-0.98.1.tar.gz $ wget http://topraksuenerji.org/open_source/amsn.tar.gz $ wget http://topraksuenerji.org/open_source/amsn.tar.gz.asc $ tar -zxvf amsn.tar.gz $ mv amsn-0.98.1.tar.gz amsn.tar.gz.asc amsn $ cd amsn $ nano amsn.SlackBuild Edit aMSN SlackBuild script as in above snapshot and save then log in as root with "su". Now, you are ready to execute the script. # ./amsn.SlackBuild Clean old aMSN installation, if exists. # removepkg amsn Install aMSN 0.98.1 by; # installpkg /tmp/amsn-0.98.1-*_SBo.tgz

Printing to a Windows printer via Samba in Slackware

You want to print from a Slackware machine to a printer that is connected to a Windows machine on the same LAN. To achieve this, Windows host must have a share for this printer with a specified share name. Then it is easy to configure a Windows printer from a GNU/Linux client (Slackware machine) via SAMBA and CUPS. One can share files and printers between GNU/Linux and Windows machines over a network via SAMBA. CUPS provides a portable printing layer for UNIX-based operating systems such as GNU/Linux and Mac OS X. Latest Slackware release (Slackware 13) includes both "samba'" and "cups" packages. If you did not install these packages while installation, install them from the main tree in the installation DVD. Make sure that samba and cups run at startup by making /etc/rc.d/rc.samba and /etc/rc.d/rc.cups executable. # chmod 755 /etc/rc.d/rc.samba # chmod 755 /etc/rc.d/rc.cups Create a samba configuration file by; # mv /etc/samba/smb.conf-sample /etc/samba/smb.conf Now you need to start samba and cups services by; # /etc/rc.d/rc.samba start # /etc/rc.d/rc.cups start To configure a Windows printer properly via Samba and CUPS, you need to know the name of the work group of the Windows printer host (not always required), NET-BIOS host name of the Windows printer host (always required) and share name of the Windows printer (always required). You can view shared printers and disks on a Windows machine by smbclient command with below options. $ /usr/bin/smbclient -L net-bios_host_name_of_the_windows_machine -N For my case, ertan is the NET-BIOS host name of my Windows box. bash-3.1$ smbclient -L ertan -N Domain=[ERTAN] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment --------- ---- ------- IPC$ IPC Uzak IPC D$ Disk Varsayılan değer Belgelerim Disk print$ Disk Yazıcı Sürücüleri HpDeskjet1280 Printer HP Deskjet 1280 ADMIN$ Disk Uzak Yönetici C$ Disk Varsayılan değer Domain=[ERTAN] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Server Comment --------- ------- Workgroup Master --------- ------- bash-3.1$ Connect to CUPS administration panel by typing http://localhost:631/ into your favorite browser and add Windows printer to CUPS as following. Add New Printer --> Name: Specify a name Location: Specify a location Description: Enter a description Device: Windows Printer via SAMBA Device URI: smb://server/printer or smb://workgroup/server/printer or smb://username:password@server/printer or smb://username:password@workgroup/server/printer Manufacturer and Model Name: Choose driver For Device URI (Uniform Resource Identifier), insert the correct server and printer share name. If system needs wokgroup, username and password, insert them correctly also. (workgroup: Name of the work group of the Windows printer host server: NET-BIOS host name of the Windows printer host printer: Share name of the Windows printer username:password: Username and password authorized to use the shared printer on the Windows machine) For manufacturer and model type, variety of drivers will be listed, because Slackware includes "Gutenprint" (formerly Gimp-Print) driver package. Finish printer installation verifying root user name (root) and password (root's password) and print a test page to check whether your samba network printer installation successfully performed or not.

Slackware 13.0 is released!

After one of the most intensive periods of development in Slackware's history, the long awaited stable release of Slackware 13.0 is ready. This release brings with it many major changes since Slackware 12.2, including a completely reworked collection of X packages (a configuration file for X is no longer needed in most cases), major upgrades to the desktop environments (KDE version 4.2.4 and Xfce version 4.6.1), a new .txz package format with much better compression, and other upgrades all around -- to the development system, network services, libraries, and major applications like Firefox and Thunderbird. We think you'll agree that this version of Slackware was worth the wait. Also, this is the first release of Slackware with native support for the 64-bit x86_64 architecture! Major kudos to Eric Hameleers for all of his work, especially on the 64-bit port. More details may by found in the official announcement and in the release notes. Please consider supporting the Slackware project by picking up a copy of the Slackware 13.0 release from the Slackware Store. The discs are off to replication, but we're accepting pre-orders for the official 6 CD set and the DVD. The CD set is the 32-bit x86 release, while the DVD is a special edition dual-sided disc with the 32-bit x86 release on one side and the 64-bit x86_64 release on the other. And, we still have T-shirts and other Slackware stuff there, so have a look around. Thanks to our subscribers and supporters for keeping Slackware going all these years. Thanks are again due to the Slackware crew, the developers of slackbuilds.org, the community on linuxquestions.org, Slackware IRC channels, and everyone else who helped out with this release. Have fun, and enjoy the new stable release! Pat and the Slackware crew Source: http://www.slackware.com

Enabling color support of "ls" in Bash

I have noticed that executing ls command in "Terminal" and "Xterm" does not give me colorful output as in "Konsole". To get colorful output in these X terminals in bash, add below lines to your ~/.bashrc file and restart X terminal. # enable color support of ls and add handy aliases if [ "$TERM" != "dumb" ]; then eval "`dircolors -b`" alias ls='ls --color=auto' alias dir='ls --color=auto --format=vertical' alias vdir='ls --color=auto --format=long' fi To enable the same function for your root shell, add above lines to /root/.bashrc file.