Upgrading a Dual-boot Fedora and other Operating System

This entry is part 3 of 3 in the series Upgrading Fedora

This article will cover the steps for upgrading a dual-boot Fedora/other operating system (in my case Ubuntu and Windows Vista), where the other operating system handles the GRUB Bootloader. As always the first thing you should do is back up everything. This protects you from losing your data, in case something goes wrong. Because I’ll be doing this on a live system, I won’t have screenshots for the process. However the steps and images should be the similar to a single boot installation. Because this is more complicated than a single-boot installation, I won’t go into any steps for upgrading a pre-Fedora 18 system (although it should work with Fedora 17 also). Personally I think if you’re using anything older than Fedora 16, you’re most likely better off doing a clean installation than an upgrade. But if you want to do an upgrade, you *should* be able to follow the steps for upgrading to Fedora 17/18 using pre-upgrade. But you’re doing this at your own risk.

In my particular case, the steps to upgrade follow these:

Boot into the Fedora 18 partition, and login as root (or use su).

Upgrade rpm as per the single-boot instructions

yum update rpm

Update the entire system, as per the single-boot instructions

yum -y update

Clean the yum cache, as per the single-boot instructions

yum clean all

Reboot, and check your GRUB to see if it includes the “System Upgrade (fedup)” option. If so, follow the single-boot instructions. If not, then follow these steps:

Boot into the operating system that handles GRUB (in my case Ubuntu).

Open a terminal.

If you’re using Ubuntu, you’ll update grub with sudo update-grub, otherwise you’ll follow the steps for whatever distribution you’re using.

Reboot and check GRUB to see if it includes the “System Upgrade (fedup)” option. If so, choose that. If not, repeat the above steps.

After the upgrade, the computer will reboot (at least it happened in my case). Check your GRUB to see if it’s updated for Fedora 19. If not, then you’ll have to boot into the operating system that handles GRUB and update it again.

Now you’ll be able to reboot into Fedora 19 or your other operating system(s).

Upgrading a Single Boot Installation of Fedora

This entry is part 2 of 3 in the series Upgrading Fedora

This article will cover the steps involved with upgrading a single boot installation of Fedora to Fedora 19. If you’re running an older version (pre- Fedora 17), you’ll have to upgrade to either Fedora 17 or Fedora 18 before you can upgrade to Fedora 19. The easiest way of doing that is with pre-upgrade (which will allow you to upgrade to Fedora 17 only) and then following these steps to upgrade using FedUp (the Fedora Update Manager).

If you’re running Fedora 17 or Fedora 18, these steps are for you. All of these steps are done using the root (or su) account. You can either do them from a text console (CTRL+Alt+F2 through F7) or from inside of Terminal in the desktop.

Step 1:

First you need to make sure that you have the latest version of rpm installed. You can do this by running

yum update rpm

Next you’ll want to do a complete update of your system. The easiest way to do this is with

yum -y update

(the -y bypasses it asking you if you want to update–assume “yes”). Check the list of updates after it’s completed to determine whether you have a new kernel or not.

After the update is complete, you’ll clean the yum cache using

yum clean all

If you had a new kernel in the list of updates, you’ll want to reboot and then login as root/su again.


After you’ve rebooted/cleaned the cache you need to install the FedUp package

yum install fedup

You’ll want at least 4 GB of free space available on your / drive. If you need to clear space do so before you start the upgrade.

When you start the upgrade, you can either use the network or iso method (network is preferred as it gets you all of the updates in one shot). To use the network option, you type

fedup-cli –network 19 (that should be two dashes – – not one long hyphen)

First, fedup will install it’s repositories and download it’s kernel images (vmlinuz-fedup and intramfs-fedup), and then it will check the updates needed. It will download these updates (I had 1,293 listed plus others afterwards) and prepare everything for the upgrade. One thing it does is change the GRUB listing to include the System Upgrade (fedup) option. When it’s ready to go, you’ll be prompted to reboot the system again. You’ll choose the System Upgrade (fedup) option to start the actual upgrade.



 Downloading Updates Screen


