porteus 5.01 xfce

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
vinnie
Black ninja
Black ninja
Posts: 83
Joined: 13 Jun 2024, 08:25
Distribution: alpine

porteus 5.01 xfce

Post#1 by vinnie » 17 Jun 2024, 00:44

I would like to report two anomalies, sorry if I am talking nonsense. :D

1) when I turn off and on again it seems that the /tmp directory is not deleted.
I use an ext partition and the filesystem resides in "/mnt/sdb2/porteus/changes/" , so maybe that is the reason.
Or is it because I added write and read permissions to all users to "/mnt/sdb2/porteus/" , I am not sure .

2) From the xfce "logout" menu I pressed suspend and it worked, but I tried hibernate and instead it looks like the computer actually shut down.
I honestly don't know the difference between suspend, hibernate and hybrid sleep, however II set sufficient swap space.

edit:
according with this description is right that the pc poweroff in hibernated state, but I do not understand how it should have restored the state.
Suspend to RAM (aka suspend, aka sleep)
The S3 sleeping state as defined by ACPI. Works by cutting off power to most parts of the machine aside from the RAM, which is required to restore the machine's state. Because of the large power savings, it is advisable for laptops to automatically enter this mode when the computer is running on batteries and the lid is closed (or the user is inactive for some time).
Suspend to disk (aka hibernate)
The S4 sleeping state as defined by ACPI. Saves the machine's state into swap space and completely powers off the machine. When the machine is powered on, the state is restored. Until then, there is zero power consumption.
Hybrid suspend (aka hybrid sleep)
A hybrid of suspending and hibernating, sometimes called suspend to both. Saves the machine's state into swap space, but does not power off the machine. Instead, it invokes the default suspend. Therefore, if the battery is not depleted, the system can resume instantly. If the battery is depleted, the system can be resumed from disk, which is much slower than resuming from RAM, but the machine's state has not been lost.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 4026
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

porteus 5.01 xfce

Post#2 by ncmprhnsbl » 17 Jun 2024, 02:20

vinnie wrote:
17 Jun 2024, 00:44
1) when I turn off and on again it seems that the /tmp directory is not deleted.
I use an ext partition and the filesystem resides in "/mnt/sdb2/porteus/changes/" , so maybe that is the reason.
Or is it because I added write and read permissions to all users to "/mnt/sdb2/porteus/" , I am not sure .
i'll have to check into this, it doesn't seem right for /tmp to retained in /changes... could be the case, i don't use persistence myself and havn't looked too deeply into it.
from what you've said, i'd say look into "magic folders" which offers fine grained control over what to keep http://www.porteus.org/component/conten ... lders.html
i think those instructions are still valid..
also check out "rootcopy" for a totally manual aproach
vinnie wrote:
17 Jun 2024, 00:44
but I do not understand how it should have restored the state.
so, you're on the right track. what you need is to set a resume path of your swap partition in boot/syslinux/porteus.cfg on the APPEND line
like eg. using the UUID of the swap

Code: Select all

resume=UUID=759b4862-96c6-4239-926d-gg4adbf7a961
one way to get your swap UUID:

Code: Select all

blkid | grep swap | awk '{print$3}'
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Ed_P
Contributor
Contributor
Posts: 8473
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

porteus 5.01 xfce

Post#3 by Ed_P » 17 Jun 2024, 04:30

The /tmp folder is in the /mnt/live/memory/changes/ folder on my Safe Boot system. No changes=EXIT & no save.dat file.
Image

Added in 59 minutes 48 seconds:
But not in my /mnt/live/memory/images/changes/ folder when I boot with changes=EXIT and my save.dat file.

Code: Select all

guest@porteus:/mnt/live/memory/images/changes$ ls -l
total 0
drwxr-xr-x 12 root root 329 Jun 15 02:40 etc/
drwxr-xr-x  3 root root  19 Jun 14 22:40 home/
drwxr-xr-x  3 root root  21 May 28 06:45 lib/
drwxr-xr-x  3 root root  44 Nov 26  2023 lib64/
drwxr-xr-x  3 root root  29 Sep  5  2022 opt/
drwx------ 14 root root 240 Jun 14 22:40 root/
drwxr-xr-x  5 root root  45 Jun 14 22:40 usr/
drwxr-xr-x 11 root root 121 Jun 15 02:41 var/
guest@porteus:/mnt/live/memory/images/changes$ 
Even though my /tmp folder shows files.

Code: Select all

guest@porteus:/tmp$ ls -l
total 0
-rw-r--r-- 1 guest users  0 Jun 17 01:26 MozillaUpdateLock-B0CAD03C64332C8A
drwx------ 2 guest users 40 Jun 17 01:26 Temp-028ccf48-b730-49b2-a54a-c9fb166c7039/
srwxrwxrwx 1 guest users  0 Jun 17 01:24 dbus-NGyFeRk2hI=
guest@porteus:/tmp$
Ed

rych
Warlord
Warlord
Posts: 677
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 5.0 x64 OpenBox
Location: NZ
Contact:

porteus 5.01 xfce

Post#4 by rych » 17 Jun 2024, 07:11

vinnie wrote:
17 Jun 2024, 00:44
/tmp directory is not deleted
ncmprhnsbl wrote:
17 Jun 2024, 02:20
it doesn't seem right for /tmp to retained in /changes
/tmp is normally/always/constantly saved to /changes. Unless you use the EXIT: cheatcode, then since /etc/changes-exit.conf by default doesn't mention it, it's not saved from RAM to the disk even on exit. Alternatively, one could force /tmp to always live separately in RAM as a tmpfs, as described in /tmp mounted as tmpfs

Post Reply