Last two weeks, I had 3 people complaining that Magnolia doesn't install on their linux machines, the same thing happened to 2 customers on MacosX.
The problem with the linux machines was for the 3 of them with the number of open files, every time the installation process stooped at the task 38 with the following message:
38 tasks have been executed, for a total of 265 tasks.

General messages

• Could not perform installation: javax.jcr.NoSuchWorkspaceException: resources

then after raising the number of open files the installation went ok.

On macosX as we know the problem comes with the impossibility to have two instances of Magnolia in one single Application server, so everthing goes fine when Magnolia is installed on two different servers.
Again I had some clients complaining that Magnolia doesn't work on their mac. I had to provide a zip with Magnolia configured in two different app servers so they can test it.
In my opinion, we can't ask our Macintosh customers to configure a second server on a different port and install magnolia, I don't see the "simply is beautiful" on telling them to do so.

Maybe we cannot do much about it, but it would be nice to have somewhere on the release notes an information on those two issues. So we can point our future customers to them if they have a problem during installation.

We know that some customers wont give it a second try, if already during the installation it just doesn't work....