Ready for Reboot Screen


GRUB Bootloader Screen


The Upgrade Screen


The upgrade consists of both a graphical upgrade screen (the “f” with a progress bar) and a text-based upgrade screen (showing everything that’s happening). When it’s completed, you’ll be presented with the Fedora 19 login screen.

Setting up a Google Relay host using Postfix on Fedora 19.

When I set up my Amahi Home Server a few years ago, one of the things that I wanted to do was be able to send the logs and other emails that normally go to the root account to my gmail account. This way, I could quickly scan the information without having to actively log into the server. My options were to either register my own domain name and go through the steps to set up MX records and servers, or to relay it through another gmail account. I chose the second, since I already have the accounts, and registering and hosting the domain costs money (plus I’m already given a .yourhda.com domain with Amahi).

When I started to set up the relay, it took a while. I ended up finding quite a few sites on the Internet with different methods of configuring the relay (most of which didn’t work right). When I reinstalled my Amahi Server this past weekend (upgrading it to their latest version), I forgot to save the postfix configurations, so I had to redo them. Thankfully it was a simple matter this time. I’ve only done this on Fedora 14/19, but I’m pretty sure the steps will be similar, if not the same, for an Ubuntu based distribution. All of these steps are being done as the root (superuser) account. If you’re using your administrator account, you’ll have to precede each command with sudo.

Creating your Relay

If you haven’t done so already, you need to install postfix first.

yum install postfix

Next you need to open the /etc/postfix/main.cf file in your favorite editor (I use nano, but you can use whatever you prefer).

nano /etc/postfix/main.cf

At the bottom, add the following lines:

# sets gmail as relay
relayhost = [smtp.gmail.com]:587

# use tls

# use sasl when authenticating to foreign SMTP servers
smtp_sasl_auth_enable = yes

# path to password map file
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd

# list of CAs to trust when verifying server certificate
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt

# eliminates default security options which are imcompatible with gmail
smtp_sasl_security_options =

Next you’ll have to edit (or create) the sasl_passwd file that’s used in the postfix configuration above

nano /etc/postfix/sasl_passwd

The format of this file is this:

[smtp.gmail.com]:587 username:password

After creating this file, you need to run the postmap command to create the hash of the password file and then make sure that postfix owns the files (as they are created by root originally).

postmap /etc/postfix/sasl_passwd


chown postfix /etc/postfix/sasl_passwd*

Finally reload postfix using this command:

/etc/init.d/postfix reload

Testing your configurations

If everything worked correctly, you should be able to test your mail setup by sending an email from the command line.  There are multiple methods for this, but I’ll show you two of them here.

The first method uses the mail command. (you should be able to do this as either root or a regular user) youruser@emaildomain.com should be replaced with your intended recipient’s email address.

mail -s “Subject: Test email from linux server” youruser@emaildomain.com

The editor will open up, so you can type a message in the body. You’ll use CTRL+D to exit this editor.

Next, if you want to CC anyone, you can add their email addresses, and/or press CTRL+D to exit this portion.

The email should send. Check your inbox (and spam folders) to see if it’s arrived. If not, you can check /var/log/maillog (or in /var/log/mail) to find out what’s wrong.

The second method uses the echo command to send everything to the mail command for you.

 echo “Enter the body part of the email” | mail -s “Subject: Test email from linux server” youruser@emaildomain.com

If you want to CC someone else into the email, the format of the command is

 echo “Enter the body part of the email” | mail -s “Subject: Test email from linux server” youruser@emaildomain.com -c seconduser@emaildomain.com

Forwarding the root emails to your relay

Now this is all pointless unless you make sure that all emails destined for the root mailbox get forwarded to your external account. You could do this a number of ways (such as configuring each application that might send an email to your root to send them to the external account also), but the two easiest ways are to create a .forward file, or create an alias.

