lkml.org 
[lkml]   [1999]   [Apr]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: archive filesystem interface
Hi!

> I'm working at the moment on an extension to the linux filesystems
> (supporting hard links). The goal is to provide a library allowing the
> association of a unique key number to any file in the filesystems
> mounted on a given machine. When this is done, this key can be used
> to

I thought that major:minor:inode# is expected to be such unique
number. (Of course this is not true in some cases, but genereally
should be :-).

> The idea is to be able to associate information to any file in the
> filesystems, without constraint on the directory the file is stored in
> or the name it is given. Another goal is to provide a simple mechanism
> by which the information stored in a database is maintained up to date
> (i.e. can be made sensitive to file/key deletion).

What is this expected to be good for?

Pavel
--
I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel
Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:51    [W:0.054 / U:0.144 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site