I have been experimenting with Ubuntu 8.04 codename "Hardy Heron" on two of my personal systems and the Linux test system stack I mentioned last post. I have not written much about 8.04 until now because, being pre-GA, there was not much I wanted to get into as far a discussion of its Enterprise Desktop Worthiness Quotient (EDWQ?)

I started testing with 8.04 Alpha 6, on my IBM X30 laptop. When that looked pretty good, I tried it on my Acer 5610 laptop, temporarily replacing Mint 4.0 there. I used both of those computers for while to do various things like write previous blogs and other perosnal documents, surf the web, and so forth. I kept them updated nearly daily, just to see how 8.04 was trending.

I later installed the Alpha 6 version at the office on one the Dell DX260's in the test stack. The point of this was to configure Evolution 2.22 to get a feel for how that was shaping up. Well, that and I had this cool new set of computers that were crying out to test something.

Personal GA

When 8.04 GA'ed, I did a clean install on the Acer 5610 and tested it for the evening.

To this point, I was looking at personal usability stuff, not Enterprise. My first off the cuff reactions to that were:

1. I like the new artwork, especially the abstract Heron on the desktop background. I showed it to my wife, and she does too. I showed it to some folks at the office, and got a "Yuch: too brown" reaction. Looks like the preference stuff I talked about in " Color Theory" are still true...
2. When I first brought up 8.04, I had no network connections. 8.04 "saw" the wireless card, and configured it. The wireless card "saw" all the local access points. I just had to pick one and all was good. But I knew to click on that icon and map that AP. Not sure a new Linux person would not have been frustrated there.be nice if a pop up or something mentioned "Pick an AP point to get started" or something.
3. Compiz seems to work really nicely on the Intel GMA 950 chipset on the Acer 5610, and I did *not* have to tell xorg anything about the screen resolution: It was correct from the get-go. Compiz even works on the X30 with its tiny amount of graphics memory: Vista should be hanging its head in shame. I turned Compiz off on the X30, preferring a crisp screen response to a pretty one. No point turning it off on the Acer: It snaps along pretty well there.
4. I'd have no issues installing this OS for a non-computer person. My brothers Mint 4.0 install is not in danger of being replaced though.
5. It seems like every Linux lately gets a bit faster: A bit crisper. I assume this is the latest set of tweaks to both Compiz and the Kernel. Ubuntu also tossed AT&T style Init a while back to get boot cracking along more quickly and that seems to be getting better all the time.
6. The new version does the best job yet identifying and configuring the ENE Technologies chipped MMC card slot on the Acer. Still does not see the card insert event to mount the card automatically, but if it is there at boot it sees it, and data transfers from it are faster than before.

LTS

This particular release of Ubuntu is more interesting than Ubuntu-average as it pertains to the subject of its viability as an ELD (Enterprise Linux Desktop). This is one of the Long Term Support versions of Ubuntu (the last LTS version being 6.06), with the desktop version of 8.04 being supported for the next three years (April 2011) and the server version for the next five years (April 2013). Given the amount of time a large company takes to get a new release of a desktop image ready, tested with all the corporate apps, and then pushed out to all the desktops, three years support is pretty much a requirement.

Ubuntu, knowing 8.04 was going to need to be supported for a while would tend to focus more on functionality and security related issues than latest and greatest eye candy, or at least that is my assumption. This is the kind of assumption that I'll be looking to test.

While I read some things in the trades about 7.10 being unstable because of how much feature and glitz the Ubunites added, I have to say that I never saw that. 7.10, and its Mint 4.0 variant, have been dead reliable for me other than the few Evolution issues I have already documented in this blog.

GA

With the arrival of the GA version, I installed it not only on my personal Acer 5610, but my BMC laptop, a Dell D620, and did a fresh install over the Alpha 6 version running on one of the DX260's in the test system stack. For the D620 and DX260 installs I took some notes:

First off, I used the 64 bit installer on the D620 because its Core 2 Duo CPU's support that. My first ever 64 bit personal computer install. Done 64 bit servers before, but for some reason, even with the 64 bit capable hardware like the D620, I had never installed a 64 bit OS. The Acer with its Core Duo processors (Not Core 2 Duo, surely one of the most ill advised processor naming conventions on the planet today, Isn't Core 2 Duo alot like say Core Two Dos?) and the DX260 with its P4 received 32 bit versions.

Install

There are seven screens that appear after you click the 'Install' icon.

