The setup for my desktop will not work for my laptop. My laptop is not always on, and is not always available around the home network to be backed up. I needed a system that would automatically backup my laptop whenever it is on, but only once a day. I have been doing manual backups, but that is a hassle. I may eventually employ this backup method to my desktop so I don’t have to keep it on all the time either.

Here are a couple of problems I needed to overcome. If I mounted a server drive from my laptop, and backup remotely to the server, rsync would not preserver the hard links. This not only takes up a lot of disk space, but every file would need to be sent over to the server during every backup. Over wifi, a typical backup would take longer than a day. Not ideal for a daily backup. I therefore, had to initiate the backup from the server. This meant, sshing into the server, mounting the laptop as a drive in the server, and starting the backup from the server end.

I searched for solutions to these problems, and came up with a multitude of answers that were not particularly ideal for me to impliment. One solution was to use NFS to mount the drives in fstab. I did not want to put it in fstab because, I did not want it to mount automatically when the server booted (or the laptop for that matter). Another solution was to continuously poll for the existance of the laptop, from the server, and when it ‘appeared on the network’, start a backup. I then would have to keep track of it to make sure it was only backed up once a day. None of these solutions suited me well.

What I did…

Through a bit of more studying and searching, I discovered that a remote script can be run by ssh. I use ssh all the time to connect to my server, and finding that I was able to start a script on the server just by initiating an ssh session was a revelation to me.

Another tool that I found was “anacron“. Anacron is kind of like cron, but enables you to run something x number of days, weeks or months. And, if the computer is not running at midnight, anacron will make sure the program will run sometime during that day as long as the computer is on sometime in that day. Unlike cron, anacron does not enable you to run a program multiple times a day, or at exact times. This is exactly what I was looking for and anacron was already installed on my laptop, and was already set up to run upon boot.

This is not exactly a step by step tutorial, as you need to know how to get around your system, and run things as root.

I wanted the backup process to be automatic, so I needed to set up ssh keys. I have never set up ssh keys before. There are a lot of tutorials on the net to help along; and I picked this one: http://news.softpedia.com/news/How-to-Use-RSA-Key-for-SSH-Authentication-38599.shtml

This is the command to generate the keys. I wanted unattended backups, so I did not enter a passphrase.

# ssh-keygen -t rsa

I also ran these commands to copy the files to the appropriate directories and files:

# scp .ssh/id_rsa.pub username@hostname.com:~
# cd $HOME
# cat id_rsa.pub >> .ssh/authorized_keys

I also had to copy the keys from the .ssh directory in my home directory to the .ssh diretory in the /root directory.

Read over the ssh tutorial sited above, and when you are done you should be able to ssh into your server with:

# ssh username@remote.hostname.com

I like sshfs to mount my remote directories.
if it is not installed on your server, do it by running:

# sudo apt-get install sshfs

or find it in the Ubuntu Software Center.

You will also need a recent version of Back In Time. I have v1.0.8 installed. The difference between the newest version and older ones, is that the newer version can have multiple profiles. That is, you can have a different profile for each computer you want to back up from your common point (server).

I added the Back In Time stable repository ppa. This will give you the latest and greatest version of Back In Time. If you don’t need multiple profiles, you can install Back In Time from the Ubuntu Software Center and it will be fine. Do this command to add the repository:

# sudo apt-add-repository ppa:bit-team/stable

Then do:

# sudo apt-get update
# sudo apt-get install backintime-gnome

Some explaination is needed here that probably should have been mentioned sooner. My server has ubuntu-desktop installed on it (that is, a full gui interface). The Back In Time profile configuration is easily done with the gui. Then the actual backups can be done with the command line. This also means that if you don’t have a server, your desktop computer should work just fine to backup your laptop with these instructions. There is nothing really “servery” about the process.

OK, some preliminary work:

You need to make a mount point on your server where you want to mount your laptop drive. Create a blank directory where you want it mounted. I chose “/home/ubuntu-laptop” as my mount point.

Create directories on your laptop and on the server where you want the script files to go. On my laptop, I put my backup script in “/home/myhome/Scripts_and_Programs/server_backup”. You can put yours where ever you want. On my server I put the script in “/home/myhome/Scripts”.

