Another virus is making headlines, and it is being passed around the old fashioned way with the modern day equivalent of floppy drives. I remember years ago there was a lot of hand wringing by "security experts" about floppy disks. Back then, viruses could pass from disk to machine quite readily. It looks like only Microsoft machines are being targeted. I have not heard anything about Linux being targeted by this virus.
Now these older infection methods are back, yet they have added a little twist. The Agent.btz virus has been around for a couple of months and gains entry onto your system through an infected USB thumb drive. After infection it replicates itself and starts looking for networked drives on your system and downloads a binary file from a website. What this binary does, nobody knows. Yet some say it will go active when January 20th rolls around, which happens to the day our President is sworn in. May make for an interesting inauguration.
The thumb drive have become the modern day floppy, and it was just a matter of time before the old methods of using floppies to pass viruses have now made a comeback to use USB drives.
I am really happy that I have switched to Linux. For now, there is now worrying about virus software updates, windows updates, etc. I just turn the machine on, and it is ready to go. I guess it is only a matter of time before Linux desktops gets targeted. Linux Servers have been hit with worms, etc. in years past, but that all seems to have died away.
At home, I do run a few server processes, like sshd, etc. I contemplated running Samba and setting up a file server that I would be able to map drives to my Windows box. But for now, I am keeping it simple.
Thursday, December 4, 2008
Monday, December 1, 2008
Speed Up Ubuntu Boot Time
Here is a simple way to speed up the boot time of your Ubuntu system. It involves recreating the readahead profile. Readahead is a daemon that runs in Ubuntu that loads a set if files into page cache that accelerates the first time of loading of programs.
The initial install of the OS comes with its own default set of files. But every system is a little different and you can rebuild this profile in one easy step once you have every thing installed.
Your run this profile program once during boot-up, then after that you are set. I tested this out on a couple of different system and found that you can shave between 5 and 10 seconds off of the boot up time.
Here is how it works.
First boot your system. At the Grub prompt hit the 'esc' key.
At the next menu the default kernal should be selected, so hit 'e' for edit. Then arrow down to the line the starts with the word 'kernel'. Arrow all the way to the end of this line (after the words 'quiet' and 'splash') type the word:
profile
Then hit 'enter' and then hit 'b'
Your system will then boot. For this first boot-up your system will take about twice as long as the profiling program sets up for the readahead. But after the next boot, you just bring the system up the regular way, and you will notice a little faster boot time.
This procedure is not something that I would do everyday, but if you install a new system, do a major upgrade, etc. then it may be helpful to run through this procedure.
The initial install of the OS comes with its own default set of files. But every system is a little different and you can rebuild this profile in one easy step once you have every thing installed.
Your run this profile program once during boot-up, then after that you are set. I tested this out on a couple of different system and found that you can shave between 5 and 10 seconds off of the boot up time.
Here is how it works.
First boot your system. At the Grub prompt hit the 'esc' key.
At the next menu the default kernal should be selected, so hit 'e' for edit. Then arrow down to the line the starts with the word 'kernel'. Arrow all the way to the end of this line (after the words 'quiet' and 'splash') type the word:
profile
Then hit 'enter' and then hit 'b'
Your system will then boot. For this first boot-up your system will take about twice as long as the profiling program sets up for the readahead. But after the next boot, you just bring the system up the regular way, and you will notice a little faster boot time.
This procedure is not something that I would do everyday, but if you install a new system, do a major upgrade, etc. then it may be helpful to run through this procedure.
Saturday, November 29, 2008
Partition and MBR Restore Using TestDisk
After a little poking around with my Windoze PC, the one that would not boot, I decided that either the partition table, or the Master Boot Record (MBR) were somehow corrupted. The machine would boot using other disk drives, so the motherboard was not bad. The manufacturer sent this machine without any restore disks, or Windows XP disks, so I was pretty much SOL in simply re-installing the OS.
After backing up the data that i needed from the drive, I decided I would try to rebuild the partition table and boot record using an open source software package called TestDisk.
Here is the general procedure, I booted the PC using an Ubuntu Live CD. I went to the menu: Sytem --> Administration --> Software Sources
and enabled the Universe Repository and re-downloaded the available software information. Then at a command line: sudo apt-install testdisk
Then ran testdisk from the command line by typing
sudo testdisk
Then I followed the step by step instructions for restoring a partition table here.
This utility worked like a charm! The computer is back up and my wife is happy. When the wife is happy, the husband is happy!
After backing up the data that i needed from the drive, I decided I would try to rebuild the partition table and boot record using an open source software package called TestDisk.
Here is the general procedure, I booted the PC using an Ubuntu Live CD. I went to the menu: Sytem --> Administration --> Software Sources
and enabled the Universe Repository and re-downloaded the available software information. Then at a command line: sudo apt-install testdisk
Then ran testdisk from the command line by typing
sudo testdisk
Then I followed the step by step instructions for restoring a partition table here.
This utility worked like a charm! The computer is back up and my wife is happy. When the wife is happy, the husband is happy!
Friday, November 28, 2008
Using Ubuntu to Recover Data from an XP Drive
I have several PCs in my house. One of them, a Microsoft Windows XP stopped booting for me. I was not sure if the motherboard went bad or the disk drive. This PC had a lot of files on it that were important for my wife and her on line studies. Unfortunately, I was a little re-miss in making routine backups. I did not want her to lose here files, and wanted to at least get the latest copy of her files saved off before I performed major surgery o
Luckily, I had a couple of Ubuntu Live Cd's on hand.
I simply placed a live CD in the bad computer and booted into Ubuntu. The live CD noticed the bad drive, which was no longer bootable, and mounted it. It seemed that just the boot record od the drive was bad, as all of the data was still there. I sort of lucked out, that I was able to recover all of the data in her Windows directory.
I copied the files I needed from the disk that was not longer bootable onto my usb thumb drive. This is done under the "Places" menu. The process was really easy, as you can just use click and drag.
Once I had the file copied I exited out. I am not sure if the motherboard is bad, or if it is the disk drive. I may just wipe the drive and start fresh. Still have to make a decision on that one.
Luckily, I had a couple of Ubuntu Live Cd's on hand.
I simply placed a live CD in the bad computer and booted into Ubuntu. The live CD noticed the bad drive, which was no longer bootable, and mounted it. It seemed that just the boot record od the drive was bad, as all of the data was still there. I sort of lucked out, that I was able to recover all of the data in her Windows directory.
I copied the files I needed from the disk that was not longer bootable onto my usb thumb drive. This is done under the "Places" menu. The process was really easy, as you can just use click and drag.
Once I had the file copied I exited out. I am not sure if the motherboard is bad, or if it is the disk drive. I may just wipe the drive and start fresh. Still have to make a decision on that one.
Sunday, November 23, 2008
Find Your Hardware and Parts in Ubuntu
In Ubuntu, the best information can be gleaned from the system using the command line interface.
Here is an Ubuntu command that will tell you just about every thing you need to know about the hardware that is running on your system
From your desktop hit-F2. Check the "Run in Terminal" check box
and enter:
sudo lshw |less
Then enter your password when prompted.
You will then get a listing of all the hardware and parts that make up your PC or laptop
Here is an Ubuntu command that will tell you just about every thing you need to know about the hardware that is running on your system
From your desktop hit
and enter:
sudo lshw |less
Then enter your password when prompted.
You will then get a listing of all the hardware and parts that make up your PC or laptop
Friday, November 21, 2008
Ubuntu vs. Centos
I have been using Ubuntu at home for my desktop, while at work, it has mainly been Redhat.
In recent years, we have not had to build systems at our site, since they were sent to us pre-loaded with the OS, or we just install a CD, run a script, and the OS and associated software self installs. So easy a monkey can do it.
Today I had the chance to set up a server using CentOS. If you do not know, CentOS is basically a Redhat OS with all of the branding removed. CentOS is built from Redhat source code, so it is essentially completely compatible with any Redhat system. I have installed a lot of systems in my earlier days, but have been out of the fresh install game for quite some time since all of our programs and operating systems come pre-loaded. My recent install experience has been confined to just Ubuntu on a couple of home PCs.
Well, as mentioned, today I had a pile of CD's downloaded from the Centos site and proceeded to set up CentOS 5. Everything went as planned. The only difference I noticed was that the disk partitioning portions was not quite as intuitive as with Ubuntu. In addition, the number of CD's that were needed was a little bit of a pain.
I find that the method that Ubuntu uses for software updates a little more intuitive. Plus, it is easier to find information in the internet if something goes wrong. On the plus side, since there are so many initial packages to choose from (with all of the CD's), you get a much more complete installation for development work.
With CentOS, it was a just little struggle to compile some needed software from scratch where a few header files were missing. With Ubuntu, I thing I would have a much greater problem, since it is "desktop centric." Not really a bad thing, just a different focus.
In recent years, we have not had to build systems at our site, since they were sent to us pre-loaded with the OS, or we just install a CD, run a script, and the OS and associated software self installs. So easy a monkey can do it.
Today I had the chance to set up a server using CentOS. If you do not know, CentOS is basically a Redhat OS with all of the branding removed. CentOS is built from Redhat source code, so it is essentially completely compatible with any Redhat system. I have installed a lot of systems in my earlier days, but have been out of the fresh install game for quite some time since all of our programs and operating systems come pre-loaded. My recent install experience has been confined to just Ubuntu on a couple of home PCs.
Well, as mentioned, today I had a pile of CD's downloaded from the Centos site and proceeded to set up CentOS 5. Everything went as planned. The only difference I noticed was that the disk partitioning portions was not quite as intuitive as with Ubuntu. In addition, the number of CD's that were needed was a little bit of a pain.
I find that the method that Ubuntu uses for software updates a little more intuitive. Plus, it is easier to find information in the internet if something goes wrong. On the plus side, since there are so many initial packages to choose from (with all of the CD's), you get a much more complete installation for development work.
With CentOS, it was a just little struggle to compile some needed software from scratch where a few header files were missing. With Ubuntu, I thing I would have a much greater problem, since it is "desktop centric." Not really a bad thing, just a different focus.
Subscribe to:
Posts (Atom)