To copy, preserving permissions AND structure AND recursively, from a remote system to your local system:

rsync -r -a -v -e ssh server1.address.com:/dir/youwant/to/copy/ /local/location/for/directory/

Please note that the code above assumes that you are using key based authentication and not password.  For password based authentication, it would look more like this:

rsync -r -a -v -e ssh remoteuser@server1.address.com:/dir/youwant/to/copy/ /local/location/for/directory/

To remove all files matching a certain extension (xml in my example) in a directory:

find . -type f -name "*.xml" -exec rm -f {} \;

To go into a location, find all files that match a certain extension (jpg in my example) and move them to a different directory:

find . -name "*.jpg" | xargs -i mv '{}' /location/to/move/them/to/ 

To recursively remove empty directory from the directory you are currently in (your pwd):

find -depth -type d -empty -exec rmdir {} \;

These are a few of the commands that I’ve found useful in the past few weeks.  I hope you find them useful as well.  I’ll be test driving quite a few different distributions and reporting back what I find as well as experimenting with various different commands…I really like find because it is so powerful so look for some more posts with uses of the find command.  Thanks for reading and sorry for my lapse in posting this past month!

Some Random Helpful Hints originally appeared on Yet Another Linux Blog on June 10, 2011.

‘tail’ can be used alone or can be combined with other commands like ‘grep’, ‘ls’ etc.

To use ‘tail’, let’s first create a text file. You can create the file by issuing following command in terminal;

touch my_file

Now open my_file with your favorite text editor (nano in my case) and write some lines. For this article, I have written the following 15 lines;

this is the 1st line
this is the 2nd line
this is the 3rd line
this is the 4th line
this is the 5th line
this is the 6th line
this is the 7th line
this is the 8th line
this is the 9th line
this is the 10th line
this is the 11th line
this is the 12th line
this is the 13th line
this is the 14th line
this is the 15th line

Now issue the following command in terminal;

tail my_file

It will print the last 10 lines which would be the “this is the 6th line” through “this is the 15th line”.

You can control the number of lines which ‘tail’ will print. You can either increase or decrease the number of lines. For example, if you want ‘tail’ to show only last 3 lines, you can do this by issuing the following command;

tail -n 3 my_file

Now it will print only last 3 lines. You can use any number of lines instead of 3. Or you can use a plus sign like;

tail -n+7 my_file

‘tail’ will start printing from 7th line to the end of the file.

You can view the desired file with respect to size. Issue the following command in terminal;

tail -c 14 my_file

And it will show the output of last 14 bytes. In my case, the output was;

the 15th line

‘tail’ not only displays the static output of a file but it can also monitor the file for changes. A ‘-f’ option is used with ‘tail’ and it starts acting like a monitoring tool which not only displays the last few lines but also constantly updates the output as the file changes. Here is a very popular example;

tail -f /var/log/message

‘tail’ will print the last 10 lines of ‘message’ file. If you now plug-in you USB stick, you will notice that the change in ‘message’ file will instantly be reported by ‘tail’. To release the cursor press Ctrl+c.

There are many other useful options which you can use with ‘tail’ like;

tail -q my_file        # never output headers

tail -v my_file        # always outputs headers

You can combine ‘tail’ with other utilities like ‘ls’, ‘grep’, ‘head’ etc.

You can combine ‘tail’ with ‘grep’ to get lines with some specific ‘word’.

tail -n 5 my_file | grep 14

It will print only those lines out of last 5 which contains the word ’14′. In my case the output was:

this is 14th line # ’14′ will be highlighted

‘tail’ can also be combined with ‘ls’ to get the list of last few files/folders. For example, if you issue the following command;

ls -l | tail -n 2

It will give a long listing of files/folders but will show the last 2 entries of the working directory.

These are just two examples of combining ‘tail’ with other utilities. There are countless examples of combination of ‘tail’ and other softwares.

‘GNU tail’ is a very handy tool. It can output any amount of data depending upon the options used. It makes the work of an ordinary user much easer and helps him/her find information in files more efficiently. To become an expert in Linux, this is a mandatory utility over which a user must have complete mastery. Hopefully, this tutorial gets you started chasing your tail!

Chasing Your ‘Tail’ With Linux originally appeared on Yet Another Linux Blog on January 27, 2011.

You may be thinking about some way to avoid typing commands over and over. Enter the ‘alias’.

The ‘alias’ tool is a way to make the complicated things simple (and simple things simpler). You can use ‘alias’ instead of long (or even short) commands.  Now let’s see how the ‘alias’ works.

‘alias’ can make difficult and lengthy commands easy. The general format of ‘alias’ is:

alias Any_Word=”Command”

It means you linked an existing command to a (New) Word. This ‘Any_Word’ may contain anything – any alpha-numeric symbol, ‘Any_Word’ as well as ‘Command’ are interchangeable and can be used for the same purpose.

Simple Commands Made Simpler

As an example, ‘ls -l’  is used for listing directory contents in ‘long listing format’. This ‘ls -l’ can be replaced with a simpler alias. You can set the ‘alias’ for ‘ls –l’ as follows:

alias ll=”ls –l”

Now you just have to type ‘ll’ (without quotes) to get ‘long listing format’.