Creating a .forward file:

nano /root/.forward

Add the email address that you want to forward the emails to and save the file.


Note that this will bypass the root mailbox altogether. If you want root to continue to receive the emails, you have to add root to the file with the following format



Editing the aliases file and adding the root alias

nano /etc/aliases

Then add the following entry (replacing youruser@emaildomain.com with your external email address)

root: youruser@emaildomain.com

Finally run the newaliases command to make sure you’re using the updated version of /etc/aliases.


With that, you should be set up. Now anytime an application sends a message to root, you’ll receive it on your external email account as well. Please note that you’ll still need to log in and clean out the root mail account occasionally, as the messages are still being sent there.


Troubleshooting and Updates for Fedora 19

If you run into any issues with postfix, you need to check /var/log/maillog for problems. The easiest way to do this is with cat /var/log/maillog | tail and then attempt to resend your email that you used to test the configuration.

If you run into any issues, such as gmail rejecting your email with something similar to “530 5.7.0 Must issue a STARTTLS command first.” (and you have the smtp_use_starttls=yes command in your main.cf) file, you need to do the following things:

In main.cf, add the following line

smtp_tls_policy_maps = hash:/etc/postfix/tls_policy

then create a tls_policy file in /etc/postfix that has the following line

[smtp.gmail.com]:587 encrypt

Then run postmap /etc/postfix/tls_policy to create the hash of the file.

If you run into a warning or error similar to “warning: TLS library problem: 25188:error:02001002:system library:fopen:No such file or directory:bss_file.c:169:fopen(‘/etc/ssl/certs/ca-certificates.crt’,’r’):”, you need to change that line in main.cf to ca-bundle.crt. This is because Fedora 19 doesn’t have the ca-certificates.crt file anymore. It uses ca-bundle.crt instead. Something to note here is that after you fix the certificate issue, the email will send. So if you’re testing your configuration, you’ll end up with multiple test emails.


Fedora 19 Installation Guide with Screenshots

The Fedora Project recently released version 19 “Schrödinger’s Cat”, and because I may be using it to teach a course in the future (or a future release), I created an installation guide along with some screenshots. Full Disclosure, the basic outline of the guide came from an article on tecmint.com and the screenshots came from the Fedora Project’s documentation. There screenshots are a million times better than what I came up with.

Some caveats of course. You will be wiping data and applications from your computer and installing new applications. The operating system will change. If you want to dual-boot between Fedora and another operating system (most likely Windows), then you need to take some precautions before you start this guide. This guide is meant for someone who wants to wipe their computer and start over fresh.

If you’re planning on a dual- or more boot system, then my recommendation is to use one of your current operating systems to resize your hard drive. At a minimum you’ll want 25 GB of space available for Fedora (and you should know that you won’t be able to do much with that little space). Personally, I have Fedora installed on three computers as part of either dual- or triple- boot scenarios (and one as an Amahi Home Server). The minimum space that I gave Fedora was about 40 GB, knowing that I don’t plan on installing anything extra. The reason that I say to use one of your currently installed operating systems to resize the partitions is because it will definitely try to preserver your data (NOT that I don’t think Fedora would).

Also note that I’m providing download links to most (if not all) of the available versions of Fedora 19. The differences vary from the type of desktop environment that you’ll see, to whether or not you’ll even see a desktop environment.  My guide won’t go through to the actual desktop (if you want to see that, I recommend the tecmint article), so the steps will be the same regardless of which version you download (as long as you download a desktop version–not the Installation DVD or NetInstall CD).

So, without further ado, here we go:

Fedora 19 ‘Schrödinger’s Cat’ Installation Guide with Screenshots

Download Fedora 19 DVD ISO Images

Depending on which version of Fedora 19 you wish to install, you can find the downloads at the following links.

