Slashdot Mirror

The 480p ogv file was only 75% bigger. Both files seem very high quality so I wonder what encoding parameters were used.

Can you give examples of good Exchange replacements?

Yes, for that see DVL. Seriously, though you have to define what activities you need to do before you can ask for a replacement. MS Exchange is marketed in many niches and fails (on the surface) in most. The most spectacular is its failure as a mail server replacement, if you look at it as such. If you look at the wonderful cover of plausible deniability it gives executives by randomly losing and delaying mail, then that is a success.

Anyway, try looking these. Keep in mind that, unlike with M$ products, you can combine pieces of several packages.

• Kolab — http://www.kolab.org/
• Citadel — http://www.citadel.org/
• Dingo Calendar Server — http://andrew.triumf.ca/dingo/
• Darwin CalendarServer — http://trac.calendarserver.org/
• Bedework — http://www.bedework.org/
• Zimbra — http://www.zimbra.com/
• OpenGroupware — http://www.opengroupware.org/

If you are simply looking to improve reliability of e-mail they a plain Mail Transfer Agent (MTA) will do. Before it became too embarrassing for M$, it used to be recommended practice to put one of these in front of MS Exchange to improve reliability and security. Also look up ClamAV, Spamassassin and how to do greylisting.

• simta — http://rsug.itd.umich.edu/software/simta/
• Dovecot — http://www.dovecot.org/
• Postfix — http://www.postfix.org/
• Exim — http://www.exim.org/
• Sendmail — http://www.sendmail.org/
• qmail — http://www.qmail.org/

However, before you can think about "replacing" MS Exchange, you will have to get rid of the staff that selected and deployed it in the first place. They ignored all the licensing shortcomings, the bad reviews, high price and ongoing technical failure to instead push ideology over technology. People making decisions based on ideology are not going to accept any technical or economic arguments...

'the cloud' is old networking/telephony terminology. Describing interconnection of two sites, you'd diagram the systems at either end, and their local links, but once the links enter the network you don't know or care how the routing happens (generally). This part of the network was 'the cloud' (and was diagrammed as a cloud).

By inference, cloud computing would be where you know the computation is happening somewhere on the network, but you neither know or care exactly where.

See this thread back in 1995 -
http://groups.google.co.uk/group/bit.listserv.techwr-l/browse_thread/thread/d6384bd640275c43/14da0963ed1c294a?hl=en%0Eda0963ed1c294a

Or the first diagram in RFC 1587 (1994):
http://rfc.dotsrc.org/rfc/rfc1587.html

I joined a telecoms company the year before that and the term was in use there, can't vouch for earlier.

Oops, I'm describing one of the many micro distros out there (I forget which one, but I have a feeling it was derived from muLinux). Damn Small Linux (DSL) is a step above these micro distros - a little more robust and a little heftier (weighing in at a whopping 50 MB and 128 MR RAM I think). For your case, I think just about any stable tiny (or micro) distribution that supports PPP should do. Some more tiny linux distros here.

http://mulinux.dotsrc.org/
Old as hell (1998), but the base system is 1 floppy, another for the workstation progs, another for the x11... So for a 16 mb SD card I think it can work...

But there is video.

Or this one in case the first is overloaded.

(Groklaw article where I took the links from is here.)

So of course it can run, and run well, on older hardware. The only question is what you have to give up to make it work well.

Something like this: http://www.cygwin.com/ ?
And there's a ports site, too: http://cygwinports.dotsrc.org/ KDE, Gnome, Xfce4 and many apps. Very nice :-)