Puppy Linux Discussion Forum

[Indy'spup]

looks like we're narrowing down the culprits, cool

One thing though, I had to pass on that great macpuppy, was just to heavy for this project. My latest issues with the i attribute have been with mijnpup, much lighter without enlightenment.

[jukingeo]

Hello All,

I am wondering if there was any progress made in regards to this topic.

I too am looking for a read-only system based on Puppy (I have Wary 5.1.1 as of now).

In my case what I would like to do is set up game room systems that would run a program called MAME (SDLMAME in Linux) and DWJukebox. (I do have other applications as well, but these two programs would be what I would mainly be using).

As far as I know, both programs run off of 'rom' information and thus are "read only".

Now the reason why I am interested in a 'read only' lock down once everything is set up is because I would like to put everything on a Compact Flash card instead of a hard drive. As most of you may already know, being flash memory, a CF card is sensitive to being written to many times. Thus I am very interested in something that would allowed to be run in ram, but then any saved settings would be discarded upon shut down instead of saved to the CF.

So even though my reason is different from the OP, the desired end result is the same.

Thank You,

Geo

[rcrsn51]

[Mechanic_Kharkov]

Hi, All. I currently have a system without HDD, that boots from CD, then reads pupsave.2fs and pup-431.sfs files from sda1 (flash stick). Now I'm looking a way to tel the system to do not save pupsave file neither on shutdown nor periodically by a timer.
Sometimes the decision to discard current session comes during the session itself but not at boot time. And if I know that no important changes are made to system then there is no need to wait while system saves file (on my system it can take very long time when not under X). And it slightly differs from "Locked-down" installation" to "Sometimes locked-down" one, in other words "with user controlled session saving".
So, the questions are:

• Is there any ability to intercept anywhere in system (configs, scripts, even kernel code) the entry point where actual session file save is initiated?
  
• If it is possible, then where to dig (for newbie, pls)?

The main idea (to make backup file, and then restore it on start-up) is not such suitable because of flash write-endurance. And it would be a great to have an option to forbid pupsave.Xfs saving during session (not only at boot time).

I also found this post (about 'pfix=kiosk'). This sounds exactly what I need to implement in my own setup. But there is an idea only in the post, no implementation.

Hope for Your help.

[Sylvander]

See this post.

[Mechanic_Kharkov]