Of course there are variations on that opinion. But that is neither here nor there. The purpose of this tutorial is to help you get a PostgreSQL server up and running quickly and easily. To make this simple we will make this a part of our Ubuntu Server series, so all you have to do is have your Ubuntu Server up and running (see my article “Installing Ubuntu Server 9.04” to get started.) Once you have that server up and running you are ready to get your PostgreSQL server up.

Installation

The first thing you need to do is to install the necessary software. Since this is Ubuntu, it’s quite easy. Open up a terminal window and issue the command:

sudo apt-get install postgresql

Once the software is installed you are ready to set it all up.

Change the default user password

One of the first steps you want to take is to change the default password for the user postgres. Sine we are using Ubuntu you will have to use the sudo command to change to the postgres user like so:

sudo su – postgres

You will have to enter your sudo password after which you will now be issuing commands as the user postgres. The next step is to gain access to the postgresql command prompt with the command:

psql

Your new command prompt will look like:

postgres=#

NOTE: The only user that can open the PostgreSQL prompt without defining a database to work with is the user postgres. Other users would have to gain access to the command prompt with a command like:

psql DB_NAME

Where DB_NAME is the name of an existing database.

Changing the password is as simple as issuing the command:

\password postgres

You will then be asked to enter a password and then verify that password.

Your default password has not been changed. You can exit from the PostgreSQL prompt by issuing the command:

\q

Create a database

Now, while still logged in as the postgres user, let’s create a database. For this you do not have to be logged into the PostgreSQL command prompt. Instead just issue the command:

createdb testdb

Where testdb is the name of the database you want to create. To check to make sure that database was created go back to the PostgreSQL command prompt (remember, the command psql) and enter:

\l

You should see a listing for your new database like:

testdb | postgres | UTF8 | en_US.UTF-8  | en_US.UTF-8

Once again, log out of the PostgreSQL command prompt with the command:

\q

Create a user

By default, the only user that can connect to a database is the postgres user. This will be of no help when you need to connect with another user. To create a new user (that can connect to databases) you would issue the command (as the user postgres):

createuser –superuser USERNAME

Where USERNAME is the name of the user you want to create.

Final thoughts

Now you should have a basic PostgreSQL installation with a test database and a user, besides postgres, that can work with the tools. Next time we work with PostgreSQL we’ll discuss more challenging issues with this outstanding database tool.

Related posts

• Set up MySQL database replication (1)
• Install phpmyadmin for easy MySQL administration (6)
• Have WordPress back-ups emailed (3)
• Database Monitoring Software Db2rss (1)
• Backup MySQL Databases In Linux Regularly (11)

And then there’s OpenGoo. OpenGoo is an open source collaboration tool that is fully web-based, easy to use, simple to install, and free to use. But is OpenGoo for you and your company? This tutorial will show you how to get an OpenGoo installation up and running so you can kick the tires and find out if it is exactly what you need.

Features

OpenGoo offers all of the standard features of a business-level collaboration suite:

• Text documents
• Spreadsheets (coming soon)
• Presentations
• Task Lists
• E-mails
• Calendars
• Web Links
• Contacts

All you need to install an OpenGoo server is:

• Apache >= 2.0
• MySQL >= 5.0 (5.2 recommended)
• MySQL >= 4.1 with InnoDB support

Now, let’s get on with that installation.

Install

This installation will be done on a Ubuntu 9.10 setup. I have installed this on both desktop and server installation, but regardless of which you have installed, you will need a LAMP server running.

The first thing you need to do is to download the zip file from the OpenGoo download page. I downloaded and installed the 1.6 beta version which works nicely.

Once that file is downloaded, move that file to /var/www. Now, change to the /var/www/ directory and then unzip it with the command:

sudo unzip opengoo_1.6.beta-2.zip

NOTE: If you downloaded a different release, edit that command to reflect the release number.

Once that files is unzipped rename the directory with the command:

sudo mv opengoo_1.6.beta-2.zip opengoo

Now change into the /var/www/opengoo directory and issue the following commands:

sudo chmod -R ugo+w /var/www/opengoo/config

sudo chmod -R ugo+w /var/www/opengoo/cache

sudo chmod -R ugo+w /var/www/opengoo/upload

sudo chmod -R ugo+w /var/www/opengoo/tmp

With all the right permissions in play, it is time to create the database. I like to use PhpMyAdmin to make database creation simple. For more information about installing this tool check out my article “Install PhpMyAdmin for easy MySQL administration“. Use this tool to create a database called “opengoo” (No quotes).

Time to begin the web-based installation.

Fire up your browser and point it to:

http://IP_TO_SERVER/opengoo

Where IP_TO_SERVER is the actual IP Address of your OpenGoo server. You will be greeted with usual welcome screen that will tell you exactly what is going to happen during the installation. Click the Next button to continue on.

The second screen will run the environment checks. If everything gets and OK (and it should be if your LAMP server is up and running and you’ve taken care of all the permissions) click the Next button to continue on.

Figure 1

The third page of the installation (see Figure 1) is the first step that should require you to input any data.

The information should be fairly self explanatory. There is one point of note: If you plan on allowing access to your local LAN you will need to change the Absolute script URL to reflect the proper IP address (or domain).

Once you have all of this information in place, click the Next button which will take you to the congratulations screen where you only need click the Finish button to assume you’ve completed the installation.

Figure 2

Ah, but there is one more step. Figure 2 shows the final step for the installation. Here you need to create an administrator for your installation.

Setup your administrative user and click Submit. You can now log in to your OpenGoo server with your administrative user.

The basic interface

You will log into your OpenGoo server by entering the same address you did for the installation. When you log in you will be at the OpenGoo Getting Started Page (see Figure 3).

Figure 3

The OpenGoo installation will offer a very simple information page that will help you get started on your decision. But as you can see, the interface is laid out quite well. The tools are accessible and very user-friendly.

After using OpenGoo for a while I can assure you if you like Google’s suite of tools, you will like OpenGoo.

Final thoughts

If you are looking for a very cost effect collaboration solution look no further than the open source OpenGoo suite of tools. Not only is it easy to use, it’s simple to install, and free of charge.

Related posts

• Open Office 3.1 (17)
• Open Office 3 Final (21)
• Microsoft SharedView (0)
• Microsoft Office Migration Planning Manager (1)
• KonoLive Getting Things Done Software (4)

There are a hundred and one thousand things that can go wrong with any web server installation. From a fresh installation to an installation that has been running for a long time, you never know when something is going to cause your web server to go astray. When it does happen, it’s always nice to know that, usually, Occam’s Razor applies.

In this tutorial you will find some advice that will help you through some of the more common issues that can pop up with an Apache web server.

Is your server actually running?

Believe it or not, this has happened to plenty of administrators. You take the server down, do some maintenance, and when you go to check out the server you’re getting errors. The first thing you do, naturally, is check out that /etc/apache2/apache.conf file to make sure your syntax is correct. But it’s perfect! What’s up? The first thing you might want to check is to make sure the server is running. But you don’t want to just issue the command to start the server or reload the server. Instead, issue the command:

sudo /etc/init.d/apache2 status

Which should return something like:

* apache is running (pid 9751).

If not, start the server with either:

sudo /etc/init.d/apache2 start

or

sudo apache2ctl start

NOTE: If you are using a distribution like Fedora, SuSE, or Mandriva you will need to first su to the root user and issue the above commands WITHOUT using sudo.

It’s not running and it won’t start

Did you just make changes to your Apache configuration file? Are the changes correct? If you’re not sure, you can use the apache2ctl command to check the syntax of your configuration file. This is done with the command:

sudo apache2ctl configtext

The above command should report:

Syntax OK

If you don’t get an OK, you will get information that points to the errors in your configuration file.

Apache wants to download .php files!

This is another common issue. When you add a new tool on your web server (such as Drupal), if your configuration file is set up properly, any .php file might not be displayed. Instead any attempt to view a .php file will instead have your browser trying to download the file. Why is this? Apache must be informed that certain extensions are to be displayed, not downloaded. This is done from within the Apache configuration file. Open up that file (in the Ubuntu server it will be /etc/apache2/apache2.conf) and first look for the following line:

DirectoryIndex index.html