1. For the first one, I picked "English". That seemed to make the most sense to me at the time.
2. This makes one of the most annoying new features appear: The time zone chooser. The picture of the world zooms in when you try to pick a TZ (I was going for Chicago, and the picture kept sliding about trying to escape the mouse. There was an old program I used to have for MS Windows back in the 3.1 days that you could put on someones computer and then sit back to watch them scream. It made all the desktop icons dance out of the way of the mouse so that you could never click on anything. The new TZ set feature reminds me of that program. Easier to just use the pick list, which thankfully is still included.
3. Screen 3 of 7 is what keyboard to use, and I have never once seen this program not know my keyboard type. I assume that there are issues here in other locales to make this screen worth stopping on.
4. For 4 of 7, I picked the manual disk layout option. I tried the default option with Alpha 6 and everything was laid out in one partition. That was not what I wanted so for GA I went my usual way:

        SDA1 is '/' and SDA3 is '/home'.

5. 5 of 7 I gave the computer my name, the name of the default account I wanted, and the name the computer should have on the network.
   
6. 6 of 7 was the recently added screen where it tries to find old userids from which to derive the settings. It found nothing. This was odd. It did not find anything on my Acer 5610 either, yet it has Vista as a dual boot, and this D620 has XP. Both had previously existing Mint installs too. This feature has never really done me any good to date. Someone must find it useful though.
7. 7 of 7 verified all my settings. I pulled the trigger, and for about 8 minutes things were copied off the CD. It spent about 2 minutes configuring things, and then was ready to boot to Ubuntu 8.04 LTS GA.

The 2.6.24-16 versioned kernel stopped to check out my hard drives on the way up, which added some boot time the first time.

There were no updates in the package repositories even four days after the GA date, which might be a first. Usually there is a last minute something or the other. Maybe being LTS they are more cautious about releasing things.

I proceeded to add the packages I need: things like Avahi, Sensors, HDDTemp, Macutils, HFS support, the debug packages for Evolution, Pidgin-SIP, WINE, and the 32 bit compatibility libraries (on the 64 bit installed D620 only).

Evolution was then configured, same as I ever do, against the MS Exchange 2003 servers.

Why Evo: a quick review

i have stated some of these next things about using MS Exchange from Linux several times, but I can not assume that everyone who might be reading this right now is familiar with everything I have ever written on this topic. Too easy to get here via a direct Google transporter. If you are a pure Linux, or at least Open Standards based shop, you might be thinking to yourself "Using MS Exchange is just suboptimal: Why not use something else?". Reality is that 50% of the big shops out there use MS Exchange, so no matter: it is something that just has to be coped with.

To work as an Enterprise desktop here, I need to be able to get at my MS Exchange sourced Calendar and email from Linux. The only ways to do this that is viable *at the moment* is:

• The Gnome Projects Evolution package, with the MS Exchange Connector (WebDAV)
• Using a web browser to get email off the MS Exchange servers Webmail. I am on record as not really liking this option because the web client is very heavy without real benefit and could use a strong lesson from Gmail on how to do Webmail right.

I do not currently consider the KDE Office stuff as all that workable against MS Exchange, but I am waiting for KDE 4.1 to see if the rumored updates/improvements in this area are in fact there.

Whats in a Name?

Evo is now at release 2.22, jumping from 2.12 in the last release. That is not as wide a jump as it sounds: they are just lining up the Evo release number with the Gnome release number. Nothing really new stands out in the user interface, although I have a feeling it has many subtle upgrades and tweaks and I just have not found them yet. Like those newspaper games in the comics section: "What is the difference between these two pictures?".

EVO Has Needs Too

Lots of them.

Evolution is a problematic beast. It is a large project, and none of the new tweaks appear to be in the code size reduction department. The only thing I noticed different during configuring the email client to use MS Exchange is that is appears to do a better job looking around for available GAL (Global Address List) servers. Every time I have configured it, it has presented a different one. Before, I always got the same wrong one. What algorithm it is using is still not obvious. I still have to over-ride it to put in the one I want it to use: the one nearest to me in the network.

I have noted in these early experiments with Evolution is that it is far more stable on the Dell D620 laptop than the Dell DX260 desktop. The laptop is far more powerful, with dual core 1.73 Ghz processors (7984.3 BogoMIPS) and 2 GB of RAM. The single 2.0 Ghz P4 (3989.49 BogoMIPS) and 512 MB of RAM of the DX260 just don't seem to be a good place for Evolution to live. It fails frequently there, and when it fails, I have to run my cleanup scripts before I restart it. Not a quality, Enterprise level experience. Sure, the DX260 is hardly what a current hardware shop would be using, but I expected Linux and its apps to work in 512MB.

Quick poking with a diagnostic sharp stick, and I have the performance problem down as not enough RAM on the DX260: With Evo up and running under the D620, only 15% of the RAM or 300 MB is in use for programs. With Evo running on the DX260, 50% of the RAM or 256MB is in use by programs.

I expected the desktop system to be crisper, given its faster hard drive, but the extra RAM on the laptop appears to more than compensate for the lower RPMS of the disk (4200 versus the desktops 7200), at least as far as Evolution is concerned.

When Evolution fails (and so far this is only on the DX260, but not the D620), it is always the MS Exchange connector that is failing. The main Evolution client stays up and running, but without access to the MS Exchange server, that is not very useful. I guess I really should say it is not useful unless you have other email protocols still up and running in any case. If you have Evo set up with IMAP, POP and other email protocols, the failure of the MS Exchange backend would only affect that one mail store, leaving the others to process email to their hearts content. I have in fact set up Evo from time to time to use IMAP and WebDAV-I.E,-Connector to the same mail store, so that when Evolution Connector fails I can still read email until such a time as it is convenient to blow out of Evo and run my cleanup scripts and restart Evo. That only works if you MS Exchange server is set up to run IMAP as well as the murky MAPI-plus-RPC protocols though at the same time though.

Based on the fact that it is working fine on my D620 I infer that my Dell 745 would run Evolution under 8.04 without issue, but will wait for Mint 5.0 before I do anything OS re-configuring there.

IM trying

Another of the suboptimal areas of MS Infrastructure that I have to deal with is our current IM standard.  MS Office "Communicator". Quotes because, like "Sharepoint", it only really works *at the moment* if you are running an MS sourced desktop. IE: you can communicate or share only if you are of the MS Windows population of computer users. Its like starting off a collaboration project by telling a part of your contributing population "we don't want to hear from you, because you think differently"

The Pidgin project is working on getting a SIP client going that will inter-operate, but I have had no luck to date with it, and neither have several of my Linux using compadres.

The good news is that unless I am running MS Windows someplace, like a VM, I do not have to deal with getting IM's. IM if hot hot hot out there, but for me it maps to YAIV: Yet Another Interruption Vector. Unless I need it for real time problem diagnosis, I tend to stay out of it.

Coming Soon

Ubuntu is out and looking good (even if Evolution needs a pretty stout system to run well), but that is only the beginning of the spring season. Still up are Mint 5.0, which of course is Ubuntu 8.04 polished to a fine sheen, Fedora 9, and OpenSUSE 11. More on those as they go GA.

There are some advantages to being in my job. Not only do I get to see all the cool new hardware, "play" with the systems of my youth (VAX 7000 anyone?), and see the same diversity of software as hardware, but I get to sort through the hardware discard pile. The discard pile has been pretty tall lately too, what with all the machines we are able to retire because of new technology like X86 virtualization. Sometimes a computer gem or two appears in that pile that gets hauled back to my office and then late one night after everyone has gone home, gets Linux installed on it.

He Started It!!

I moderately recently wrote a post about the possibility of using Mepis as an Enterprise Linux Desktop in an MS Windows infrastructure based shop. I thought I was being fairly clear about the ground rules of that particular evaluation, especially the "Needs to work with MS Exchange to work here" part. I said nothing about its suitability in places where one is lucky enough to *not* have to deal with undocumented and arcane MS Windows protocols. My thesis is that until Web 2.0 is able to abstract the end user away from the MS-created protocols or the special way MS creates non-standard versions of standards like Kerberos or WebDAV, a successful Enterprise Linux desktop will have to be able to deal with them directly.

"Off Label Mepis" was not universally popular with the Mepians of the world, especially over at MepisLovers. In the discussion of my post at MepisLovers one of the factors called into question about my testing method was that I had done it in a virtual machine. Every time I read a comment like that it is like going back thirty years to the early days of VM on the mainframe and frequently having OS/VS2, DOS/VSE, or MVS people tell me that VM was not a good place to test things. What is old is new again. Still, it is within the realm of the possible that things like timing issues of a VM [I.E. the way a virtual machine does not really know what is happening in real time, since all it sees are the times it is being dispatched] can affect a test. I have never had that happen on a test of Evolution against MS Exchange from a VM before, but anything is possible.

I repeated the test on real hardware, and my results did not vary on the key point that Evolution did not work against our MS Exchange server. That pretty much was what I expected, but it didn't take me that long to set it up to verify it so it was worth doing. I try not to ever dismiss a criticism if it might have any validity.

Ever since that comment I have been thinking it would be nice to have some standard hardware to be able to compare one version of Linux to another *at the same time*. Serial OS loads for a comparison are a pain in the stern. What if I want to go back and check a different thing or forgot to test something? Easy on a VM. A pain to reload and repatch on real hardware, even as fast as stuff like Ubuntu or Mint load these days.

I do have a small collection of old laptops: Compaq M300's. These are interesting to test with, especially for Linux on a laptop type things. But they are slow and have different amounts of memory. I talked about these units a while back, when I was first comparing Kubuntu and Ubuntu.

What came into my possession was four identical Dell GX260's. They had all sorts of advantages over the M300s:

• Small Desktop form factor. The GX series came in three case sizes. These were the smallest. These computers are old enough there is no picture on the Dell website though.
• Stackable: Little feet line up with dents in the case of the other unit. Four tall, it is almost a prefect cube shape.
• Moderately fast for my normal level of test gear: 2 Ghz Pentium 4, 512 MB RAM, 20 GB hard drives.

Also very nice was that my old production desktop system was a substantially similar DX340, so things I do with the 260's are mostly comparable with what I do on the 340 [same 2.0 Ghz Pentium 4 CPU], other than that the 340 has 1.2 GB of RAM and an 80 GB hard drive.

Virtualization Strikes Again

It is worth noting that the four DX260's came into my Linux-loving arms *because* of the success in our R&D labs of virtualization. I talked about this a bit in "Virtually Greener". The particular lab these came out of has gone from just over 250 computers pre-virtualization to todays 120 computers: more than a 50% reduction in the lab. These four plus a couple of others are the only ones that were re-deployed in other missions. The rest have been sent to the great computer recycler in the sky. Or maybe New Jersey. Someplace.

These four desktop systems had been sitting side by side on a shelve in a 19" rack, their small form factor actually working pretty well in that regard. They had been running various levels of MS Windows Server for testing things. Now they are going to show up over at Linux Counter.

The Six

Add in my current production desktop, a Dell 745, and I have six different systems to run six different versions of Linux *at the same time*. The 745 is currently running Mint 4.0, and will go either to Mint 5.0 or Ubuntu 8.04 in the near future. I have been testing 8.04 on a my personal laptops (IBM X30, Acer 5610) for a while now, and it is very impressive.

• The 340 has been running PCLinuxOS 2007 since I last posted about it here. I donated money to that project to get access to the faster servers and more recent / additional packages and updates, so it is fully set up and tweaked out the way I like it.
• 260 number one: Ubuntu 8.04 beta (LiveCD)
• 260 two: Fedora 9 Alpha (LiveCD)
• 260 three: OpenSUSE 11.0 Alpha (LiveCD)
• 260 four: Mandriva 2008.1

The 260's and 340 are hooked to an Avocent switch, a Dell 1280x1024 17 inch LCD panel (172FP), a Sun USB keyboard, and a Dell USB mouse. I was able to get all but one of them running correctly at 1280x1024, but Mandriva and OpenSUSE has to be told to use that resolution, preferring 1024x768.

All were installed on the entire hard drive. All use GRUB. Poor LILO. Seems its fortunes have passed.

The one 'running correctly' hold out is Fedora. It works fine off the LiveCD, but gave several problems on the install. One of which is that there can be no swap space defined while installing it. It is a documented problem that Fedora knows about so I assume the next release of two will fix it. The other is that once installed it will not boot at all. Just won't. When I want to look at Fedora 9, I just run it on the LiveCD for now.

Only Mandriva is an official release, so I will not make any judgments here about the relative anything about these OS's, other than to say Ubuntu as a Beta is farther down the road to GA readiness, and was dead easy to install, but the updates are still coming fast and furious in 'Update Manager', so it clearly is not done quite yet. It is less than a week away from GA as I write this in mid-April. Fedora 9 is set for Mid-May, and OpenSUSE 11 mid June.

I wanted to get this config and what I am planning on doing with them set up here in this post, so that I can refer to this test set up as these releases come to GA'ness over the next few months, and I can look at them on a more level playing field. As always, I will be trying to figure out the big question: Which of these desktops work as Linux Enterprise desktop OS's (whether they were designed to or not).

Finally, you might have noticed Mepis is not among the test stuff. If I had one more 260 computer, it might have been. But probably not. Mepis, according to the folks in the MepisLovers forum, is waiting for KDE 4 to add all the bits and pieces required to support MS Exchange, eschewing Gnomes stuff that is already there. I do not know if that is accurate or just the opinion of the poster, but until I see a hint someplace that Mepis or KDE 4 has made some moves such that they interact better with the MS Infrastructure I have to deal with here at the office, I will probably not spend any more time on it.

And now for something completely different..

i just wanted to insert a quick note here, in case anyone was wonder what has happened to the rate I have been posting recently. The answer is:

1. Bladelogic
2. End of quarter, end of fiscal year
3. Reviews

I have been involved in the activities around bring BMC's latest member of our family into the fold. The BladeLogic acquisition has been hugely exciting, but it has kept me pretty busy.

Then, we not only closed a quarter but closed a fiscal year, and at time like that I take off my R&D Support hat, put on my Production IT hat, and help where I can.

Finally, this is review time for my team, and writing reviews take me a great deal of time and effort...writing time that I don't spend writing here.

That's my story, and I'm sticking to it.

This post is to do a wrap-up of the topic I have been posting about on and off here for a while about the new mission critical NAS server cluster based off CentOS5. Previous posts in this series, starting August 29th of 2007:

1. Tru64 NAS Server Replacement Project
2. NFS, GFS, nodirplus / readdirplus, and Tru64 updates
3. CentOS 5 NAS Cluster
4. CentOS 5 HA Cluster Speeds and Feeds
5. Kernel Hackage
6. One Week Later 
7. Bug 431253
8. GFS or NFSD?

We are not quite done with the migration of all the file systems off of the Tru64 TruCluster. It's original ~4.5 Terabytes have been slowly absorbed by the new Linux cluster. We have been very cautious. We wanted to make sure that we introduced change in a controlled manner, in case we had any more of those HP-UX client type issues lurking in the woodwork. Dan Goetzman, chief NAS abuser, did find another one, and only this week too. More on that below.

Semantics

We also have the fact that we are still running our modified version of the CentOS 5 OS. Neither RedHat nor CentOS either one has closed the issue we opened (See post "Bug 431253" above), and I think that is a smoking gun waiting to shoot some folks in the toes. Here is why I think that: The file open / close semantics used to "live" inside the code provided by each file system. Ext3 file open / close code could therefore could be slightly (or even very) different from GFS or XFS or some other file system, since each file system was written at different times and places by different people for different reasons, and in some cases like XFS or JFS, for different operating systems than Linux. XFS comes to us from SGI, therefore Irix, and JFS is from IBM / AIX.

Recent kernels have provided the file access semantics internally. An installable file system is not required to use them, but they are available to all. The file system maintainers have started to move from the code inside each of the various file system types to routines in the kernel. It makes sense: Why maintain this common code in all these different places?

GFS went 'there' (to using the kernel file access routines) first, and it is our belief that that this is where the HP-UX client issue was introduced. The kernel routines (written by a subset of people who more than likely did not write all the internal routines contained in all the different file systems) don't work 100% the same way as those buried in the file system code. This might be a bit of understatement.

Since Dan's reading on the subject leads him to believe that the other FS types were going to migrate to letting the kernel handle the semantics, that was/is going to put everyone in the same boat. The broken HP NAS client boat. So the metaphor is not too mixed, the smoking gun is then used to shoot a hole in the bottom of the boat, passing through ones toes and perhaps some aquatic life forms.

We don't have to migrate to a new version of the CentOS OS any time soon though. CentOS is working fine. Dan's file semantics kernel patch is working and has long runtime on it, so we have confidence we can move forward. We do have some motivation to move forward if we can: The TruCluster is off both hardware and software support.

Ouroboros Tru64 TruCluster

The Tru64 TruCluster hardware now has so much excess capacity, since its formerly brimming file systems have been "drained" over to the CentOS cluster that any hardware failure could easily be dealt with by self-cannibalization. Ehww. Sounds ugly when I type it that way. True though: we have two ES40 server nodes, each with four GB of RAM and four CPU's. There are empty RAID sets of all disk capacities (36GB, 72GB, 144GB). The fiber channel cards, Brocade switches, memory channel, etc are all twinned out for the TruCluster. If something fails, it fails over to the surviving bits, and in the seven years we have had this gear the only failures we have had have been either of disks or failures of imagination. In failure mode, we can choose to either ignore it now, or use the redundant  capacity, raid other Alpha based gear for parts (I still have VMS servers running on Alpha gear which in a pinch might give up their lives), or worst case do a time and material call to HPQ. More than likely, the TruCluster will just eat itself though, reducing in size and capacity as it goes. That takes care of the hardware.

The software is a different story. It can not eat itself ... hopefully. It never has anyway. It is stable and we have not patched it in literally years. Before that the patch rate was pretty low, and consisted of mostly point patches for specific problems. Stability of the OS / NAS bits is good news and bad news.  Good that it is stable. Bad when things like NFS V4 are starting to creep into the shop, which the TruCluster just will not deal with other than by forcing the client to downshift to V3 or V2.

Easy Does It

This slow migration of critical file systems allowed Dan to not be spending such a concentrated, focused time on data migration, but to go slow, do a good job, and think about each move in depth. Quality still counts, especially when you are moving your most critical bits and bytes!

As I write this, I just looked at the status of the move on the internal Wiki: the vast majority of the file systems that have for literally years lived on the TruCluster are now over on the CentOS 5 cluster. We have been running builds and packaging against them for months. 

The uptime of the cluster as a whole has been satisfactory. We have had no customer facing service outages at all, and even if there have been rolling upgrades or individual node outages, they have been inside the design parameters. The point of doing this as a cluster was to be able to offline a node, work on it, then have it rejoin the cluster, and Dan has taken advantage of that to upgrade the ILO cards and do various other service related things. I looked at one of the three nodes a moment ago, and it has over sixty days of uptime. That does not matter though: the customer facing service uptime has been pretty much since we put it into service last December.

The main thing, and this is the key point is that our customer never knew we did anything to the cluster, and that was just exactly like what we used to do with the TruCluster, even if the underlying OS, and clustering technology, and hardware, and therefore technical procedures are completely different.

Sun Client Bug

Since I last posted here, we have discovered one more unruly client. This time is is Solaris, and the fix is a patch to that OS, not something to the server. Dan as usual has been all over the problem. Here is what he found. First a note in web forum from Casper Dik at Sun:

Casper H.S. *** <Casper.***@xxxxxxx> writes:

"Ross" <nospam@xxxxxxxx> writes:

Thank you, Casper!
Here is the output:
bash-2.05$ cd testdir
bash-2.05$ ls -f
.. testfile .

Ah, yes.

The chmod code is broken and can't deal with "." and ".." not
being the first two entries of a directory.

Casper appears to be a pretty valid authority on such things, according to some research someone on my team did, turning up this:

• http://blogs.sun.com/casper/
• http://en.wikipedia.org/wiki/Casper_Dik
• http://www.sun.com/cgi-bin/sun/bigadmin/xpertApp.cgi?session=16_prm&xpert=cdik&action=bio

Dan used Casper's information to find this:

"There is a Solaris BugID for this exact problem, they seem to know about it.
 It appears to be only fixed for Solaris 9 and 10;

125499-01 - For Solaris 10 on sparc
123394-01 - For Solaris 9 on sparc

I [Dan] applied the patch to [a Sun system we use a lot], and all is well.
Fix is going to be on the Solaris side for this one...

The patch fixed chmod/chown as that is what it patched. It looks like chgrp is still broken, same exact defect.
So far, I cannot find where Sun has fixed chgrp for the same problem"

This is not a show stopper as near as we can tell, at least for us. Your shop, and mileage of course will vary. Peeling back the covers a bit, Dan found the underlying bits to this that were causing the problem:

Relative Costs, Relative Features

I have noted here before why we went to the complexity and expense of the TruCluster, but assuming you have not read everything in this blog over the years about that subject. That goes all the way back to the beginning in 2005, in posts like "Linux and NAS", where I noted this:

"We take a 2 tiered approach to NAS storage for R&D Support. In our first tier is the 5 9’s type storage. The stuff that just can’t go down. The bits and pieces that are used on our “assembly line” to build and manufacturer our own products. The kind of storage that, if it were down would idle hundreds of people around the world in R&D and endanger our time to market. And we know with a great deal of pain just how critical this storage is, because we used to use a storage appliance there, and it could not survive our network. It crashed all the time, and we paid for it dearly."

We paid pretty dearly for the TruCluster too: round numbers about 140k per Terabyte. Sure, a single SATA disk has a Terabyte now, and for a bit less money per TB. For fun, I divided the cost of the TruCluster per TB cost by the cost of a TB SATA disk, and the spreadsheet said that the disk basically cost nothing, as a percentage. Tweaking up the accuracy a bit higher in OpenOffice Calc, I get 0.00277. Pretty near free.

I will not say that the CentOS 5 based system is as good as our TruCluster is/was. It is both better and worse, and depends on how you look at it. How you define "better". That it achieves high customer facing uptime was a requirement. That it is as fast or faster (and it is faster at some things, such as CIFS) was also a requirement. It would not even be worth pursuing without those very minimal goals. It is less expensive. On the down side, our little Linux machine is not as HA, since nothing invented on this planet yet today can match TruCluster on that score. Sigh. <tongue-in-cheek> I guess that is why it had to die. </tongue-in-cheek>

There are things the new server did not have to be. One obvious thing is that it did not have to be the same SSI cluster architecture as what came before it. TruCluster is just one possible SSI cluster. The best one out there, but there are others. There is a Linux SSI project, although we gave up waiting for it to mature to the same place (or near enough for our needs) as TruCluster. According to the feature matrix of the current OpenSSI product it looks like it might be viable for NAS now: NFS-HA is listed in any case, plus " A highly available cluster filesystem with transparent failover.". Maybe our next generation NAS server will have a look there. The technology moves so fast that every generation has been significantly different than the one that came before it. But I slightly digress.

The primary design goal of the TruCluster based NAS server was not to use the technology for its own sake but to have NO customer facing service outages. The new server did not have to be SSI. It just had to achieve the same thing from the point of view of our R&D customer. Serve files fast and reliably: be NAS data-tone.

The TruCluster is/was far more high performance on the I/O subsystem, to say the least. Hundreds of disk arms versus the one SATA one in this comparison. Cache in the NAS heads. Cache in the HSG80 disk controllers. Cache inside the disks. Disks spinning 25% faster. It is not a fair or even sane comparison. At best if gives a hint about how one might go about building a lower cost solution with high density disks as a starting place. Even at the high cost of the 2001 Tru64 based solution, the avoided cost of downtime paid for the TruCluster over and over and over. I tracked it once. I figure, based on how bad the NAS appliances had hurt us, and based on a few times when the TruCluster stumbled on various issues, but did not fall due to its design, that we came out about two million dollars *ahead*.

With the passing of Tru64 into that dark night, the new kid on the block comes with a very different price point and way of doing things. I have posted the design here already (in the links above), and the speeds and feeds. so I will not beat that to death. The main point here is that our current tier 1 file server solution, 7 years down the road from out last one, is not the same technical solution, but leverages commodity parts and prices, is assembled a slightly different way to achieve the same service goal, and runs about 1.5% of the cost per Terabyte.

That cost is not the whole story. The Tru64 Trucluster came with vendor support. Hardware and Software. Some of the best in the biz too: Ex Digital folks with a passion for their gear. Our solution is supported by us, and while the hardware has support contracts with Sun and Apple, we also have onsite spares of most of the major subsystems so that we can get the unit subsystems back up and running fast. If it works right, most downs should *not* be customer facing.

So far, so good.

I have read a great deal about the OLPC XO-1 over the last two years, and I have written about it myself a few times, starting with my "Linux Inflection Point" post from April 13th, 2006. More recently I spent some time with a couple actual XO-1's at the BarCampAustin III event, which I talked about a couple of posts ago. Yesterday, my "Give One, Get One" unit showed up at my house. It even had a blue "head" ( O ) on the case, which I hoped for, but could not ask for. You get what you get. There is a large emoticon on the case made with the X0 that sideways looks like a persons body and head. There are twenty different head colors and twenty different X/body colors for the large XO emoticon that decorates the head unit of laptop, for four hundred different color combinations. I wanted Blue/Blue, got Blue / Light Green. Close enough.

In all the reading I have seen about the XO-1, outside the OLPC website and Wiki, most of them have been reviews of the technology: Hey, look how small it is. How can a 433 Mhz processor possibly be fast enough? 256 MB RAM? How is that usable? How do you open this thing?. Lookie: it's Fedora Core 7 with a 2.6.22 kernel and a totally new user interface (called Sugar)! I wonder if I can put Ubuntu on here... USB and SD slots! Cool.

Sometimes the articles are reviews of how kids interact with the cute little boxes: Opened it in no time. Had web cam going in less than five minutes. Lots of laughing and smiling and happiness.

I couldn't wait to get one and play with it myself and see what my reactions would be. Having read a bit, and played with Anne Gentle's units, I had a head start. I was not going to be the dopey adult how could not even get the thing open or anything. I had some idea what the special keys did.

I admit it: Like most techies, I went for the technical side first. I hunted for, found command line and poked around the OS. Under the covers, it looked like every modern Linux I know. I inserted a 2GB SD card, and it mounted it. I stored files there. Then I started to think about how kids might play with it. What they might learn. How this might appear to someone who had never seen a computer before, or at least had never had a chance to touch one. Play with one.

It started to remind me of my first chemistry set. I did the regimented experiments that came with the box for a while, but then I just started to play with it. Try different things. I accidentally made a clear silicate looking ball of material without knowing how I did it or what it was. I also thought of the time I pulled a broken alarm clock out of the trash can and took it apart. My dad asked me what I was doing: he didn't know it was from the trash, and thought I was taking apart a perfectly good alarm clock. Back then alarm clocks had a motor and gears, and I had it apart to see what it was, how it worked, and to see if I could fix it. My dad thought I had just busted a perfectly good alarm clock. It went back together, and it worked for years after that, but in truth I was not really sure how exactly I had fixed it. I intuited my way around the thing poking and prodding and turning things till everything spun, and it was all OK after that.

That is what the XO is, but for a new world. A world where not having computer / technical skills means you are limited in the things that you can do. 

After a night of messing with the music application, and the Python programming application, adding new applications like Gmail via the free downloads at the OLPC Wiki, downloading US Grants biography from the Gutenburg project to use the XO-1 as an ebook reader, and generally messing around, I put the XO-1 down around 12:30, and picked up my iPhone to look at what todays schedule looked like.

iPhone Attack

My technologist mind reeled. My wife, who was sitting next to me working a Sudoku Puzzle on her iPhone (national rank: 425 on the NYT puzzle she tells me, unless they had another of her favorite "diabolicals" in which case it is probably lower) asked me a question about the XO. I am unable to recall it. My mind was flashing back out of the play zone I had been in and back to the other world I live in. The contrast between the technology of the iPhone and the technology of the XO stood out in stark contrast.

Here in my one hand was this tiny Internet tablet, with a processor 1.5 times the Mhz speed of the XO, same RAM, 8 times the "disk" space, hugely brighter and more vivid screen (even if lower resolution) with higher DPI. 1/6 or less the weight. 4 times as many radios. Sure, the iPhone is more than twice as much money, and that is right now before the XO gets the volume up. No educational software to speak of: not yet anyway. The iPhone is, frankly, a rich person / countries toy or perhaps instrument. A very shiny, blinding one. For a brief moment I lost sight of what the XO was. Suddenly it was was this other thing. This seemingly slow, low tech thing that made no sense to me. I lost sight of the child. All I saw was the high tech thing in my hand and wondered why I would ever use this other device.

By and large I won't, other than to play. It is not for me. The concept of the XO is hard to grasp. Mysterious. It is not a toy. It is not technology. It is not, at least to start, Linux.

It is like Zero

Zero

Charles Siefe wrote a great book back in 2000 about the mysterious and dangerous number Zero. Zero is a very interesting and not very well understood number. Without it, all of modern science does not work. I know this not just because of the book, but because Commander Samatha Carter told Daniel Jackson that on Stargate: SG1. Without Zero modern physics can not exist. Infinity can not be dealt with. Math breaks down and can only do very basic things. As obvious or at least as accepted as zero is today, it had a long and tortured trip to acceptance, and there might still be a few that have not accepted it. Without zero there is no space program, no computers, no modern medicine. Without knowing how to use zero, one is doomed to a life of low tech.

You don't have to know zero if all you plan on doing with your life is living with things you can build with your hands, or perhaps certain other low tech pursuits. There is not anything wrong with only wanting those things either. However, if you want to get involved in the modern world there are things you have to know. Things you have to learn. Concepts that have to be mastered. Zero is one of them.

Technology is another. Learning the simple mechanics of a keyboard, or the logic of a program, or music or any of a myriad of other things that we all take for granted in the western world. My kids grew up with Linux computers from the time they could first type. They could install software, and later even tear down and rebuild desktops and laptops. They had access to this stuff from the very beginning of their days. They were very lucky.

XO-1

The XO-1 is a learning tool, and it is a superior one. It may be slow by modern standards, but it is not in a Mhz race. We technological types often get lost on the spec sheet, forgetting things like my first computer (A TRS-80 Model 1) ran at 4 Mhz. It only ran on 110v, could not be networked other than by a 1200 baud modem, and could not be schlepped about. It still managed to help me learn Basic though.

The XO is the delivery vehicle of a much larger concept than speed and feeds and the underlying technological platform that seems so woefully slow and small to my iPhone educated eyes.

It's job is to teach. To enable. The principles on the OLPC website take us part of the way there:

Our five core principles—

Child Ownership: I wear my XO like my pair of shoes.

Low Ages: I have good XO shoes for a long walk.

Saturation: A healthy education is a vaccination, it reaches everybody and protects from ignorance and intolerance.

Connection: When we talk together we stay together.

Free and Open Source: Give me a free and open environment and I will learn and teach with joy.

It is far more than that though. If the XO-1 is never delivered to every child on the planet (the only way one could keep these cute little things off eBay and in the hands of the kids is if they are ubiquitous), it does not matter. OLPC has been criticized as being heavy handed. Home schoolers in the US are angry because it is not easy for them to get them (it takes 30,000 USD minimum commitment outside the Give One Get One program that is now over to get one here in the US). Intel is woofed because AMD provides the processor. Microsoft is woofed because Linux is at the core of the OS.

None of that matters. Sure, as a Linux person I am happy about Linux as the Core OS, but that is not the key thing. The key thing is that the people that love the XO-1 and are giving them to kids, and the people that hate it and are doing everything they can to get *their* computer into the hands of the kids of the world are all doing the same thing. A US President used to call such things a hand-up, not a handout. They are giving kids who would never otherwise have had a chance to get a hold of technology and related ideas and paradigms a chance.

They are delivering Zero to the world.

Last week in "New MAPI connector project for Evolution" I wrote about the new MAPI access project I had uncovered for Evolution. I mentioned there I was a bit dubious about how they would be able to do the API work that HP was not able to do over the course of years with HP OpenMail. I think the plan to get it going relied on the fact the MS was going to publish the API's as part of the EC's ongoing anti-monopoly legal actions and MS's responses. A very long and complicated and generally hairy subject beyond the scope of this simple post.

Over at ZDNet, I read this article today titled Gaps found in Microsoft Exchange API documentation.

I am reading a bit between the lines here, and extrapolating from history, but I am pretty sure this is the cause of the problems I have had with testing the new MAPI service provider.

Last week I grabbed up my trusty IBM T41 laptop, which is running OpenSUSE 10.3. I had two big experiments I wanted to do. In the late night hours I loaded up both the KDE4 desktop, and the MAPI stuff from jjohnny.

MAPI

As one would expect from a basically Alpha / early beta project, there was no real doc to speak of. The FAQ gave me the clues I needed once I had installed the RPM's to get the MAPI service to even show up. That was in fact the hardest bit. Here is what basically worked, right before it did not work at all.

1. Downloaded the three required RPMS from jjohnny (at the link above) to a special directory
2. Installed the RPMS with 'sudo rpm -uvh *.rpm' while in that directory. No Errors.
3. Rebooted to be sure the box was clean of pre-running processes
4. Brought up Evolution
5. Enabled the MAPI service provider in 'edit/plugins'. This was key! Before that, the "domain" question would not appear in the account setup dialogs.
6. Set up MS Exchange account info in 'edit / preferences'
7. Exited Evolution and again rebooted just to be sure everything was all clear. Felt like I was using MS Windows. :)

