I have an old server at work. It hasn't been used since last Spring. It lasted a fair amount of time (4 years)... yet it is still a fairly capable machine: 1.1GHz Xeon CPU, 2GB of RAM, 1 IDE system disk, a 3ware ATA RAID controller with 8ea 80GB drives (RAID5) and redundant power. I believe it was purchased in late 2001.
One of the RAID drives died and I put in a replacement today. I didn't need to rebuild the existing RAID because I wanted to do a new install anyway... but it makes me wonder if I should even bother. I mean, the drives that are in it now are at least 4 years old. They are an accident waiting to happen. So, I have a few options... I can retire the machine and scrap it... or I could spend around $800 and buy some new ATA drives. I figure that the hard drives are the most vulnerable piece in the system... other than say... the fans... that I'll replace if they are showing some wear.
Let comments be your answer!
Max Spevack sent out an announcement on the fedora-announce-list today regarding the future of RPM. I'm on the mailing list and I include the email here because I think it should be of interest to a wide variety of Linux users.
Sent by: Max Spevack
On: Thu 14 Dec 2006 10:42:03 AM MST
There has been a lot of discussion in the past few months about RPM -- its present state, its future plans, and its leadership team. In particular, the Fedora Project has received numerous requests asking us, "what are you guys doing about RPM?"
Here is our answer, in a few words. Then if you want more, you can read the rest of this note:
The Fedora Project is leading the creation of a new community around RPM. One in which the leaders can come from Fedora, from Red Hat, from Novell, from Mandriva, or from anywhere. Job #1 is to take the current RPM codebase and clean it up, and in doing so work with all the other people and groups who rely on RPM to build a first-rate upstream project.
The OpenVZ development team sent out a email today announcing the availability of kernel-2.6.9-023stab037.3. The main difference was stated as:
In-kernel sysfs/uevent layer is now updated to be compatible with FC5 and SLES10 userland.
What that means, I believe, is that whenever one tried to create a VPS of a distro that expects a newer kernel than 2.6.9, that distro would get very cranky... so installing FC5 and SLES10 VPSes used to require using the OpenVZ testing kernel based on 2.6.18. With this kernel upgrade, that no longer seems to be the case. Since I don't have any FC5 nor SLES10 VPSes, I haven't tested this out. Hmm, I wonder if FC6 as a VPS is supported yet?
After looking at a lot of the changes on the changelog page, there seems to be a lot of fixes. I've updated my OpenVZ Host machines and rebooted and it seems to be running nicely... but one always has to watch
/var/log/messages on the Host OS as well as
/proc/user_beancounter on the VPSes.
I think I have all of my VPSes tuned up well enough because I haven't noticed any
failcnt increments in some time.
Warren is the guy who has been running Gallery for a few years now. Me? I ran it at my previous job but I didn't get into it much.
Now I'm running Drupal and on the default Apache/PHP install, PHP is limited to 8MB of RAM. That works fine for most everything... but when you get into graphics processing, it isn't even close. Graphics Processing? The image upload (and photo gallery) module for Drupal take an uploaded image file and then generates a preview size (640x480) image and a thumbnail (125x125?) image. It can use ImageMagick or the GD image processing packages.
I got contacted by SearchServerVirtualization.com to write an article about OpenVZ, and like... it was actually a paying gig. :) In the article I introduce OpenVZ as well as explain the process container form of virtualization. Obligatory quote:
There are a number of virtualization products for Linux and while I have used a number of them, the one that best fits my needs is OpenVZ. OpenVZ uses a form of virtualization called "process containers." OpenVZ is not a hardware emulator nor a virtual machine but a form of operating system-level virtualization that offers a way of grouping processes (running programs or system services) together to create a Virtual Environment (VE) or a Virtual Private Server (VPS).
There were eight folks in attendance for Chad Bohannan's presentation on the Linux Virtual File System (VFS), Filesystem in Userspace (FUSE) and his porting of MaiaFS from a small embedded OS to FUSE.
Chad has been working with a couple of space satellite research projects with MSU-Bozeman and his goal is to port Linux to their launch vehicle and use the MaiaFS as a "forgetful" filesystem for data collection.
Chad covered the basics of the VFS, FUSE, and showed us actual code for MaiaFS. He explained that it is very easy to create and modify filesystems since the VFS/FUSE system provides all of the functions for everything and you just replace the functions you need and can ignore the ones you don't need.