I suggest working from Live Kiosk from: http://www.livecd.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi
I am developing a
"kiosk" type of system, where I want to a) boot up fast and b) be able to switch
off and back on and restart with a clean image.
I have
1Gbfilesys to play with (CF or similar) and 128-256mb
RAM.
I was hoping to do
something like this:
1. Make the disk
read-only
[Simon Guerrero]
I am developing a kiosk type of system, where I want to a) boot up fast
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
the system from a normal live CD. Perhaps you should check out
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
fast
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mattia Dongili schrieb:
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
fast
and b) be able to switch off and back on and restart with a clean image.
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Mattia
Dongili
Sent: 04 October 2005 12:10
To: 'debian-devel@lists.debian.org'
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
October 2005 12:05
To: Simon Guerrero
Cc: 'debian-devel@lists.debian.org'
Subject: Re: Developing a kiosk type system - advice needed
[Simon Guerrero]
I am developing a kiosk type of system, where I want to a) boot up fast
and b) be able to switch off and back on and restart with a clean image.
Part
Yes, you're right about suspend2 - I figured if I mount most of the
filesystems ro, then create the writeable ones each time from static images,
I shouldn't have issues with corruption - right?
Simon
Part a is a bit tricky, but should be solvable. Part b sounds like a
about a) an partly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Guerrero schrieb:
Hi
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
Hi
Doh! I forgot about tmpfs. That would be fine. I think I should start again.
8-)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Torsten Marek
Sent: 04 October 2005 12:49
To: 'debian-devel@lists.debian.org'
Subject: Re: Developing a kiosk type system
Am Dienstag, 4. Oktober 2005 12:41 schrieb Simon Guerrero:
1. Make the disk read-only
How about a software application of what many hardware PC guards (and
likewise) do:
Use unionfs as a layer that you put away at any reboot to obtain the
original system.
Regards
Rudi Effe
--
To
Moin Simon!
Simon Guerrero schrieb am Dienstag, den 04. Oktober 2005:
Yes, you're right about suspend2 - I figured if I mount most of the
filesystems ro, then create the writeable ones each time from static images,
I shouldn't have issues with corruption - right?
In theory, however some
12 matches
Mail list logo