If that file doesn’t include index.php nearly all sites that use php will be rendered useless.

The second line to look for is:

AddHandler application/x-httpd-php .php

If you find this line, and it is commented out, make sure you uncomment it by removing the “#” character. If it is not there add it to the bottom of the configuration file.

And, as always, when you make a change to the configuration file, restart Apache.

Know where to look for problems

Finally, it is crucial that you know where to first turn when the above doesn’t help you out. Any time I have an issue with Apache where Occam’s Razor does not apply, the first place I turn is the log files.

If you look in /var/log/apache2 you will find, at least, the following files:

• access.log: This keeps track of any connection made to your server.
• error.log: This keeps track of any errors that occur with Apache.
• other_vhosts_access.log: This is where virtual hosts will log when the virtual host has not been prescribed its own log file.

Of course, as your site evolves so will your available log files. Regardless of what you find in /var/log/apache2, that is where you should always first turn when you have problems. Even before you google.

Final thoughts

Now you should be able to handle some of the more common issues with the Apache server. And if your problem isn’t common, you also know where to turn to find clues that will lead you down the right path to correction.

Related posts

• Portable Web Server (8)
• Local Apache Web Server Wampserver (3)
• How to: Install a LAMP server (6)
• Host your own webserver (18)
• Wordpress template tags you should know (4)

Because of these changes, the Mandriva of today is not the Mandrake of yesterday. The latest version of Mandriva (named 2010) is a modern take on the Linux distribution and in this article you are going to be treated to a walk through of the installation. NOTE: This installation will be done via VirtualBox, so some of the information you might see may or may not apply to your installation.

This installation will be accomplished with the help of the Live CD. You can download the Live CD from the Mandriva download page. You will notice, on that page, there are a number of different downloads. For this installation the download you want is the One 2010 download. Once you have downloaded that Live CD and burned it onto disk, put that disk in your target machine’s disk drive and reboot the machine.

Unlike most Live CDs, with the Mandriva Live CD you will have to answer some questions as well as agree to a EULA. This always takes me by surprise, but it’s a necessity if you want to boot up Mandriva. So agree to that EULA and boot up the Live distro.

Once you are up and running you will see the Install icon on the desktop. Double click that icon to begin the installation. And, of course, the first screen you will see is the inevitable “Welcome” screen. You can just click the Next button to actually begin the installation.

Figure 1

Partitioning

The first work you will have to take care of is the partitioning of your drive. Figure 1 shows the user-friendly configuration tool. With this tool you can either choose to use the free space (the easiest method), or you can create your own, custom partition configuration. As you can see (in Figure 1) this is being installed on a Virtual hard drive 16 Gigs in size. Since this space hasn’t been partitioned, it sees it as free space. So I will select the Free Space option and click the Next button.

Unused hardware support

Figure 2

This is a feature unique to the Mandriva installation. Once you have partitioned the hard drive the installation will compare the available hardware against the installable packages. Any packages that would not be used by the available hardware are not installed. This ensures your kernel will not be loading unused modules which will only slow down boot process, take up space, and use battery. Figure 2 shows the this screen. Just click Next and allow this process to happen. This will take some time (depending upon the speed of your hardware and the amount of packages that will not be installed).

Figure 3

Installation progress

After you hit the Next button you will immediately see the installation progress window (see Figure 3). Depending upon your hardware, this could take some time. Of course you will also be greeted by different information windows during this step. You will learn nothing new by watching…so grab yourself a soda or go play some WoW for a bit and come back when the installation progress reaches its goal.

Figure 4

Bootloader

After all of the packages have been installed you will have to deal with the bootloader installation. Your best bet is to stick with the defaults. If you load the bootloader on the wrong disk your installation will not boot.

As soon as you click the Next button you can then add, delete, or modify all of the entries in your boot menu. This is another section of the installation process that you should leave to the defaults. The only reason you would want to modify any of this information is if you are dual booting or you need to pass specific parameters to Grub for one of your entries. But more than likely, this step will be left to the defaults, so just click the Next button in this window as well.

The final installation window is the bookend for the Welcome screen – the Congratulation screen. This window will inform you to remove your Live CD and reboot your machine. Do this to complete the installation process.

Final steps

Figure 5

Of course you are not completely finished. Did you notice something missing from the installation process? No root password was created and no users were created. Both of these steps are taken care of post-installation. In fact, both configurations are taken care of in one screen (see Figure 5).

After you complete this step, click the Next button only to find yourself on one more screen. This final screen wants you to register with Mandriva, take a survey, and contribute to Mandriva. You can decline all of this if you like by scrolling down and clicking the Decline buton.

After you either decline or complete the various optional information you will finally get to log into your newly installed Mandriva 2010 Linux installation. congratulations, you are the proud user of an outstanding, user-friendly Linux box.

Related posts

• Why Every Windows User Needs a Linux Live CD (0)
• Ubuntu Privacy Remix (3)
• Testdisk – A Free Data Recovery CD (0)
• Run Linux Live CDs In Windows (4)
• Remastersys: Outstanding solution for backup and custom Live CDs (2)

And what’s best is you don’t have to jump through a bunch of hoops to get munin up and running. In this tutorial you will see how to get your Munin server up and running and monitoring your system and a sample client configuration that will monitor a client node. As you might expect, I will continue to build upon the Ubuntu Server series and install Munin on a Ubuntu 9.04 installation. NOTE: This same installation will work on Ubuntu 9.10 as well.Server installation/configuration

Installing Munin on the Ubunter server is simple. Open up a terminal window (or log into your server console) and issue the command:

sudo apt-get install munin

The above command will also install munin-node which is the client-side software. This is fine, so let it happen. Upon installation Munin will install the configuration files in /etc/munin, the executable in /etc/init.d/, and the web files in /var/www/munin.

The first thing that will need to be done is to configure your server correctly. Open up the /etc/munin/munin.conf file and look for this section:

dbdir     /var/lib/munin
htmldir    /var/www/munin/
logdir     /var/log/munin
rundir     /var/run/munin

Out of the box, this will work just fine.  But if you have any other needs that would dictate any of these directives change, change them here.

The next section to look for is this:

# a simple host tree
[localhost.localdomain]
address 127.0.0.1
use_node_name yes

What the above section does is monitor the server Munin is installed on. This configuration only needs to change if you have specific requirements. Also, if you need to add a client (node), this is where you add it.

In order to instruct Munin to monitor a remote machine you need to add a new host tree. Say, for instance, you want to monitor a machine on the IP addres 192.168.1.150. To do this you would add:

[MACHINE NAME]
address 192.168.1.150
use_node_name yes

Where MACHINE NAME is a name to indicate the job (or user, or department, etc) of the machine.

Once you have these configurations and save the file. Now to move on to the /etc/munin/munin-node.conf file. There is only one configuration you would need to add in order to monitor nodes. Look for this line:

allow ^127\.0\.0\.1$

Beneath this line you will want to add (in order to enable our new node):

allow ^192\.168\.1\.1$

Save this file and restart the Munin server with the command:

/etc/init.d/munin restart

Installing for client

All you need to do for your client is to install the munin-node package. To do this issue the command:

sudo apt-get install munin-node

On the client machine. Now start munin-node with the command:

sudo /etc/init.d/munin-node start

Munin will begin to monitor this client now.

The graphs

When all is up and running, point your browser to http://ADDRESS_TO_SERVER/munin/

Figure 1

Where ADDRESS_TO_SERVER is the actual address of the server. Very shortly after you install Munin you may only see a listing of the nodes being watched (see Figure 1). This is okay, it will take some time before data is actually collected.

After a while you will notice data collected and graphs developing. If you click on the localhost.localdomain link you will see data beginning to collect (see Figure 2).

Figure 2

Final thoughts

Munin is a very powerful tool that allows you to gather crucial data about your systems and networks. Now that you have Munin installed and running you can begin to extend the server by adding more and more clients as well as plugins. You will quickly find Munin to be a very valuable tool for data analysis on your various systems and networks.

Related posts

• How to install Nagios on Ubuntu server (10)
• With Ubuntu 9.10 Arrives Wubi 9.10 (1)
• Why you should switch your parents pc to ubuntu (19)
• Which Ubuntu Derivative Is Right For You? (15)
• What makes Ubuntu so user friendly? (47)

