From owner-freebsd-hackers Mon Jul 19 9:30:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 7AC3D151D5 for ; Mon, 19 Jul 1999 09:30:16 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id MAA08438; Mon, 19 Jul 1999 12:29:52 -0400 (EDT) Message-Id: <199907191629.MAA08438@cs.rpi.edu> To: Oscar Bonilla Cc: freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: PAM & LDAP in FreeBSD, and userfs too. In-Reply-To: Message from Oscar Bonilla of "Fri, 16 Jul 1999 12:36:48 MDT." <19990716123648.C3049@fisicc-ufm.edu> Date: Mon, 19 Jul 1999 12:29:48 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I thought now would be a good time to chime in on some of my wild schemes... The reason I am interested in 'userfs' is to enable me to write a version of 'nsd'. Those of you familiar with Irix will recognize it. For others, what it does is to present the name-space on a machine as filespace. The advantages of this is that we can greatly simplify out libc to use the file/namespace that nsd provides. For example 'getpwent()' now becomes file accesses to /ns/.local/passwd/NAME. Another advantage that this abstraction provides is that it allows transparent alterations of the databases in use, even to the extent of NOT having to restart each client that may be using a specific database. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message