Welcome to the Tiny Core Linux Wiki at tinycorelinux.net!

dCore OpenOffice Guide


This guide manually installs Apache OpenOffice in dCore. It does not appear present in Debian/Ubuntu repositories or PPA. The installation is not as hard as it seems, fortunately the mksquashfs and sce-deb2sce commands perform the heavy lifting.

The download, extraction and SCE creation process will temporarily require up to ~1GB of space. After cleanup, however, the resulting openoffice.sce is only 167MB. Only use /tmp/ as a temporary working directory, therefore, if adequate system RAM is available. Otherwise temporarily use a mounted data partition, even the TCE directory, being careful not to accidently modify or delete any important dCore system files. After successful OpenOffice installation all downloaded and temporary working files can safely be deleted.

There is no easy update process. If a newer version becomes available and an update is desired, backup or remove the outdated openoffice.sce, download the newer version and repeat these installation steps.

Although not tested, it may not be wise to load both OpenOffice and LibreOffice simultaneously.


Apache OpenOffice download site:


Download the Apache OpenOffice Linux 32-bit (x86) 146MB v4.1.3 DEB (not RPM) file to /tmp/ or a data partition:


Note older releases are also available if desired.


Run the following commands from a terminal, tab-autocomplete is your friend.

Extract downloaded archive:

tar xvf Apache_OpenOffice_4.1.3_Linux_x86_install-deb_en-US.tar.gz

Change to extracted (en-US) sub-directory:

cd en-US/DEBS/

Remove desktop-integration directory:

rm -rf desktop-integration

Now left with 41 separate .deb files.

Retrieve and load sce-deb2sce (helper command to process the .deb files):

sce-import -o sce-deb2sce
sce-load sce-deb2sce

Loop convert all 41 .deb files into individual SCEs (takes a while):

for f in *; do sce-deb2sce $f; done

Remove all *.sce.md5.txt files:

rm -f *.sce.md5.txt

Force unsquash all separate SCEs into a single squashfs-root working directory:

for f in *.sce; do unsquashfs -f $f; done

Create the OpenOffice SCE:

mksquashfs squashfs-root openoffice.sce

Create the openoffice.sce.md5.txt file:

md5sum openoffice.sce > openoffice.sce.md5.txt

Copy openoffice.sce and openoffice.sce.md5.txt to the SCE directory:

cp openoffice.sce openoffice.sce.md5.txt /etc/sysconfig/tcedir/sce/

Add OpenOffice to OnDemand (or sceboot.lst as desired):

sce-ondemand openoffice


Load openoffice.sce:

sce-load openoffice

Create an OpenOffice executable symlink:

ln -s /opt/openoffice4/program/soffice ~/.local/bin

Note additional symlinks can be created, review available executables in /opt/openoffice4/program/.

Test OpenOffice, run:


Welcome to OpenOffice wizard opens. Blank user info is okay, just select 'next' and 'finish', OpenOffice 4 should launch.



A large ~50MB ~/.openoffice configuration directory gets created, which is not acceptable for dCore systems that do no have a persistent /home directory (extremely large backup).

There is an ~24MB temporary /home/tc/.openoffice/4/user/extensions/tmp/ directory that can safely be emptied.

The other is a large ~24MB /home/tc/.openoffice/4/user/uno_packages/ directory, which contains the spellcheck dictionary and should not be deleted.

Users wishing to keep /home/tc/ small for backup should move the entire /home/tc/.openoffice/ configuration directory to a mounted partition. In this example the TCE directory is utilized as it is always mounted at boot, although any mounted data partition should work. Be careful not to alter any important dCore system files. Example move and symlink:

cd /home/tc/
mv /home/tc/.openoffice/ /etc/sysconfig/tcedir/
ln -s /etc/sysconfig/tcedir/.openoffice .openoffice

OpenOffice loads numerous files into the /opt/ directory when loaded, which is included by default when backing up dCore. These files should be excluded from backup by adding the /opt/openoffice4/ directory to /opt/.xfiletool.lst:

echo "opt/openoffice4" >> /opt/.xfiletool.lst


Finally run a backup to save configuration changes:



Terminal output running soffice will indicate 'Could not find a Java Runtime Environment'. Although not required for most tasks, if Java is important for the user try installing Java Runtime Environment.