[SOLVED] An alternative "changes" cheat code
Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
Ed_P
Re: [SOLVED] An alternative "changes" cheat code
Post#17 by ThePilot » 06 Aug 2013, 11:44
Hello everybody! I'm brand new here, and had a question regarding this...
I want to do a frugal install (so it's loaded to RAM) but I want all my changes saved to my HDD (I'll be using the entire drive for Porteus).
Should I just use normal changes=/dev/sda1 or should I do changes=EXIT:/dev/sda1? Isn't doing it with EXIT similar to how Puppy Linux does things?
Sorry for the confusion...I'm just trying to figure things out a bit.
Thanks!
I want to do a frugal install (so it's loaded to RAM) but I want all my changes saved to my HDD (I'll be using the entire drive for Porteus).
Should I just use normal changes=/dev/sda1 or should I do changes=EXIT:/dev/sda1? Isn't doing it with EXIT similar to how Puppy Linux does things?
Sorry for the confusion...I'm just trying to figure things out a bit.
Thanks!
ThePilot
-
donald
- Full of knowledge
- Posts: 2106
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
Re: [SOLVED] An alternative "changes" cheat code
Post#18 by donald » 06 Aug 2013, 12:12
Hi Pilot
The difference is:
If you use changes=/dev/sda1/"some Folder"
your changes are written to that folder in real Time
If you use changes=EXIT:/dev/sda1/"some Folder"
The 'EXIT:' extension tells the 'changes=' cheatcode to keep all
of the files that have been added/deleted/modified during the
session stored in memory until you shutdown or reboot.
Your RAM works as a buffer which gets dumped on the drive only once,
when the session is finished.
'changes=EXIT:' cheatcode has following advantages:
- Porteus works as fast as in 'Always Fresh' mode as all modifications
to files and folders are performed in RAM.
- reduced number of read/write cycles should extend the life of SSD
drives and usb sticks.
The only disadvantage of the 'EXIT:' extension is that the session
does not get saved in cases where you experience a hang (kernel crash)
or power interrupt.
Please use with caution!
The difference is:
If you use changes=/dev/sda1/"some Folder"
your changes are written to that folder in real Time
If you use changes=EXIT:/dev/sda1/"some Folder"
The 'EXIT:' extension tells the 'changes=' cheatcode to keep all
of the files that have been added/deleted/modified during the
session stored in memory until you shutdown or reboot.
Your RAM works as a buffer which gets dumped on the drive only once,
when the session is finished.
'changes=EXIT:' cheatcode has following advantages:
- Porteus works as fast as in 'Always Fresh' mode as all modifications
to files and folders are performed in RAM.
- reduced number of read/write cycles should extend the life of SSD
drives and usb sticks.
The only disadvantage of the 'EXIT:' extension is that the session
does not get saved in cases where you experience a hang (kernel crash)
or power interrupt.
Please use with caution!
donald
