How to exit a frozen Puppy...and bring up a terminal in CLI mode?

Issues and / or general discussion relating to Puppy

Moderator: Forum moderators

williams2
Posts: 1059
Joined: Sat Jul 25, 2020 5:45 pm
Been thanked: 302 times

Re: How to exit a frozen Puppy...and bring up a terminal in CLI mode?

Post by williams2 »

I don't think any Puppy that I've used has ever frozen.

Running out of ram can cause the OS to freeze.
This is more likely to happen on ram-challenged machines.

The Linux kernel has an Out Of Memory process killer, but it doesn't work properly in some kernel versions.
earlyOOM seems to work well, see: viewtopic.php?f=105&t=2980

To run entirely in RAM the savefolder/savefile would need to have their contents copied to RAM in 'init', and then copied from RAM to the savefolder/savefile in 'r.shutdown'.
Normal Puppy does not do that

No, Puppy does not do that.

I agree with @mikeslr

In regular mode 12, the save file is mounted rw and is the top layer of the aufs file system
and any changes to the fs are written directly to the top layer (the save file)

In mode 13, the save file is mounted rw but is now the second layer in the aufs file system.
The top layer is a tmpfs file system in ram.
aufs treats the save file layer as read only.
Changes to the file system are written to the tmpfs layer.
Saving the changes that were made to the file system (by clicking the save icon, for example)
copies any changes that were made since the last save, copying from the top tmpfs layer to the second layer (the save file layer)

All files in the save file layer (the 2nd layer) are visible in the Linux virtual file system, unless the file is also in the top tmpfs layer in ram.

User avatar
bigpup
Moderator
Posts: 6836
Joined: Tue Jul 14, 2020 11:19 pm
Location: Earth, South Eastern U.S.
Has thanked: 874 times
Been thanked: 1472 times

Re: How to exit a frozen Puppy...and bring up a terminal in CLI mode?

Post by bigpup »

To the operating Puppy file system, you see in Rox file manager.
Everything in both the save ramdisk (tmpfs) and the save file/folder is visible.

When it is all layered together by aufs.
It is one complete file system, to the running Puppy and programs in it.

Something only in the save ramdisk is still in the operating file system.
Anything!
Deletions, additions, copy, move, paste, setting changes, something a program does, etc.....
But until you say put it in the save.
Stuff in the save ramdisk, is not going to be there, after a shutdown and boot up.

one advantage of pupmode 13 and it using a save ramdisk.
You can get it so messed up it will not run.
If you never update the save.
A reboot is back to before you did anything.
But you can also forget to tell it to save.
On reboot, you lost whatever you wanted, to still be in Puppy.
I have done that a few times :shock: :thumbdown: :oops:

The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected :o

Post Reply

Return to “Users”