Subject: Re: fdclose conflict
To: Michael L. Hitch <email@example.com>
From: Rob Healey <firstname.lastname@example.org>
Date: 12/06/1994 08:03:08
> On Dec 5, 8:46pm, William Coldwell wrote:
> > I diddled with conf.c and fd.c to fix a conflict with kern_descrip.c in the
> > latest sup, but ended up breaking my kernel with a jump to 0 MMU fault.
> Funny - I did the same thing, and I get a jump to 0 fault when I try
> to enter the debugger.
I just did what they did for the other ports, changed fdclose in
fd.c to Fdclose and changed the prototypes in conf.c to use
the capitol F like they did for Fopen.
Less filling, tastes great... Now if they can just stop tweeking
the C library so much, it takes forever to compile and install
when they change a line here or there to make it pretty; i.e.
Anybody know if the server side of YP/NIS or lockd has been hacked
yet? The only reason you can't use NetBSD in a commercial environment
is that it can't lock files over NFS to commercial boxes and it can't
be a NIS server yet; sigh.