Everything looked OK, except that when I started Evolution, it would crash dump. I sent that to the Gnome folks.

Now I see this article and lights start going on. I wondered how the Evo people were planning on getting this ramped up so fast: They had 2.24 as their target release!

I checked right before penning this article: no new RPMs for MAPI since last week. I will keep trying as I find or have new things to try. For now though, WebDAV/Connector is still my Linux way into my MS sourced calendar.

If you have ever been to a BarCamp like BarCampAustinIII, then you know that each one is a unique, lightening in a bottle, not to be missed if at all possible. If you have never been, then it should be added to the list of things to do before you ... err... something less dramatic than “Die” but makes the point about the event. Insert your own drama there. Lets just say that it is right up there with sliced bread.

If you have not been, describing one is not easy. Here is a travelogue to attempt to give a flavor of what this event is like.

This year I was in the "official" role of volunteer. I showed up a day ahead of the event to see what needed helping-with, and tried to help. This evolved into meeting the others on the organizing committee that were working with Whurley to put the event together.

The venue was the very impressive “Idea City” of GSD&M, on West 6th Street near Lamar in Austin (as the name implies...). This is the place where they come up with some of the best commercials on TV: My favorite being the one where the designer is taking the couple through a building showing them pictures of he previous work, including the IBM building in Seattle, and basically being full of himself. Finally, he settles into his desk chair and addresses the couple, asking how he might help them. The woman pulls a water faucet out of her purse and says “Design a house around this”, then waits amused for his reaction. The building was perfect for what BarCamp needed.

