'Changes' directory grows in size too much?

a very small Live CD shaped to look and act like Puppy Linux.


Moderator: fredx181

Post Reply
williwaw
Posts: 2038
Joined: Tue Jul 14, 2020 11:24 pm
Has thanked: 182 times
Been thanked: 387 times

'Changes' directory grows in size too much?

Post by williwaw »

I an trying to understand the size of my changes directory

I am booting with changes=EXIT: and the changes dir seems too grow much faster than it should.
sometimes

editing a single line in .bashrc added 1.5mb
apt updated added 122mb
installing curl with apt added 42 mb in spite of apt reporting 1.4 mb would be added to disk
installing chromium with apt added 281 mb in spite of apt reporting 242 mb would be added to disk

when remastering, does my new sfs loose any of this 'extra' space?

dancytron
Posts: 757
Joined: Fri Dec 13, 2019 6:26 pm
Has thanked: 552 times
Been thanked: 236 times

Re: 'Changes' directory grows in size too much?

Post by dancytron »

The Quick Remaster program deletes a lot of stuff automatically. Some other stuff, like the browser cache, you can delete manually before you remaster.

User avatar
fredx181
Posts: 3250
Joined: Tue Dec 03, 2019 1:49 pm
Location: holland
Has thanked: 408 times
Been thanked: 1412 times
Contact:

Re: 'Changes' directory grows in size too much?

Post by fredx181 »

williwaw wrote: Mon Jul 31, 2023 10:42 pm

I an trying to understand the size of my changes directory

I am booting with changes=EXIT: and the changes dir seems too grow much faster than it should.
sometimes

editing a single line in .bashrc added 1.5mb
apt updated added 122mb
installing curl with apt added 42 mb in spite of apt reporting 1.4 mb would be added to disk
installing chromium with apt added 281 mb in spite of apt reporting 242 mb would be added to disk

when remastering, does my new sfs loose any of this 'extra' space?

Could be wrong, but I assume you get the size numbers from the splash-screen while saving ?
If so, first; these numbers may not be perfectly accurate, and: the size it shows is in fact 'what's new and will be copied', there are often files overwritten, so then they don't actually add to the size of the 'changes'.
For example: doing apt update first time will indeed add +/- 122mb, but second time the (same) cache files used will be overwritten, so then not really adding to the size of the changes.
(edit: similar goes for browser profile and/or cache files, first time run it may add a lot)
To get real comparison (before<>after save), do from file-manager right-click > 'How Big' on your changes folder (or /mnt/live/memory/images/changes-exit/ which is the same but bind mounted) before and after saving.
edit: that is; from pcmanfm or thunar right-click, not from rox, but you can run from terminal too howbig /mnt/live/memory/images/changes-exit/
EDIT;

editing a single line in .bashrc added 1.5mb

That is not really from the line in bashrc, at a fresh boot there are always some files created (see in /mnt/live/memory/changes/ these are the recent changes), I suspect there's the reported 1.5mb coming from.

Post Reply

Return to “DebianDogs”