Date: Mon, 1 Jul 1996 14:11:25 -0600 (MDT) From: Nate Williams <nate@mt.sri.com> To: Garrett Wollman <wollman@lcs.mit.edu> Cc: Nate Williams <nate@mt.sri.com>, current@freebsd.org Subject: Re: compile_et & mk_cmds? Message-ID: <199607012011.OAA11223@rocky.mt.sri.com> In-Reply-To: <9607012006.AA10537@halloran-eldar.lcs.mit.edu> References: <199607010418.WAA08199@rocky.mt.sri.com> <9607011827.AA09845@halloran-eldar.lcs.mit.edu> <199607011842.MAA10492@rocky.mt.sri.com> <9607011927.AA06982@halloran-eldar.lcs.mit.edu> <199607011930.NAA10874@rocky.mt.sri.com> <9607012006.AA10537@halloran-eldar.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Which programs use it? > > At the moment, libcom_err and libss are used by the `kadmin' > facility. It is also possible to use libcom_err with Kerberos itself > (there are hooks in libkrb for that purpose, or at least there were > last time I touched it). So this is for kerberos, which is what I asked about originally? > There are other third-party subsystems that > use it (such as Kerberos v5, Zephyr, and my little > integrated-services-object-format library that will find its way into > FreeBSD in the mid- to long-term future). But for now it's only used for kerberos, right? > It's a very useful > facility. I have been comtemplating extending the err(3) interface to > provide Common Error entry-points in addition to the usual `errno' > entry points. It has *NO* documentation, so anyone trying to use it that doesn't work for MIT will end up rolling their own solution since they have *NO* idea what it's used for. Either document it or remove it please, it's taking up space. Libforms was also going to be used 'in the future' too, but given how busy *all* of us are and the very unlikely possibility that it will change I'd rather have 'useful now' tools rather than 'useful later' tools. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607012011.OAA11223>