>>>>> On Sat, 15 Apr 2000 23:30:04 +0200, Marc Lehmann <[EMAIL PROTECTED]> said:
> On Thu, Apr 13, 2000 at 01:11:14PM +0200, "Andreas J. Koenig"
><[EMAIL PROTECTED]> wrote:
>> > description: [Installing/Managing/Uninstalling Software]
>> > userid: [MLEHMANN]
>> > chapterid: [17] was [12]
>>
>> 17 instead of 12? I don't understand. The names of the two chapters are
>>
>> 12) Option, Argument, Parameter and Configuration File Processing
>> 17) Archiving, Compression and Conversion
>>
>> What gives?
> Hmm, the module does not have anything to do with [12], and [17] fits
> the _current_ (it requires some work to work on non-versioned/non-linux
> systems) usage best (Archiving). The only other option I can see at the
> moment would be "Misc. Modules".
> (i.e. "it's not oversight, but purpose")
Grrrrr. So now I read the README and cannot find a sentence that
justifies App:: namespace.
WHAT IT IS
This module traces any dynamically linked program for
filesystem-modifying calls such as rename, open64, unlink, remove
etc. It will save all the files before they were modified. It can
then undo and redo the changes as often as you want.
At the moment, Linux is probably the only system that is
supported.
Sounds pretty cool, much cooler than the name:-)
It's all about archiving and about file systems, but not about
applications. Maybe Filesys::Monitor, Filesys::Trace, or
Filesys::KernelCalls would describe the purpose of the core module
better?
Well, it's not really about file systems as such but rather about a
thing between kernel and file system, so the File:: namespace might
even work better, maybe File::NoOverwrite or File::Shelter?
--
andreas
