On Tue, Jun 02, 2009 at 12:11:35PM -0700, Matthew Dillon wrote:
>     What I did on my laptop to make it work was put
>     /usr/pkg/openoffice.org2.4/share/fonts on a small UFS partition
>     (my /boot) and then null-mount it onto
>     /usr/pkg/openoffice.org2.4/share/fonts.
>     OpenOffice has other issues unrelated to the filesystem... it has issues
>     trying to locate files due to the prioritized linux emulation path
>     lookups.  It gets very confused sometimes.

I had a quick look at the source distribution; the build system is full of
arcane and unneeded stuff. Like configure scripts auto-generating perl
scripts, themselves sourcing environment variables from two possible different
shell scripts, one bash, one tcsh for good mesure, etc...
It also has its own make program, and about a dozen old versions of other
programs and libraries thrown in the tarball for fun.

Pure madness.
I can only imagine what sort of bugs and assumptions lie in the source code

Aniway, I tried your trick of null-mounting fonts/ from /boot. It works for
reading documents but fails when trying to save them:

"Error saving the document blah:
Write Error.
The file could not be written."

blah.ods is in my /home pfs, and chmod 0666.

The auto-save feature gives a different error message:

"Openoffice.org could not save important internal information due to
insufficient free disk space at the following location:

You will not be able to continue working with OpenOffice.org without
allocating more free disk space at that location."

There is 80 GB of free space on this fs. Could it be counting free inodes ?

Francois Tigeot

Reply via email to