Return to BSD News archive
Xref: sserve comp.sys.powerpc:31054 comp.sys.intel:27871 comp.os.misc:3650 comp.unix.bsd:15801 comp.unix.pc-clone.32bit:7954 comp.unix.sys5.r4:9000 comp.unix.misc:15386 comp.os.linux.development:22007 comp.os.linux.misc:32736 comp.os.linux.misc:32737 comp.os.386bsd.development:2963 comp.os.386bsd.misc:4647 comp.protocols.kerberos:3669 Newsgroups: comp.sys.powerpc,comp.sys.intel,comp.os.misc,comp.unix.bsd,comp.unix.pc-clone.32bit,comp.unix.sys5.r4,comp.unix.misc,comp.os.linux.development,comp.os.linux.misc,comp.os.linux.misc,comp.os.386bsd.development,comp.os.386bsd.misc,comp.protocols.kerberos Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!swrinde!news.uh.edu!uuneo.neosoft.com!bonkers.taronga.com!peter From: peter@bonkers.taronga.com (Peter da Silva) Subject: Re: Interested in PowerPC for Linux / FreeBSD / NetBSD? Followup-To: comp.os.misc,comp.os.linux.misc,comp.os.386bsd.misc,comp.protocols.kerberos Organization: Taronga Park BBS Message-ID: <D1oHxG.5ny@bonkers.taronga.com> References: <3cilp3$143@news-2.csn.net> <SCHWARTZ.94Dec27155146@galapagos.cse.psu.edu> <D1nL8D.8GE@indirect.com> <SCHWARTZ.94Dec31002050@galapagos.cse.psu.edu> Date: Sat, 31 Dec 1994 14:08:04 GMT Lines: 31 In article <SCHWARTZ.94Dec31002050@galapagos.cse.psu.edu>, Scott Schwartz <schwartz@galapagos.cse.psu.edu> wrote: >Huh? I'm proposing that they use a straightforward, reliable, system >proven by years of experience and slated to become an internet >standard, in order to reliably, safely, and securely share filesystems >between their computers. I'm sure that Kerberos is reliable and proven by experience and all that, but straightforward it is *not*. I suspect it's a documentation problem. All the Kerberos documentation seems to assume that you have a working Kerberos environment already, or at least that you've used one in the past so you know what it's all supposed to look like. If you were to publish (or point people to, if it's already been published) a "cookbook for setting up Kerberos IV on your system" (Yes, IV, 'cos that's the one that's shipping with the various BSDs) it would resolve a hell of a lot of the opposition to Kerberos. (On BSDI, if you take the system as default installed, and it's got a default route pointing through a PPP or SLIP link, and that link's down, attempting to login causes about a 90 second delay followed by a kerberos error message... Why? I don't know. Maybe I broke something installing the TIS firewall stuff? Maybe when we get through playing OSF/1 release musical chairs for a while I'll look into it...) I would love to be able to take advantage of Kerberos, but getting it set up is not a priority at work right now, and the documentation, as I said, has a large amount of double-dutch in it...