A collection of thoughts, tips, musings and the occasional recipe. Basically all the stuff I am supposed to remember.

Fixing :perl: warning: Setting locale failed." errors on a Debian or Ubuntu system.

The short short version is that I run the following four commands in sequence:

  1. export LANGUAGE=en_CA:en
  2. export LANG=en_CA.UTF-8
  3. locale-gen en_CA.UTF-8
  4. dpkg-reconfigure locales

Of course this example is specific to a Canadian English UTF-8 system. In the US, the language might be defined as something like en_US.UTF-8.

How to restore your GNOME panel bar after accidentally removing it.

I accidentally deleted the GNOME bar while messing around with it. I could have rebuilt it by hand, applet by applet, but I thought that there must be some way to reset it back to the default. It turns out that this is a pretty straight forward thing to do.

In the /etc/xdg/menus folder are the templates for the default menus. The one we are interested in is "applications.menu.orig.dpkg-new".

Simply copy this file to your /home/<usr_id>/.config/menus/ directory and then rename it to "applications.menu"

I got this tip from the following forums:

Resizing your Linux based NAS

In an earlier article article I outlined how to manually create a NAS device with standard Linux tools. This article shows you how to resize the array that you created. In the example that I used, we have replaced our 1 terabyte drives with 2 terabyte drives. Then we extend our logical volume and the file system that sits on top.

Warning, if the data is important or mission critical, BACK IT UP! One wrong step and you could very likely hose all of your data!

The first thing we need to do is replace the drives, one at time. This may take a while (about 4 hours per disk on my machine) as the array has to be rebuilt each and every time you replace a drive. During this period you are vulnerable to data loss as you no longer have a valid parity drive. If another disk fails in this time period then will likely lose your data. In case you missed it before, BACK UP YOUR IMPORTANT DATA FIRST!

On my machine the drives were installed into hot swappable drive trays, and the SATA chipset supported hot swapping. Your system may differ, in which case you may need to shutdown and reboot to swap every drive.

On my machine I just removed the first drive. I checked dmesg and noticed that the drive I removed was /dev/sdd.

MMCKaspersky Administration Kit does not Launch.

Every once in a while when I try to launch the Kaspersky Administration Kit interface, I get an error message stating that:
MMC cannot open the file C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\CS Admin kit.msc.

This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient access rights to the file".
The solution is to simply delete the file located in C:\Documents and Settings\AdminUser\Application Data\Microsoft\MMC\CS Admin Kit. Of course replace the AdminUser part with the username you are using. For MS Server 2008, Vista, and Windows 7, that path will be C:\Users\AdminUser\Application Data\Microsoft\MMC\CS Admin Kit.

Fedora Equivalent to Debian/Ubuntu's build-essential

I have been playing around with Fedora and Cent lately to get re-acquainted with RPM based Linux distros (it has been 8 or so years since I last bothered).

Anyway, I have grown very used to having certain bundles available to me. For example, on debian or Ubuntu, I would

sudo aptitude install build-essential

to get all of the required packages for compiling software. It seems that Fedora does this a little differently. For the moment, the closest equivalent to build-essential that I could find is:

 sudo yum groupinstall "Development Tools" "Development Libraries"

More to follow on my adventures in RPM-land.

How to manually remove stuck printer jobs from a Windows based print server

As it turns out, this is a pretty straight forward thing to do.

First we stop the the print spooler. I like doing this from the command line like so:

  1. net stop spooler

but you can just as easily stop the spooler from the "Services" control panel applet.

The next step is to delete the temporary files that store the data that is to be sent to the printer:

  1. del %systemroot%\system32\spool\printers\*.shd
  2. del %systemroot%\system32\spool\printers\*.spl

Finally we restart the print spooler, again from the CLI:

  1. net start spooler

Credit where credit is due, this info I pulled from http://www.ghacks.net/2008/12/11/how-to-deal-with-stuck-print-jobs/ There were a lot of results when I search Google, but this one went straight to the point (I like that).

Syndicate content