Or if you frequently misspell ‘ls’ as ‘sl’ and don’t want to install ‘sl’ package, then, you can use the following alias:

alias sl=”ls”

Now, whenever you type ‘sl’ in terminal, it will give you same results as ‘ls’.

Now consider even simpler example. To close a Terminal (or logout), you have to type ‘exit’ in Terminal. This ‘exit’ command can be made even simpler by using the following ‘alias’:

alias x="exit"

Now, you only have to type ‘x’ in Terminal to ‘exit’

Other examples of ‘alias’ are:

alias cp="cp -iv"
#make copy operation interactive and verbose

alias rm="rm -iv"
#make remove operation interactive and verbose

alias mv="mv -iv"
#make move operation interactive and verbose

Make Package Management A Bit Simpler

If you use Debian (or its derivatives) then you will be familiar with APT.  It is an excellent package manager.

In Ubuntu, to install software using APT, you have to use the following command:

sudo apt-get install <sofware_name>

It is a long command and consumes a lot of your time and energy

You can shorten this command by using ‘alias’.  Issue the following command in Terminal:

alias Install=”sudo apt-get install”

You can obviously use your own word instead of ‘Install’.

Now, you just have to type:

Install <software_name>

to install the (same) software. Simple, isn’t it?

You can simplify other aspects of APT. For example, you can use the following ‘alias’:

alias Remove=”sudo apt-get remove”

to uninstall a software.

Some other examples of attaching APT with ‘alias’ are:

alias Update=”sudo apt-get update”

alias Upgrade=”sudo apt-get upgrade”

alias Search=”apt-cache search”

alias Autoremove=”sudo apt-get autoremove”

alias Autoclean=”sudo apt-get autoclean”

alias Purge=”sudo apt-get remove –purge”

and so on…

A Very Interesting ‘alias’ For A Difficult Keyboard Button

On some keyboards, the dot (.) button is at very difficult position and if you have to use it more than once, it becomes even more difficult.  That’s why ‘cd ..’ is the command which I mistype the most.  This complication can be easily removed by using following ‘alias’ (you can use any other word instead of a dot):

alias .=”cd ..”

alias ..=”cd ../..”

alias ...=”cd ../../..”

alias ....=”cd ../../../..”

Using Internet From Terminal

If you regularly use lynx to browse the internet in terminal then you have to type long urls with lynx to visit the web pages.  You can simplify these long urls by using ‘alias’:

alias Google=”lynx http://www.google.com/”

alias Yahoo=”lynx http://www.yahoo.com/”

alias yalb =”lynx http://linux-blog.org/”

and so on…

Now just type Google, Yahoo or yalb to visit the respective web sites.

Simple ‘alias’ For More Complicated Commands

Long commands are not only difficult to remember but also take more time to type; when you have to use them on daily basis, you become frustrated when typing them again and again and again… So, ‘alias’ are more suitable for long and complicated commands.

Let’s consider an example.

To find the top 10 largest files in your system, you can set the following ‘alias’:

alias top10files=”find . -type f -exec ls -sh {} \; | sort -n -r | head -10”

You can even mix different commands with ‘alias’.  For instance, if you regularly use ‘tail’ and direct its output to file to later view that file, you can set a very simple ‘alias’ to do this cumbersome operation in 1 word:

alias Tail=”tail /var/log/messages > hello.txt;cat hello.txt”

Now just enter ‘Tail’ and viola! All is done at once.

You can use any file with tail and direct its output and you can even use ‘nano’ or ‘vi’ to view/edit its output.

Here’s another example… ‘alias’ to connect to a remote server:

alias any_name=”ssh <remote_server_address> -l <username> -p <port>”

You can even create ‘alias’ for your bash scripts, like:

alias clc=”sh /home/user/myscripts/calc.sh”

Now that you have set a few different ‘alias’  you might want to check that which ‘alias’ are set on your system.  To do that, just issue the following command:

alias

and it will list all the set ‘alias’ you have.

To remove an ‘alias’, just issue the ‘unalias’ command, like:

unalias Google

and now typing Google in terminal will do nothing (as it was set with lynx).

To remove all the ‘alias’, issue the following command and all the ‘alias’ are gone:

unalias –a

We have discussed the way of setting the ‘alias’ for different kinds of commands.  But setting ‘alias’ in this way be temporary.  When you reboot you PC, all the ‘alias’ which you have set will be gone.  This does not mean that you have to set all the ‘alias’ every time you boot your PC.  If you have set an ‘alias’ and you liked it so much that you want it to permanently reside in you PC, just add this alias in ‘.bashrc’ file in you home directory. For example, if you want ‘alias’:

Install <software_name>

to permanently reside in your PC then user your favorite text editor and add the following line in your ‘~/.bashrc’ file:

alias Install=”sudo apt-get install”

Now this ‘alias’ will not vanish into thin air when you reboot your PC. Only those ‘alias’  which are listed in ‘~/.bashrc’ file will be permanent.

This guide is just a preview about ‘alias’.  It is just about basic ways of using ‘alias’ to make your life simpler.  ‘GNU alias’ is a tool which can simplify your life immensely.  But unfortunately this tool is not given the attention it deserves.  In short, it is such a powerful tool that if you give it proper time, it can make you forget typing