There were last minute crisis: The train with the t-shirts for the event had literally derailed. Last minute scrambling had another set on the way, and they arrived less than 12 hours before the doors opened.

The folks from Viewzi.tv set up an impromptu studio in a corner of the lobby, while some of us assembled the lanyards and badges. Turns out this was Viewzi’s launch event, but I did not know that at the time. Some of us went home for so sleep before the main event, others carried on well into the night.

Saturday morning at 8:00am chaos was in the process of not so much being tamed but having pointers placed into it. BarCamps have some people planning what they will talk about for months, and others deciding at the last minute what the will do. part of it depends on who comes, and what the wisdom of the group is. In this sense, a BarCamp is to a technical conference what Open Source is to closed. I being new to the BarCamp “Staff” thing had started to figure out that no one was going to tell me what to do or how to help. If I had to be told, it appeared it was going to be easier to just work around me. So I started finding things to do and owning them. Unpacking T-Shirts onto tables. Laying out the tables. Retrieving the badge Sharpie pens from whoever just stole them *this* time. Near me others set up paper charts on the wall that people could put post-it notes on with session names for the various conference rooms. They like Sharpie Pens over there it should be noted. Someone else was dealing with the bands, and the food, and the beer, and the battle bot, and the zillion other details that have to be done, and the all had been decided (as near as I could tell) at the last possible moment.