Download Fedora 19 DVD This is the complete installation DVD typically used for servers.

  1. Download Fedora 19 32-bit DVD ISO – (4.2 GB)
  2. Download Fedora 19 64-bit DVD ISO – (4.1 GB)

Fedora 19 GNOME Desktop This is the Gnome 3.x version of Fedora 19. It’s what the screenshots are based on.

  1. Download Fedora 19 GNOME Desktop 32-bit – (919 MB)
  2. Download Fedora 19 GNOME Desktop 64-bit – (951 MB)

Fedora 19 KDE Desktop This is the KDE version of Fedora 19.

  1. Download Fedora 19 KDE Live 32-Bit DVD – (843 MB)
  2. Download Fedora 19 KDE Live 64-Bit DVD – (878 MB)

Fedora 19 Xfce Desktop This is a minimalistic desktop environment. But still as effective as Gnome or KDE—just without the eye candy that they provide.

  1. Download Fedora 19 Xfce Live 32-Bit DVD – (588 MB)
  2. Download Fedora 19 Xfce Live 64-Bit DVD – (621 MB)

Fedora 19 LXDE Desktop This is another minimalistic desktop environment. It’s look is similar to the “Classic Windows” look from XP and other Windows versions.

  1. Download Fedora 19 LXDE Live 32-Bit DVD – (656 MB)
  2. Download Fedora 19 LXDE Live 64-Bit DVD – (691 MB)

Download Fedora Net-Install CD This CD provides you with the bare essentials to get started installing Fedora 19. If you do not have access to a broadband network, I don’t recommend this one.

  1. Download Fedora 19 32-bit Net-Install CD – (353 MB)
  2. Download Fedora 19 64-bit Net-Install CD – (317 MB)

Fedora 19 ‘Schrödinger’s Cat’ Installation Guide Steps

Step 1. Boot the computer with the Fedora 19 installation media. To install Fedora 19, press the ‘ENTER‘ key to Start Fedora 19, or it will start automatically. If you need specific troubleshooting options, you can choose ‘Troubleshooting’. Once Fedora 19 boots, you’ll be presented with the login screen below. You do not need to enter a password to log in at this screen. Also, if your computer goes to screensaver mode, you will be presented with this same screen.

bootscreen-livecd  livedesktop-login

Boot Fedora 19 Media Image

Step 2. Choose “Install to Hard Drive” to start the installation. Or you can choose the “Try Fedora” option to try it out, without making any changes to your computer. You’ll have to option to install from inside of the Activities menu. Either way, once you’ve decided to install Fedora 19, you’ll proceed on from here.


Choose Install Hard Drive Screen

Step 3. Select your language and click on “Continue“. You can also choose to automatically select the keyboard layout based on the language you select by clicking the appropriate check box near the bottom. If you don’t do this, you’ll have the option of choosing your keyboard layout later on.


Select Language Screen

Step 4. The next screen is the “Installation Summary” screen, where you’ll configure the location, date and time, keyboard, software packages (not available in the Live CD), network hostname, and storage. To make the changes, you’ll click on each option. If there are conflicts, you’ll see a yellow triangle and a warning at the bottom of the screen. The “Begin Installation” button will be grayed out until you’ve fixed any conflicts.


Fedora 19 Installation Summary Screen

Step 5. Date, Time and Time Zone settings.

If you need to change the Date and Time settings, click on “Date & Time” from the main summary screen. You can select your location (or a near-by city) from the drop-down lists or by clicking on the country. Then click on “Done” to return to the main summary screen. If you want Fedora to automatically update your time from Internet Time Servers, leave Network Time set to “On”, otherwise click it to turn it off. It’s recommended that you leave this on, unless you won’t be connected to the Internet.


Date and Time Zone Screen

Step 6. You’ll need to click on the “Installation Destination” option, and choose Installation destination i.e hard drive and click on ‘DONE‘. You should be prompted to select the type of installation after this. If it returns to the summary screen, come back in, and de-select then select your hard drive (by clicking on it), then click Done.