I use static ip addresses for my home network devices. You can set up a static ip for your laptop and server in the network manager, but I chose to let the rounter do it. My router lets me pick a certain ip to be assigned by its DHCP. It is based off the mac address of my laptop wifi connection and my server eithernet card. My laptop is assigned 192.168.1.5 and my server is 192.168.1.11. By letting the rounter assign the addresses, I am free to take my laptop somewhere else, and some other wifi rounter will be free to assign my laptop any address it needs to.

Test your connections. ssh into your server. If your ssh keys were setup correctly, a command like:

# ssh -X myname@192.168.1.11

should work, and no password is necessary. On your first connection, you may be asked to accept the key. Answer “yes” and proceede.

Now, try to mount your laptop drive from your server. My command to do this is:

# sshfs myname@192.168.1.5:/home /home/ubuntu-laptop

If you go to “/home/ubuntu-laptop”, on your sever, you should now see your laptop files. Again, the first time you do this, you may be asked to accept the ssh keys. You will also be asked for your laptop password. You could set up another set of ssh keys for your server if you would like, but the sshfs command has an option to get your password from somewhere else and that is how I did it. That will be explained later.

If all is well up to this point, you can fire up the Back In Time gui to configure your backup. On the command line, the command to enter is “backintime-gnome”. You still should be ssh’ed into your server, or be at a server terminal. Notice that my ssh command from above has the option -X in it. This will allow X display forwarding so you can run a gui program from your terminal box.

in your ssh’ed terminal box, that is connected to your server, type:

# backintime-gnome

This should bring up the Back In Time gui, ready to configure.  Click the “settings” icon on the Back In Time gui. If you are using a newer version of Back In Time, you can select a “New” profile. Mine is called “ubuntu-laptop”. Then you need to decide where to put your backups. I have a usb drive mounted at /home/shared2. You need to traverse to the point where you want your backups to go using the folder icon to the right of “Where to save snapshots”. Leave “Schedule” disabled as this will be handled in one of the script files.

Click the “Include” tab and add the folders you want backed up. Remember that I have my laptop mounted at /home/myname/ubuntu-laptop on my server. This is where you need to go to include the included folders. Notice I have a seperate entry for my Thunderbird email folders. This is because I have any hidden files .* excluded from being backup up and my Thunderbird email folders are inside a hidden directory.

Click the “Exclude” tab. Add any files or folders you do not want backed up. As you can see, I added an entry to skip all my configuration files with .* . You need to decide what you want backed up. I also excluded my download directory, my virtual machines folder (large files for experimentation only), and any other directories where I might have other systems mounted in.

Click the “Auto-remove” tab and decide how many backups to want to retain.

Click the “Options” tab. I added one checkmark here that was not already checked. I checked “Continue on errors (Keep incomplete snapshots). I did this because I had a snapshot fail because of some protected .files. I suggest you click this box, at least at first. Then after you make backups, you can look at the log file to see what failed. Otherwise, you will never get a backup if there is an error somewhere.

I did not adjust any of the “Expert Options”.

Click “ok” and this should bring you back to the main “Back In Time” window. If you like, you can make your initial backup by pressing “take snapshot” icon. Your first backup may take a good amount of time, depending on your wifi connection, and the size of your backup. Mine included many video files, and took well over a day and a half. Subsequent backups are quite quick, depending on what new or changed files your need backed up.

If all is successful to this point, you can close the “Back In Time” gui. I suggest you wait until your initial backup is done, as the backup will continue even after you shut the gui, but this may cause problems when you try to setup the rest of the system.

Now the meat and potatoes:

This is the script “start_laptop_backup.sh” that is run on the laptop side, to initiate the backup.

#!/bin/sh
# Automated backup of laptop, that is not always on, to a server that is always on.
# By: John McDougall
# Aug. 11, 2011
#
# This is a script that is run on the laptop. It starts a script on the server named backup_ubuntu-laptop.sh
#
# Is the server pingable?
# try three pings, wait maximum one sec for reply, be quiet
echo “Starting laptop side script”
echo “testing to see if server is accessable”
if ping -qc 3 -W 1 192.168.1.11 > /dev/null; then
echo “yes… Server is up. Will now attempt backup”
echo “Connecting to server.”
ssh -X john@192.168.1.11 /home/john/Scripts/backup_ubuntu-laptop.sh
echo “Server disconnected… Closing laptop side script”
else
echo “no… Server is down. No backup done now”
fi

