You guys are too nice. I had to mail-bomb my sister mercilessly to get the message across.
Your computer-illiterate friends and relatives don't know how to delete hundreds of emails at once, even if they're all identical. (Well, this was true a few years ago.) A one-line cron job can immobilize them for an hour or more while using less total space and bandwidth than the smallest Microsoft Office document.
I suppose a well placed goatse.cx link would do the trick, too.
Crusty slashdotter condescending to the condescending CS student.
Total loser (me) pointing out the prior condescension.
Total loser pointing out what a loser the last loser is.
There, and in tail form, no less.
Now you have to shift to the obvious meta level to point out how I'm wasting everyone's time with this thread. Except maybe the newbie CS students looking for an example of recursion to which they can relate.
I've had good luck using a similar class of machine as an X terminal. Of course the graphics were limited by the video card. The then-current KDE (about a year ago) worked fine over a 10Mb Ethernet.
I also went with Debian, and I also found the machine capable of light work. But, as an X terminal, it was perfectly responsive for everyday work with "modern" software. (The 640x480 screen was a little small for Mozilla.)
I can recommend bridging wireless networks as a fine way to avoid wiring a trunk for multiple access points. I did this with my house, and it works fine, despite not using dedicated hardware. (I've just got a collection of PCs, all with wireless client adapters, some with access points connected by Ethernet. Software does the bridging. The Airport Extreme solution sounds *much* more robust than mine, and you should *definitely* go with that if you don't have administrative access to the hosts.)
Slashdot Mirror
You guys are too nice. I had to mail-bomb my sister mercilessly to get the message across.
Your computer-illiterate friends and relatives don't know how to delete hundreds of emails at once, even if they're all identical. (Well, this was true a few years ago.) A one-line cron job can immobilize them for an hour or more while using less total space and bandwidth than the smallest Microsoft Office document.
I suppose a well placed goatse.cx link would do the trick, too.
There, and in tail form, no less.
Now you have to shift to the obvious meta level to point out how I'm wasting everyone's time with this thread. Except maybe the newbie CS students looking for an example of recursion to which they can relate.
I've had good luck using a similar class of machine as an X terminal. Of course the graphics were limited by the video card. The then-current KDE (about a year ago) worked fine over a 10Mb Ethernet.
I also went with Debian, and I also found the machine capable of light work. But, as an X terminal, it was perfectly responsive for everyday work with "modern" software. (The 640x480 screen was a little small for Mozilla.)
I can recommend bridging wireless networks as a fine way to avoid wiring a trunk for multiple access points. I did this with my house, and it works fine, despite not using dedicated hardware. (I've just got a collection of PCs, all with wireless client adapters, some with access points connected by Ethernet. Software does the bridging. The Airport Extreme solution sounds *much* more robust than mine, and you should *definitely* go with that if you don't have administrative access to the hosts.)