FreeLists / openbeos / [openbeos] Re: kernel mime_table module

[Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>]

On 2005-01-09 at 17:10:52 [+0100], François Revol wrote:
> > On 2005-01-09 at 16:33:35 [+0100], François Revol wrote:
> > 
> > > I fact I want to add that to Zeta to get something like lsof, which
> > > is
> > > sometimes very useful :)
> > > Now, having that in the kernel-side of the fd will account for fs
> > > which
> > > support hardlinks, while having that in the vnode itself can leed
> > > to
> > > races if the node is open from 2 different paths.
> > > (not supporting hardlinks in BFS doesn't mean we can't support them
> > > at
> > > all, in fact *bfs* doesn't support hardlinks only because it has to
> > > support queries)
> > 
> > Why should the query support affect the ability to support hard
> > links? IIRC
> > AGMS's RAM FS supports both.
> 
> True bu it isn't bound by having an on-disk layout.
> BFS stores the nodes leaf name in itself, as well as the inode of the
> parent folder. that wouldn't work for hardlinks.

The inodes wouldn't need to store those info, if the indices would 
reference entries instead of nodes.

CU, Ingo