This is what this script does: First, I try to ping my server to see if is available. If it passes that test, I connect to the server over ssh and run the script “backup_ubuntu-laptop.sh”. No password needed if the ssh keys are set up properly.

Here is the script on the server side called “backup_ubuntu-laptop.sh”.

#!/bin/bash
# Automated backup of laptop, that is not always on, to a server that is always on.
# By: John McDougall
# McDougallsHome.net and radio.McDougallsHome.net
# Aug. 11, 2011
#
# This is a script that is run on the server. It is started from a script run through ssh from the laptop to be backed up.
#
# Connect to ubuntu-laptop from server.
echo “Successfully connected to server… Running server side script”
echo “Attempting to mount ubuntu-laptop to server”
sshfs -o password_stdin john@ubuntu-laptop:/home /home/ubuntu-laptop < /home/john/Scripts/ubuntu_pwd
echo $1
for i in `cat /proc/mounts | cut -d’ ‘ -f2`; do
if [ "x/home/ubuntu-laptop" = "x$i" ]; then
echo “laptop is mounted. ”
# Start Backintime
echo “Starting backintime”
# backintime –backup
backintime –profile ubuntu-laptop –backup
echo “Backup finished”
echo “Unmounting ubuntu-laptop”
fusermount -u /home/ubuntu-laptop
echo “ubuntu-laptop unmounted. Exiting backup script and disconnecting from server”
exit
fi
done
echo “laptop not mounted… Can not backup”
exit

This script first mounts the laptop via sshfs. Notice the “-o password_stdin” option. This enables the password to be entered from another source. In this example, I have the password in a file called laptop_pwd in my Scripts directory on the server. As mentioned earlier, you could set up ssh keys for the server and eliminate the password in a file thing if you feel that is unsafe to do.

This script then confirms that the laptop is indeed mounted. It then initiates the backup with the command “backintime –profile ubuntu-laptop –backup”. After the backup is finished, the script unmounts the laptop and closes down.

To test all this, open a terminal window on your laptop and start the script “start_laptop_backup.sh” and watch its progress. If all worked out, and you already made an initial backup, it should run relatively quick.

Now to automate it all with anacron:

You can find a little tutorial on anacron at “http://www.thegeekstuff.com/2011/05/anacron-examples/”.
To configure anacron, you must modify the file /etc/anacrontab on your laptop. I did this in a terminal window using the command:

# sudo nano /etc/anacrontab

I added one line to the bottom of the anacrontab file as shown above. The first parameter “1″ means it should be run once a day. The second parameter “13″ means it will start approximately 13 minutes after the machine is booted. You can change this to whatever you want. Set it at a time where it won’t interfere with the busy boot process, and anything else you might do as soon as you turn on your computer. The third paramater is a label you make up to identify this process. The fourth parameter is the command to execute. By placing “nice” before the command, if the system is very busy, the backup process will wait until the system is less busy. You can look up the manual page for “nice” by typing “man nice” in a terminal window.

That about does it. If everything worked so far, you are ready to reboot your computer. Anacron should run and a backup initiated. Anacron will only run once a day even if the laptop is turned on several times a day, or left on for days. You will still only have one backup per day. You can look at the files in /var/spool/anacron. ubuntu-laptop (or what ever label you used in the anacrontab file) should be listed there. Open it up with nano or gedit, and it should list the last date that line in the anacrontab file was executed.

I hope this post helps you in your laptop backup.  It might seem kind of complicated, but I enjoyed the process of learning and figuring it all out.  Have fun in exploring linux!

John – K7JM

John – K7JM

Another Ham discovers Linux’s ham friendliness.  ARRL’s website has another nice story about a Ham using Ubuntu Linux and fldigi to renew his love for Amateur Radio.  Check out the post HERE.  Good going Steve (KØSRE)!  For more of Linux In The Ham Shack, check out “Linux In The Ham Shack” podcast.

- John, K7JM

Anyway, that is not really what this post is supposed to be about.  This post is about a nice theme that I came across for my Ubuntu desktop.  Ubuntu, besides being FREE with lots of FREE applications, it is very nice looking, and if you want to dig deeper, you can make it REALLY nice looking.