Choose Installation Drive Screen

Step 7. Next, you’ll see the Installation options, where you can view and modify your file-system as needed. In this post we will use automatic partitions. If you are dual-booting, you’ll want to review and modify your partitions manually.


Select Partition Type Screen


Manual Partition Screen (if you choose the “I want to review/modify my disk partitions before continuing” option).

Step 8. If you didn’t choose the option to automatically select your keyboard in the language settings, you can choose keyboard layout and click on ‘DONE‘.


Select Keyboard Layout Screen

Step 9. In the network configuration screen, you’ll enter your hostname and click on ‘DONE‘.


Network Configuration Screen

Step 10. Once everything is configured you can click the “Begin Installation“ button to start.


Main Summary Screen

Step 11. While the system is installing, you have the option to choose the Root password, and create a user.

Your password should follow these recommendations at a minimum to ensure security:

  • At least 8 characters in length.
  • Contains at least one upper-case character, one symbol, one number, and one lower-case character.
  • Do not use dictionary words (easily guessed) or publicly known information about yourself or people close to you (no pet names, anniversaries, nicknames, etc).


Installing Packages Screen

12. Click on Root Password to set your root password.


Add root Password Screen

Step 13. Click on User Creation to create your normal user. The recommendation is to make this user an Administrator, and create more “Standard” users after you’ve finished the installation. Otherwise, you’ll have to become “root” or “super user” in order to do any type of administrative tasks. If you follow this recommendation, you should use a “standard” user account for your normal day-to-day activities.


User Creation Screen

Step 14. Installation completed. Reboot your system after ejecting media.


Installation Completed Screen

My Annoyances in Ubuntu and Evolution

I recently installed Ubuntu 11.10 64-bit and Fedora 16 64-bit on my e-machines W3400 desktop (Yes, I know, why on an e-machines). There are a few minor issues that I have with the experience so far (at least in Ubuntu). Some are in Ubuntu itself, while others are in the Evolution email application. My hope is that someone from Canonical, Gnome, or the communities sees this. And that they will do something to fix these issues, or at least give me some guidance on why they are there. So here we go. Also it should be noted that I’ll probably be editing this post a lot, as I find other things. Ubuntu: 1. When installing a 64-bit version, there should be a check box to automatically install the 32-bit libraries. I shouldn’t have to google how to do it (ia32libs), nor should I have to rely on an application (Skype, for example) to do it for me. I realize that it’s just one application that you have to install. But, the average user won’t know this. They may (or may not) be able to find the information easily enough. And some of the information is outdated. All that would be required is a check box that says something like: Install 32-bit compatibilityThis will allow you to run 32-bit applications on your system. Required if the application maintainer hasn’t created a 64-bit version. or something similar. 2. WTF is the ‘white-list’ for in the indicator panel? Things that need to be there (read as Skype, amsn, pidgin) aren’t seen. I tried setting it to “‘all'” in dconf-editor, but it wouldn’t take. Setting it to ‘all’ in gsettings works (at least as far as what dconf-editor shows) but they still aren’t visible. I ended up having to add the cinnamon desktop manager to finally see my icons. And it didn’t work in XFCE/Xubuntu desktop either. Either set the white-list to ‘all’ by default, make it easier to configure this, or generate a list of applications that most likely need to be in the indicator panel–and when they are installed, add them to the white-list automatically. For reference, this is the “Systray” or “Notification Area” (XFCE). This would also make it easier for certain applications like HPlip to “find” the Systray and open properly. Evolution: 1. If I Choose “Mark As Read” from the folder menu, I have the option to never see the confirmation dialog again. However, if I right click on a folder name, I get the dialog box EVERY time. Either put the option in that box as well, or honor the choice made from the other box automatically. I mean it’s the same application, and the same option. If it were an application suite (like Office or LibreOffice) or an Operating System, you would expect “communication” between the pieces. So why not here? 2. One minor annoyance of mine is in the Preferences. The option to Sync mail locally with Remote folders (this isn’t the exact wording) is nice. But I think that it should be renamed to “automatically sync mail for offline viewing”–since that’s what it does. I thought that it was a way to keep my gmail account synced up without having to set it to automatically check for new messages… Nope. Well, technically it might work for that. 3. Something that I would like to see is an auto configure for mail accounts. For example, if my email address ends in @gmail.com, when I click “Next”, it should automatically set the imap server information (or pop). Granted, you would need to add a check box or radio button on the first page with either IMAP, IMAP+, or POP as options. But, it would be nice to save some time in configuring my accounts. I also realize that they would have to maintain a list of the more popular email providers (and their setup information). And that they would have to update this information whenever one of the providers (Google) decides to change their configuration settings. But, it would make life easier for the end user, and possibly encourage more people to use Evolution. I think that’s enough for now. As I mentioned earlier, I’ll have more in time. Have a great day everyone:) Patrick.

