Re: Developing a kiosk type system - advice needed
-----BEGIN PGP SIGNED MESSAGE-----
Simon Guerrero schrieb:
> 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
that might be one way, but I don't know if there are any problems if frozen
programs have open files on /tmp or /var, since the processes are resumed before
any run-level scripts (?).
Maybe I am missing something, but if you have /tmp and /var as (size-restricted)
tmpfs's when you create the image in the first place, what is the problem with that?
Torsten Marek <email@example.com>
ID: A244C858 -- FP: 1902 0002 5DFC 856B F146 894C 7CC5 451E A244 C858
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----