With respect due guys, a 4 Gb RAM system is not yet a "standard" system. Most has to do with less.
No one is saying that 4Gb RAM is a "standard" system, only an explanation was offered about why some limit exists on a liveUSB system, and that limits appear to be the available RAM.
Of course, your suggestion for alternative installation, and others alternative suggestions are all welcome!
AS: thanks a lot for confirming that things work as expected. In fact, your case may no longer work in a month from now because the more updates you install in the live-session the less free space remains. LO only needs Java from the repo, so to install it in a live-session and maintaining the maximum free space one should only update to the latest version of lomanager, then run lomanager, and after that update the rest.
Archie: a selective install of any LO-component was possible with the old versions of OO only because at that time Tex compiled these components from source which was a lot of work and required tons of PCLinuxOS server-space. However, OO/LO is a modular system and to have for example only Writer you need ~90% of the entire suite anyway, so you do not save much disk-space by installing only one component. The idea of getopenoffice
(and its successor lomanager
) was to save hours of hard work for compiling from source and freeing up 2GB of our server-space by pulling-in the default packages directly from the OO/LO-servers.
the ultimate "space-saver" is to copy the directory /opt/libreoffice3.4
from a installed system to a new system, and start the applications from within there. Not the nicest solution but for those who like to fiddle this could be an alternative.
iso-image (original or your own remaster) of whatever size
there is always no free space
because only the files from the master system are compressed into the iso-image. You remaster a larger/smaller system and you get a larger/smaller iso. You start that iso and you get access to the files/apps which were on the master system the remaster was created from but not any free space that was available on the master. The only free space a live-session can use is to access the RAM of the PC you run the live-session (iso) on. And as stated many times this free space is ~45% of the RAM of the PC. Moreover, this free space is decreasing with any action you perform in that live-session, just do the occasional df -k
and you can monitor the decrease. Of course you can have persistence or mount some extra partition in the live-session but this is irrelevant for lomanager because lomanager will use the free "disk-space" under /root/ which is equivalent to the available space provided by the system RAM -> 45% at the beginning and then decreasing.
For all these reasons you can run lomanager on a system with at least 3GB of RAM at the beginning of the live-session, and in case you play around too much before running lomanager, it may tell you that it can not be run because you ran out of sufficient free space in the live-session to install LO. I added this live-session setup possibility (same is true for addlocale) because it may be nice to install LO already in the live-session (provided you have sufficient RAM) and then install that live-session to the hard-drive so the newly installed system will already include LO.
hope this info is useful,