Moving to Linux– Ways to make the transition Easier (Part 2 of 2)

In Part 1, I started to describe the steps to ease the transition from Windows to Linux. This is all based on an article by Katherine Noyes at PC World (links are in Part 1). Now I will continue with the next three steps.

4. Give the end-user a way out. What this means is in the beginning, I would suggest a dual-boot setup. Make sure that the GRUB Screen shows up for at least 10 seconds. DO NOT wipe out any restore images on the drive. This way, if your end-user wants to go back to Windows, they can (either by booting it, or by restoring their computer to the factory settings).

Encourage the end-user to use Linux as much as possible. Tell them if they have issues, they can always boot to the more familiar (Windows), and email you (or call/IM/whatever) with their question. But make sure they know that they are better off with the Linux side. If you choose to do this, then I would suggest that on “Patch Tuesday”, the end-user boots into Windows, and leaves it overnight. That way they aren’t in a situation where they boot to Windows and have a huge number of updates waiting for them (or a system that is compromised immediately).

***This applies the “Remove the Pressure” section from Ms. Noyes article, to Home Users. While you can still put a second computer in the area, it may not be feasible (depending on your situation). For example, my mother lives about 5 hours away. So, I would only be there for a short time. And she uses dialup, so it’s not like she can boot any computer and just go.

Plus the dual-boot option is not as big of an issue for Home Users as it would be for corporate users.***

5. Set up for Success. Most of the tips in this section have been mentioned in other sections (and/or Ms. Noyes articles). Essentially this falls into some sub-steps.

  1. Make sure you have the apps that the user needs. This is similar to the “Begin With Key Apps” section. You want to make sure your end-user can do most everything that they could do before.

    Also you may want to make sure the apps are easy to find. Either place shortcuts on the desktop, or make sure you have clear instructions in the cheat sheet.

  2. Set up the administrative tasks so the user doesn’t need to worry about them. Unless your end-user is pretty computer-savvy, they probably don’t like having to deal with updates and other administrative tasks. By default Linux will apply security updates automatically. You should try to set it up to update everything automatically, so the end-user doesn’t have to worry.

    You may want to put a dialog box up (or a terminal screen) to show the end-user what’s happening. This way, they don’t inadvertently shut the computer down (or the Internet connection down) while the updates are happening.

  3. Set up password managers, keys, email clients, and other necessary things. If the end-user’s email can be read from a client (Evolution, KMail, Thunderbird, etc) then set these up for them. You may want to generate gpg keys for their computer (and email accounts), along with RSA Keys. Set up their password manager, so they can store all of their needed passwords (for websites and other things like their wireless router)–with the passwords, if possible.

    If you plan on having the end-user ask questions on support forums, set them up with accounts on the forums. Configure their settings for minimal emails (except for replies to their posts) and show them how to get to the forums and find information/ask the questions. This may also lower the amount of support time you have to spend.

