RE: Developing a kiosk type system - advice needed
Thanks for your responses. The "suspend and always resume without
overwriting" is done by software suspend, with no problem. It is the
difficulty of resuming the writeable parts of the filesystem (/var and /tmp)
each time from an image which I am not sure about.
I am thinking about adding a script to the rc2.d (or other runlevel) which
cat /ramdisks/var.img > /dev/ram1
mount /dev/ram1 /var
cat /ramdisks/tmp.img > /dev/ram2
mount /dev/ram2 /tmp
...would that do the job? Maybe it is simpler than I thought :-/
[mailto:firstname.lastname@example.org]On Behalf Of Mattia
Sent: 04 October 2005 12:10
Subject: Re: Developing a kiosk type system - advice needed
On Tue, October 4, 2005 1:04 pm, Petter Reinholdtsen said:
> [Simon Guerrero]
>> I am developing a "kiosk" type of system, where I want to a) boot up
>> and b) be able to switch off and back on and restart with a clean image.
> Part a is a bit tricky, but should be solvable. Part b sounds like a
about a) an partly b): would suspending (S4) to a swap file once and the
always resume from that without overwriting it reach the goal?
Note: never tried it.
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
This message has been checked for all known viruses on behalf of Sungard
Vivista by MessageLabs.
http://www.messagelabs.com or Email: email@example.com
For further information http://www.sungard.com/vivista
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email