Re: The argument for fs assistance in handling archives

Spam
2004-09-05T14:13:47Z

> Salut,

> On Fri, Sep 03, 2004 at 10:22:55AM +0200, Helge Hafting wrote:
>> Requiring another syscall to open forks other than the primary
>> breaks _all_ existing software because it obviously don't use that
>> syscall yet. And then it doesn't provide any advantages over the
>> file-as-plain-directory way. . .

> Actually...

> We might tune the sys_open() call to take an additional argument (the
> stream ID), and introduce a compatibility interface into *libc which
> chooses strid=0 by default if the plain old open call is being used.

> Maybe this can be handled transparently by cpp..

How are things like copy handled today? Is it just some code linked
in during compilation (ie, the application handles the copy itself)
or is it a library function in libc? If it is in libc then it ought
to be enough if libc is patched to support the new semantics with
file-as-dir etc.

~S

> Tonnerre