While working to verify some packages in Ubuntu 12.04 had backport patches installed properly I needed to list installed package versions. To do this you can install a package called apt-show-versions which will allow you to list all installed packages and their versions with ease. This likely works on most Ubuntu versions but was tested on Ubuntu 12.04 also know as Precise Pangolin and Ubuntu 12.10 also known as Quantal Quetzal. Follow the instructions below to install apt-show-versions and then list all installed packages and their versions.
While doing some testing this evening on Backtrack Linux 5 R3 I had issues with apt or aptitude complaining about some dependencies for packages I had compiled from source. One of the packages I first ran into issues with was bluez which is installed by default on Backtrack. I wanted to apply a patch to the source code and then reinstall bluez which I was able to accomplish. The issue started after that when apt started complaining that bluez was not installed any longer. Below I describe how I modified the apt dependencies tracker file which fixed my unmet dependencies errors.
Locating the Ubuntu version is easy regardless of if you need to locate the Ubuntu Linux version from the CLI or via the Ubuntu GUI. I always forget what the CLI command is so this is as much reference for myself as it is sharing with others. Below I describe how to determine Ubuntu version from the Ubuntu Linux CLI and the Ubuntu Linux GUI.
Today a scenario came up where I needed to run an older version of Firefox to make sure that there was full support for an applications web interface that I was using. There is not standard way to do this though following the steps below will allow you to install and run multiple Firefox versions without much hassle.
While working on the computer shop network I had to modify the configuration on our switch which is a Cisco Catalyst 2950. After making a bunch of changes I was testing things to make sure all was working as expected however after taking a break and logging back into the 2950 it appeared that all of the changes made had been reverted. I was assuming the Catalyst 2950 had lost power briefly which means all of the changes were lost since they had not been saved to the startup config yet. To verify my assumption I needed to look at the amount of time the switch had been up however “uptime” is not a valid iOS command. Below is information on the command used to verify uptime on a Cisco Catalyst 2950.