I usually have my Ubuntu Desktop all decked out with some sort of modified Emerald theme, with transparency, and glowing frames and pulsating buttons and such.  As I was searching around one of the many Ubuntu web sites, I came across a proposed theme for the next version of Ubuntu coded named Maverick Meerkat due to be released on 10/10/10.  I am sure this nice theme I found will not be a default theme, as purple and orange seem to be someones liking on the Ubuntu development teams.  I am personally not that thrilled about the purple/orange theme, and usually look for other options.

The theme I came across is a beautiful blue theme called Ambiance Blue.  It is not fancy, or full of glowing parts, or throbbing buttons, but is a very nice looking simple blue theme.  The Ambiance Blue Theme can be downloaded from HERE.  See the picture of my theme below, or click on the small screenshot to see a larger view of one of my desktops.  Yes, in Ubuntu, you have MULTIPLE VIRTUAL DESKTOPS.  Very Nice!

- John

The ARRL web site had a nice entry about Ubuntu for Ham Radio.  The article could have been four times as long and not cover all the aspects of why Ubuntu Linux is good for Ham Radio.  Also, several of the applications that the author mentioned in the ARRL article that he used with WINE, have alternates available for Linux, including PCB layout software, and Circuit analysis.  Almost ALL FREE.  Besides, Ubuntu’s super easy to install Ham Radio repository of applications, HERE is a page full of stuff, ranging from the latest and greatest to older Linux Ham Radio programs.  Ham Radio is about innovation, and experimentation.  It is sad to see so much of it is built up on a closed, unexperimentalable, unmodifiable, and costly solution like Windows.

73,
John – K7JM

The corner of my web page with a link to view my Ham Radio log file.

Being a Ham Radio operator, I’ve wanted, for some time, to display my log file on my web site. I’ve been researching it for some time, and mostly ran into methods that require java or php, or some sort of web scripting. This is beyond me and I wanted something simpler; and this is what I have come up with.

My computers run on the Ubuntu Linux Operating System.  I came across a small command line utility program called txt2html.  The name pretty much explains what it does.  It has many features that include many formatting options; one being, that I can pre-append a file to the front of another file.  I tested this feature to apply a preformatted html heading to my log page.  I made a simple sample of a text log page listing contacts, and ran it through txt2html and it attached my header to the log page and spit it all out as an html file ready to display on my web page.

My sample log page was called log.txt and looks like this:

call            QTH
k7jm            Helena, MT
wa7vxm          Butte, MT

My sample heading was called ‘log_file_heading.html’ and looks like this:

K7JM’s Log File

I put it all through txt2html with a command like this:

txt2html --append_head ./log_file_heading.html ./log.txt >./log.html

And the output file ‘log.html’ looks like this and is ready to display on your web page:

call            QTH
k7jm            Helena, MT
wa7vxm          Butte, MT

I wanted to automate a way to put this file on my web site without getting too complicated.  The simple ftp command would work, but it takes a bit to automate it. After a bit of research, I came across ‘kermit‘.  ‘kermit’ is a simple program that takes data from a file and performs the commands listed in the file.  Perfect.  I put the following commands in a file called ‘log.kermit’:

ftp open ftp.myhostsite.net /user:myusername /password:mypassword
put ./log.html /www/whereyou/wantit/log.html
exit

I then called kermit like this:

kermit ./log.kermit

and it is done.

To make things a bit cleaner and more automatic, I created a script file called ‘log_doit.sh’ that looks something like this:

txt2html –append_head /home/john/Desktop/log_file_heading.html /home/john/Desktop/cqrlog.html >/home/john/Desktop/log.html
kermit /home/john/Desktop/log.kermit
exit

Now, to do the whole process, I just had to update my log file, save it, and run the script ‘log_doit.sh’ and it would be on my web site.

A New Way – With cqrlog

After I put all this together, I remembered hearing about a Linux logging program called cqrlog, on the ‘Linux In The Ham Shack‘ (link updated 9/2010) podcast.  If you are a Ham Radio Operator or use Linux, I strongly suggest you give this great podcast a listen.  It is always entertaining, and they have covered some very useful stuff for the Ham that is running a Linux operating system.

Anyway, I downloaded and installed ‘cqrlog’ and started playing with it.  I was specifically looking for a way to export the log file so I could run it through ‘txt2html’.  Lo and behold, ‘cqrlog’ does one step better; it exports the log right into the ‘html’ format.  Wow! Perfect!.

