[376] in SIPB_Linux_Development
Bug report, SIPB Hesiod package
daemon@ATHENA.MIT.EDU (svalente@MIT.EDU)
Tue Feb 1 23:22:57 1994
From: svalente@MIT.EDU
Date: Tue, 1 Feb 94 23:22:46 -0500
To: haynes@cats.ucsc.edu
Cc: linux-dev@MIT.EDU
In-Reply-To: Jim Haynes's message of Mon, 24 Jan 1994 16:58:41 -0800 <199401250058.QAA22118@hobbes.ucsc.edu>
Nobody else seems to have responded to this, so I've decided to.
(Sorry about the delay...)
> 1. hesiod.3 man page is missing
> 2. shouldn't /usr/athena/include/hesiod.h be included?
When I put together the package lists, I was in a hurry to get
something together so that people could get a working usable system,
not a working development system. I consider the subdirectories
/usr/athena/lib/lib*.a, /usr/athena/include, and /usr/athena/man/man3
to be development directories. Rather than sorting them out, I just
through all those directories into the "lib" package.
Sometime later, I'll sort out the lib package into several smaller
packages (kerberos-lib, hesiod-lib, discuss-lib, etc.) but I'd like to
keep those files out of the main packages.
> 3. when hesiod.h was made it put the hesiod.conf file in / instead of
> in /etc/athena. Which doesn't matter if you don't need a hesiod.conf
> file, but to use your binaries I have to use one.
That's weird... Well, I rebuilt the hesiod library and this time it
created hesiod.h (from hesiod.h.sed) correctly (using /etc/athena). I
didn't have to edit the file by hand, which I think is a good sign.
> semi-competent users like me are going to need named.boot and friends
> to get Hesiod working. And please the ones from the current Athena
> release, not the kluges that are or might be in the distribution on
> athena-dist.mit.edu.
You'll have to help me out here... Our system does not have a
hesiod.conf or a named.boot. The source tree I build "hesiod" from
simply contains libhesiod.a and hesinfo. I'm not clear on what's
really missing, or the relation between hesiod and named... Could
someone explain this?
Have a nice day.
-Sal.
