From owner-freebsd-hackers  Sun Jul 14 17:40:05 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id RAA19967
          for hackers-outgoing; Sun, 14 Jul 1996 17:40:05 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA19922
          for <hackers@FreeBSD.org>; Sun, 14 Jul 1996 17:40:03 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA07356; Sun, 14 Jul 1996 17:33:08 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199607150033.RAA07356@phaeton.artisoft.com>
Subject: Re: "login classes"
To: nate@mt.sri.com (Nate Williams)
Date: Sun, 14 Jul 1996 17:33:08 -0700 (MST)
Cc: sef@kithrup.com, hackers@FreeBSD.org
In-Reply-To: <199607141532.JAA14476@rocky.mt.sri.com> from "Nate Williams" at Jul 14, 96 09:32:58 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> > Well, I was a Busy Boy today.  While doing some other task%, I decided to
> > start implementing login classes for FreeBSD.
> 
> Do you have a better description of them other than 'allowing you to use
> separate authention'?  It seems I've heard lots of folks 'wish' for them
> in different contexts, so I'm not exactly sure *what* they do at any
> level, other than they can do many things. :)

Good point.  The recent discussion on session management for SMBFS
per user authentication is a good example of something you would need
to put in up front to not rule it out under the weight of backward
compatability.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.