Subject: Re: fdclose conflict
To: Stephen J. Roznowski <firstname.lastname@example.org>
From: Michael L. Hitch <email@example.com>
Date: 12/05/1994 22:11:51
On Dec 6, 12:04am, "Stephen J. Roznowski" wrote:
> > From: William Coldwell <firstname.lastname@example.org>
> > 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.
> > *** /ftp/src/sys/arch/amiga/dev/fd.c Mon Dec 5 20:32:56 1994
> > --- fd.c Mon Dec 5 18:41:55 1994
> > ***************
> > *** 434,440 ****
> > /*ARGSUSED*/
> > int
> > ! fdclose(dev, flags, devtype, p)
> A much simplier fix is to make fdclose static inside fd.c. I've
> done this and am currently running a kernel built this way.
If fdclose() is static in fd.c, then how can it ever get called? It
has to be external so that the tables in conf.c are initialized properly.
Michael L. Hitch INTERNET: email@example.com
Office of Systems and Computing Services
Montana State University Bozeman, MT USA