I learned a lot by using txt2html, but now I can skip that step completely and just export the log file in html format and run a simpler script that runs ‘kermit’ to upload the file to my web site.  Click HERE to see the actual page on my web site.  As of when this was written, the file is a test one that was created by playing with ‘cqrlog’.  It will change once I start using ‘cqrlog’ for real.

John – K7JM

call            QTH
k7jm            Helena, MT
wa7vxm          Butte, MT

After I installed Ubuntu 9.04 – Jaunty Jackalope, I posted a lengthy list of problems I encountered during and after the process. You can read it by clicking HERE.

I received a great reply from Rob laying out some important facts about updating a major distribution of most any variety.  I encourage you to read Rob‘s reply Here: May 9th, 2009 at 11:25 am.

It seems, however, that my experience with Jaunty was not unique.  My blog post has been ready by many other users looking for solutions.  Here is a partial list of search entries that resulted in finding and reading my post.

• solution gdesklets jaunty

• menu bar missing gnome ubuntu 9.04

• jaunty jackalope install/upgrade experie

• install kept back upgrade brasero jaunty

• desktop effects could not be enabled

• ubuntu 9.04 partial upgrade brasero

• error gdesklets ubuntu 904

• partial upgrade ubuntu 9.04

• tracker jackalope reindex

• ubuntu alternate install +grub boot load

• +nvidia +drivers +jaunty +not +loaded

• jaunty partial upgrade problem

• jaunty jackalope partial upgrade

• ubuntu 9.04 no menu bar

• ubuntu 9.04 failed to open gdesklets

• ubuntu 9.04 sansa not connecting

• missing menu bars jaunty

• 9.4 jackalope indexing error

• downloading files from sansamp3 player t

• ubuntu 9.04 tracker applet missing

• jaunty jackalope menu bar disappear

• ubuntu jackalope tracker reindex

• ubuntu 9.04 missing password

• ubuntu jaunty not detecting sansa

• upgrading to jaunty jackalope partial up

• gdesklets jaunty fix

• desktop effects could not be enabled

• ubuntu jaunty sansa

• tracker indexing error jaunty

• how to start the compiz gui in ubuntu 9.

• ubuntu 9.04 recovery menu

• menu bar missing in ubuntu 9.04

• applet is not loading ubuntu jaunty jack

• ubuntu update manager icon disappeared

• jaunty jackalope recovery menu

• “open movie editor” ubuntu 9.04 mp3

• ubuntu 9.04 problem hp laserjet printer

• ubuntu 9.04 sansa not connecting

• how to install gdesklets in ubuntu 9.04

• compiz buggy since upgrade to jaunty

• kernel failed install when updating to 9

• partial upgrade jaunty error open office

• sandisk jaunty

• nvidia picked up during live not after I

• missing 9.04 from grub

• jaunty install software failed

• ubuntu 9.04 missing compiz menu

• ubuntu 9.04 tracker “what is”

• how do i fix a failed ubuntu 9.04 instal

• sansa clip not working on ubuntu 9.04

• reindex ubuntu 9.04

• not work tracker ubuntu 9.04

• ubuntu 9.04 gdesklets

• tracker ubuntu 9.04 “re-index”

• jaunty disable tracker

• ubuntu 9.04 partial upgrade cannot resta

• jaunty compiz startup

• ubuntu 9.04 + update error

• ubuntu 9.04 nvidia not detected

• power button missing from ubuntu 9.04

• sansa not connecting in jaunty

• kino ubuntu 9.04

• ubuntu partial upgrade jaunty

• some of the menus are missing on ubuntu

• ubuntu 9.04 reindex

• tracker applet missing ubuntu jaunty

• ubuntu 9.04 gdesklets

• ubuntu jaunty auto detect sandisk sansa

• ubuntu 9.04 vlc media player error

• xbmc failed to detect distribution jaunt

• upgrade ubuntu jaunty jackalope gui err

It is obvious that there were too many errors, many of the same ones I encountered, while installing Jaunty.  I (and others) would love to hear about your experience installing Jaunty.  Good or bad.

John – K7JM

