public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Daniel Poelzleithner <poelzi@poelzi.org>
Cc: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Suggestion: xtime as new inode attribute
Date: Fri, 18 Dec 2009 09:59:16 -0500	[thread overview]
Message-ID: <20091218145916.GI2123@thunk.org> (raw)
In-Reply-To: <4B2B4B1D.2000806@poelzi.org>

On Fri, Dec 18, 2009 at 10:27:57AM +0100, Daniel Poelzleithner wrote:
> I think you missunderstood my intension. I wasn't thinking about a
> distribution but the installation on a system. All my systems grow in
> installed packages over time, i think that is something every hard core
> user experiences.
> You test 4-5 programs for a new task you have to do, but over time you
> only use 1-2 of them and simply forget you installed some more programs
> for this.
> With xtime there is a very clean way to find which packages are
> installed and are never used for a long time and can therefore suggested
> to the user to be uninstalled. The cleanup script of course will highly
> depend on the package system used and how the packages are organized and
> named.

This sounds like something a distro might want to do; and as such,
I'll note that if such a feature is *really* wanted, it's something
that can be done in user space --- for example, by adding a hack to
/lib/ld-linux.so which sends a ping-o-gram to a daemon that then
updates the relevant database.  That way you don't penalize every
single inode for something that is only needed for some inodes
(namely, the executables).

An extended attribute might also do, although in that case I'd
strongly suggest that the timestamp field only be updated if the last
execute time is over 24 hours old.  That way you're not constantly
updating the file system for very frequently updated executables such
as "/bin/ls".  Do we really need to know whether /bin/ls was executed
24 seconds ago as opposed to 30 minutes ago?

						- Ted

  reply	other threads:[~2009-12-18 14:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 18:57 Suggestion: xtime as new inode attribute Daniel Poelzleithner
2009-12-17  1:00 ` Simon Horman
2009-12-17  5:47 ` Jeffrey Hundstad
2009-12-18  9:27   ` Daniel Poelzleithner
2009-12-18 14:59     ` tytso [this message]
2009-12-17  7:06 ` Bryan Donlan
2009-12-18  9:19   ` Daniel Poelzleithner
2009-12-19  0:19 ` Junio C Hamano
2009-12-19  1:48   ` Frans Pop

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=20091218145916.GI2123@thunk.org \
    --to=tytso@mit.edu \
    --cc=jeffrey.hundstad@mnsu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=poelzi@poelzi.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