On Mon, Nov 25, 2013 at 7:36 PM, Ze'ev Atlas <[email protected]> wrote: <snip>
> The same thing about stupid limitation is the lack of standard catalog in > Unix. That limitation needs to go away. > I am confused by this. What would you put in such a catalog? The absolute path name plus file name, such as /u/myid/some/subdir/somefile.txt ? If so, why? If you know the name, the system knows where it is. Or do you must mean the file name without the path, such as "somefile.txt"? If this latter, how do you distinguish /u/myid/somefile.txt from /u/yourid/somefile.txt? Would the catalog have both entries? If so, then if you reference "the file" via this catalog, which file do you actually access? Or is this UNIX file catalog really something like I described which is used by the "updatedb" and "locate" commands? I.e. something where the end user interactively asks for possible matches, then selects the one they really need from the list of possibilities. I don't expect this to be made a kernel function, but it can be done as I do it via a "midnight cron" which uses updatedb to scan for the changed (added and deleted) files and updates the "catalog" for the locate command. If you really need real-time update, then this could possibly be done, at least on Linux, via something like the "icrond" daemon, which uses the "inotify" interface which can be used to monitor the filesystem in real time. > ZA > -- This is clearly another case of too many mad scientists, and not enough hunchbacks. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