Using ‘Alias’ in Linux originally appeared on Yet Another Linux Blog on December 23, 2010.

Permissions are important for keeping your data safe and secure.   Utilizing permission settings in Linux can benefit you and those you want to give access to your files and you don’t need to open up everything just to share one file or directory (something Windows sharing often does).  You can group individual users together and change permissions on folders (called directories in Linux) and files and you don’t have to be in the same OU or workgroup or be part of a domain for them to access those files.  You can change permissions on one file and share that out to a single group or multiple groups.  Fine grained security over your files places you in the driver seat in control of your own data.

Some will argue that it may be too much responsibility…that placing this onto the user is foolish and other aforementioned operating systems don’t do this.  You’d be right…XP doesn’t do this.  However, Microsoft saw what Linux and Unix do with the principle of least privilege and have copied this aspect from them.  While the NTFS filesystem employs user access lists with workgroups and domains…it cannot mirror the fine grained, small scale security of Linux for individual files and folders.  For the home user, Linux empowers control and security.

I’m going to go over how users and directory/file permissions work.  So, let’s setup an example that will allow us to explore file permissions.  If you have any questions, just ask it in the comments section at the end of the article.

File Permissions Explained

The picture to your left is a snapshot of my $HOME directory.  I’ve included this “legend” to color code and label the various columns.  Let’s go through the labels and names of things first and then work on understanding how we can manipulate them in the next section.

As noted in the picture, the first column (orange) explains whether or not the contents listed is a directory or not.  If any of these happened NOT to be a directory, a dash (-) would be in place of the d at the beginning of the listing on the far left.

In the second, third, and fourth column (Green, Blue and Red) we find permissions.  Looking at the gray box in the bottom-right corner gives us an explanation of what each letter represents in our first few columns.  These tell us whether or not each user, group, or other (explained in detail later in this article) have read, write, and execute privileges for the file or folder/directory.

In the 5th column (white) the number of hard links is displayed.  This column shows the number of actual physical hard links.  A hard link is a directory reference, or pointer, to a file on a storage volume that is a specific location of physical data.  More information on hard links vs. symbolic (soft) links can be found here.

In column 6 (light blue) we find the user/owner of the file/directory.  In column 7 (gray blue), the group that has access to the file/folder is displayed.  In column 8 (pink), the size of the file or folder is shown in kilobytes.  In column 9 (fluorescent green), the last date the file or folder was altered or touched is shown.  In column 10 (grey), the file or directory name is displayed.

We’re going to pay specific attention to the first four columns in the next section and then follow that up by working with the sixth and seventh by going over user/owner and group.  Let’s move on to go over all of those rwx listings and how we can make them work for us.

Read, Write, Execute – User, Group, Other

First, let’s go over what different permissions mean.  Read permission means you can view the contents of a file or folder.  Write permission means you can write to a file or to a directory (add new files, new subdirectories) or modify a file or directory.  Execute permission means that you can change to a directory and execute ( or run ) a file or script for that file or directory.

The User section shown in green in the picture above shows whether or not the user can perform the actions listed above.  If the letter is present, the user has the ability to perform that action.  The same is true for the Group shown in blue above…if a member of the group that has access to the file or directory looks in this column, they will know what they can or can’t do (read,write, or execute).  Lastly, all others (noted in the red column above).  Do all others have read, write, and execute permissions on the file or folder?  This is important for giving anonymous users access to files in a file server or web server environment.

You can see how fine grained you might be able to set things up with…For example, you may give users read only access while allowing a group of 5 users full control of the file or directory.  You may want to switch that around.  It’s entirely up to you how you want to setup permissions.

More about Groups

Let’s go through setting up a group and adding a few users to it and then assigning that group permissions to access a directory and file.

Create a file inside your home directory by opening up a shell or terminal and typing:

touch ~/example.txt

You’ve now created a file called example.txt inside your home directory.  If you are already there, you can list the contents with the ‘ls’ command.  Do that now.  If you’re not already there, type ‘cd ~/’ and you will be taken to your home directory where you can ‘ls’ list the files.  It should look similar to the following:

[devnet@lostlap ~]$ ls -l
total 40
drwxr-xr-x  2 devnet devnet 4096 2010-05-24 17:04 Desktop
drwxr-xr-x  6 devnet devnet 4096 2010-05-24 13:10 Documents
drwxr-xr-x  9 devnet devnet 4096 2010-05-27 15:25 Download
-rw-rw-r--  1 devnet devnet    0 2010-05-28 10:21 example.txt
drwxr-xr-x 13 devnet devnet 4096 2010-05-26 16:48 Music
drwxr-xr-x  3 devnet devnet 4096 2010-05-24 13:09 Pictures
drwxr-xr-x  3 devnet devnet 4096 2010-05-24 13:04 Videos

Next up, let’s create a new group and a couple of new users.  After creating these we’ll assign the users to the new group.  After that, we’ll move the file and lock it down to the new group only.  If everything works as planned, the file should be accessible to root and the other 2 users but NOT accessible to your current user. You’ll need to be root for all of these commands (or use sudo for them). Since I have sudo and don’t want to continually type sudo, I used the command “sudo -s” and entered my root password to permanently log in as root in a terminal for the duration of this how-to. OK, Let’s get started:

[root@lostlap ~]$ useradd -m -g users -G audio,lp,optical,storage,video,wheel,games,power -s /bin/bash testuser1
[root@lostlap ~]$ useradd -m -g users -G audio,lp,optical,storage,video,wheel,games,power -s /bin/bash testuser2

The above commands will create two users that should be pretty close to your current logged in user (as far as group membership goes).  If the groups you’re adding the user to do not exist, you may get a warning that the groups don’t exist…no worries, just continue.  If the above commands don’t work on your system (I used Arch Linux to do this) then you can use the GUI elements to manage users and add a new one.  You won’t need to add them to any extra groups since we just need a basic user.  Next, let’s create our ‘control’ group.

[root@lostlap ~]$ groupadd testgroup

The above command creates the ‘testgroup’ group. Now let’s add the two users we created to this group.

[root@lostlap ~]$ gpasswd -a testuser1 testgroup
[root@lostlap ~]$ gpasswd -a testuser2 testgroup

The command above adds both our test users to the test group we created. Now we need to lock the file down so that only those users inside of ‘testgroup’ can access it. Since your current logged in user is NOT a member of ‘testgroup’ then you shouldn’t be able to access the file once we lock access to that group.

[root@lostlap ~]$ chgrp testgroup example.txt

The above command changes the group portion of file permission (discussed earlier) from a group your currently logged in user is a member of to our new group ‘testgroup’. We still need to change the owner of the file so a new terminal opened up as your current user won’t be the owner of example.txt.  To do this, let’s assign example.txt a new owner of Testuser2.

[root@lostlap ~]$ chown testuser2 example.txt

Now when you try to access the file example.txt you won’t be able to open it up as your standard user (root still will be able to access it) because you don’t have the permissions to do so. To test this, open up a new terminal (one where you are not root user) and use your favorite text editor and try to open up example.txt.

[devnet@lostlap ~]$ nano example.txt

Both testuser1 and testuser2 will be able to access example.txt because testuser2 owns the file and testuser1 is in the testgroup that has access to this file. However, your current logged in user will also have READ rights to it but will not be able to access it. Why? Let’s take a look at the permissions on example.txt

[devnet@lostlap ~]$ ls -l example.txt
-rw-r--r-- 1 testuser1 testgroup 8 2010-05-28 10:21 example.txt

Notice that the user, group, and other (1st, 2nd, and 3rd position of r,w,x – see the handy diagram I made above) have permissions assigned to them. The user can read and write to the file. The group can read it. Others can also read it. So let’s remove a permission to lock this file down. Go back to your root terminal that is open or ‘sudo -s’ to root again and do the following:

[root@lostlap ~]$ chmod o-r example.txt

Now go back to your user terminal and take a look at the file again:

[devnet@lostlap ~]$ ls -l example.txt
-rw-r----- 1 testuser1 testgroup 8 2010-05-28 10:21 example.txt

Once that has been accomplished, try and open the file with your favorite text editor as your currently logged in user (devnet for me):

[devnet@lostlap ~]$ nano example.txt

Your user now should get a permission denied error by nano (or whatever text editor you used to open it). This is how locking down files and directories works. It’s very granular as you can give read, write, and execute permissions to individual users, groups of users, and the general public. I’m sure most of you have seen permissions commands with 777 or 644 and you can use this as well (example, chmod 666 filename) but please remember you can always use the chmod ugo+rwx or ugo-rwx as a way to change the permissions as well. I liked using letters as opposed to the numbers because it made more sense to me…perhaps you’ll feel the same.

Hopefully you now have a general understanding how groups, users and permissions work and can appreciate how the complexity of it is also elegant at the same time. If you have questions, please fire away in the comments section. Corrections? Please let me know! Thanks for reading!

Linux File Permissions, Groups, and Users originally appeared on Yet Another Linux Blog on November 3, 2010.

You can use the tar command to make this a snap.

Tar combines multiple files into an archive and you can use it to preserve permissions and file structure and then you can compress the archive to save space.

tar -c --recursion -p --file=backup.tar directory

The -c flag creates an archive for us.  –recursion goes through all subdirectories.  The -p flag preserves permissions on all the files.  This is handy if you have certain folders or files that you need to sticky with individual users or groups.  The –file flag is the option for outputting to a file name.  You can also add multiple directories that you’re zipping up like the following:

tar -c --recursion -p --file=backup.tar directory1 directory2 directory3

After you have the file output as backup.tar it’s time to compress it.  The most standard way to do this is to use the gzip command:

gzip backup.tar

This command will output backup.tar.gz to the current directory which will take up less space than that of a standard 1-to-1 copy.  There are many other flags and options that you can use with the tar command.  For an in depth look at those flags and options, check the tar man page by typing ‘man tar’ in a terminal or view it online here.

UPDATE:

Commenter ‘jack’ has offered a few extra flags to combine the archiving and zipping into one command:

tar -c -z --recursion -p --file=backup.tar directory1 directory2 directory3