This list is by no means complete. Only you, and the end-user, will know what all needs to be set up ahead of time. The important thing is to show them how to do these things (so they can update passwords and keys or configure things in the future).

6. Give the user a Cheat Sheet. Similar to the plan from Ms. Noyes’ article, you should create a cheat sheet for the end-user. Make sure it’s clear, and easy to follow. If the sheet includes commands or links, I would recommend placing a copy on their desktop–as well as printing it out. This way the user won’t make a mistake when typing the commands or going to the site.

In the future, I plan on making a sample cheat sheet for people to use. It will only be a template, and should be configured for their needs.

I encourage your comments–especially other points that should be considered.

Have a great day:)

Moving to Linux– Ways to make the transition easier. (Part 1 of 2)

This is based on Katherine Noyes article called “Switching to Desktop Linux? 6 Ways to Ease the Migration” located here.

Ms. Noyes does an excellent job of explaining how to ease the transition, if you’re in a corporate environment. But, what if the “users” are your family, or friends? How can you ease that transition? Most of the steps are similar (and you can probably use her article as the guide). I’ll try to put the steps in terms of home users though. (And probably in the future, I’ll be attempting this with my 75 year-old mother).

Here are the Steps:

1. Determine what the user’s needs are. If your end user is a gamer, then you probably won’t be successful in switching them (or at least all of their computers) to Linux. While there are improvements in the gaming front on Linux, it still has a long ways to go.

However, if your end-user mainly surfs the Internet, and checks their email (or basic finances), your switch will be a lot easier. They can surf with virtually any operating system. But, they will have to accept the change.

2. Choose the right distribution. Like Ms. Noyes article, this is an important step. Unless you will be available to help the end-user on a near-constant basis, you need to find a distribution that will be easy to use, easy to learn, and as similar to Windows as possible.

Ubuntu and Kubuntu are probably the most common choices, however Fedora or Linux Mint (which is based on Ubuntu) would possibly work too. The most important thing is to set it up to do most of the administration stuff in the background (updates and things like that). You could probably create (or download) a script that will perform all needed updates whenever an Internet connection is detected, and set it as a cronjob.

3. Choose the right desktop. In the case of home users, the choice isn’t so much which one to use (based on their experience), as it is to configure the desktop for them. Set up their commonly used icons (Internet, email, games, financing, etc) as shortcuts on the desktop. You could even go so far as to rename them to “Internet, Email, etc) to help out.

In Ms. Noyes’ related article (located here), she describes KDE as more complicated. I would have to say that it’s a YMMV (Your Mileage May Vary) situation. When I first started using Linux, I found KDE to be easier to adjust to. Mainly this was due to the fact that it’s so similar to Windows. Currently, I use GNOME, but still think KDE would be easier.

I would avoid the XFCE and other alternative desktops–especially if the end-user isn’t very computer savvy. This is because the extreme differences in some of them may turn the end-user off.

In Part 2, I will continue discussing the ways to make the transition to Linux easier.

Have a great day:)

Your Lawyer May Be Using Linux, Shouldn’t You?

I just finished reading this article “Lawyers Can Leave Windows For Linux OS (Ubuntu)” and thought it would be good to post.

Essentially the author lists the reasons why lawyers could (and possibly should) switch to Linux–especially Ubuntu. They list the facts that older versions of WordPerfect (commonly used by law firms) work, the cost is non-existent (at least not the calculated cost of learning a new OS), and the need for antimalware is non-existent also. Then the author points out the various apps that are available to you.

Ubuntu is the preferred operating system, mainly because of it’s use of Sudo (“su” do) which makes logging out of your basic user and into the root account almost unnecessary. This is a good point, since it’s a bad idea to allow users to log in as root (mainly because they’ll stay logged in as root).