The Wiki was being updated as things were decided, and as sessions were set. Not too many: just a few that the folks setting up knew were coming or were giving themselves. By 10:00 AM the doors were open, and it was clear that chaos was to continue. I decided to be the greeter, and show folks where to sign in on the iMacs, hand them badges and Sharpies, and point them to the swag table (now laden with over 2000 free T-Shirts), the free drinks from Vitamin Water and Sweet Leaf Tea, and the sessions wall. The iPhone DevCamp folks arrived and were set up in a room, only to be seen from time to time thereafter when they needed food

I don’t know when the session board filled up. It was pretty quickly after that: All sorts of things were up there, from the announcement and demonstration of Operas new mobile and mini-browsers (8:00pm, Omega Room), to cloud and other social networking sessions to a hands on session at 12:00 by Anne Gentle about the OLPC XO laptop. I went to that session, abandoning my post of greeter after two hours. Someone else flowed in to the obvious vacuum and greeted folks. At this point I was really starting to get the magic that is a BarCamp, where everyone helps out to do what has to be done and keep chaos just slightly at bay. It even got better.

The XO’s are tiny: Smaller than I expected, but they are way cool. Anne had two: Her personal unit from “Give One, Get One”, and a spanish keyboarded developer version she was using to write documentation for the units. Among other things in that session, we set them up and used the “Dolphin” application to have them acoustically ping each other and report their distance to each other in meters. 3.4 Meters.

