[990] in arla-drinkers

home help back first fref pref prev next nref lref last post

RE: proposed PAG handling changes for Arla

daemon@ATHENA.MIT.EDU (Lyle Seaman)
Tue Jul 20 12:31:30 1999

From owner-arla-drinkers@stacken.kth.se Tue Jul 20 16:31:30 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 25458 invoked from network); 20 Jul 1999 16:31:29 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
  by bloom-picayune.mit.edu with SMTP; 20 Jul 1999 16:31:29 -0000
Received: (from majordom@localhost)
	by sundance.stacken.kth.se (8.8.8/8.8.8) id SAA10954
	for arla-drinkers-list; Tue, 20 Jul 1999 18:27:02 +0200 (MET DST)
Received: from gw.stormsystems.com (stormsystems.com [209.49.190.30])
	by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id SAA10950
	for <arla-drinkers@stacken.kth.se>; Tue, 20 Jul 1999 18:26:52 +0200 (MET DST)
Received: from fs1.office.stormsystems.com (exchange.office.stormsystems.com [172.29.1.5])
	by gw.stormsystems.com (8.9.3/8.9.1) with ESMTP id MAA09969;
	Tue, 20 Jul 1999 12:25:44 -0400
Received: by fs1.stormsystems.com with Internet Mail Service (5.5.2448.0)
	id <PHD3G6WZ>; Tue, 20 Jul 1999 12:25:43 -0400
Message-ID: <B5C3AE5DDF77D211BD2500A0C9D3A6A11C0028@fs1.stormsystems.com>
From: Lyle Seaman <LSeaman@stormsystems.com>
To: "'Jeffrey Hutzelman'" <jhutz@cmu.edu>,
        Chris Wing
	 <wingc@engin.umich.edu>
Cc: arla-drinkers@stacken.kth.se
Subject: RE: proposed PAG handling changes for Arla
Date: Tue, 20 Jul 1999 12:25:42 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk

The ability to attach to a pre-existing PAG was not a design feature.  It
was an unfortunate side-effect of using groups.  Nor was the use of groups a
design feature, it was merely the most expeditious way of providing the
desired inheritance behavior.  It generated its fair share of problems over
the years.  A more general mechanism (such as a convention that one pointer
in the u area would be available for third-party use) would have been far
better, but required OS support. 

Some tools have been written which take advantage of the ability to swap
PAGs, but they could use another mechanism just as easily, which could have
its own capability.  

Which is not to say that I think restricting setgroups is a *good* idea, I
just don't think that it's necessarily a bad one, either.

home help back first fref pref prev next nref lref last post