From owner-freebsd-stable Fri Jul 28 10:19: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 785E837B9EE for ; Fri, 28 Jul 2000 10:18:55 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA04636; Fri, 28 Jul 2000 10:18:41 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA26261; Fri, 28 Jul 2000 10:18:40 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 28 Jul 2000 10:18:40 -0700 (PDT) Message-Id: <200007281718.KAA26261@vashon.polstra.com> To: stable@freebsd.org Reply-To: stable@freebsd.org Cc: dwmalone@maths.tcd.ie Subject: Re: rdist and pam In-Reply-To: <200007281055.aa78980@salmon.maths.tcd.ie> References: <200007281055.aa78980@salmon.maths.tcd.ie> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200007281055.aa78980@salmon.maths.tcd.ie>, David Malone wrote: > > > I should mention that ssh does support a challenge-response > ^^^ > I presume you mean cvsup here. Yes, sorry for the typo. > > > 3) I wasn't sure if you can adjust what gets pushed out to > > > clients from a central config file. We have per > > > machine exceptions. > > > Actually I am testing just that sort of feature now, in preparation > > for the next release. :-) > > Cool - sounds useful. How far through this are you? The enhancement was submitted to me in fully working form by Olaf Wagner. It adds the concept of client classes, which are a lot like FreeBSD's login classes. There is an associated login.conf-like configuration file to control various aspects of what each class may do. For example, you can hide certain collections or even certain branches from some clients. From the point of view of those clients, the hidden collections and/or branches don't even exist. The config file syntax and the mechanism are extensible. I am doing a little restructuring of it and a lot of testing, with the goal of releasing a new version before the summer is over. > If you're interested I can send you some examples of how we use > per-machine exceptions here, which might give you some ideas. That would be great. Please send them to . > > Yep, it's some strange interaction between some window managers and > > the M3 graphics library. It's mentioned in the BUGS section of > > cvsup(1). > > I'll try to find a similar workaround for tvtwm - should I let you > know if I find one? Sure. But even the work-around mentioned in the man page doesn't really solve the whole problem. I think it has something to do with M3's use of the WM_TAKE_FOCUS window manager protocol. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message