Lunch arrived (Banzai Burritos from Wahoo’s), and Anne decided to set up the XO’s in a central area so others could see them. When she had to go for a while, I stood with them so others could walk by and have a look. For the next three or four hours people flowed by the XO’s and we talked about them and the OLPC project. There were two consensus items: US schools need to have these things. All of them. Home Schools. 1A schools. All of them. The 30,000 US dollar price that is the entry to buying them (outside of the now past “Give One, Get One” program) is just too high for small and / or rural schools. The other was that the “Give One, Get One” program needs to return.

The sessions continued (about eighty or so sessions were now on the board), and the iPhone guys peeked out, blinked in the light, scooped up some more caffeinated beverages, and ran back to their conference room to continue their battle with the new SDK for the iPhone. Early thinking was reported to be that most preferred the “Jailbreak” method so far

At some point the Battle Bot went crazy but I was off running an errand for whurley and missed the whole thing. Viewzi has it on their web site, and whurley has a link in his blog already.

The live music kicked off with Soulhat out back in a courtyard area. “Dillo Dogs” from Wahoos arrived. That is what someone told me they were called anyway. They are not on the Wahoo menu, and that is too bad: Best Hot Dog I have ever had. I admit, I do not eat much meat and I am not really sure that Hot Dogs normally are classifiable as meat, but I made an exception for these and disappeared them.

