Hi,
np->allocsize is the number of bytes allocated for the file, right? (rounded
up to a block multiple).
Is it okay for np->allocsize to be initially as big as needed to contain the
file, rather than the actual disk space allocated for the file? AFAICS, it
is sufficient if diskfs_grow does the
On Wed, 10 May 2000, Martin v. Loewis wrote:
> No, you are right. DII and DSI and part of the standard. They are just
> not very useful, except for very specialized applications. Instead of
> the DII and the DSI, those applications could use an internal API of
> the ORB as well - for example, peo
According to the glibc manual, the result of setjmp must not be
assigned like diskfs_catch_exception does: it must be either
immediately used in a do/while/for/if/switch statement or
ignored. Has GCC relaxed this restriction?
On Wed, 10 May 2000 04:15:33 Brent Fulgham wrote:
> On Wed, May 10, 2000 at 01:33:11AM +0200, Marcus Brinkmann wrote:
> > Hi,
> >
> > maybe my ramblings will be useful for other inodeless fs implementations
> > later.
> >
> > 3. Making up inode numbers on the way:
> > Simply start with 1 and go
Date: Tue, 9 May 2000 22:55:21 +0500 (GMT-5)
From: Sergey Izvoztchikov <[EMAIL PROTECTED]>
On Wed, 10 May 2000, Mark Kettenis wrote:
> Indeed. I don't really have experience with CORBA, but I don't think
> the issues in this thread are relevant in this stage of Hurd
> developm
> As I understand ORBit is going to have DII, DSI in near feature.
> And I think that DII and DSI supposed to be in ORB. Correct me
> if I'm wrong.
No, you are right. DII and DSI and part of the standard. They are just
not very useful, except for very specialized applications. Instead of
the DII
