Something very strange has happened with my 6.0.3 : I have it installed on my 2Gb usb,and it takes 204Mb,but today I was forsed to reinstall 6.0.3 again as it suddenly (and I have no idea why) became 1.4Gb!!I have no idea why it increased so much and didnt know how to solve it so I reinstalled it.Do you have any ideas what was that?
And one more question - in case if some trouble happen again - how can I save all changes(in KDE mostly) and transfer it into some safe place,so that I could activate them next time if I reinstall SLAX?
Max ... boot with the cd, no changes= specified, and do all your initial setups -- which are clearly being stored in memory at this moment. When you have it as you like, before exiting do a #dir2lzm /mnt/live/memory/changes ./changes.lzm. When that finishes, copy that changes.lzm file off to whatever media you like.
Then, the next time you boot slax, after root/toor login, run #activate /mnt/path-to/changes.lzm. Then do your #startx command to get kde running -- you will see that all your changes are back. If you copy that changes.lzm to your /slax/modules subdir then they'll automatically appear at the next bootup. If you need to do more changes, boot again with no changes= specified, and do the same dir2lzm, only this time name it changes2.lzm, etc -- so when you boot after that your changes will get loaded in sequence.
If you include these changesN.lzm files in your remaster, they'll then be a permanent part of your slax cd.
There is IMO a fundamental problem with using changes= in the standard way -- you'll wind up carrying around 2 copies of everything you add to your slax system.
It seems that 'changes' in Slax 6.0.3 eat to much :) . I cant start slax with changes if there is less than 70 mb on my drive. and in fiew hour of uptime 'changes' grew up to 200 mb (i was only listening music).
I've written this script to save my changes in a lzm file and using slax always in fresh mode.
The first time you can boot normally and save changes.
than you can reboot in fresh mode and trash the big changes folder. http://w16.easy-share.com/1699948830.html
Bye
Well it is a solution, but anyway changes in 6.0.3 aren't working properly. And i dont want to trash Big changes folder on each boot and after that activate your module. It is better than nothing , but it's not so comfortable as it shoul be.
Anyway i'll have a look at your module, thx.
warez wrote:
Well it is a solution, but anyway changes in 6.0.3 aren't working properly. And i dont want to trash Big changes folder on each boot and after that activate your module. It is better than nothing , but it's not so comfortable as it shoul be.
Anyway i'll have a look at your module, thx.
You have to trash it only the first time for don't loosing your old changes, and the boot always in fresh mode.
You must save manually each time you like.
Bye
Pastrugno wrote:
You must save manually each time you like.
Bye
Well that is the reason i don't like this solution.I would prefer using 6.0.2 with automatic saving of changes folder.
I could make a script that saves everyting on shutdown , but i am currently expiriencing problems with electricity (i don't have an UPS) so i dont watn to loose information just because i've forgot to save changes.
Could you describe in further detail what your module does exactly please?
thanks
Whe you start my script it puts the modules mounted on the fly in the /slax/modules dir.
Take all the changes and compresses them in a lzm module in a dir that you can choose (better /slax/modules/), so when you reboot in fresh mode you have all your changes up and you can trash your changes dir.
It asks you if you have just another changes.lzm file for not loosing your old changes and add the newer changes.
I don't speaak english very well, so excuse me if I can't explain it better.
Bye
Sounds very interesting. That's something that I wanted to do long time ago. Let me finish my persistent storage module, then I'll take a look yours. Do you mind if I send you some patches if I discover some?
Sounds very interesting. That's something that I wanted to do long time ago. Let me finish my persistent storage module, then I'll take a look yours. Do you mind if I send you some patches if I discover some?
thanks
xpt
Ok, you can write me at pastrugn at alice dot it.
I've written a new script and I'm debugging it.
It will be ready soon.
Bye