Beer flowed from Independence Brewery, (where my favorite as a home-brewer myself turned out to be a very nicely done Pale Ale.) Darkness fell, sessions continued. Music, conversations with all sorts of people.

Then came the next band: Karaoke Apocalypse. A terrific cover band with people singing lead for them from the audience. At least the band always sounded good. The people that had been spread over the courtyard moved up close to the stage. A Unicorn kicked it off, quickly followed by “Snax”, and then it went all over the place from there. I went inside to attend a session given by Opera.

At 10:00 PM, local ordinance required that the outdoor music cease, which most thought was a shame as it was still rocking. Consensus opinion: Isn’t this Austin? Music capital of Texas? What is up with this 10 PM thing? Sessions continued indoors: the iPhone guys having moved into a different conference room, and ordering then snarfing down a few Pizzas. I guess they missed the Dillo Dogs.

The conversations continued: this was one day, and there was just no way to meet everyone, and find all the people you might have something in common with. Every person I met was interesting, open, outgoing, and intelligent: Clearly BarCamp selects for positive traits in people.

Midnight arrived, and BarCampAustinIII came to an end. We cleaned up Idea City so that GSD&M would not regret having had us in for the day, and then folks went their various ways. Some were getting ready for more SouthBySouthWest activities on Sunday. Others were headed out for a very late / very early bit of food. I had three hours yet to drive to get back to the swamplands from Austin. Sleep came very easy, but it was not a good weekend to have the DST thing kick in. Monday is not going to be fun.

