LeeNukes

Well, I’m coming to you from a freshly installed Fedora 12 laptop. It’s currently in Alpha, but personally it feels much more like Beta software, nice job guys, really nice job. This is certainly going to be my upgrade path from Fedora 10.

There are a few bugs here and there, for example AVC errors during install from the live CD which I believe is an SELinux alerter.

Well, my note for today is how to enable finger print login.

So, I heard Fedora 12 has fingerprint login, so how do I enable this I thought. Well, the laptop is a Lenovo 3000 n200 which has a fingerprint reader built in.

I had a look around, and here is how I enabled my fingerprint to login:

1) Goto System -> Preferences -> About Me
2) Click Enable Fingerprint Login…
3) On the wizard, choose the finger to register and click Forward
4) Swipe the chosen finger then click Forward and then Close

When it comes to logging in, click your username, then on the next screen click the icon that looks like a hand, then swipe the registered finger.

Job done.

Well, as of early this morning GMT QuakeLive is now compatible with Linux and Mac.

I’m just installing the browser plugin now but so far so good. Very easy too. Will let you know how it goes.

Catch me on there, I’m landstalker_uk

Please See this article/thread: http://lxer.com/module/newswire/view/124264/

They report having problems with TomTom software due to the client software not being Linux compatible.

I had a quick look on winehq and they have TomTom Home 1.X running quite well: Wine Application Database

Where is the problem? Just use wine, sure its not native blah blah and it doesn’t mean they are helping Linux with clients etc but stop moaning and just install wine.

For some reason only known to Microsoft, telnet isn’t installed by default in Windows Vista, although its easy enough to install, but a pain when working remotely and you get kicked off by UAC whilst working via VNC, then you get a DOA connection :D

Anywho, here is how to do it:

1. Click your Start button and navigate to Control Panel.
2. From Control Panel double click Programs and Features.
3. Click “Turn Windows features on or off.”
4. Choose Telnet Client from the list.
5. Click the OK button.
6. A dialogue box will appear to asking you to confirm the installation.

Once this is installed you will now be able to issue the telnet command from the cmd/command prompt. Most useful and used often to test for listening services and open ports.

CNet have recently done a review of this netbook/laptop here:

http://reviews.cnet.co.uk/laptops/0,39030092,49303204,00.htm

They gave it a fair comment, I’m still not sure. As they say though, if you’re happy with what is pre-installed then you’ll have very little problems. It IS cheap and it does what its supposed to, its just not upgradeable.

My original review of this device from October 2008 is here: http://www.leenukes.co.uk/?p=75

I’d never in my couple of times of setting Nagios up managed to get the nagios.cmd part to work correctly.

Always getting this common error:

Error: Could not open command file '/var/nagios/rw/nagios.cmd' for update!

An error occurred while attempting to commit your command for processing.

I HAD read the FAQ but it hadn’t helped.

Essentially the nagios.cmd file allows people using the Nagios web interface to do things such as disabled/enable notifications on hosts and servers etc.

I found this worked if I did:

chmod 777 /var/nagios/rw/nagios.cmd

I could then do whatever I liked on the website, so it was an ownership/permissions problem. Searching the internet told me to ensure that the user that my webserver is running as (apache) was a member of the nagioscmd group.

So, I opened up my /etc/group file and added it, tried again after restarting apache and nagios services, same problem, did the chmod 777 and all was well again.

I had considered scripting the chmod command to run, but I thought NO, I’ll fix this.

Found a solution that works enough for me, rather then just adding apache to the nagioscmd group, add apache to the nagios group. I found that the ownership of the file being created was nagios.nagios not nagioscmd.nagioscmd.

This worked for me, try it, it might work for you. I don’t know what other issues this may cause, security or otherwise, but I can’t see it doing too much damage?