Chainloading GRUB2 in a dual-boot Linux Setup

So my setup is like this on two computers: Ubuntu Linux (used most frequently), Fedora Linux, and either Windows XP Home or Windows Vista. On my laptop, I have Fedora controlling GRUB, and on my desktop, I have Ubuntu controlling it. The two biggest issues that I’ve run into are these: when I update/upgrade the non-controlling distro, it overwrites GRUB and takes control, or when I update/upgrade the non-controlling distro, I have to log into the controlling distro and update GRUB to make those changes appear.

In researching this, I’m finding a couple of things out. First “Beginning in Fedora 18, GRUB2 can no longer be installed to a partition.”, so it will have to control everything. Well, technically, I can probably force GRUB2 to install in a partition, but I’ll probably just use the Fedora version of it to control everything for simplicity (plus I like the background more than the plain black one for Ubuntu).

The first step is to either install or move one of the grubs to a partition. In my case, I wanted to move the Ubuntu GRUB to it’s partition. WIth GRUB2 though, this is harder than it would seem. GRUB2 doesn’t like using partitions, because it’s not as stable as putting it in the Master Boot Record (MBR). It has to use blocklists in order to determine what operating system is where.

So, in order to force grub to install in a partition, you have to use the –force option. (note that it’s two dashes – – not –)

grub-install –force /dev/sdXY # Where X is the letter from fdisk that represents the boot order, and Y is the partition number.

You’ll use fdisk -l to decide which partition GRUB should be installed on. For example, if you only have one drive, it would most likely be sdaY, if you have two drives, it could be sdaY or sdbY; depending on which drive your operating system is on.

Next you’ll have to reboot into the operating system that you’re going to use for the main version (in my case, Fedora). When you boot up, if you don’t see that operating system listed in the GRUB menu, you’ll have to use a LiveCD to fix it. In my case, as I didn’t have anything on the Fedora partition that was important, I simply reinstalled it.

The first thing you’ll want to do in the operating system that will control GRUB, is to install it in the MBR. You can do this with

grub-install /dev/sda  #(or sdb or sdc or whatever letter corresponds with your hard drive).

After installing GRUB to the drive, you’ll need to edit your etc/grub.d/40_custom file to add in the chainloader.

You’ll add something similar to this:

