Alexander Viro wrote:
>
> 6) unions in superblocks (and inodes) are nasty. Use separately-allocated
> private parts of either and keep pointer to them in ->u.generic_sbp and
> ->u.generic_ip, resp. It's less critical for superblocks, but for inodes
> it is pretty serious.
Is it expensive to all
Jamie Lokier wrote:
>
> Ben Fennema wrote:
> > My first question is, CAN I actually use lookup and readdir on a file
> > (Is it ls being too smart by looking at the thing, deceiding its not a
> > directory, and giving up -- or is it the kernel?)
>
> The kernel will more or less do what you ask,
Alexander Viro wrote:
>
>
>
> On Sat, 11 Mar 2000, Ben Fennema wrote:
>
> > Ok, I'm trying to implement streams in UDF.
> > They are kind of like resource forks/extended attributes.
>
> And our support of 'forks' is a bloody mess (as the whole idea of forks
> is - what can you expect from Cra
Ben Fennema wrote:
> My first question is, CAN I actually use lookup and readdir on a file
> (Is it ls being too smart by looking at the thing, deceiding its not a
> directory, and giving up -- or is it the kernel?)
The kernel will more or less do what you ask, though Alex Viro's
concerns are val
On Sat, 11 Mar 2000, Ben Fennema wrote:
> Ok, I'm trying to implement streams in UDF.
> They are kind of like resource forks/extended attributes.
And our support of 'forks' is a bloody mess (as the whole idea of forks
is - what can you expect from Crapple?). _Please_, wait with it until
the dc
Ok, I'm trying to implement streams in UDF.
They are kind of like resource forks/extended attributes.
Anyways, how they work is a inode has a pointer to a streams directory,
which contains all the streams for the inode as files in the directory.
So like:
FILE ---> stream dir
Stre
