[5133] in Kerberos
Re: Porting KRB5 to Linux?
daemon@ATHENA.MIT.EDU (Russ Taylor)
Wed May 10 14:18:36 1995
To: kerberos@MIT.EDU
Date: 10 May 1995 17:49:54 GMT
From: rtaylor@cie-2.uoregon.edu (Russ Taylor)
On 10 May 1995 15:45:53 GMT, Roman Gollent (roman@portal.stwing.upenn.edu) put forth into the Codex of Shub-Internet:
> Russ Taylor (rtaylor@cie-2.uoregon.edu) wrote:
> : Okay, first what changes did you make in Makefiles?
> : If you made any, it's not out of the box.
> I'll tell you how many changes I made: 0.
> : Second, how about posting said changes, or explaining why bash causes
> : problems for you, which also suggests it wasn't "out of the box".
> I never said Bash caused a problem with the Kerberos compilation. It
> did cause problems with the Screen and the Kernel
> compilation. Everyone agreed that Bash was at fault.
> : When a distribution dies because of incorrect typing (which I can fix),
> : missing libraries (which requires tracking down what they MEANT to use),
> : and unexplained errors like "parse error before "ssu0000" in std_rqs.c
> : (which I've not gotten a good explanation for), I no longer consider it to
> : be an Instant Port (tm). Not that I'm flaming the authors, I'm just
> : flaming the people who give useless tips like "it compiles out of the box",
> : because it isn't.
> I think you are trying too hard to find faults in something that is
> available free. I was also not trying to give you a tip about
> anything. You made the statement that Kerberos does not compile out of
> the box. I followed up by saying this is wrong, because of the fact
> that it worked without a hitch for me. And you are flaming the
Roman, you seem to be missing the point. The fact that it won't compile
happens to be a major fault. BTW, installing KRB5 requires running a
config script, which DOES change the files, so you are in fact lying when
you said it took no changes. I don't mind getting no anwers to a request
for assistance, I do mind posts by mindless sorts like yourself who can
contribute nothing more useful that "Well, it worked for me!!!". That
happens to be absolutely no help if it isn't working for someone else,
something which any high school graduate should be able to comprehend.
So get off your high horse, and offer some useful tips for porting, or
shut the hell up.
> authors. Find something more constructive to do with your time.
Like finding a version of Kerberos that works under Linux?
I'm working on it.
--
"Why do little blue midgets keep beating me with fish?" -- the Tick
