Hi sixofeight,
My first idea was not full developped as it's stupid to Load a full Office suite in RAM.
Look at this :)
Hi sixofeight,
My first idea was not full developped as it's stupid to Load a full Office suite in RAM.
Look at this :)
@moulefrite
....it's stupid to Load a full Office suite in RAM....
Yes, but that is what they are NOT doing!!!The Princip of "Modules" is:
you put huge Software like Office, gimp, Browsers etc with all needed
dependancies in a single Container (= modul).This Module you can put anywhere.
It will NOT be loaded at boot (but it could if you want).
If you need Office, you just click that Module and activate it.It's then in your Programms-menue and in ram of course
The Point is that when you don't need Office any longer, you click the Module
again, deactivate it and the whole Office suite disappears (out of menue out
of ram and out of the Filesystem).This is not a Install/deinstall as usual.
If you don't need Office for the current Session, don't activate it.
I recommend you go to porteus.org and download a "standard iso"
(kde or mate/xfce/lxde/razor-qt) burn a live-CD test it and you will see.
I think sooner or later I will get banned here
Hopefully not
The problem I have with modules is that they're stand-alone for portability - which means they contain everything they need to run on their own. The trouble with that is that with similar modules, you get repeats of certain libraries and files which ultimately add more data (and in this case, uses more RAM) than it needs to if it was statically linked like a proper program.
@Trixar_za
That's right, if a module puts all files/folders only in his own Folder.
But what if a module injects his files/folders into the running Live-Filesystem like
a normal install? Wouldn't a 2nd module notice that some needed files are
already there?
If memory serves, in Porteus it only does that for common libraries and modules that come with the base install. The uncommon ones will be created for each module and will not be shared between similar modules because it prevents the event that should one module be removed, the others won't suddenly suffer because of it.
@Trixar_za
Yes, you're right.
The Point of removing...I've overlooked.
( I usually overlook something )
Thanks for the deeper look on it.
What I do to minimize ram occupied by unnecessary files is:
- download packages with all necessary dependencies
- prepare a text file inluding complete list of them
- use tazpkg install-list
to install the application when I need it
It works very well for me, but I use only frugal usb stick (or rootfz stored on local hdd), so I don't care of removing all those files afterwards - just restart system and that's it.
@tazpider
This is also my way of doing it.But if a program is really good,
( double checked ),I include it in my Installation and build a new iso.
By doing so I don't have to configure the Preferences again and again.
I have several isos (along with an Info-file about the changes),so I can go back
to an earlier version.
Yes, but the current problem is :
your have 2 laptops ,
you have a wireless and Ethernet connection,
you have 2 users on each computers,
you have 2 external monitors and
2 keyboards in 2 diffrent language :
2*2*2*2*2 = 32 iso's ! lol x) That's why I recommend a solution where all the user profil should be written from a single file with a grub command at boot time.
You must log in to post.