Because different distributions handle this task differently, we will examine how Fedora (and friends) handle the task and how Ubuntu (and friends) handle the task. As well we will also examine a neutral method that can always work in a pinch. All three methods will be command line, so stretch out those fingers and get ready to type.

Fedora (and friends)

The Fedora distribution uses the chkconfig command to update and query system run-level information for system services. The usage of this command is:

chkconfig OPTIONS SERVICE ON/OF

Where:

• OPTIONS are the various options the command offers.
• SERVICE is the service you want to add at startup.
• ON/OFF is either on or off – depending on if you want the service to start or not.

The confusion with the chkconfig command generally boils down to runlevel. The typical Linux runlevels are:

• 0 – Halt
• 1 – Single user mode
• 2 – Multi user mode
• 3 – Multi user mode with networking
• 4 – Not used
• 5 – X11
• 6 – Reboot

So with chkconfig you can also define at which point the service starts. So let’s say you want Apache to start at boot and you want it to start for levels 3, 4, and 5. For this you would issue the command (as the root user):

chkconfig –level 345 httpd on

Now, if you don’t want Apache to run at boot you could issue the command:

chkconfig httpd off

If you want to know what services are running at boot you can issue the command:

chkconfig –list

The above command will list out all services that are starting at boot time.

Ubuntu (and friends)

Ubuntu (and friends) takes a totally different route to the same destination. Instead of using chkconfig Ubuntu uses the update-rc.d command. This command makes things pretty simple. The command structure is:

update-rc.d SERVICE OPTIONS

Where OPTIONS are available options and SERVICE is the service you want to start.

With update-rc.d there is an option that makes it simple: defaults. So to add sshd to the start up process, you would issue the command:

sudo update-rc.d sshd defaults

To remove the same service from start up you would issue the following command:

sudo update-rc.d sshd remove

Now let’s take a look at a fail safe, nearly-universal method

rc.local

There is another means of getting a service to start. I recommend using either of the two above before you try this means. The rc.local file is a file that is executed at the end of the multiuser runlevel. By default, this script does nothing, but you can add to it so that it does.

Say you want Apache to start at boot up, and you want to do so from rc.local. You can do this by adding one of the following lines at the end of your /etc/rc.local file.

Fedora:

/etc/init.d/rc.d/httpd start

Ubuntu:

/etc/init.d/apache2 start

Save that file and you should be good to go. If you change your mind and do not want that service to start at boot, just remove the line you added.

Final thoughts

The above should allow you get that service that needs to start at boot working correctly. Make sure, however, you use the distribution-prescribed method before you use the rc.local method.

Related posts

• Get To Know Linux: The /etc/init.d Directory (4)

One would think that an easy task. It actually is, once you know how it is done.  And in this article I am going to show you two different ways of making the connection to your Samba server. You will need to have a working knowledge of how the Samba server is set up as well as a username/password configured on the Samba server. There are also a few steps to take on the desktop for one certain method of connection.

The two methods I will describe are: Using GNOME’s Connect To Server dialog and the command line. The latter will be used to show you how to set up auto mounting for Samba.

The graphical method

Figure 1

If you take a look at the GNOME Places menu you will see an entry labeled “Connect to server…”. This is what you want to use in order to connect to your Samba server. When you click on that a new window will open. From the Service type drop-down select “Windows share” (see Figure 1).

When you select that entry some of the configuration options will change. As you can see (in Figure 1), I have entered the necessary options to connect to a Samba server on my internal network. You will want to replace the information so it reflects your needs. The only tricky bit of information might be the Folder entry. If you are connecting to the root directory on the share you will not need to enter anything there. Say, for instance, you share is /media/samba/user. If you want to connect to that directory leave the Folder entry blank. Say, however, you want to connect directly to a sub-folder within that share – you can enter that folder here. This, of course, isn’t needed because you can always traverse the sub-directories with simple navigation. You can also choose to add a bookmark instantly, from in this window.

Figure 2

Once you have all of the information entered click Connect and you will be greeted with a new window that requires you to enter a password. Also, if you do not supply a Domain name in the previous window, you will be required to enter it here.

You can also set this up to remember your password either until you logout or until, well, forever. Once you have entered the password/domain click the Connect button and a new Nautilus window will open inside of your Samba Share.

Using the command line

Now we’re going to use the command line to accomplish a similar goal. The biggest difference is that we are going to actually mount the Samba share into another directory, very much the same way we would mount a second hard drive.

There are a few pieces to put together before we actually take care of the mounting. First let’s create a directory that the Samba share will be mounted to. So from the terminal window issue the following command:

sudo mkdir /media/samba

Now let’s make sure our users can read/write to this directory with the command:

sudo chmod -R u+rw /media/samba

Okay now let’s make sure we can see the Samba shares from the command line. We’ll do that with the smbclient command like so:

smbclient -L //SAMBA_SERVER_ADDRESS

Where SAMBA_SERVER_ADDRESS is the actual IP address of the Samba server.

Figure 3

You will be prompted for your username and password. If you get an error it could be that the usernames don’t match on each end. If that’s the case you could add the -U switch to the command like so:

smbclient –user=jlwallen -L  //SAMBA_SERVER_ADDRESS

You should see output similar to that shown in Figure 3.

Now it’s time to try to mount the Samba share to the /media/samba directory. To do this issue the command:

sudo mount -t cifs //SAMBA_SERVER_ADDRESS/SHARE -o username=USERNAME /media/samba/

Where:

• SAMBA_SERVER_ADDRESS is the IP address of the Samba server.
• SHARE is the share name.
• USERNAME is the username to connect with.

If that works you can now make this an automated mount by adding the following line to your /etc/fstab file:

//SAMBA_SERVER_ADDRESS/SHARE     /media/samba    cifs  credentials=/etc/samba/user.cred 0 0

Where SAMBA_SERVER_ADDRESS is the IP address of the Samba server and SHARE is the share name.

Notice the user.cred file. This is one last thing we need to create. With your text editor create this file and place into it:

username=USER

password=PASSWORD

Where USER is the username to log in with and PASSWORD is the password to use for authentication. The final step is the give this new file the proper permissions with the command:

sudo chmod 600 /etc/samba/user.cred

You can ensure this works by issuing the command mount -a which should mount your Samba share.

Final thoughts

You should now have an auto-mounting Samba share – or the ability to easily connect your GNOME desktop to a Samba share. Samba is a very powerful tool that not only can share files with Windows machines, but with Linux machines as well.

Related posts

• Set up your new Ubuntu Server as a Samba Server (3)
• Get To Know Linux: Understanding smb.conf (3)
• Auto mounting a Samba share in Linux (5)
• Simple GNOME Note Taking with Tomboy (1)
• Quick Archiving in GNOME (1)

CentOS is a community-driven spin off of Red Hat Enterprise Linux. This is different from Fedora in that it is not: 1) Not bleeding edge and 2) Geared toward Enterprise and not average desktop usage. CentOS is built to be 100% compatible with its bigger brother Red Hat Enterprise Linux while remaining a completely free operating system. In a nutshell CentOS is Red Hat Enterprise Linux without the branding and graphics. So, if you’re looking for an enterprise-class desktop operating system, and you do not want to spend the cash necessary for RHEL, CentOS is the distribution you’ve been looking for.

But how easily does it install? If you have ever installed Linux using the traditional installation disk method you will be just fine. It will, however, require some patience – and a torrent client.

Download and burn