The -z flag will gzip the archive after you’ve used tar to create it.  Substituting -j in for -z above will bzip the archive.  Thanks for the tips jack!

Backup Directories and Subdirectories Preserving File Structure originally appeared on Yet Another Linux Blog on April 14, 2010.

Read about Repository Control in PCLinuxOS

You’ll be looking for the ‘sections’ blank when viewing repository details and you’ll just need to add ‘testing’ to the end of the line (don’t replace the entires there already).  Once that is done, click the reload button in Synaptic and allow it to refresh your local rpm cache.

Click the ‘search’ button and search for the keyword ‘kernel’.  Look for the highest number of kernel that is returned.  At the time of this writing, the 2.6.26.8 kernel was the newest kernel for PCLinuxOS (it has .27 patches all over in it…so it’s quite a nice kernel).  Click and install that kernel and allow it to select any packages it needs to install.  Once installed, you can remove the word testing from the repository (this is recommended to prevent your system from downloading ALL testing packages/updates) and click the reload button for Synaptic.

Reboot and choose the new kernel on your grub menu.  Test things to see how they work.  If everything is good to go, congratulations!  You’ve just installed the latest kernel in PCLinuxOS.

To make this kernel the default one, you can use the PCLinuxOS Control Center and Change the Way the System Boots.  I’ll cover this in a later post.  Hope this helps a few of you out there.  I know it is often asked on IRC.

Install the Latest Kernel in PCLinuxOS originally appeared on Yet Another Linux Blog on December 17, 2008.

Build Your Own PCLOS

So, HowtoForge has a perfect desktop for PCLinuxOS 2007…how about something similar for 2008 MiniMe? I won’t go into near as much detail as they do there but I’ll go over how I get my desktop up and rolling after a fresh install of PCLinuxOS Minime 2008.

MiniMe is the lesser known offspring of PCLinuxOS 2007 that ships with a 2.6.22.15 kernel and is a minimalistic installation of the KDE desktop 3.5.9. Texstar provides this distribution for those wanting to remaster their installations…it’s a base for other remastered projects like PCLinuxOS Gnome. Remastering and the Make LiveCD wizard enable users to customize their distribution and make a bootable backup CD with all their customizations OR release their own customized distribution. You can also use the Make LiveUSB wizard to create your very own thumbdrive PCLinuxOS.

I found it strange that no one had written anything about MimiMe-to on getting PCLinuxOS 2008 MiniMe up and running as a desktop replacement so I decided to give it a go. The aim of this article isn’t to copy Howtoforge’s great series on perfect installations…but to show how I get PCLinuxOS 2008 Minime up to a perfect installation for me. This means all web video, audio, fonts, and tools I need are installed. So let’s get at it.

What Do We Need?

First and foremost, do a complete upgrade of your fresh installed system. Open Synaptic >> Reload >> Mark all Upgrades >> Apply. It’s going to take a while to get all the updates you’ll need. Do NOT enable the testing repository until after you install your graphics driver at the end of this article…just perform a straight update from main.

Now let’s start installing stuff that is needed on a daily basis. I’m more of a lightweight type of guy so I don’t need robust office applications so my tastes may not line up with yours. Please substitute applications where you see fit…the repositories most likely have them.

To give a brief, high level overview of my daily use applications:

• firefox3
• Opera
• K3B
• konversation
• pidgin
• skype_static
• koffice
• gimp
• Amarok
• claws-mail
• kdeaddons-kate
• kdeaddons-ark
• kdegraphics-ksnapshot (for taking screenshots)

Those are the high level applications I use on a daily basis to get things done. Whenever you are prompted to mark other packages for install, go ahead and and choose “mark”. Click apply and let the your daily use applications install.

Handy Wizards for PCLinuxOS 2008

MiniMe 2008 comes with some handy wizards for you to use to get started. On your desktop after install is a folder called “Utilities”. If you open this folder up, you will find the following options:

1. ATI-Nvidia Driver Install
2. Alsa Sound Configuration
3. Internet Setup
4. Make LiveCD
5. Make LiveUSB
6. Redo-MBR
7. Set Clock

You can use any of these you want to get things rolling. You’ll have to enable your network through the PCLinuxOS Control Center because MiniMe does not setup a network connection by design out of the box. Remember, it’s a base for building, not a full fledged distro. We have to craft it how we want it. I recommend NOT installing a graphics driver until the very end…mainly because there are some problems currently with the 173.xx driver conflicting with some packages in the testing repository. So hold off on graphics install if you can until the very last.

Make LiveCD is exactly what it sounds like. You can make a LiveCD based on your install. So after you get everything setup the way you want it to be, you can double click Make LiveCD and a wizard will guide you through creating your own customized LiveCD backup of your install.

Make LiveUSB is also exactly what it sounds like…you can make a bootable version of a USB stick with PCLinuxOS MiniME. This how-to does not cover this since we’re going for a desktop replacement and not a minimalistic install. You may want to select this option though after you’ve got things configured as you want them.

The rest of the options are fairly straightforward and do exactly what they say. Make sure you take the time to get all things working (except graphics driver) before you move on.

What Else Should We Install?

