PLEASE NOTE: Native Lighttpd Windows builds are available at http://en.wlmp-project.net/
The last available Lighttpd for Windows build that I created using Cygwin was Lighttpd for Windows 1.4.17. Updated September 29, 2009.

Because of a recent post on the lighttpd forum, I have decided to release my binary and source rpms of version 1.4.12. I built these all on an up to date version of RedHat Enterprise Linux version 4 (RHEL4). These rpms should work on both RedHat and Fedora. My versioning notes it as ‘KWEL4’; my ‘Enterprise Linux’ rpms.
Please note that you will need gamin (part of the standard distro) and lua, which I am also providing. Also note that if you want to install the mod_mysql_vhost rpm, you will need to have mysql (of course) and perl-DBI installed, both of which are part of the standard distro.

Download here

This site was offline from mid-day Friday September 22nd through the evening of Monday September 25th. The machine actually moved location, and DNS had to be updated to reflect the new IP address.
Why did this happen, you ask? Simple; we moved and so did the webserver.

In other news, Lighttpd for Windows version 1.4.12 should be released later this week.

This represents how I feel, along with how I’d react if I also had “powers.”

UPDATED: links are outdated. (Link was: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2.0b2-candidates/rc2/firefox-2.0b2.en-US.win32.installer.exe) Firefox 2.0 Beta 2 is out. Link pointed to the en-US version. If you need a non-English or non-US version (Link was: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2.0b2-candidates/rc2/) browse this directory.

So my band’s website and my business website (which is in its infancy) got hacked by the “Red Hackers Association.” My hosting provider for those sites have still not fixed the problem. Note that this site that you are currently viewing is not hosted by that company, but on my cable modem connection. Both sites were offline on Tuesday through Thursday (August 1st – 3rd), and today have the defaced rhetoric:

Here’s the full text of theire defacement:

Red Hackers Association / RedHack Team (Kizil Hacker’lar)

� own with Israeli sionism and barbarism! Down with the US imperialism! Long live the international solidarity of peoples! Long live socialism! Israel is doomed to be destroyed, the peoples of Middle East and the rest of the world will annihilate! – Abas la imperialisme est sionisme. Abas la Israel. Vive la solidarlite international des peuple. Vive RedHack �

MaNYaK | Tio | CrX | Partizan | Cruel | drk4ph3x | Csoft

Red Hackers Association / REDHACK TEAM 1997-2006

Abas La imperialisme und Sionisme. Hoh Di Internationale solidarlited – Israil Assasino!! AND F@#$ USA and ISRAEL

irc.ulak.net – #redhack
Her$ey iLLegaL .]

red-hack.org

Raise The fLag Of SociaList StruggLe Toward ImperiaList War And CapitaList CoLony..!

Thanks, jerks.

PLEASE NOTE: Native Lighttpd Windows builds are available at http://en.wlmp-project.net/
The last available Lighttpd for Windows build that I created using Cygwin was Lighttpd for Windows 1.4.17. Updated September 29, 2009.

Before I start, I want to put up a quick disclaimer:
This guide is intended to help out people who want to compile lighttpd for windows using the cygwin environment. It is just a basic, small howto to help get you started. It is in no way complete by any means. I am assuming a lot of things in this tiny tutorial. For example that you are running 2000, NT, XP, or 2003 Server, and NOT 95/98/Me or something ancient like 3.1 or DOS 6.22. I also will be assuming that you have cygwin installed with all associated compile tools, and that you have some familiarity with cygwin or a unix/linux shell.
Ok, with that said, are you ready? OK here goes:

Untar and un-gzip the lighty source package and enter its directory. Run:
./configure –prefix=C:/whatever/directory/you/want
(NOTE: use forward slashes above. Also, that is it “dash dash prefix” – 2 dashes.)
make
make install

Create a lighttpd.conf (or copy a previous .conf) to the etc directory
in your lighty install path. Try to run lighty from within the sbin
directory (from a C: prompt, not in the cygwin environment):
lighttpd -f ..etclighttpd.conf (NOTE: use backslashes this time)

It will complain about cygwin1.dll missing. Copy it from C:cywginbin (or where ever you installed cygwin) to lighty’s sbin directory. It will complain about more files missing; simply repeat the same procedure of copying the missing files from cygwin’s bin directory to lighty’s sbin directory. It will run eventually, test by going to http://127.0.0.1 (localhost) once an error does not pop up.

For more hints, check out the contents of the batch files I provide in
the sbin directory, and good luck.

I will accept comments, in order to help other do-it-yourselfers, but I will only make corrections to this mini-guide if I’ve made a huge mistake. Please do not point out that this guide is incomplete. I already know that, and have said it above. Thanks.

Reference: lighttpd forum – http://forum.lighttpd.net/topic/1102#2997 (Wayback Machine link; original seems gone.)

According to Netcraft, GMail is alternating between Linux and Solaris 8?

I always read and heard that Google runs Linux exclusively on their huge cluster. (here’s another link)
So I wonder if…:

• …Netcraft is determining the operating system incorrectly
• …Google is actually using Solaris 8 on some of their machines in the cluster
• …Google is using a few systems with Solaris as a “gateway” to their Linux cluster
• …I am the first person to notice this outside of Google. (Or at least the first to create a blog entry about it.)

Maybe we will hear something official. Or if there has been some kind of information released by Google regarding Solaris 8, please add a link to it within the comments.

P.S. – If you were wondering what GFE/1.3 is, it is Google’s web server software, which is rumored by some people to stand for Google Front End (version 1.3).

PLEASE NOTE: Native Lighttpd Windows builds are available at http://en.wlmp-project.net/
The last available Lighttpd for Windows build that I created using Cygwin was Lighttpd for Windows 1.4.17. Updated September 29, 2009.

Let’s say that you want to run one Lighttpd web server on two different ports. Port 80 for the production site and Port 81 for development.

1. Set your port for production use, either by leaving server.port
commented or set:
server.port = 80
AND
set your standard document root:
server.document-root = “/path/to/production/version”

2. Add these lines to your config:
$SERVER[“socket”] == “:81” {
server.document-root = “/path/to/testing/version”
}

3. Restart lighttpd.

4. Connect to http://hostname:81 or http://[your IP]:81 (http://192.168.1.1:81)

TROUBLESHOOTING TIPS:
If you still can’t connect, check your firewall settings. RedHat Enterprise Linux and Windows XP with Service Pack 2 are covered below.

For RedHat Enterprise Linux, do:
[root@localhost ~]# iptables -F
to flush all firewall rules as a test. Connecting to port 81 should not be a problem after that. A safer option is to just open up that port rather than dumping all your rules, if you are running a production box.

On Windows XP with SP2, go to Start->Settings->Control Panel->Windows Firewall. If ‘On’ is selected, click the ‘Exceptions’ tab at the top, and then click the ‘Add Port…’ button and type in 81. If you are using another firewall, do the equivalent for that firewall. Although I do not recommend it, you could turn off all firewalls momentarily to see if the config is set up properly, but that is very dangerous.

(This Mini-HOWTO inspired by the answer I provided here: http://forum.lighttpd.net/topic/958)