A taste of Linux.

Much essential information is held in 'man pages' which are essentially information about a program which may also contain command line instructions, and any other relevant information, and is usually accessed in a console terminal. I have found that it is awkward to read these pages and remember the information because of the difficulty in scrolling within it.

But now this seems to have been resolved by using Konqueror ... all you need to do is to put 'man:/' into the location bar and it then displays the 'UNIX Manual Index'. However, this is still a bit of handful to find your way around, but, if you know the name of the program or command that you need information on then you can just put 'man:/????' into the location bar where '????' is the name of the command or program. And it is so easy to scroll up or down, or find the information that you want using the find command [Control + f].

Foiling the Phishers.

Phishing is a growing form of online fraud. It blends old-fashioned confidence scams with innovations in technological trickery. The best way to avoid becoming a victim is to remember that real companies almost never send email asking you to submit any personal data.

Phishers use "spoofed" [fake] emails and fraudulent websites designed to fool you into divulging personal financial data such as credit card numbers, account usernames and passwords, and in America your Social Security numbers, etc. By hijacking the trusted brands of well-known banks, online retailers and credit card companies, phishers can fool you.

They often include fancy graphics, trademark symbols, and an authentic-looking email address in the "from" line, but all of these things can be faked easily. One of the easiest ways to tell that it comes from a phisher is if the message tries to scare you into giving up personal and financial information by saying that your account needs to be verified, updated or confirmed. If you think a message might be legitimate, contact the organization by phone or open a new Internet browser window and type in the company's Web address. Do not cut and paste material from suspicious email messages and never reply to a suspected phisher.

Be smart. Be safe.

Nigerian Scam.

On another fraud front, many people have been contacted by perpetuators of what's known as the Nigerian Advance Fee Fraud or "4-1-9" scheme -- so named after the section of the Nigerian penal code that addresses fraud schemes. These are often quite creative as people are discovering.

A large number of victims are enticed into believing they have been singled out from the masses (often by using your family names) to share in some multi-million dollar windfall profits. Don't fall for such frauds either.

Promise yourself to be so strong that nothing can disturb your peace of mind. To talk health, happiness and prosperity to every person you meet. To make all your friends feel that there is something in them. To look at the sunny side of everything and make your optimisim come true. To think only of the best, to work only for the best and expect only the best. To be just as enthusiastic about the success of others as you are about your own. To forget the mistakes of the past and press on to the greater achievements of the future. To wear a cheerful countenace at all times and give every living creature you meet a smile. To give so much time to the improvement of yourself that you have no time to criticize others. To be too large for worry, too noble for anger, too strong for fear and too happy to permit the presence of trouble.

Recently two drives on the computer got confused and started spilling out error messages when I rebooted. Eventually I tracked it down to this;-

fsck ext3. no such file or directory while trying to open /dev/hdf1. The syperblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem and not swap or ufs or something else, then the superblock is corrupt and you might try running e2fsck with an alternate superblock

The exact message that was being shown at the start of this saga was

buffer i/o error on device hda1, logical block 0

and then the logical block would increase by one until I switched the machine off. This was looking serious so I started asking questions in the forums and chatrooms in irc and came across RIP [Recovery Is Possible]. but to recover a hard drive I'd need a new one to recover onto, so off I toddled to get one.

Back home and thinking about it, I'd better partition this drive before I use it, so into the machine it went and I loaded up knoppix, set the root password,and then formatted it using gparted. Came out of knoppix which had now done its job and went back into RIP. Both drives were unmounted and i was able to use ddrescue to copy information off the dodgy disk onto a brand new disk.

It was rather scary doing it, but having done it successfully once I feel confident about doing it for the other three drives in the box, once I've got the new hard drives that is :).

Recently I had a hard drive die on me, I knew it was dead but I still went ahead and rebooted. Which meant of course that when it appeared in fstab it immeditaley threw the machine into a tizzie. So i tried 'emacs /etc/fstab' from the command line but only got a read-only version, and I got the same when I tried using vim. So I was scuppered.

I tried using knoppix as a live distro to enable me to edit fstab but it couldn't see inside my lvm drives.

And then I found my centos 5.0 installation disk and was able to gain access to fstab via Linux Rescue, using the mantra of 'mount/sysimage/etc/fstab'. Then it was easy to just comment out the relevant line and then save and reboot. But to the centos developers, please, don't put light grey writing on a black background, its virtually unreadable! To read it I had to turn off the main light and read it just with the back light screen monitor.