There just is not any way to really describe the way a BarCamp like this is. I can tell you we gave away over 2000 T-Shirts, saw more than 700 folks attend, had more impromptu, in-the-moment technical conversations that are possible at a more regimented conference, and on and on, and it still would not come close to giving you the flavor of what one of these is like. The good news is if you missed BarCampAustinIII, BarCampAustin4 has already been announced. I have no idea why the switch from roman numerals to numbers, but I assume it is because the Roman numerals were about to become a great big pain, given the success of these events.

Pictures of the whole thing are available on Flickr: http://flickr.com/groups/barcampaustin3/pool/

On January 18th, 2008, Jacob Johnny posted to the evolution-list@gnome.org the following very interesting note:

This is an announce mail for the preview of Evolution MAPI provider.
This provider can connect to Exchange 2007 servers and also to Exchange
2003, 2000 and 5.5 (untested).
After seeing enormous interest by the users in Exchange 2007
connectivity, we have prepared a preview of the current development code
from the branch. The evolution-mapi-provider is a standalone rpm but in
future it may be part of the Evolution/EDS rpms. It has a dependency on
OpenChange's ( http://openchange.org ) libmapi and Samba4. 
I'm maintaining the build service project for the provider and I'm
planning to give RPMs for OpenSUSE, SLED, Fedora and Ubuntu. We would be
doing incremental releases of this periodically and may have nightly
builds for this pretty soon (Don't ask me when ;-)
The below url should let you access the Samba4, libmapi and Evolution
MAPI Provider rpms.
http://download.opensuse.org/repositories/home:/jjohnny:/evolution-exchange-mapi-provider
Due to the recent outage of OpenSUSE Build Service, we aren't able to
get the rpms ready. So I have built RPMs for opensuse 10.3/i586 alone
and is available at:
http://gnomebangalore.org/~sragavan/exchange-mapi/i586/ . 
The build for the project is already queued. So it is possible that by
the time, you read the mail, the rpms might have been published already.
So go check out and give your valuable feedback.

If you follow the "openchange" link above, there is more very interesting verbiage and links:

...the 
Evolution plugin download page has been updated to reflect the current
state of development. The plugin which is now maintained by the
Novell Evolution team since October 2007 has greatly been improved
and now offer support for Calendar, Tasks, Address Book and Emails.
All the information needed to try it out is available
here.

These are for Fedora 8 and OpenSUSE only right now. No Debian .debs to be found here, which only makes sense. If Novell is maintaining it, that set of Distro's is RPM based. Kind of interesting that Fedora is all over it already.

The Debian Alien import tool could probably be used to pull in the provider, but I am guessing at this early a stage that would be problematic. The download page states that they are trying to get this code complete by the end of March so that it can be included with Gnome 2.24. I am thinking that

MAPI and SMAPI and Bears, oh my

I find all of this very interesting for a historical reason. Back in the early days, before I was Manager of R&D Support, but after I was a full time VM System Programmer, I spent some time on the Production support team. I whiled away my days doing things like hooking up BMC to the Internet, installing Linux for the first time, and managing our internal email systems. We used something called HP OpenMail back then, which later was sold to Samsung, where it was rev'ved a few times (from 2001 to 2007), then died.

OpenMail was a terrific tool, letting clients of all types from all sorts of platforms connect and read email and access their calendars if they were able. One of it's cool tricks was that there was a version of MS Outlook that ran against it. HP had tried over the years to make MAPI work, but ran into some snags. One of the snags was that the standard MS had published for MAPI, called Simple MAPI (or sometimes called SMAPI back then) was not a feature-complete standard. This MS Knowledge base article compares MAPI and SMAPI.

The problem for HP was that they found out that not everything that MS Outlook does when talking to the MS Exchange mail server was documented in the standard. There were apparently quite a number of undocumented RPC's that let all the extended functionality of Outlook work. MS's response at the time was to state that MAPI was a complete protocol, in that it let you get at your email, even if it was a “reduced experience” relative to the Outlook/Exchange combo burrito.

HP was looking at putting OpenMail on NT as a server platform, and reverse engineering the RPC stuff so that MS Outlook users could have a “full experience”, but entered instead into a deal with MS that effectively killed OpenMail a few years down the road, even though HP was seeing some big successes with the product.

Full Circle

The history of this ties in to this post in a couple of ways.

First: If you are in an MS Exchange shop (A place where you use MS Exchange as your mail servers), then it is historically a very high wall to use any clients other than MS Outlook and its MS sourced brethren with MS Exchange. If you want calendars and to-dos, and server side out-of-office greetings, and you are not using MS Outlook, you have to use the web client. If you are using the web client, and it is not via MS's own IE, you will get a “reduced experience”.

Evolution, with the Connector changed all that, since it plugged into the same place on the MS Exchange server as the MS web client. That “plug-in” was the WebDAV protocol. Not 100% standard WebDAV, but close enough that the Ximian-now-Novell folks were able to make it work fairly quickly.

Evolution supports IMAP and POP protocols of course, but those standards do not define anything about calendars or in fact anything other than email. useful if you want to email enable a Visual basic program, but not for a full blown email client. I was also told by some folks a while back at a LinuxWorld that it is fairly common that MS Exchange shops turn off the open protocols for some reason. Ostensibly (as related to me) for “security” reasons. But they could not turn off WebDAV without killing the web client at the same time, and that was/is Evolution Connectors way in.

Second: MAPI is not WebDAV obviously, and while I have not torn deeply into it, the MAPI-plus-RPC soup one needs to figure out to make Evolution work as a 100% native MS Exchange client is a seemingly complicated bit or work. HP did not go there. Yet the Novell Evolution MAPI Provider project is shooting for March, after starting on it last October!

It will be interesting to see when Ubuntu picks up the packages. Hardy Heron is set for April, and its Gnome version will be 2.22 as near as I can tell from internal Gnome package numbers of the alpha 5 release of 8.04. That puts 8.10 as the first possible 2.24 Gnome release for Ubuntu, and that is not till the fall of 2008. I'll want to be testing this well before that! Looks like it will be time to drag out the OpenSUSE system and get to testing.

If this works, then unlike Brutus, where there is an MS Windows system acting as a software shim, Linux would be able to natively connect to MS Exchange. That will be of deep interest to any wanting to run Linux Desktops in an MS infrastructure shop. If EvoMAPI can avoid the code fragility I have seen with Connector (such as in my recent Mepis posts [ -2- ]), that will be very very welcome.

Stay tuned....