The first, and arguably the lengthiest, step is to download the installation DVD (or you can download the 6 installation CDs if you do not have a DVD burner. Navigate your browser to the CentOS download page and navigate to the architecture you want to download. Once there you will click on the DVD torrent link which should hopefully open up your torrent client to begin the download. Once the torrent download is done (and the DVD is pieced together) burn the image to disk and you are ready to install.

Begin the installation

Obviously the first thing you will need to do is insert the DVD into the machine you wish to install CentOS on and then reboot. When you do you will be greeted with a text-based screen offering a few choices, since we are just going to go straight to the installation, hit Enter when prompted for installation. Anaconda will start up and the first graphical window will appear – the ever-pointless “Welcome” screen. Hit Next to finally begin your installation.

The next two windows are all self-explanatory (and not worth wasting screenshots on). You have:

• Language selection
• Keyboard selection

Figure 1

Now we get to the meat of the installation: The partitioner. The first phase of the partitioner (see Figure 1) requires you to:

• Choose a partition layout.
• Decide if you want the system encrypted.
• Select the drive(s) to use.
• Choose advanced storage options (Add iSCSI or disable dmraid).
• Review the partitioning layout.

When you select Next, depending on your choice of partition layout, you may be warned about deleting data. If you are unsure, make sure you go over the choices and dismiss the warning.

The next window requires you to set up networking. You have two choices: DHCP or Manual. The configuration of either choice is very simple. If you do set up your networking manually take note of the hostname. You can leave the default (localhost.localdomain) or you can be creative and add a descriptive hostname. Just don’t use an FQDN here as that could cause networking issues.

The new few windows are also self explanatory:

• Timezone
• Root password

Remember, this is not a Ubuntu-based installation. The root password is very important. Do NOT base this on a dictionary word. Use your best judgement for administrator passwords here.

Figure 2

The next screen (see Figure 2) is the package selection screen. You can go with the default, which will create a standard GNOME-based desktop installation. Your choices in this window are:

• Desktop – GNOME
• Desktop – KDE
• Server
• Server – GUI
• Virtualization
• Clustering
• Clustering – Storage

I will opt to shy away from the standard install and go with a KDE desktop (later I will deal with other options). You can also add additional repositories at this point and choose to customize now or later.  If you choose to add new repositories you will have to have an active network connection.

When you click Next the installation will check all dependencies and then move on with the install. When the dependency check passes (and it should), click Next and the installation of packages will begin. Depending upon how many packages you have selected (as well as the power of your machine) the installation time will vary.

Finally, once all packages are installed, you will be asked to Reboot your system. Click the Reboot button and remove the install DVD (the installer will auto-eject when able). The system will then reboot and you will have a working CentOS 5.4 installation. Oddly enough, if you go with KDE you will be surprised to find out CentOS has not updated to KDE 4.

Of course, upon first boot, you will have to take care of some house keeping. Included in this house keeping is:

• Enabling/configuring a firewall
• Setting up SELinux
• Setting time/date
• Creating a user
• Sound card test
• Install additional software (if applicable)

Final thoughts

Although the CentOS installation isn’t nearly as easy as installing from a Live CD, the installation process doesn’t require a degree in engineering to get through. And when you’re done, you will have a fine (although outdated in some instances) working Linux distribution that is geared toward (but not only for) enterprise use.

We’ll deal with CentOS more in the future (as well as other distributions). But for now, enjoy your installation.

Related posts

• Leave No Trace in KDE with Sweeper (6)
• Konqueror tips and tricks (2)
• Get To Know Linux: The Pager (4)
• Get To Know Linux: Process Management (1)
• Get To Know Linux: Desktop Environment vs. Window Manager (6)

The first thing you will want to do is check the Sane supported scanner listing on the Sane Project site. But don’t let your scanner not being on that list stop you. My Epson Perfection V30 was not on the list and I still managed to get it working with the help of iscan. The iscan package is a simple scanning tool for Epson scanners.  You can find the iscan tool within Synaptic. The iscan tool also integrates perfectly into The GIMP, so all your image needs can be met within one tool. But iscan is not the only option. There is also the Xsane tool, which is far more powerful than iscan. Let’s take a look at both of these scanning utilities to see how scanning is handled under the Linux operating system.

NOTE: This article is not going to cover getting your scanner to work under Linux. If your scanner is not listed in the Sane hardware listing, your best bet is to google your model numer and your distribution. For example, in my case I would google epson perfection v30 ubuntu 9.10. You should come up with results that will tell you what approximate drivers to use to get your scanner working.

iscan

Figure 1

We’ll first look at iscan. This tool is, by far, the easier of the two tools to use. And, like its bigger brother XSane, it integrates perfectly with The GIMP. That doesn’t mean you have to use iscan from within The GIMP. Once installed you will find iscan within the Graphics sub menu of the Applications menu. The entry will be called “Image Scan!” (No quotes). Or, if you’d rather, you can start iscan from within The Gimp by going to the File menu, then to the Create sub menu, and selecting the “Scanning (iscan)” entry. Both will start the iscan interface.

When you fire up iscan you will notice how simple the interface is (see Figure 1). This scanner utility is just as easy to use as any Windows or Mac utility. The only configuration option for iscan is your print command. That is how simple this tool is.

With your picture in your scanner hit the Preview button to first get a preview of your image. Once the image is up you can then select the portion of the image you want to scan, select the Destination (either file or printer), and click the Scan button. When you click the Scan button you will be asked to give the file a name. The scanner will then do it’s job and save the file for you. It’s that simple.

XSane

Figure 2

XSane can be found in your distributions repositories. So whether you use Ubuntu or Fedoar (or anything in between), you should be able to open up your distributions Add/Remove Software tool and find XSane easily. XSane, like iscan, is a graphical frontend for the Sane project. But XSane is a bit more serious of a tool. You can see (in Figure 2) there is much more to XSane than your average scanning tool. In Figure 2 you see the standard windows that open along with the Main window. Pictured are the  Main windows (far left), Preview window (center), Standard Options window (top right), and Histogram (lower right). You can also include an Advanced Options window, and a Batch Scan window.

But even with all of the extra options, acquiring a scan with XSane is just as simple as with iscan. Follow these directions:

1. Place your photo on the scanner.
2. Open XSane.
3. Click the Aquire preview button in the Preview window.
4. Adjust the size, rotation, and scale at the bottom of the Preview window.
5. Adjust the color in the Main window.
6. Select the file type in the Main window.
7. Adjust the scan resultion in the Main window.
8. Click the Scan button in the Main window.

When the scan is complete a new window will open that allows you to further adjust your image. In this window you can apply a despeckle or blur filter, adjust the geometry, rotate the image, clone image, do optical character  recognition, and save the image.

And what about the Histogram window? This window allows you to fine-tune the color of your image. You use this tool after you preview and before you scan. You will be suprised at how well you can perfect the color of your scans with this tool.

Final thoughts

For my preferences, I lean toward XSane to handle my scanning tasks. But iscan does the job quite well. Either tool will allow you to take advantage of that flatbed scanner you have in your office while using Linux. One less excuse to continue using Windows. ;-)

Related posts

• Document Scanning With Digital Cameras (5)

There are a number of possible applications that can take care of this task. In this article I am going to illustrate a few of those tools for you so you can choose which one is the right one for you.  So, without further adieu, let’s get on with the installation and usage. NOTE: All of these tools can be found and installed using the new Ubuntu Software Center. For more information on that tool, take a look at my article “The new Ubuntu Software Center“.

Gmail Notifier

Figure 1

The Gmail Notify  is a very innocuous panel applet that also pops up warnings when you have calendar event notifications set up . The setup of this applet is simple. When you first run the Gmail Notifier a windows will appear (see Figure 1) where you enter your Gmail username/password and configure any options you want. But ultimately all this little applet does is reside in your panel and checks your Gmail Account for new email and pops up alerts.

Make sure, during the configuration, you set your Browser path or when select “Go To Inbox” from the right click menu, no action will be taken.

This entry in the Gmail Linux desktop apps is one of the less flashy, but also less intrusive as, say, the Prism take on desktop Gmail.

Check Gmail

This entry in the desktop Gmail space is one of my favorites. One of the main reasons why I like this one so much is that it only takes a simple mouse over on the panel applet to see a full listing of your Gmail inbox. Now, before you even try to start this application up there is a problem. Out of the box the Check Gmail applet will not be able to log into your account. You will go batty trying to make sure you type in your password correctly. The problem is the executable file in /usr/bin. I’m not sure why the developer has not fixed this (the error has been known since 2007), but here’s the fix:

wget http://checkgmail.svn.sourceforge.net/viewvc/*checkout*/checkgmail/checkgmail
sudo mv checkgmail /usr/bin/
sudo chmod +x /usr/bin/checkgmail

Figure 2