Today I've been playing around with irssi and getting that up and running. First problem was that it wasn't installed but that was easily rectified. Then to find a theme that I liked which was different from the default theme, which had pale purple writing on a dark purple background to the bars at the top and bottom of the irssi program. The combination of colours I found was totally unreadable, so the need was rather urgent. On the irssi website [http://www.irssi.org/] I looked in the themes folder until I found one that I liked, eventually plumping for the 'spring.theme'. And then goltor over on #gllug was talking me and Peter through getting it all set up and running, suggested that we download and use 'adv_windowlist.pl' from http://tenr.de/misc/misc.php?a=misc and save it into irssi/scripts/autorun/ ready to run next time we started irssi. So I /quit irssi and then restarted it, joined freenode by using the /server freenode command and then once that had joined I put in /join #gllug and then a couple of other channels that I wanted too. To swap between the windows just use the ALT+number key. And thats about as far as I've got in running irssi at the moment.

Seeing in my rss feed that OpenOffice.org had released version 2.3.0 this morning I hurried to get it. Downloading from the OO.o website led me to the version that I was already using, so I followed the link in my distrowatch feed to the new download. Once I'd got it and untarred the file I saw the familiar fold of rpms which I was able to install using Clive-H's familiar incantation. And then I found a problem.

Whenever I clicked my menu item for OpenOffice I got the 2.2 version.So how to change it? I couldn't access the menu editor because the panels were locked, so the obvious answer was to unlock the panels and then to click on the link to the menu editor. Again find my link to OpenOffice writer and just change its link from '2.2' to '2.3', save everything and then it all worked okay again, and i was able to load OpenOffice.org 2.3.0. I then had to accept the terms as usual before writer came up with its familiar screen, and I was in business and ready to play.

I have some problem where xmms just chases its tail through its play list when run as user, but works admirably when run under root, which isn't ideal. So I've been looking for another music player and I've tried out Rhythmbox, which at first didn't work because I didn't have the right codecs for it. It turns out that you also need these 'gstreamer-plugins-ugly' and also 'gstreamer-plugins-bad' from the rpmforge repo [and their dependencies obtainable using yum] and then just let her rip. It does need some minor tweaks to its preferences to get it to index your music collection the way that you want, but then it just works fine. And if it does crash for whatever reason a 'Bug-collector' window appears asking you to submit details of what happened and what you were doing at the time. Whether you submit your crash report is entirely your own decision, as you can just close it and no further action is taken.

After some further fiddling I've solved the xmms problem by renaming its folder [.xmms] in the home folder to .xxmms and then restarting xmms. This forces it to recreate its preferences and resets it all, and gets rid of its irritating behaviour of tail chasing :). Once its working properly you can delete .xxmms as its of no further use.

Ever since I upgraded to Centos 5 I've been having problems with the Openoffice.org 2.2 I'd installed from binaries. Every time that I went to open a file in it it opened a 'Filter Selection' box and refused to open my file, which could be opened perfectly easily using OOo1.5 from Centos. That way I knew that the problem lay with OOo2.2 rather than the files themselves. So I went on #openoffice.org on freenode and asked there, and two people attempted to help me sort it all out. Eventually it was concluded that I'd found some rare bug which didn't easily manifest itself as no-one else had reported this problem.

So I asked on #gllug [Greater London Linux Users Group] and clive-h gave me a lot of help and advice, most of which didn't work until Clive-h suggested 'rpm -ivh --force --nodeps openoffice.org*.rpm' which I was reluctant to do as I've never forced an install before, but nothing else had worked. So I did it and it worked, OOo2.2 was now opening files that it couldn't or wouldn't open before. All kudos to Clive-h! The only thing that I can think of about the previous incarnation of OOo2.2 was that it was an incomplete installation, and thats why the force had worked.

On my shiny new CentOS 5 I do have one slight problem ... when I log on and startx has run I get this error message "cannot open theme file /usr/share/apps/kdm/themes/RHEL". I then have to click the OK button with my mouse before I get a login box for my user name and password. So I checked and there is no RHEL folder and only a circles and a Bluecurve folder. So I went onto the #centos channel on IRC [Internet relay chat] and asked about it.

it turns out that I needed to alter usr/share/config/kdm/kdmrc, and the line that has to be changed is Theme=/usr/share/apps/kdm/themes/RHEL and I changed it to 'circles' and then rebooted. And I was able to log out properly which was another of my problems. When the login screen reappeared after my reboot there was a big flower and two boxes requesting my login details, it was working! Once in I went back to the above mentioned file and changed the theme to 'Bluecurve' and logged out, to be met with two login boxes in a more official looking blue background, which is what I prefer. Another problem solved :)