Ubuntu 9.04 – code named Jaunty Jackalope, was released on April 23. I am always (maybe too) eager to upgrade to the next version of Ubuntu as new features are always added, making it an even better operating system. Yes, for the uninformed, Ubuntu is a computer operating system. Your computer may run Windows or if it is a Mac, it may run OS X. My computer, along with millions of others runs the totally free and open Linux version called Ubuntu.

Typically, version updates are made right over the Internet. It will download a zillion files and update everything, taking, possibly, several hours to do. I read an article on some web site that I could download the distribution and update it from a burned CD. Since I had two computers to update, I decided this might be a time savings way to go.

Here is my experience:

I downloaded the Alternate Install disc over night. I popped the disk into my computer and it immediately detected that the disc had a distribution upgrade on it and asked if I wanted to “upgrade”. I said yes, and off we went. It then asked if I wanted to update any files that may be newer than on the disc, by connecting to the Internet and downloading them. If I selected “NO”, I could “simply” update my system later and it would pick up the needed files. I chose to do this as I figured it would get the system up an running the quickest.

Before I go into details, I must say that I have a co-worker that also runs Ubuntu. He chose to update from over the Internet. He said that he had to restart the process several times because it kept on stopping. It was probably because there were millions of others trying to do it at the same time. Also, it downloaded over a thousand files. It took a long time, but in the end, he said everything seemed to work ok.

Back to my update. As the update progressed, it asked several times about configuration files, and whether I wanted to keep the current ones or up date them. I had no idea what to do on these. One option was to merge them, which I did several times. I have no idea if that did anything. I kept getting an error saying the latest kernel version xx-xx-xx would not start. Oh, Oh. That is very not good. It came down to one of my choices in updating the grub menu.lst. After several errors, it came back and asked that question again. I chose “update to developers version” or some such thing. Yeah, the new kernel loaded.

The process finally finished and it was time to reboot. When it did, my 3D graphics did not work. Meaning Compiz was disabled. I tried to load a new Nvidia driver with not much luck. I decided maybe I needed to do that update that was mentioned earlier. I chose “update” and boom, it decided to download several hundred files. This was the part that I though I was avoiding. Once it downloaded them, I got a message saying that all the files weren’t downloaded, and suggested a “partial upgrade”. I chose to do that. I ran “update” again and it picked up more files, but this time the update process crashed when it was time to install them. After much head scratching and searching the Internet, and many hours passed, upon boot-up, I selected “recovery mode”, and selected a sub menu that said something about repairing packages. I chose that option. It recognized that there were updates, and it loaded them successfully. After that, my “update manager” seemed to work. There were many other users out there that were looking for the same answer.

My Nvidia drivers were still not loaded. It detected a new version of the driver, but when I tried to enable it, it gave me a message back that said it was previously enabled. So did I just disable it, or was it enabled? I went into the settings, and this time I was able to turn desktop effects on. But, the Compiz GUI was missing. I re-installed Compiz and I was able to turn everything back on. What a pain.

Somewhere in all of this, my screen locked up because the screen saver came on. When I tried to log back in with my password, it said my password was “invalid”. Oh, no. I clicked the “Switch user” button, reselected myself (which said I was already logged in) and it took my password correctly. After several more hours of Internet searching, I found that many other have had this problem even before the new version of Ubuntu. I eventually came up with the fix after digging into the depths of files that have never seen the light of day.

Before I started the upgrade process, I did a complete partition clone saved to an external drive. I also separately backup the home directory of my and my family’s accounts. I also went through and did screen shots of all the menus. I did this, because I had a past experience that failed and I had to reinstall the entire operating system, and I couldn’t remember all the different programs I had installed. This was a good idea, as I was soon in for a big surprise.

It seemed that everything finally came out ok, but I noticed that an icon on my menu bar was missing. It was for the search applet. I very much needed that. It indexed all of the files in my home directory, and could search for anything in a second. I have the “open clip art” collection on my drive which consists of thousands of pieces of clip art. There is no way to search this collection without the indexed search applet. The applet also categorized its results and actually displayed thumb nails of its results. A very handy thing for searching through clip art. The problem was, I did not even know what this little program was called. I could not even search for it on the Internet. It took another hour or so of time to finally figure that it is called “Tracker”. I reinstalled it. The configuration files were in place so it came back like it should – except, it kept saying there was an error and had to re-index. Oh no, maybe this is why it disappeared. It seems to be buggy. I don’t know what I will do without it.