Once you have done that, Check Gmail will be able to log into your account. Once logged in you will see a tiny red and white applet in your panel that you can right click to get a menu of items to select from (see Figure 2) or you can hover your mouse over to see the first few emails in your inbox and the first couple of upcoming events in your calendar (see Figure 3).

Figure 3

If you do a single left click on the icon your browser window will open for you to log into Gmail. If you right click and select Compose Mail you will also be first taken to the sign in page. Even if you configure Check Gmail to save your password you will still have to sign in to your account before you can read or compose. This is a bit of a frustration and should not be a default behavior. This even happens if you already have a Gmail window open that is authenticated to your account.It would also be nice if you could set the background of the pop up to be transparent so it would be a bit less intrusive, but the application is very usable.

Gmail Prism

What would be a listing of Gmail Apps without including an actual web-based app. I mentioned Prism in my article “Install Prism on Linux for easy to use web apps“. You will find the Prism app listed in Synaptic as Google Mail or Prism for Google Mail. Very little needs to be said about the Prism app other than it’s nothing more than a stripped-down browser window that logs you into your Gmail account. There is no applet to remain out of your way – just a window.

Which is best?

From my experience (and for my preference) Check Gmail gets the vote. Although it has some issues that must be overcome before it will work, once it is working it is the usable of the Gmail applications available. If you rely on Gmail, and check it regularly, you would do well to at least give one of the above a try.

Related posts

• Two Quick Email Tips To Save The Day (19)
• Offline Gmail Buzz (12)
• Gmail UI For Thunderbird (3)
• Are You Up For An Email Client With Unique Features? Read On! (16)
• Yahoo to offer unlimited Email Storage (8)

But can this tool take the place of the original tools? Can the Ubuntu Software Center usurp both Add/Remove Software and Synaptic? Let’s examine the tool and draw our conclusions.

The ultimate goal for the Ubuntu Software Center is to become a single point of focus for software management in Ubuntu. Effectively, the Software Center is going to become the Ubuntu version of the iPhone App Store. Here are the current and planned features:

• Install open source/free software (Version 1).
• Install commercial/non-free software (Version 3).
• Rate and review software (Version 2).
• Replace Synaptic and Gdebi (Version 2).

So by Version 3 the Ubuntu Software Center will be a total one-stop shop for Linux software installation in Ubuntu. Exciting times indeed. But right now we’re at Version 1 and the big question is, does it stand up to previous tools. Let’s take a look.

The interface

Figure 1

When you fire up the Ubuntu Software Center (done by clicking on the entry in the Applications menu) the main window is laid out very clearly (see Figure 1) will be the Banshee (since it has been referenced a number of times on Ghacks.)

To locate Banshee either click on the Sound & Video category (from the main page) or enter “banshee” (no quotes) in the search field and hit Enter.

Figure 2

When the listing appears, select the entry, and click on the right-pointing arrow that appears (see Figure 2). When you click that arrow you will be presented with an information window that allows you to either install the software or visit the software’s web page.

Figure 3

In order to install the selected software, click on the Install button (see Figure 3) which will require you to enter your sudo password. Upon entering your password a new pane will open up showing the progress of the installation. Depending upon the size of the application, this progress could take a while. The speed of the download will also be directly effected by the newness of the 9.10 release and how busy the repositories are.

Once the software is installed you will be returned to the information window that will look a bit different. Where the “Install” button was is now a “Remove” button and, if available, a screenshot will appear.

Adding repositories

Where adding new software sources in Synaptic could be somewhat confusing to new users, adding these same sources in the Software Center has become incredibly easy. All you have to do is follow these steps:

1. Click on the Edit menu.
2. Click the Software Sources entry.
3. Enter your password if you haven’t already authenticated.
4. Click on the Other Software tab in the Sources window.
5. Click the Add button.
6. Enter the entire line (the same line you would add to the /etc/apt/sources.list file in the text area).
7. Click the Add Source button.

You’re done. You no longer have to enter multiple pieces of information for a repository to be added.

Final thoughts

At first I was skeptical about the new Software Center. But after using the tool, and seeing where the tool is heading, I like what I am seeing (and using). I think Ubuntu is going to have a major hit on their hands with the Software Center.

Related posts

• Adding Repositories to Synaptic (1)
• With Ubuntu 9.10 Arrives Wubi 9.10 (1)
• Ubuntu Karmic Koala preview (22)
• Synaptic tips and tricks (3)
• Installing Flash in Ubuntu 9.04 with Firefox (23)

The Firefly Media Server (formerly mt-daap) is a fast DAAP server that is simple to install and even easier to configure. Firefly resides on a single Linux machine that doesn’t have to be a powerhouse. In fact, you can install this lightweight server on Ubuntu Server and you’re almost ready to go. In this article you will see how to do just that – install and configure Firefly Media Server on Ubuntu Server.

Features

The Firefly server has all of the features you will want in a DAAP server:

• Supports Unix/POSIX
• Beta for Windows in the works
• On the fly transcoding of OGG, FLAC, Apple Lossless, and WM
• User-created smart playlist support
• Integrates with iTunes and many other DAAP-supporting media players
• Serve streaming radio stations

Installation

Since we are installing on a Ubuntu Server, the installation is simple:

1. Open up a terminal (or just log into your servers’ console)
2. Issue the command sudo apt-get install mt-daap
3. Enter your user password

That’s it. Now it’s time to set it up.

Configuration file

There is only one configuration file for Firefly: /etc/mt-daapd.conf. This file is quite easy to set up. For a basic DAAP server, out of the box, there is really only one option you must configure. If you open up the configuration file look for the line:

mp3_dir = /home/media/music

This is the line you will need to change to reflect the directory you will serve your media from. For my setup I created a new sub-directory in /opt called music. Do this with the command:

sudo mkdir /opt/media

Now you have to make that directory readable by the DAAP server with the command:

sudo chmod ug+r -R /opt/media

Now all files and sub-directories created with the /opt/media directory will have the proper permissions such that the DAAP server can serve up the files.

Of course what you have just set up is a very basic DAAP server. There are a lot of other options within the configuration file you can set up, such as:

• servername: This is the name your DAAP server will broadcast. By default the server will be listed as Firefly RELEASE_NUMBER HOSTNAME (Where RELEASE_NUMBER is the release number of the Firefly installation and HOSTNAME is the hostname of the server.)
• password protection: This will cause any user attempting to access the DAAP server to have to enter a password in order to see the files.
• port: If you need to use a port other than the default (3689), configure it here.
• extensions: The file types you want to allow to be served by your DAAP server.
• Valid codectypes: These are the configurations for the format conversion. There are already lines for this in the configuration file – you just have to uncomment the ones you want to add for internal conversion.
• rescan_interval: If you want to enable background scanning you need to uncomment this entry and set an interval. This will enable you to add new files without having to restart the DAAP server to pick up the new files. Very handy if you frequently add new files.

There are other configuration options, but those are the ones you will want to focus on first.

Start the daemon

After your configuration file is complete, go ahead and move your media files into the directory and then start the server with the command:

sudo /etc/init.d/mt-daap start

With the server up and running you can fire up a DAAP enabled client, like iTunes or Songbird (Note: Songbird requires the addition of a DAAP add on), and you should automatically see the files on the DAAP server.

Final thoughts

Setting up a DAAP server is a great idea for a small internal network where you want to be able to share out a multi-media library. Anyone looking to set this up, and has a Linux server up and running, would do well to give Firefly a try. The simplicity, size, and speed of this server makes it the perfect candidate.

Related posts

• Songbird 0.7 RC1 Released (3)
• iTunes Music Server pulpTunes (7)
• Winamp iPod Plugin (5)
• View and Edit information of songs with More Tunes (1)
• The Complete Media Player Review (Part 1) (15)

Of course, ideally, you will want to install XBMC on a machine intended for multi-media use. It will work on lower-end video cards, but the interface will be somewhat slower. For a complete listing of supported hardware check out the XBMC hardware page. Now, let’s get on with the installation.

Ubuntu

I will give you a warning here: The most recently supported Ubuntu is 8.10. That does not, however, mean it will not install on anything later. I have XBMC installed and working fine on Ubuntu 9.04. With that in mind here are the installation steps for Ubuntu.

