Puppy Linux Discussion Forum

Reducing ram used by Puppy

Computers using Grub4Dos as the boot loader.
Use Geany editor.
-open the file: menu.lst
-find: pfix=fsck
-replace with: pfix=nocopy,fsck
Note: nocopy and fsck are separated by a comma and no spaces
-save

Computers using Grub2 as the boot loader.
Use Geany editor.
-open the file: grub.cfg
-find: pfix=fsck
-replace with: pfix=nocopy,fsck
Note: nocopy and fsck are separated by a comma and no spaces
-save

In addition to reducing ram use, you will also see a slightly faster boot speed.

wizard

@wizard
How would that work for KLs?

For one I'm using - KLV-vmHost-rc3, it doesn't have pfix=fsck in its grub.cfg.
It does have something called w_changes=RAM2 though.
Would something like you show just be added somewhere on the linux line?
Also is the order it is placed on the line important?

Thanks

@JusGellin,

KLV can't use the Puppy Linux kernel command line parameter and options like pfix=fsck. The initrd is different.

There is a list of the KLV parameters I'll dig out the link for

I'll consult @wiak if we can manage an additional command line option for a something similar in KLV

@wizard

wizard wrote: ↑Tue Oct 22, 2024 9:33 pm

Reducing ram used by Puppy

Computers using Grub4Dos as the boot loader.
Use Geany editor.
-open the file: menu.lst
-find: pfix=fsck
-replace with: pfix=nocopy,fsck
Note: nocopy and fsck are separated by a comma and no spaces
-save

Computers using Grub2 as the boot loader.
Use Geany editor.
-open the file: grub.cfg
-find: pfix=fsck
-replace with: pfix=nocopy,fsck
Note: nocopy and fsck are separated by a comma and no spaces
-save

In addition to reducing ram use, you will also see a slightly faster boot speed.

wizard

Interesting and thank you.

I'm not the brightest bulb in the internal workings of Puppy, so looked into fsck.

An AI answer came back as (which can be and has been sometimes misleading):

What does fsck do in Puppy Linux

Sources
forum.manjaro.org favicon
puppylinux-woof-ce.github.io favicon
oldforum.puppylinux.com favicon
reddit.com favicon
forums.opensuse.org favicon

Answer
Fsck (file system check) is an important utility in Puppy Linux that checks and repairs file systems. Here are the key points about fsck in Puppy Linux:

Purpose and Function
Fsck examines the file system for errors and inconsistencies, and can repair many common issues.
It helps ensure the integrity and stability of the file system.

Usage in Puppy Linux
Fsck can be run automatically at boot time by adding the "pfix=fsck" boot parameter.
This tells Puppy to perform a file system check during the boot process.
It's commonly used to check and repair the Puppy save file, which stores persistent changes.

When It Runs
With "pfix=fsck", fsck will run at boot time before mounting file systems.
It only runs a full check if the file system is marked as "dirty" or if the maximum mount count is reached.
The maximum mount count and check interval can be configured with tune2fs.

Benefits
Helps prevent data corruption and file system errors
Can fix issues that may prevent Puppy from booting properly
Maintains the health of the save file and storage devices

Manual Usage
Fsck can also be run manually from a live Puppy USB if needed to repair a system that won't boot

By using fsck regularly, either automatically or manually, Puppy Linux users can help maintain the stability and reliability of their systems. The "pfix=fsck" boot option provides a convenient way to integrate file system checks into the normal boot process.

So my question is:

Does the benefit of reducing RAM use (by how much?) with a slightly faster boot speed outweigh the 'security' of having fsck run at boot time?

@Chelsea80

Does the benefit of reducing RAM use (by how much?) with a slightly faster boot speed outweigh the 'security' of having fsck run at boot time?

The change from pfix=fsck to pfix=nocopy,fsck does not negate fsck at boot. Nocopy is a separate parameter and simply reduces the amount of Puppy that is copied and stored in ram. The amount varies with each distro.

Thanks
wizard