Mike's Jukebox Distro is really just a floppy image that you add to a CD full of mp3's, using it as the El-Torito boot image. It has a complete Linux kernel and madplay, along with BusyBox. A simple shell script uses "find" to get a list of all mp3's on the CD, and it then plays each of them in order. tty3 is used for the player output, tty1, and tty2 have shells to allow the user to "play" while it's playing music.
PHP Auth is a very flexible framework for PHP applications that is loosely based on phplib. It requires PHP4 session support. The main difference between PHP Auth and phplib is the improved auth class. Additionally, PHP Auth includes support for user registration and user-level and admin-level account administration (change username, password, etc.). It currently has support only for MySQL, however, the database functionality is completely abstracted away from the rest of the code, so changes for other database systems should be trivial.
It's more of a user education problem
I, too, tire of people who act like this problem is unique to Microsoft operating systems. The reason it's not hit Linux yet (note: yet) is that 1) there aren't as many Linux users and 2) they're far more educated, on average, than most Windows users.
Even under Linux, though, folks download and execute programs all the time. A great example is a Makefile. How easy would it be to wipe out the user's home directory from a poison Makefile? How often do you check those when you download software?
Better yet would be to modify the user's .profile to scan their inbox and send annoying email to all their friends every time they log in. Better than that would be to send a copy of the original program, complete with poison Makefile, to all your friends and a subject line of "check out this cool bot that I wrote". It's a couple more steps than ILOVEYOU, but the point is that it would be just as easy, probably easier to program.
When I first started playing with the Internet 12 years ago, we passed our programming efforts around in shar files, or uuencoded tar files. A shar file is an executable shell script that recreates all the original files when you run it, and stores them in a format that can be mailed, posted to newsgroups, and split apart (kind of like an executable uu). While rare, there were cases of poisoned shar files that would wipe a system if executed as root. There was even one for VMS systems that would build the command "del sys$system:*.*" piece by piece and execute it at the end. For those of you lucky enough to be unfamiliar with VMS, that's the rough equivalent of "rm /bin/* /sbin/* /usr/bin/* /usr/sbin/*".
The point is that the ILOVEYOU worm, and similar worms, are not unique to Windows. It would be helpful if Microsoft made it more difficult to execute email attachments, but in the end, it's a user education issue, and Microsoft has been exceedingly lax in that area. A Microsofty, when pressed for comment on the ILOVEYOU worm, actually said (paraphrased) "as we've said before, people should only open attachments that come from an acquaintence." And yet ILOVEYOU worms almost always come from an acquaintence.
For now, Linux users are more educated. If Linux starts making inroads on the corporate desktop, things could get interesting. If you think Linux mail clients are smarter than that, remember that many will automatically decode a uuencoded file, and uuencoded files keep the permissions. The mail client can be made smart enough to not set the x bits, but are they now?