From: btrfs@spiritvideo.com
To: linux-btrfs@vger.kernel.org
Subject: revert to static snapshot on reboot
Date: 8 Jan 2012 22:43:04 -0800 [thread overview]
Message-ID: <20120109064304.18411.qmail@otpproductions.com> (raw)
Hi all --
I just installed my first btrfs-based linux tonight, and I must say it
gives me a very warm feeling! Congratulations on all your hard work
and your fine product.
I administer laptops for a small school, and we want to implement what
Deep Freeze (http://www.faronics.com/enterprise/deep-freeze) does for
Windows -- no matter what a student does after they log in, when they
reboot it is all forgotten and the computer has returned to a standard
state.
I would think this would be a FAQ, but I have searched the web and
mailing list for the past couple of hours.
Of course it's easy to mount a snapshot, but then if students make
changes the snapshot changes.
The plan that occurs to me is to make a snapshot of the system in the
state that I want to always boot. Then, I would rewrite the init
script in the initrd to (a) delete any old tmp copy of the snapshot;
(b) copy the static snapshot to a tmp copy; (c) mount the tmp copy.
That's a little harder than I was hoping to work -- is there an easier
way to get this functionality?
I have a small ext4 boot partition containing grub, vmlinuz and
initramfs. Everything else is in a big btrfs root partition. I am
running Fedora 14, with Fedora-patched linux 2.6.35. I could upgrade
if necessary.
Thanks,
Bob
--
I blog about my work at the school at SmallSchoolIT.wordpress.com
next reply other threads:[~2012-01-09 6:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 6:43 btrfs [this message]
2012-01-09 9:51 ` revert to static snapshot on reboot Hugo Mills
2012-01-09 15:21 ` Niels de Carpentier
2012-01-12 21:38 ` Hugo Mills
2012-01-12 22:01 ` Niels de Carpentier
2012-01-09 18:43 ` Kai Krakow
2012-01-11 3:42 ` Anand Jain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120109064304.18411.qmail@otpproductions.com \
--to=btrfs@spiritvideo.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).