I got an image for Xubuntu, and upon booting from the CD, I saw an option that I hadn’t noticed in earlier editions (most of my installs were upgraded directly from 6.10 to 7.04.

The option read “Install with driver update CD”.

At first, I took little notice – because I knew the install routine, and I wasn’t looking for distractions.. then i got a little excited. In my imagination (?) “Install with driver update CD” would use ndiswrapper to search for drivers for non-supported network cards (like the wireless ZyXel card I got from woot.com recently)

“Insert a driver CD and press ENTER (i386)”

a few moments passed and I saw…

“Re-insert install CD and press ENTER”

Many minutes have passed and the power light on this wireless card has yet to perk up…

I found the solution on the ubuntu wiki … the driver has to be a linux driver – it isn’t intended to run ndiswrapper for you.. here’s the link: https://wiki.ubuntu.com/Ubiquity/DriverUpdates

Incoming search terms:

• ubuntu driver update Cd
• ubuntu use driver update disc
• use driver update disc ubuntu
• itunes xubuntu
• insert a driver cd and press enter
• insert driver cd i386
• ubuntu driver update cd install
• ubuntu install driver update cd
• ubuntu use driver update disk
• driver update disk ubuntu

Tonight I’m just doing the install and updating, and then I’ll check to make sure it boots well, and I’ll let it run for awhile to see if it gives any errors. Tomorrow I’ll look at setting up LAMP and other tools.

Some time next week I’ll begin migrating data over from the old server (a junked desktop) onto this one. I’m sure most of it will go fine, but I’m running a MediaWiki that i’ve grown very fond of.. I’m not sure how i’ll transfer it yet, i will probably try a mysqldump and cross my fingers.

• IBM Series x 345 Server, Model 8670 – 51x
• IBM ServeRAID – 4Mx Ultra 160 SCSI controller, p/n 06P5736, 06P5737
• ServeRAID version 7.12, downloaded from wherever you can find it, the file is called 32r274.iso, p/n 33P2640 or 19k6131 (?)
• There is some indication for the older version of ServeRAID version 5.10, 5.10.1, 5.10.2, & 5.10.3. Don’t use these. Opt for the 7.12 version – it’s easier to find and updated.
• I’ve had a lot of search hits for people looking for serveraid support cd v5.10, but I believe you’re barking up an outdated tree! I am adding a torrent for the correct ServeRAID Support cd v7.12, p/n 33P2640. The only caveat is that I will probably be the only seed for this file and my up speed is locked at 10 kb/s. I believe it is legal to distribute this, please correct me if i am wrong!!! The image size is ~ 459mb.

In the next few days, I’ll be experimenting with Xubuntu configurations and learning better OOP PHP skills to develop better apps for the server.

Incoming search terms:

• ibm x345 ubuntu
• ubuntu ibm x345
• ubuntu x345
• 06p5737 configutation utility
• serveraid 8i x345 windows 2008 server
• serveraid 7 12 download
• installing ubuntu on x345
• install debian on ibm x345
• ibm x345 serveraid driver
• serveraid support cd x 345

I have been working with the “/etc/apache2/apache2.conf” include file called “/etc/apache2/sites-available/default”; this is where the VirtualHosts are set. I’ve been trying to add a server side include (SSI) with

but I get an error that says one of the following (depending how I tweak it):

• /etc/apache2/sites-enabled/000-default:3: was not closed.
• Expected (something) but saw (something else)

I guess the point of the error is that the include tag won’t close properly, but it seems like no matter what I try I can’t get it to work. In my hunting, I found that it was an identified bug that was repaired in 1998… or so they say. I have to admit that I’m not sure if I should be placing the include inside any of the Directory tags, or if it goes in the VirtualHost tag.. or somewhere entirely different. Here are some of the resources I found helpful, and I’ll modify the post when I get it figured out. I do have a strong suspicion that this problem is related to an Unbuntu build of Apache, not Apache itself!!

• http://httpd.apache.org/docs/2.0/howto/ssi.html
• http://www.howtoforge.com/forums/archive/index.php/t-2513.html

I’m tired of futzing with it tonight.

I did solve one other problem today while I was installing sendmail through webmin. I repeatedly had the error:

• apache2: Could not determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName

whenever I forced a restart of Apache; it turns out I wasn’t paying much attention when I installed the server, and I didn’t give it a fully qualified domain name – i used “huanix” instead of “huanix.com” .. the fix is simple, all I had to do was edit:

• edit /etc/hosts
• etc/hostname

to add the FQDN (huanix.com) and things worked out swell..

Another fix that may be just as easy is to open up the apache config file (in Ubuntu, /etc/apache2/apache2.conf), and add the line ServerName huanix.com. I might try a wildcard, like *.huanix.com, but i don’t know..

Incoming search terms:

• apache2 ssi
• ssi apache2 set
• ssi lampp

1. Put some hardware together; I don’t have specific reccommendations here, except that you should use a dedicated computer. It doesn’t have to be powerful, but you may need to upgrade if you begin serving a lot of traffic (not likely in my case).
2. Secure a copy of Linux; I prefer Ubuntu lately, for my server I use a version called Xubuntu – http://www.xubuntu.org. Until you become a “pro”, you’ll want to install a desktop version, not the Server Install. (It’s easier to add server software than it is to add a GUI)
3. After installing Linux, you’ll also need to add server software. Apache is the defacto standard for servers. If you installed Ubuntu (Xubuntu), you can add Apache2 through the Synaptic Package Manager, to get Apache from the Apache Software Foundation (ASF) – http://www.apache.org. The folks at the ASF develops a lot of neat stuff, you’re looking for the HTTP Server.
4. Register your domain(s) – http://www.aitdomains.com
5. Estabilsh NameServer management – http://www.zoneedit.com
6. Go back to the registrar to modify nameservers to point to your IP.
7. Poke a hole in your Router/Firewall. You only need one small hole for Port 80 (called the HTTP port). This step will open up your server to respod to calls to your IP (and URL’s). This is where the idea of “acceptable risk” starts. When you open up port 80 people who access your server will have access to something called your “Document Root”, typically /var/www/. Now is when you become just a little more paranoid about your permissions and security.

Now you have to modify your VirtualHost settings in Apache2 to get the sites to respond properly. This is easier if you know in advance that the URL is actually being directed to your server – something I didn’t do in advance. Here are some tips:

• In Apache2, you edit a file called Apache2.conf to get your server running properly. This file has a call to include the Virtual Hosts directory- it’s at the bottom of /etc/Apache2/Apache2.conf, and it looks like this:

• # Include the virtual host configurations:
• Include /etc/apache2/sites-enabled/[^.#]

• The sites-enabled directory has a link called default-000 that leads to the ACTUAL Virtual Host file, /etc/Apache2/sites-available/default
• The easiest thing to do is copy the entire entry, and make one paste for each Domain you want to host.
• The only things you HAVE to change in each entry are “ServerName www.example.com” and “Document Root /var/www/example” – here, you will create a main folder to host each individual site.
• This is THE page to describe Name Based VirtualHosting on Apache2: http://httpd.apache.org/docs/2.0/vhosts/examples.html
• One key to remember is that you should put your hosts in order of your expected traffic. The top should be the site you expect to receive the most traffic.

]]> http://www.huanix.com/2006/11/18/setting-up-hosting-for-several-websites-at-home-using-one-ip/feed/ 0