From: Florian Philipp <lists@binarywings.net>
To: Gentoo User List <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] OT: Fighting bit rot
Date: Mon, 07 Jan 2013 21:11:35 +0100 [thread overview]
Message-ID: <50EB2BF7.4040109@binarywings.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
Hi list!
I have a use case where I am seriously concerned about bit rot [1] and I
thought it might be a good idea to start looking for it in my own
private stuff, too.
Solving the problem is easy enough:
- Record checksums and timestamps for each file
- Check and update records via cronjob
- If checksum changed but timestamp didn't, notify user
- Let user restore from backup
However, I haven't found any application in portage for this task. Now,
the implementation is easy enough but I'm wondering why it hasn't been
done. Or do I just look for the wrong thing? The only suitable thing
seems to be app-admin/tripwire but that application also looks like
overkill.
[1] http://en.wikipedia.org/wiki/Bit_rot
Regards,
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next reply other threads:[~2013-01-07 20:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 20:11 Florian Philipp [this message]
2013-01-07 21:07 ` [gentoo-user] OT: Fighting bit rot Paul Hartman
2013-01-07 22:05 ` Florian Philipp
2013-01-07 21:33 ` Michael Mol
2013-01-07 22:10 ` Florian Philipp
2013-01-07 23:20 ` Alan McKinnon
2013-01-08 7:27 ` Florian Philipp
2013-01-08 7:55 ` Alan McKinnon
2013-01-08 16:16 ` Florian Philipp
2013-01-08 16:42 ` Alan McKinnon
2013-01-08 17:41 ` Pandu Poluan
2013-01-08 19:02 ` Florian Philipp
2013-01-09 2:55 ` Pandu Poluan
2013-01-08 19:53 ` [gentoo-user] " Grant Edwards
2013-01-08 20:30 ` Florian Philipp
2013-01-08 21:45 ` Alan McKinnon
2013-01-08 22:15 ` Grant Edwards
2013-01-08 23:37 ` Alan McKinnon
2013-01-09 2:47 ` Grant Edwards
2013-01-09 8:31 ` Alan McKinnon
2013-01-09 14:48 ` Grant Edwards
2013-01-09 15:36 ` Holger Hoffstaette
2013-01-09 16:32 ` Pandu Poluan
2013-01-09 16:42 ` Grant Edwards
2013-01-09 20:52 ` Alan McKinnon
2013-01-09 20:53 ` Alan McKinnon
2013-01-08 15:29 ` Grant Edwards
2013-01-08 15:42 ` Michael Mol
2013-01-08 16:28 ` Florian Philipp
2013-01-08 17:35 ` [gentoo-user] " Volker Armin Hemmann
2013-01-08 19:06 ` Florian Philipp
2013-01-08 20:57 ` Joshua Murphy
2013-01-08 21:49 ` Alan McKinnon
2013-01-08 19:11 ` [gentoo-user] " James
2013-01-09 4:40 ` Volker Armin Hemmann
2013-01-09 15:17 ` walt
2013-01-09 18:57 ` Volker Armin Hemmann
2013-01-09 0:12 ` [gentoo-user] " Randy Barlow
2013-01-07 23:31 ` William Kenworthy
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=50EB2BF7.4040109@binarywings.net \
--to=lists@binarywings.net \
--cc=gentoo-user@lists.gentoo.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