We’ll need to install a few more things to get seamless operation for PCLinuxOS on the web. There are also some packages that will make your PCLinuxOS experience a bit better that we’ll install at this step as well:

• gtk-qt-engine
• RealPlayer-rpnp
• flash-player-plugin
• java-1.6.0-sun
• flac-1.2.1
• mplayer-skins
• mplayer-gui
• mplayer
• win32-codecs-all
• sound-juicer
• flash-player-plugin-opera
• cabextract (for extracting wireless drivers if you have need to)
• webcore-fonts
• unrar
• rar
• xine-plugins
• AdobeReader_enu

Please remember to allow synaptic to mark anything extra that the packages require. After installing these packages, your browsing experience and overall appearance of PCLinuxOS should be ready for improvement. I’ll go through how I setup a few applications to give them a nice look and feel. Let’s start first with GTK applications look and feel.

Setup gtk-qt-engine in PCLinuxOS

Open the KDE Control Center and look under “Appearance and Themes” for the section “GTK Styles and Fonts”. Use the drop down menu to pick out your favorite GTK theme…and if your favorite isn’t there, fire up Synaptic again and do a search for it…chances are, it is there. Once you’ve chosen a style (I use clearlooks) click “Ok”.

This package gives your GTK applications a Gnome Feel in KDE. Without it, things look ugly. Face-in-pillow-to-be-kind-to-burglars ugly.

Get Your Fonts Setup

Configure Fonts

I setup my fonts a bit strange. I use the same webcore font (Microsoft Font) for almost everything because I like the way it looks. To do this, I set it up in the KDE Control Center and choose “Appearance & Themes” >> “Fonts”. Then, I setup each area except Fixed Width with Verdana for the font. You may like Ariel or another font…so choose it there. Don’t be afraid to experiment! Find fonts that suit you and make your desktop shine

When you’re through with the KDE Fonts, don’t forget to setup fonts in Firefox and Opera as well (if you desire to…I always do).

Setup KDE default Applications

While still inside the KDE Control Center, choose “KDE Components” and then “Component Chooser”. On this page, make sure your favorite applications are present as the default application for each area. Those to choose from are email client, text editor, instant messenger, terminal emulator, and web browser. For my email, I setup claws mail by clicking “use a different email client” and clicking the small square to browse applications. I did the same for web browser to make sure KDE knew to use Firefox and not Konqueror.

Enable Super Key for Compiz (if you use it)

If you use compiz and wanted to install it the package name is task-compiz-fusion-kde. Install this package but do NOT run it yet if you have an ATI or Nvidia card. We’ll need to install the graphics driver first. If you have another chip manufacturer (Intel, S3) for your graphics card, you should be able to install and use compiz right away.

To enable the super (windows) key, open the KDE Control Center, go to “Regional & Accessibility” and then to “Keyboard Layout”. Toggle check “enable keyboard layout” and make sure your region is in the right hand side box area as active. Click apply.

Setup Konversation in a Sane Manner

Configure Konversation

I think the default configuration of Konversation isn’t very friendly. So I take a few minutes when first firing it up to configure things. Perhaps you’ll agree with me on these. For example, I don’t like tabs on the bottom of my screen. I’d rather have those channels of chat on the left hand side so I can see them. I also like to have shell-like tabl completion. That means when I hit the tab key after typing a few letters of someones nickname, Konversation will complete their name without me typing it…much like the shell (konsole) can do with directory names. Start up Konversation. Click edit and then click the edit button again. Make sure you’ve input the nickname you need to input. If you are a freenode regular and have a registered nickname, enter NICKSERV and your password in the blanks under “Auto Identify”. Click “ok” twice and then connect.

Under “Settings” choose “Configure Konversation”. Go to the section “Behavior” and choose “General”. In “completion mode” use the drop down menu to select “Shell-Like”. I like to minimize Konversation into the tray and also like it to notify me when my name is mentioned. To do this, inside this same window toggle check “Enable System Tray” as well as the two other check boxes underneath it.

Now lets move the tabs to the left: Under “Interface” click “Tabs”. On the “placement” drop down menu choose “Left”. That’s it for Konversation.

Setup Kopete in a Sane Manner

Hiding Groups & Users

If you use Kopete instead of Pidgin, I’ll walk you through setting it up so that it has a more pidgin appearance. When you first launch Kopete, it will prompt you to setup your accounts. You should have no problem setting up all but the gtalk ones. Go ahead and setup all the other ones…we’ll set gtalk up in a second. First, let’s get the existing ones to display in a sane manner.

Under “Settings” choose “Hide Offline Users”. Then choose “Hide Empty Groups”. This will make sure not to display your offline buddies (of which I have too many all the time) in Kopete.

Next choose “Settings” and “Configure”. Click on Appearance. Click the “Chat Window” tab and choose “Get New”. A window will pop open with new themes to install. I like the theme called Fresh so I highlight it and click the install button. Close out all the windows except the configure one and then highlight “Fresh.AdiumMessageStyle” to switch to it. Click Apply.

Now click on the “Contact List” tab. Un-check “Arrange metacontacts by group” & “Show tree branch lines”. Under “List Style” choose right aligned status icons” and then check the “Use contact photos when available” checkbox. Click Apply.

