should readahead allow generic paths?

[Jon Masters]

On Thu, 2007-10-11 at 09:50 -0400, Steve Grubb wrote:
> On Thursday 11 October 2007 03:59:52 Jon Masters wrote:
> > Seems to me that it'd be more useful if the readahead package
> > configuration files (default/later) could use wildcards for path
> > components such as firefox, python, etc. (so that you don't have quite
> > the disconnect/lock-step requirement between these packages).
> 
> I've been working on a tool that scans certain important paths looking for any 
> file that is unpackaged. What I've found is that a lot of files get installed 
> where the package creates the directory structure, but does not actually own 
> it. IOW, a packager will do:

> I think one thing that would help performance overall is that packages must 
> own all the directories they create and delete them when its uninstalled. 
> This removes directory entries and improves search time.

You're (partially) joking though, right? I mean the time spent in the
kernel searching a directory path due to these is small fry ;-)

Valid point though!

Jon.