Open up your /etc/apt/sources.list file and add the following to the end:
deb http://ppa.launchpad.net/team-xbmc-hardy/ubuntu hardy main
deb-src http://ppa.launchpad.net/team-xbmc-hardy/ubuntu hardy main

Save that file and then issue the command:

sudo apt-get update

Once the update is complete issue the following command:

sudo apt-get install xbmc

If you want to install extra skins, issue this command:

sudo apt-get install xbmc-skin-*

Figure 1

You will find the XBMC menu entry in the Sound And Video sub-menu of the Applications menu. When XBMC opens you will see a very user-friendly interface (see Figure 1).

Now it’s time for a less than user-friendly installation. Because there have been no rpm files created for Fedora, the installation requires a number of steps which will lead you to compiling XBMC. These steps will work for Fedora 8, 9, and 10 as well as CentOS 5.2. Here we go. NOTE: You will need to be the root user for this installation.

If you don’t already have Subversion install, do so now with the command:

yum install subversion

Once Subversion is installed, check out XBMC from subversion with the command:

svn co https://xbmc.svn.sourceforge.net/svnroot/xbmc/trunk

Now install the rpmfusion repository with one of the following commands:

Fedora:

rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm

and

rpm -Uvh http://download1.rpmfusion.org/nonfree/fedora/rmpfusion-nonfree-release-stable.noarch.rpm

CentOS 5 (32 bit):
rpm -Uvh http://apt.sw.be/redhat/e15/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.e15.rf.i386.rpm

CentOS 5 (64 bit):

rpm -Uvh http://apt.sw.be/redhat/e15/en/x86_64/rpmforge/RPMS/rpmforge-release-0.3.6-1.e15.rf.x86_64.rpm

Now the fun begins. This installation command is all one line:
yum install SDL* glew glew-devel libmad-devel tre tre-devel libogg libogg-devel libvorbis libvorbis-devel boost boost-devel bzip2-devel bzip2-libs fribidi* lzo lzo-devel mysql-libs mysql-devel jasper jasper-devel faac faac-devel enca enca-devel hal hal-devel hal-libs cmake gperf nasm libXmu-devel fontconfig-devel freetype-devel libXinerama-devel pcre-devel gcc-c++ sqlite-devel curl-devel mysql-devel libcdio-devel libmms-devel faad2-devel flac-devel libsmbclient-devel libXtst-devel

The next step creates a symbolic link for the libmysqlclient.so file. The command is one of these two (depending upon your architecture):

For i386:

sudo ln -s /usr/lib/mysql/libmysqlclient.so.15.0.0 /usr/lib/libmysqlclient.so

For x64:
sudo ln -s /usr/lib64/mysql/libmysqlclient.so.15.0.0 /usr/lib64/libmysqlclient.so

Now cd into the XBMC directory (should be in the directory you are currently working in) and issue the following commands:

./bootstrap

and

./configure

and

make

If you see an error related to jpegint.h, then you might have to issue the following command:

cp XBMC/xbmx/lib/cximage-6.0/jpeg/jpegint.h /usr/include

If you have to issue the above command, then issue the make command again.

Finally issue the command:

make install

And XBMC will install.

On Fedora distributions you might have an issue with SELinux. If so you will need to issue the following commands:
chcon -t textrel_shlib_t '/usr/local/share/xbmc/system/players/dvdplayer/avutil-50-i486-linux.so'
chcon -t textrel_shlib_t '/usr/local/share/xbmc/system/players/dvdplayer/avcodec-52-i486-linux.so'
chcon -t textrel_shlib_t '/usr/local/share/xbmc/system/players/dvdplayer/avformat-52-i486-linux.so'
chcon -t textrel_shlib_t '/usr/local/share/xbmc/system/players/dvdplayer/swscale-0.6.1-i486-linux.so'

That’s it for the Fedora/CentOS installation. You should find XBMC in your Video menu. If you can’t seem to find a menu entry you can always enter xbmc in either a terminal window or the run dialog.

Final thoughts

XBMC is an outstanding media center software. It will play your CDs and DVDs flawlessly. If you have the hardware for this software, it is a much better solution than most other Linux video solutions.

Related posts

• Xbox Media Center Cross Platform Alpha (2)
• XBMC Media Center Final (13)
• The perfect multimedia device (3)
• Ten Video Sharing Services Compared (1)
• SMPlayer 0.5.51 (17)

In this article I am going to show you a few tips and tricks that you can apply to the Konqueror web browser to make your Konqueror (and KDE) experience even more flexible and powerful than it already is.

KIO Slaves

KDE Input/Output slaves allows Konqueror to take advantage of external applications making it far more usable. Depending on what kio_slave you want to use the input for Konqueror will be different. Let’s take a look at some of the more useful slaves.

fish://

If you start an address with fish:// you are telling Konqueror to make use of the ssh protocol. With this you can connect to a remote ssh server and even copy/paste to that server from within Konqueror. To do this you would enter an address like:

fish://USERNAME@ADDRESS

Where USERNAME is an actual username on the remote machine and ADDRESS is the actual address of the remote machine. You will be prompted for a password, unless you already have this connection set up for passwordless secure shell connections (see “Five handy secure shell tips and tricks“).

imaps://USER@PASSWORD@ADDRESS:PORT

Where:

• USER is the actual user name.
• PASSWORD is the users password.
• ADDRESS is the address of the imap server.
• PORT is the port used for the imap server.

Quick search

If you enter gg: linux in the Konqueror address bar you will get a page with the Google results of the string “linux”. Konqueror has a lot of pre-configured quick search shortcuts like this. For example:

• gg – Google
• fm – Freshmeat
• froogle – Froogle
• msdn – Microsoft Developer Network
• odp – Open Dictionary
• tr – Technorati
• wp – Wikipedia

You can also create your own by issuing the command kcmshell4 ebrowsing in either the run dialog or a terminal window. In the new window click the New button and then fill out the following information:

• Search Provider Name: Give your shortcut a name.
• Search URI: The URI the site you are adding uses.
• URI Shortcuts: Comma delineated list of shortcuts.

So let’s say I want to create a short cut for searching amazon.com. To do that I would enter the following information:

• Name: Amazon
• URI: http://www.amazon.com/s?url=search-alias%3Daps&field-keywords=\{@}
• URI Shorcuts: az,amazon

So now if I want to do a search for the string “Linux” on amazon.com I would just enter:

az: Linux

In the address bar.

Split views

Figure 1

Not only can Konqueror do tabs, it can do split windows. Say you want to do some comparing of windows, or just want to be able to see more than one window at a time. With Konqueror you can split the view either horizontally or vertically by going to the Windows menu and selecting either Horizontal or Vertical and you can have two windows open at once for simple viewing. NOTE: Whichever window has the focus is the window that the address bar will effect. In other words, if you want to change the page on the right pane, click on the right pane and then enter the url in the address bar. If you want to close a pane <Ctrl><Shift>R will close the active window.

Final thoughts

Konqueror is a very powerful, flexible tool that can be extended well beyond its intentions. Have you found a cool trick that applies to Konqueror as either a web browser or file manager? If so, share it with your fellow Ghacks readers.

Related posts

• Windows File Manager Free Commander (3)
• ScanDir Directory Lists Manager (1)
• Leave No Trace in KDE with Sweeper (6)
• Installing CentOS 5.4 (4)
• Get To Know Linux: The Pager (4)

Fortunately there is a tool for that. The tool? Spamassassin. Spamassassin is a very versatile SPAM tool that is part of the Apache Foundation. Spamassassin uses numerous means to detect SPAM including: DNS and Checksum based SPAM detection as well as Bayesian filtering, external programs, black lists, and online databases. These tools together make for a fairly powerful detection system.

In this article you are going to see how to install and configure Spamassassin to work in conjunction with Postfix to further enhance your email server.

Installing Spamassassin

Obviously the first thing you need to do is install Spamassassin. You will find Spamassassin in the Ubuntu repositories. And since this entire series has been laid on top of a Ubuntu Server installation, that is quite convenient. So, to install Spamassassin, open up your terminal window and issue the following command:

sudo apt-get install spamassassin