I like my messages to open only one window with a new conversation opening a new tab. This prevents me from having 3 windows pop from 3 different chats from friends. Click on the “Behavior” icon on the left side of Kopete. Click on the “Chat” tab. Under “Chat Window Grouping Policy” choose “Group All Messages in Same Chat Window”. Click on the “Events” tab and make sure to uncheck “Show bubble” (unless you like notification bubbles…I hate them…I just want Kopete to flash on notification). Click Apply.

Click on the “General” tab. Make sure that the checkbox for the system tray is checked. Check the “Connect automatically at startup” box or Kopete won’t connect when you start it up. Toggle the radio button for “Open Messages Instantly”. Click Apply. Click Ok.

That should be it…I know it’s a lot but this really makes Kopete feel at home for me…almost pidgin style with better KDE integration.

Setup your gtalk follow the instructions here and make sure that if you are prompted with a pop up window choose never show this again and accept (it’s certificates for SSL and gtalk).

Improve Firefox Performance

There are tons of guides out there. I’ve looked through many of them to try and tweak Firefox performance and the one I’ve found to be the best collection of handy tips and tricks is at hugpages. Pay close attention to #13 which is the speedup I found to really make a difference.

KDE Artwork…Add More!!

I wrote an article on how to beautify the PCLinuxOS 2007 Desktop through installation of icon themes, cursor thems, wallpapers, and other improvements. Make sure that you check that post out and customize PCLinuxOS Minime 2008 and make it your own That beautification article is still valid for Minime 2008, which uses the 2007 repositories. Some of the package names may have changed but you can use the search button in synaptic to search “description and name” and find most if not all the packages.

Graphics Card

video driver installer

Setting up your graphics card is last for good reason. It should be the last thing you do unless your resolution is so horrible you need to set it up at the beginning. There is a problem with Nvidia drivers and minime. If you installed the 173.xx drivers and try to upgrade to testing, it will flag a bunch of problems. To fix things, launch konsole, su to root and apt-get clean, then apt-get autoclean.

After doing that, apt-get update and then close konsole. Use the utilities folder on the desktop to un-install the 173.xx drivers. Then perform the testing upgrade without the drivers conflicting. After the upgrade is complete, install the 177.xx drivers. This is only for the latest and greatest video cards. REMEMBER, the utilities folder has a graphics card installation tool. This is used for ATI and Nvidia cards and will install the official driver for both. A list of chipsets for each driver is inside the utility (screenshot on right) so make sure that you pick the correct driver.

If you use any other chipset besides Nvidia or ATI, your driver should be enabled by default.

Extra TidBits I like to Install

I like to be able to right click any music file in Konqueror and convert it to any format I choose. This can be done with the audiokonverter package. Search for that in Synaptic and install it if you’d like to do the same.

Ever want to search through programs you can install without opening Syanptic and without using the command line? Install kio-apt and you’ll be able to do jus that using apt:/ in the address bar where the url normally goes. Options include:

apt:/search?search expression
apt:/show?package
apt:/policy?package
apt:/list?package
apt:/fsearch?package

Want to resize your screen on the fly? Press Alt-F2 and type krandrtray. Notice the small icon that appears inside your kicker tray by the clock. You’ll now be able to resize your screen resolution on the fly. This is sometimes handy for those users who dock a laptop that has a different resolution on laptop screens than desktop ones.

Miss the Nvidia Icon in your tray like in Windows? Install nvdock and then execute it from the menu (System >> Nvidia Dock) and watch as your nvidia icon magically reappears. Right click and be brought to Nvidia Control Panel Settings.

Want some desktop search action without google desktop or the beast that is Beagle? Not a fan of tracker? Try recoll which can be installed through Synaptic.

Need a personal wiki to keep notes? I know I do. That’s why I install zim which is a personal wiki written in GTK. It allows you to quickly jot down notes and scales quickly to even provide multiple page and project tracking for your own personal notes.

Ever run across stuff on the web you wish you could clip out of a webpage and save? Enter basket. It can handle images, webpage snippets, store URLs and anything you might come across, can be saved for easy centralized access.

Screensavers are not installed by default. If you want to install screensavers, try the following packages:

• xscreensaver
• xscreensaver-base
• xscreensaver-common
• xscreensaver-extrusion
• xscreensaver-gl
• xscreensaver-matrix

Did I Miss Anything?

Did I miss anything with my helpful how-to? If so, please leave me a comment letting me know what you’d like to see added to it. I will consider this a working how-to and update it with as much as I can. These are only the applications I find useful and use on a daily basis. I installed these on a fresh install of Minime 2008 on my main system and wrote this how-to while doing it. I wanted it to be minimalistic…I don’t need much in order to be happy. Hopefully, this helps inspire you t

Customizing PCLinuxOS 2008 Minime originally appeared on Yet Another Linux Blog on October 17, 2008.

This is a pretty easy thing to do, but it seems many people come to Yet Another Linux Blog searching for exactly how to do this. ClarkConnect does not come with GCC installed by default. If you download software and attempt to compile it (using ./configure, make, make install) it will complain:

configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.

So, SSH into your ClarkConnect server and install cc-devel to install all the tools you need. Please be advised, it’s a rather large package weighing in at 87.5 MB when I installed it today.

