Difference of changes that happened during a session?

Arch based Porteus community project
Post Reply
User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Difference of changes that happened during a session?

Post#1 by istinnjazz » 16 Jun 2016, 12:22

Is there a way to determine the difference of changes that have happened during a session using a savefile?
I mean a new mount device that can show only the differences after the current boot, excluding save-file contents. Just for informative reasons, exactly only those files that will be added to the savefile during a session shutdown.

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Difference of changes that happened during a session?

Post#2 by francois » 17 Jun 2016, 03:03

Maybe changes-time script could help in some way.

Fanthom knows more about the changes-time command which is located in /opt/porteus-script:
viewtopic.php?f=81&t=3292
changes-time' script to catch latest updates to the filesystem

Code: Select all

root@porteus:~# changes-time
Use this script save Porteus changes made in definied time period.
Enter time interval or press enter for keeping default value (3 minutes):
Voltaire: Le mieux est l'ennemi du bien.

User avatar
Ed_P
Contributor
Contributor
Posts: 3061
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Difference of changes that happened during a session?

Post#3 by Ed_P » 17 Jun 2016, 04:19

Ed

User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Difference of changes that happened during a session?

Post#4 by istinnjazz » 19 Jun 2016, 15:02

Thanks for your advices. All those methods can be used.

Code: Select all

find /mnt/live/memory/changes -iname "*" -mmin -10
and

Code: Select all

changes-time
10
a good option could also be the the use of the "uptime" or "w" command,
in order use the time from the beginning of the session if you want

Code: Select all

# uptime
17:46:23 up 10 min,  0 users,  load average: 0.14, 0.16, 0.09

Code: Select all

# w
 17:48:46 up 12 min,  0 users,  load average: 0.65, 0.39, 0.19
USER     TTY        LOGIN@   IDLE   JCPU   PCPU WHAT

Post Reply