Since this program was missing, I though I would check around and see if anything else was missing. Oh boy, was I in for a shock. I am very glad I took those screen shots. I printed them out and started comparing new menus with old ones. Here is what came of it. Almost all the old configuration files were still present, which made setup a lot easier.

• Tracker – missing. When reinstalled, it appeared to be buggy.
• Gnome Do – missing. Reinstalled. Old configuration files still intact.
• Firestarter the firewall would not activate. Reinstalled and it started up ok.
• Dropbox would not start up. I had to go to their web site and download and install a new version.
• Brasero disc burner. This was my favorite disc burner. It was missing. Reinstalled.
• VLC Media Player – missing, reinstalled.
• Gdesklets – missing, reinstalled
• BitPim – missing. Reinstalled. This program downloads and uploads pictures and info from our cell phone. It was a real pain to get it going originally. I have not been able to get it running yet.
• Childsplay – missing. Reinstalled. This is an educational children’s program.
• OpenOffice Database – missing. I selected the entire suite to be reinstalled. It found the pieces that were missing and only installed them.
• PyCrust – missing. Reinstalled. This is a Python programming language front end GUI
• DeVeDe – missing. Reinstalled. This is a DVD menu creator which I really like.
• Kdenlive – missing. This is a video editing program. I have been using Kino and Open Movie Editor, so I did not reinstall this one.
• XBMC – media player – missing. I didn’t use this much either so I didn’t reinstall it.
• todisc GUI – missing. Reinstalled. This is another DVD menu creator.
• My Sandisk Sansa MP3 player would not work. This took hours of research to figure out. When I plugged it in, it did not come up in “mass storage” mode that it should have. It also spit out an error message and apparently thought it was a camera. After pulling the last two hairs out of my head, I found a solution and deleted a file somewhere on the system and it corrected the problem. I’m sure that file was there for something though!

SO, so far I have been able to get everything back working except Tracker, and BitPim. What a very large head ache.

I love using Ubuntu, but with this experience, I can tell you it is definitely not ready for the masses. How would mom or dad ever deal with something like this? Also, many “Gurus” will tell you that you should always do a fresh install when there is a distribution upgrade. How ridiculous is that? I finally got my computers networked, sharing printers, and files. I’ve configured it to death to how I want it. How is the normal Joe ever supposed to wipe all of that out and start over? I can’t remember what I did yesterday, it would take months to get everything back to normal.

As I said before, my co-worker’s upgrade turned out fine. It just took a long time. But— not as long as mine did.

John

John

With the USB bootable thumb drive, it also means that you can carry your operating system with you with all the files you like to use.  There certainly is a performance issue compared with a regular hard drive instalation, but having your e-mail, internet, audio/visual programs, ham radio programs, etc. with you all the time, available to use on any computer that can boot by USB, is an awesome thing.

Here are some detailed instructions to make a bootable USB thumb drive from the Ubuntu 8.10 live CD.

Download PDF of this page.

• Insert Live Ubuntu CD and allow it to boot up completely

• Insert Thumb Drive into a USB port and wait for system to recognize it

• Click “System” on the TOP menu of the Desktop

• Select  “Administration” under the “System” menu.

• Click “Create a USB startup disk” under “Administration”

• The “Make USB Startup Disk” program should start

• CD info for the Live CD should appear at the top

• USB information should appear in the middle. If the USB thumb drive is not inserted, you can do it now and the information should appear.

• Make sure “Store in reserve extra space” is selected.

• Move slider to the right to allocated additional memory on the thumb drive for the Ubuntu system. If you want a bit unused (eg. ½ GB) for other files, do not go all the way to the right. Note – This “unused” portion, or any files on the unused portion of the thumb drive WILL NOT be accessible when Ubuntu is booted from the thumb drive.

• Click “Make Startup Disk”

• The system will begin to copy the Ubuntu Operating system to the thumb drive.

• It may take some time for the process to complete. When it is done, close the program and unmount the USB thumb drive by right clicking on the disk icon on the Desktop, and click “Unmount Volume”

• This completes the installation of Ubuntu onto the thumb drive. Reboot the computer with the thumb drive in place and enjoy Ubuntu.