apt-get update

apt-get install cc-devel

After this package is installed, you should be able to compile software from source. Hopefully, this makes your life easier and is easier to find on the web.

Install GCC on ClarkConnect originally appeared on Yet Another Linux Blog on October 12, 2008.

The only problem with this is that ping.fm is in beta stage…and a closed beta at that. So, I began to read various different blogs to try and find any other service that might do the same thing as ping.fm.

During my search, I cam across profilactic.com, which is a central aggregate place similar to friendfeed.com. The interesting part about profilactic is that it plugs into ping.fm and every single user can be part of the closed beta for ping.fm!

This means that you can microblog/status message bebo, blogger, brightkite, facebook, hi5, Jaiku, LinkedIn, LiveJournal, Mashable, Myspace, Plaxo Pulse, Plurk, Pownce, Tumblr, Twitter, and Xanga through one single interface OR through Instant message (there is a ping.fm bot).

Here’s the kicker…profilactic.com supports 186 sites as well as the ability to create a custom site. There are too many to list. Check out their supported sites.

So, you can utilize ping.fm to instant message status updates or microblog and instantaneously have it sent out to close to 200 different sites all at once. This is handy for me since I like to use pownce a bit more than twitter but my coworkers use twitter more. My status updates are still broadcast (on 60 second delay) on twitter through my instant message to the ping.fm bot. Ping.fm also supports the iPhone and has the ability to have custom triggers.

To take advantage of these great services, head over to profilactic and signup. When you’re setting up your sites, you’ll be able to plug into ping.fm (it will require that you signup using the profilactic beta password that profilactic will provide for you during setup). Don’t forget to visit my lifestream and add me as a friend Happy micro/status/blogging!

Microblogging, Status, and Blogging 2.0 originally appeared on Yet Another Linux Blog on June 19, 2008.

Working on a separate 20 inch monitor with a distribution in development however is another story. The fonts didn’t look beautiful at all. After some installation of custom fonts, things looked better, but the resolution is a bit higher on this LCD at 1400×1050. Easy to fix right? Just increase the DPI in the KDE Control Center to 120 right? Not so fast…even when it’s set to 96×96 there, it isn’t always set to 96×96. So let’s take a look at how you can force KDE to run at the correct DPI for your monitor which will, in turn, make your fonts look MUCH better. For those of you who are satisfied with your fonts, you might want to check out the commands below to see if you’re running at the DPI you think you are.

Open Konsole and let’s check your resolution:

xdpyinfo | grep dimension

This will tell you what the actual resolution of X is on your desktop. Next, look at the DPI setting.

xdpyinfo | grep resolution

Surprised? I was. I found that at the high resolution I was running at, the DPI was set to 86×86 despite my attempts to force it to 96×96 in the KDE Control Center.

So how does one combat this? It takes a bit of calculation with a formula followed by a one line entry into your xorg.conf. Easy enough? Almost too easy…couldn’t the KDE programmers, say, employ a control center menu for this? It’s possible…let’s hope it’s in KDE 4.0.

FORMULA

First, the formula. Using the dimensions you found above, you’ll have to calculate 2 numbers…one for horizontal and one for vertical. As my resolution is 1400×1050, I will use this as the example. The formula is as follows:

displaysize = (<pixelsize>/DPI-Desired)*25.4

In my case, displaysize = (1400/100)*25.4. This equals 355. I wrote this down for later. Now I need to use 1050 (my vertical setting for resolution 1400×1050) in the same formula (displaysize =(1050/100)*25.4) which comes out to 266. Keep these two numbers handy…remember, if you want 96 or 120 DPI for your monitor…sub in those numbers for the DPI-Desired and divide your resolution by them as shown in the formula above.

EDIT XORG.CONF

Open up xorg.conf in your favorite text editor..for example, my favorite is kate so I issue the following command: Alt-F2 (a run dialog pops up) >> kdesu kate /etc/X11/xorg.conf. You’ll be prompted for your root password to access this file. After it opens, find the “Monitor” section. Just before “EndSection” place a line like the following (substitute the values you found using the formula above):

DisplaySize 355 266 # 1400×1050 100dpi

Your display size may be different…just remember to place horizontal first, followed by vertical. Now you’ll need to restart X. Close all your applications and hit Control-Alt-Backspace. Log back in and issue the command we used previously for DPI:

xdpyinfo | grep resolution

If you followed the directions above correctly, your altered DPI settings should display. Gnome does this through a handy menu that’s very easy to use. It’s head and shoulders above what KDE does with fonts and setting DPI. Using Gnome at work for the past 4 months has shown me the many areas that KDE falls behind…but it also shows me the many areas where Gnome just doesn’t get the job done. In this case, KDE fails horribly on configuring DPI for nice looking fonts. Luckily, I was able to assemble information from various places on the web to get the job done. The page that helped me the most was Matt Parnell’s Brain, a weblog that had an entry with this formula. I wanted to reproduce the information here with a bit more hand holding so new users would be able to use the tip without getting confused. Hopefully, this helps!

KDE and Xorg, Fonts and DPI originally appeared on Yet Another Linux Blog on September 20, 2007.