So, if Linux is good enough for your lawyer, then it’s definitely good enough for you. All of the benefits that are presented to the lawyers are applicable to you (with the possible exception of the case management benefits). And because you’ll be using it for more than just law-related items, there are more benefits to you.

So, you can check out Ubuntu at http://www.ubuntu.com or it’s alternative versions Kubuntu, Edubuntu (for students), or Mythbuntu (Media Center alternative). There are others, but these are the main versions.

Have a great weekend:)

Linux is NOT Windows,


I found a link to this site in a forum thread about “Why Linux is better than Windows”, and after reading it decided to pass it on. There are a few things in the article that I don’t necessarily agree with, but overall it’s accurate.

For one, in his analogy of the Lego Car, he stopped short of a good point. The analogy is basically that the new person buys a box of Lego to build a car, because everyone said it was the best car. And the person is frustrated with the fact that they have to build the car, and that it falls apart. The author ends the analogy with the line “Old: Then why did you buy Lego?” In reality it should have had one more line after that, which is “New: Because EVERYONE says it’s the best.”

The point is this. People will say “Linux is better than Windows.”, but they will not tell you that you have to put some effort into using it. They’ll say that it’s more secure, but overlook the fact that it’s secure because you have to do things a certain way (sudo, or authentication, or su -) or they don’t work right.

Another point that the author makes is that people who try Linux and switch back to Windows tend to say “You need to make it more like WIndows.” or “You need to make it easier to use.” He counters with it’s not designed for everyone to use, it’s designed for the people who created it to use. Or more accurately, The developers don’t care if it’s on YOUR desktop, as long as it works on THEIR desktop.

My counter to that is this: There needs to be a bare minimum standard for Linux (especially now days). Since the majority of the people using computers perform a few actions (surf the web, check their email, write letters or other documents, look at pictures, and listen to music), then at a minimum Linux (more specifically the shells like Gnome or KDE) should make that happen out of the box.

A thought is this: Make a tiered-installation. Have a place where the user can tell you more or less what they’ll be using the computer for, and customize their installation to meet those requirements. Make sure to point out to the user that they can customize the operating system further after it’s finished. This is just an attempt to get them up and running out-of-the-box.

They could even make it a two page tier. The first page is the one where they give a general use, and the second will include a list of applications (with their Windows counterparts listed), so the user can get those installed out-of-the-box also.

Yes, it will make the installation a little longer. Yes, it will require a little more coding and coordinating on the part of the developers. But, YES it will make Linux more ready for an out-of-box experience by the average (non-techie) users.

In short, Linux may or may not be better than Windows. But, it can definitely be made with the same capabilities, features, and productivity as Windows. And that, my friends, is more important.

Have a great day:)

From the NYTimes: The Defenders of Free Software

The Defenders Of Free Software (Subscription may be required but is free for accessing online articles. Update: If you view more than 20 articles in a single month, you’ll be required to sign up for a paid subscription.)

This article is about one person who works for the GPL-Violations.org site in encouraging companies that use Open Source software to follow the licensing agreements.

I wanted to point it out for two reasons:

    1. It discusses how deeply Open Source software really is becoming rooted into our society


  • It also discusses the fear that companies have of Open Source software developers coming after them for money


The reality is that the companies are basing their fear out of the tactics of the “Closed Source” companies–not the principles of Open Source. The developers and GPL-Violations.org are not trying to make a quick buck (although I would imagine that all of them would appreciate something in return for their efforts). They are trying to promote the use of Open Source (and trying to make sure that companies don’t steal the code).
As was mentioned in the article, while a “Closed Source” company will send lawyers after the violator (at the very least they will start with a Cease-and-Desist Letter), the Open Source community will first try to get the violator to correct the issues. ONLY If the violator refuses (or fails) to correct the issue, will they resort to Cease-And-Desist Letters or lawyers.
Kind of a better system, don’t you think?

Have a great day:)