public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robert Bradbury <robert.bradbury@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Init systems portage category
Date: Mon, 12 Oct 2009 13:52:49 -0400	[thread overview]
Message-ID: <deaa866a0910121052k47a5ae5bg45bdfdd2b5f98124@mail.gmail.com> (raw)
In-Reply-To: <deaa866a0910121042r5314319dy13472f6799bddde6@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]

I agree with Wyatt's point.

Wouldn't there be an easy way to reset the last access date on all of the
files to say 1/1/2009 on a system then execute a relatively robust
multi-user boot (and maybe a world emerge upgrade) and record which files
are actually used during that process, then determine which package they
belong to and label those with some "level of criticality"?

Its probably also true that this list of files could be part of a "critical
system backup" that one could just keep around in a bz2 file for fast
recoveries (or even as md5sum's to determine when they might have been hosed
by disk errors or viruses) -- or is this something that is already done by
some of the selinux options?  [I've never used selinux so am unsure of
everything it does.]

R.

[-- Attachment #2: Type: text/html, Size: 839 bytes --]

  reply	other threads:[~2009-10-12 17:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 15:39 [gentoo-dev] Init systems portage category Victor Ostorga
2009-10-12 16:45 ` Robert Bradbury
2009-10-12 16:51   ` Jesús Guerrero
2009-10-12 17:06     ` Wyatt Epp
2009-10-12 17:42     ` Robert Bradbury
2009-10-12 17:52       ` Robert Bradbury [this message]
2009-10-12 18:44         ` Jesús Guerrero
2009-10-12 23:53           ` Richard Freeman
2009-10-13  7:21             ` Tobias Klausmann
2009-10-13  7:42 ` Thilo Bangert

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=deaa866a0910121052k47a5ae5bg45bdfdd2b5f98124@mail.gmail.com \
    --to=robert.bradbury@gmail.com \
    --cc=gentoo-dev@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