There may or may not be some dependencies to install in order for the Spamassassin  installation to complete. Go ahead and OK those. Once this installation is complete you are ready to start configuring.

Configuration

Before we actually get to the configuration it is important to understand the SPAM scoring system. With Spamassassin, messages are tagged as SPAM only when they have enough SPAM-matching characteristics (according to a scoring level). The scoring level is 0-5, however it’s not as simple as saying a 0 means it is 0% SPAM. The system is set up so that every characteristic can add to the overall score. For example a message tested to find a base64 attachment does not have a file name filtered with both bayes+net will add 0.224 to the over all score of the message. When all of the characteristic scores are added up, if they exceed the default score you have set in the configuration file, that message is considered SPAM.

Now that you have a basic understand of how the scoring system works. Let’s start configuring Spamassassin.

The main configuration file is /etc/spamassassin/local.cf. The first option you want to configure is the default score. Look for the line:

# required_score 5.0

The first thing you want to do is uncomment that line (by removing the “#” character) and then changing the score. A score of 5 is pretty high and sure to be SPAM. Understand the more you lower that score the likely you are of missing message messages that are tagged false-positives. A score of 3.5 is a fairly reliable score that will catch a lot of SPAM but not a lot of false positives.

Above this line are a couple of other options that are important. The first is the option to set the option:

report_safe

To 0. This option can be set to either 0 or 1. A zero means that if a message is found to be SPAM the message will not be deleted, but instead the subject line will be rewritten to include a message marking it as SPAM.  This is handy to prevent users from losing important messages to false positives. This also allows you to set a lower score threshold.

To do this first look for the line:

# report_safe 1

Uncomment this line by removing the “#” character and then change the “1″ to “0″ (no quotes).

The next step is to uncomment the line:

# rewrite_header Subject *****SPAM*****

Now you can alter the “*****SPAM*****” section of this line to reflect what you’d prefer it to say. Just make sure it is clear to your users that a message with this rewritten subject line is most likely SPAM.

Now restart the Spamassassin daemon with the command:

sudo /etc/init.d/spamassassin restart

Configure Postfix

The last step is to set up Postfix to use Spamassassin. To do this open up the file /etc/postfix/master.cf and look for the line:

smtp     inet    n   –   –   –   –   smtpd

You need to alter this line to look like:

smtp      inet   n   -   -   -   -   smtpd -o content_filter=spamassassin

Finally, at the end of this file add the following:

spamassassin
unix - n n - - pipe
flags=R
user=spamd
argv=/usr/bin/spamc
-e /usr/sbin/sendmail
-oi -f ${sender} ${recipient}

Now all you need to do is restart Postfix with the command:

sudo /etc/init.d/postfix restart

Your mail server should now be scoring incoming message as SPAM or HAM.

Final thoughts

The mail server is a tricky beast. You have to ensure that users are getting their mail, but you have to make sure they aren’t receive SPAM or viruses. After completing this series of articles, you should have a pretty solid server running that will send out mail that is safe for users eyes.

Related posts

• Trap Spammers with Project Honey Pot (4)
• Tinymail Email Protection (18)
• Reduce Spam by using alternative Google Mail Address ? (8)
• Phishing Explained (4)
• Introduction Series Part 1: Spam (0)

Free File Sync is an Open Source file synchronization software that’s above everything else super-easy to use. The main interface is separated into a left and right column. Directories can be added to each column. The two main actions offered by Free File Sync are to compare or synchronize the directories and the files residing in them. A click on the Compare button at the top will generate a directory and file listing for every directory that has been added to the application.

All files and directories are displayed in both columns with a blank row in the opposite column if the file or directory does not exist there. Information about each file including its name, size and modification date are displayed in the table as well. Arrows in the middle indicate the action (e.g. overwrite file in the left column, copy file to the right column) are taken if the Synchronize button is pressed.

Statistics for each column are displayed in the footer listing the number of directories, files and the size of the data conveniently. There are also general statistics about the total number of files and folders that would be created if the user would synchronize the files. Several advanced options are available. The file synchronization program supports file filters and several different ways of comparing and synchronizing files. Files are initially compared by name, size and date which can be changed to a file content comparison instead.

Four different file synchronization options are provided by Free File Sync as well with automatic synchronization of both sides selected by default. This can be changed to mirror files that reside in the left folder to the right folder, copy or update files from the left to the right folder or a two way synchronization which synchronizes both sides simultaneously.

A batch job can be created using the parameters configured before. Batch jobs can be executed by starting the file synchronization software with the file name of the batch job as a parameter. This makes it also possible to add the file patronization as a scheduled task in the Windows Task Scheduler.

Free File Sync is easy to use. It takes only a few minutes the most to compare or synchronize files and another few to create a batch file to sync files regularly with little to no user interaction. The program is available at the Sourceforge website where it is available for 32-bit editions of Windows and Ubuntu.

Related posts

• VLC Media Player 1.0 Released (9)
• Open Office 4 Kids (11)
• Open Office 3.1 (17)
• Music Management Software Jajuk (6)
• Metamorphose File And Folder Renamer (1)

One of the best anti-virus systems for a Postfix server is ClamAV. This anti-virus tool kit is open sourced and can be used on all UNIX-like operating systems. It’s easy to install and effective. In this article we will be following our series started way back in the Installing Ubuntu Server 9.04 article. Of course we will be installing ClamAV on a Ubuntu server running LAMP and Postfix. With that in mind, let’s get busy!

Installation

The first thing to take care of is the installation of ClamAV. There are a number of tools you will need to install. Open up a terminal window and issue the command:

sudo apt-get install clamav clamav-freshclam clamsmtp

The above command should also pick up all of the necessary dependencies. The installation will also start the clamav daemon. You will restart that momentarily

Configuration

Once installed you have some configurations to take care of. There are three files you are going to have to edit:

• /etc/clamsmtpd.conf
• /etc/postfix/main.cf
• /etc/postfix/master.cf

The first file to configure is the clamsmtpd.conf file. The configuration in this file is simple. Look for the lines:

OutAddress: 10025

127.0.0.1:10026

Change them to:

OutAddress: 10026

127.0.0.1:10025

That’s it for the clamsmtpd.conf file. Now let’s move on to the heavier configurations.

Open up the /etc/postfix/main.cf file. Scroll down to the bottom of this file and add the following:

content_filter = scan:127.0.0.1:10025

receive_override_options = no_address_mappings

Save that file and now move on over to the /etc/postfix/master.cf file. Again, scroll down to the bottom of this file and add the following:

# AV scan filter (used by content_filter)
scan unix - - n - 16 smtp
-o smtp_send_xforward_command=yes
# For injecting mail back into postfix from the filter
127.0.0.1:10026 inet n - n - 16 smtpd
-o content_filter=
-o receive_override_options=no_unknown_recipient_checks,no_header_body_checks
-o smtpd_helo_restrictions=
-o smtpd_client_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o mynetworks_style=host
-o smtpd_authorized_xforward_hosts=127.0.0.0/8

Save that file.

Restarting

The first thing you need to do is restart Postfix with the command:

sudo /etc/init.d/postfix restart

Once that has restarted you need to restart clamsmtpd with the command:

sudo /etc/init.d/clamsmtpd restart

Now, if nothing has gone horribly wrong, you should have a virus protected Postfix mail server.

Updating signatures

You should never go without updating your virus signatures. This is critical for keeping your mail server virus-free as new viruses are created or old viruses mutate. Fortunately ClamAV has its own tool for this. You will need to go back to that terminal window and issue the command:

sudo freshclam

Which will update the signatures.

You might even add the freshclam command into the root users crontab for regular signature updates.

Final thoughts

Your Postfix mail server is getting better and stronger each day. Adding anti-virus is a critical step in the grand scheme of Postfix things. In our next addition to the Postfix series, we will add Spamassassin for anti-spam measures.

Related posts

• What is your Security Concept ? (9)
• Test your Anti-virus program (10)
• Stop SPAM in Postfix with Spamassassin (1)
• Secure Windows XP (0)
• Mail relaying made simple with Postfix (0)

In this article you are going to learn how to install Postfix on your already running Ubuntu Server 9.04. I am going to assume you have it networked and have a domain registered that you want to use. At the end of this article you should have a working mail server, ready for use.

NOTE: For the purposes of this article, I will use the fake domain “www.ubuntumail.net”. You will want to use your domain in place of that.

The first step is to install the software necessary. Since you already have LAMP up and running all you will need to do is install Postfix and it’s dependencies. To do this open up a terminal and issue the following command:

sudo apt-get install postfix

The installation will not only install Postfix, but will start the Postfix daemon for you. You will most likely want to test this installation by running the old telnet test like so:

telnet localhost 25

You should see something like:
Trying 127.0.0.1...
Connected to www.ubuntumail.net.
Escape character is '^]'.
220 localhost.localdomain ESMTP Postfix (Ubuntu)

If you do, success! Now you are ready to take care of the configuration steps.

Configuration

There is only one file you need to deal with in Postfix. That file is /etc/postfix/main.cf. There really isn’t much to configuring this file (for a basic installation – which is all we are dealing with right now).

To set your Postfix installation up for your domain you will want to open that file for editing like so:

sudo nano /etc/postfix/main.cf

The above command opens main.cf in the Nano editor. What you need to look for is this section:

myhostname = ubuntumail
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = ubuntumail.net, ubuntumail, localhost.localdomain, localhost
relayhost =
#mynetworks = 127.0.0.0/8
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all

As you can see, I have already configured the above section to work with our sample domain. You will need to go through the above section and insert your domain where you see ubuntumail.net. You will want to pay close attention to the mydestination line. As you can see that line contains:

ubuntumail.net, ubuntumail, localhost.localdomain

This helps to avoid mailloops in Postfix.

Some people also like to use the mydomain parameter, but since mydomain is taken from $myhostname by removing the first part (unless that would cause the domain to be a top-level domain) it can be redundant. If, however, your mail server serves your entire domain, you will need to use the mydomain parameter. For that you would insert:

mydomain = ubuntumail.net

at the top of the section shown above.

Once you have that configuration saved, restart Postfix with the command:

sudo /etc/init.d/postfix reload

To reload the mail server.

Users

As this is a Linux box, you will want to make sure you have a user created for every email address you need to serve up. So create your users with your favorite user creation tool. Since you are most likely installing on a Ubuntu Server (sans GUI), you will be using the useradd command. You can accomplish this with the command:

sudo useradd -m USERNAME

Where USERNAME is the actual username you want to use. Next you will need to give the user a password with the command:

sudo passwd USERNAME

Where USERNAME is the actual username you want to use. You will be prompted to enter the password twice.

After you have entered the users, you can then test the mail server by sending an email from an external source to see if it arrives. If there is a problem make sure the first place you look is /var/log/mail.err.

Final thoughts

At this point you should have a basic, working mail server. Postfix does make this task much more simple than did Sendmail. In my next article I will cover adding Spamassassin to your Postfix mail server to keep SPAM from getting in.

Related posts

• Stop SPAM in Postfix with Spamassassin (1)
• Quickly check mails without downloading them (8)
• Mail relaying made simple with Postfix (0)
• Yahoo Mail, Search And Messenger Upgrades (2)
• Yahoo Mail Integrates Drop.io To Support 100 Megabyte Attachments (8)

Now IBM sees a developing market for more cost-effective solutions to the Microsoft Windows/Office combination. This solution (for which I hope they find a better name than “IBM Client for Smart Work”) will consist of:

• Lotus Symphony
• Lotus Live
• Lotus Notes

The difference between the Red Hat and Ubuntu versions is quite interesting. On the Ubuntu side the Lotus tools will be doled out via cloud. On the Red Hat side all tools will be on the desktop. To me this is smart marketing because it brings both Linux distributions together to work on a single project, but doesn’t pit each distribution against one another.

I believe that both of these solutions seems sound as well as outstanding alternatives to the current Windows environment. But what about the meat of the issue – the office suite? Does it work? Can it stand up to all the competition? This is where you decided. I will show you how this office suite is installed/used and you can kick those tires and see if it is a worthy opponent.

Installing

The first thing you need to do is go to the Symphony download page and download the version of the suite for your distribution. You will have to agree to a license as well as enter your name, email address, etc.

You can download for Windows, OS X, or Linux (Ubuntu, Red Hat, SuSE). The Ubuntu file will be a .deb file and both the Red Hat and SuSE files will be .rpm files.

Once you have downloaded the file you will open a terminal window, change into the directory containing the file, and issue one of these commands:

• sudo dpkg -i symphony*
• rpm install -ivh symphony*

The former command for Ubuntu and the latter command for either Red Hat or SuSE.

You will have to agree to a license during the install, but other than that the installation is a piece of cake.

Post installation

Once Symphony is installed, you can start the suite from the command line by issuing the command:

symphony

Or you will find a menu entry in the Office sub-menu of the Applications menu.

Symphony consists of three parts:

• Word processor
• Spreadsheet
• Presentations

Figure 1

You can not start the tools separately (reminiscent of the old Star Office suite) so when Symphony starts you will be presented with the Symphony desktop (see Figure 1).

From this desktop you can pretty much do anything you need. From creating a new file (click the icon associated with the type of file you want to work with) or open an existing file from the File menu.

I’m fairly confident that anyone reading this site can work their way around the basics of an office suite, so I won’t go into the details of how to use Symphony. In later articles I will discuss some of the “power features” of Lotus Symphony.

Final thoughts

If IBM plays their cards right they can take the Smart Work desktop and turn it into something that could seriously compete with Windows. This of course would be more in line with enterprise usage and not home/personal usage. I look forward to seeing how IBM continues their presence on the Linux desktop.

Related posts

• The reinventing of the Operating System (16)
• Opera Will Reinvent The Internet On June 16 (13)
• Install Prism on Linux for easy to use web apps (7)
• Hard Disk Low Level Format (15)
• Google Docs Shares Documents Without Permisson (3)

Having a tool that can quickly, and regularly, take snapshots of your network landscape is critical to keeping tabs on your PCs. Of course you can shell out some budget dollars for a proprietary tool, but why bother when you can fire up a Linux machine and use the trusty Nmap tool for the job.

Nmap is a command line tool that rapidly scans a network gathering information about machines and ports. It is easy to use and flexible, making it perfect for the job of asset scanning. In this tutorial you will see how to set up a system that will regularly scan your network and create a report that can then be used to keep inventory of your networked machines.

Installing

Before we get to the actual scanning we need to install a couple of applications. Since I am using a Ubuntu system, we’ll run the installation using apt-get. With some simple modifications, you can do the same on a fedora system. The two applications to install are: nmap and ndiff. We use ndiff to compare the results of scans. To install these applications open up a terminal window and issue the following command:

sudo apt-get install nmap ndiff

You will have to accept dependencies, at which point the two applications will install. Upon completion of the installation, you are ready to scan.

Using nmap

Nmap is actually a fairly powerful tool. If you issue the command man nmap you will see just how powerful this tool is. You can also see how many arguments you can use with Nmap as well as what each argument does. Fortunately I will show you a simple command you can issue to make this a bit easier.

I am going to illustrate how these tools work together by running an nmap scan on a small internal network. I will then scan the network after making a change to one machine and see if ndiff catches the change.

The command for the scan is:

sudo nmap -n -PN 192.168.1.1/24 -O > network_scan

I will then run that same scan after making the change with one alteration:

sudo nmap -n -PN 192.168.1.1/24 -O > network2_scan


The above commands will output to the files network_scan, and network2_scan.

Once you have the two files you will compare them using the ndiff command like so:

ndiff -b network_scan -o network2_scan

The two options used are:

• b – Baseline.
• o – Observed.

You can think of Baseline as your control group.

Figure 1

The results of the command are shown in Figure 1.

The results show exactly what occurred in my network change. I shut down the machine associated with IP address 192.168.1.37.

Of course you could also get a much clearer picture of your network by combing through the results of the initial scan, but if you are looking for how your network topography has changed from scan to scan, using ndiff is the best way.

To see the full usage of both nmap and ndiff, take a look at the man pages. I will warn you, they are fairly complex. But this tutorial should give you a solid understanding of how the basics of the tools work.

Related posts

• Port Scanning Networking Tool SuperScan (1)
• Map your network with Zenmap (1)