menuentry “Chainload Ubuntu 9.10 on /dev/sda3” {
set root=(hd0,3)
chainloader +1

GRUB2 uses the following numbering conventions: 0 to infinity for the hard disk number, and 1 to infinity for the partition number. So, the first partition on the first disk would be hd0,1 and the second partition on the second disc would be hd1,2. Also it doesn’t matter if you used hd or sd in the grub-install command. Inside of the grub.cfg files, it’s always hd.

It’s also recommended that you set 30_os-prober to non executable with chmod -x 30_os-prober so that you won’t have multiple entries for your operating systems. And if you have other operating systems (such as a triple or quadruple boot setup), they should be added to the 40_custom file as well.

FInally you’ll run the

grub2-mkconfig -o /boot/grub2/grub.cfg

command to update grub. On Ubuntu, this command is actually update-grub.

If you don’t like the format of the GRUB menu (such as all of the different single-user (Recovery) mode entries), you can comment those out in the 10_linux file as well, and re-update grub.

So what will this accomplish? Simply put, it will ensure that if you have two Linux distributions installed on a computer, they’ll be able to update their own grub. Why’s that important? Because it makes updating kernels/upgrading versions much simpler. Instead of having to boot into the operating system, update or upgrade, and then boot into the controlling operating system and update grub before you can use the newest kernels, you simply do updates/upgrades as you would on a single-boot system.

Securing Your Computer using a Password

Ok, so I want to address this issue first. While a password is important for preventing someone from USING your computer, it really doesn’t do much good for protecting the data on the computer. Yes, you can password protect your data (using Windows), but that’s risky also. While it might stop someone from booting into the computer and opening a file, it doesn’t stop them from seeing that the file exists. And if you reset your password, there’s a good chance that you won’t be able to open the file either.

If you just rely on the fact that you have a password on your login, that’s not going to do you any good. Case in point: I have a triple-boot system (Windows XP, Ubuntu 13.04, and Fedora 19) on one computer, and a triple-boot system (Windows Vista, Ubuntu 13.04, and Fedora 19) on another. On either system, I can boot into one of the Linux operating systems and open/view/run any file on the Windows drive. They don’t necessarily have the same passwords or usernames (if there’s a password at all). So, it doesn’t matter.

In fact, if someone asks me to fix their computer, the first thing I do is create an image of it. The second thing I do is boot a LiveCD and copy all of their documents, pictures, music, and whatever else they want to keep to a USB drive. Then I either fix or wipe and reinstall the computer for them. Finally, I put all of their stuff back on the computer for them. Up until I actually start to work on the computer, I don’t even need to know their passwords. ****I should note that after I’ve completed the work and verified that everything is right, I delete the images and backups. I use the images and backups in case something goes horribly wrong. I can restore them, and start over from scratch.

The point to this article is that if you’re worried about your privacy (or are required by law to ensure the privacy of your data), you need some form of encryption software installed on the computer.

By no means, am I denying the necessity or values of using a password to prevent unauthorized access to your computer. It’s imperative for logging into and using the system.

Securing Your Computer With Encryption and Other Means

Recent events in the United States (along with other countries) and even commercials for companies like LifeLock are bringing the concepts of how to properly secure your computer back into focus. For example the LifeLock commercial which shows the doctor leaving his laptop in the taxi, emphasize the importance of encryption. While LifeLock is using this to sell their protection, the reality is that the doctor (and everyone) should have taken steps to ensure that your data is protected. The need for services like LifeLock would be reduced, if either the entire computer, or at the very least, the personal information about the patients,  was encrypted.

In the case of the NSA, and other law enforcement agencies, it doesn’t matter if you’re innocent or guilty of committing a crime. If you are detained, or suspected of committing a crime, then they will search your computer and other data devices. Think that your computer is password protected so that will stop them? Think again. Law enforcement agencies have tools that will read the data on your drive–even though it’s protected by a password. The only potential solution is completely encrypting the drive. While this isn’t a perfect solution, it’s at least better than nothing.

There are many ways of encrypting your computer, depending on what operating system you’re using. And each has their strengths and weaknesses. It’s up to you to decide which method you want to use and to make it work.

Before I go on, I want to emphasize some points about this topic…

In the case of Edward Snowden, and Bradley (Chelsea) Manning, I don’t think they’re heroes or traitors. I think they’re criminals. Pure and simple. There are laws concerning what they did, and they violated those. Not to mention the policies in their respective companies/military services that were violated. I don’t condone their actions or their reasons for their actions.

For the people who think that what these two did made a difference (because they exposed what the Government was doing), it really didn’t matter. Here’s what happened after the documents were released (in the case of Edward Snowden):  He fled for his life, and became a man without a country. The NSA requested (and received) re-authorisation to continue doing the surveillance that he exposed. They continue to do it today. The partner of the reporter who wrote the articles based on Snowden’s documents was detained in London. Even though he was released, they kept all of his computer equipment–including an X-Box. The company who hosted the email service that Snowden used was forced to shut down, due to receiving a FISA warrant. Groklaw (who isn’t involved in this situation at all) chose to shut down, in fear of having to make the same choices that Lavabit had to make.

At the end of the day, it’s not a question of guilt or innocence. It’s a question of privacy. And it’s a question about whether you want to enforce your right to privacy or not.

So what are your options, and what are their strengths and weaknesses?

My plan is to do some research on your options, and give you all of the details that I can find. I should note that this is NOT the same thing as email encryption. I’ll discuss that in a separate topic as well. Please feel free to comment with your answers to my question. I’ll confirm and add them into my articles in the future.

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.

Upgrading to Fedora 19

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

Recently I wrote an article about installing Fedora 19 on a computer. This series of posts will cover the upgrading procedures for Fedora 19. Specifically, I’m going to cover upgrading a single-boot installation of Fedora 18 to Fedora 19 using fedup (the Fedora Updater), and upgrading both a dual-boot installation with Ubuntu–where both Fedora and Ubuntu handle the bootloader (two separate articles). In theory the installation should be the same either way. But in reality, depending on which operating system handles GRUB, there might be more steps involved.

Unlike the earlier installation guide, I won’t include screenshots in this guide. This is because most of the steps will be done through the command line, or through fedup. The command line (yum) will handle everything in the typical fashion that yum does things. FedUp may have GUI dialog boxes, but they probably won’t be as intensive as the full-installation is. If I find that they are, I’ll include some screenshots.

*** Originally I was going to show how to upgrading using yum, but in reading about the method, I found that the Fedora project doesn’t support it. If you absolutely must use yum to upgrade, here is the fedora document for that.

Installing vs. Upgrading

I’ve discussed this in the past, but it’s a topic that’s worth revisiting. There’s always a debate whenever a new version of an operating system comes out, about whether you should do a clean install or upgrade. If you’re running Windows, there’s a cost factor involved (as the upgrade disc is *usually cheaper* than a full retail disc). But if you’re running Linux, the cost is the same regardless of which way you go. Plus in Linux, depending on the distribution, you may not even need a disc, as there is an upgrade manager available to handle the download and upgrade process for you.

All things being equal, it’s better to do a complete clean installation, and then reinstall all of your applications and settings. Of course you should back up everything that you want to keep before doing this (as it will wipe everything out). In Linux, you also have the option of separating your /home directories from everything else (putting it in a separate partition). This helps to keep everything safe, and also allows you to switch between distributions without losing your data.

The reason that I, and a lot of others, advocate doing a clean installation vs. an upgrade is simple. If you’re building a new house, you start with a solid new foundation–not the old foundation that might have cracks and weak spots in it. The same thing goes for your computer. Start with a fresh installation of the operating system plus updates, and then reinstall your applications. That way everything is solid, and any misconfigurations or other bugs are not there. You can always tweak things to suit your needs later.

One other reason that a clean installation is better than an upgrade is if some of your installed programs aren’t compatible with the version you’re switching to, it could cause problems (or worse a non-booting system) during the upgrade process. By doing the clean install, you know that everything is compatible, and you’re able to choose what applications you want to install (or find alternatives for incompatible ones).

Also in some cases, you won’t have a choice. Windows Home Server (while it was available) went through a change in architecture (from 32-bit to 64-bit), so there was no upgrade path. Amahi Home Server goes through this with every release. There are no supported upgrade paths, although it *might* be possible to do it. As technologies change, architectures will be dropped. Eventually you won’t be able to install a 32-bit version at all–because the number of older computers will be small enough that it won’t be worth the trouble of spinning a version for them. In the future, the same will happen with 64-bit versions, or even versions for desktop computers.

In the past, upgrading because you had a lot of files, because you didn’t have the installers for your programs, or other reasons were valid arguments. Now with the advent of online storage, and hard drives in the Terabyte ranges, these arguments don’t really hold water. Plus you can find most installers online (especially if you downloaded them originally).

If you have opinions on why upgrading is better than a clean installation, please leave a comment about them. I’ll edit this post with the best ones (especially the ones that are hardest to debunk).

And with that, Groklaw is gone…

On Tuesday, August 20, 2013, Pamela Jones posted an article on announcing that she’s shuttering the site. Her reason is due to what the U.S. Government is doing to sites like lavabit (which stored emails in an encrypted format, and was used by Edward Snowden to leak NSA documents). Essentially the Government served lavabit with a FISA warrant and gag order. The warrant put the person who runs lavabit into a conundrum–either comply or shut the site down. He chose the latter. The gag order prevents him from discussing certain parts of the FISA letter at all. He can’t even tell his lawyer about them–which means he can’t assist his lawyer in building an effective defense against them.

Ms. Jones decided that since email is the main communication that she has between her and contributors (and readers), and that since she has contributors from all over the world, it wasn’t worth the risk of having to deal with the same issues as lavabit did. So she decided to shut the site down (although it’s still up, and you can still comment on other articles there). Her last post is an eloquent discussion on how “total surveillance” makes you lose your humanity.

It places me in a conundrum of sorts also. I have nothing to hide, as far as the emails I send or receive. But I realize that others do have something to hide, and they have a good reason TO hide those things (and no, I’m not talking about terrorists or people who are committing other crimes). And while commenters on Ms. Jones’ site are speculating that she may have received the same type of FISA letter/gag order that the owners of lavabit did, I don’t think that’s the case. What I think is happening is two-fold. First is exactly what she said in her final post. That she feels violated knowing that the Government will read her emails, and keep them for up to five years to try and decrypt them (if they are encrypted). Secondly, I think she realizes that if there is a law on the books, it can be abused. Who’s to say that some corporation that she’s been writing about, won’t “convince” someone in power to serve her with a FISA letter to get everything that she has on them?

So from my standpoint, what to do… What to do… I’m not shutting the site down, as I’m not in the same position as she (or others are). If I’m served with a lawful (read as legal and properly executed) warrant, I will comply. If the warrant is not lawful, I will fight it to whatever extent that I can. One of the recommendations that Ms. Jones is doing is using a site like kolab for her email. It’s located in Switzerland, so it falls under a different set of laws than the U.S. I won’t do this, because as she pointed out earlier in her post “They tell us that if you send or receive an email from outside the US, it will be read. If it’s encrypted, they keep it for five years, presumably in the hopes of tech advancing to be able to decrypt it against your will and without your knowledge. Groklaw has readers all over the world.” By using a service from Switzerland, you’re guaranteeing that the emails will be read and held on to.

At the end of the day, Groklaw is gone. And the Internet is not a better place for it. The site was one of the most well-known defenses of our legal rights and of Open Source in general. While I don’t necessarily agree with everything she’s posted there (or people’s attitudes about certain corporations), I felt that it was an important site to have around. It kept shining a light in the dark recesses of corporate ethics (whether anyone, including Ms. Jones, realized it or not).

It’s a sad day indeed.. Just sad…

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 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/ file in your favorite editor (I use nano, but you can use whatever you prefer).

nano /etc/postfix/

At the bottom, add the following lines:

# sets gmail as relay
relayhost = []: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:

[]: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) should be replaced with your intended recipient’s email address.

mail -s “Subject: Test email from linux server”

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”

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” -c

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 with your external email address)


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 file, you need to do the following things:

In, 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

[]: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 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 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