[dhcwg] LDAP, NFS home directory attributes

Jason Spence <thalakan@lightconsulting.com> Sat, 12 January 2002 21:14 UTC

Received: from optimus.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23992 for <dhcwg-archive@odin.ietf.org>; Sat, 12 Jan 2002 16:14:16 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id QAA27176 for dhcwg-archive@odin.ietf.org; Sat, 12 Jan 2002 16:14:18 -0500 (EST)
Received: from optimus.ietf.org (localhost []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA27060; Sat, 12 Jan 2002 16:04:31 -0500 (EST)
Received: from ietf.org (odin []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA27037 for <dhcwg@optimus.ietf.org>; Sat, 12 Jan 2002 16:04:29 -0500 (EST)
Received: from shaitan.lightconsulting.com ([]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23824 for <dhcwg@ietf.org>; Sat, 12 Jan 2002 16:04:26 -0500 (EST)
Received: (from thalakan@localhost) by shaitan.lightconsulting.com (8.11.6/8.11.6) id g0CKwiv06913 for dhcwg@ietf.org; Sat, 12 Jan 2002 12:58:44 -0800 (PST) (envelope-from thalakan)
Date: Sat, 12 Jan 2002 12:58:44 -0800
From: Jason Spence <thalakan@lightconsulting.com>
To: dhcwg@ietf.org
Message-ID: <20020112125844.A6885@shaitan.lightconsulting.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
X-Operating-System: FreeBSD shaitan 4.4-STABLE FreeBSD 4.4-STABLE
X-Uptime: 12:51PM up 41 days, 21:30, 5 users, load averages: 6.13, 6.11, 6.08
Subject: [dhcwg] LDAP, NFS home directory attributes
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

Hello -

I'm not on the list, please CC me on all replies.

I was talking with somone today about the number of Freenix systems
floating around organizations and how difficult they are to manage due
to the extensive manual configuration necessary for them to use
directory services and NFS mounted directories.  We came to the
conclusion that the optimal solution would be to have officially
recognized DHCP options for things like the LDAP server with
the posixAccounts for the organization and the NFS server serving the
home directories.  As far as I can tell, no work has been done on
creating such attributes, but maybe one of you can prove me wrong.

I'm working on a project right now to do this work using non-standard
attributes and a patched DHCP client, but would really like to see
this standardized in an RFC.  My goal is to be able to plug a Freenix
box into any one of my client's networks and have it automatically
start resolving uid/gids through the LDAP server and mount my home
directory, providing a completely consistent environment wherever I
go with zero client configuration.

 - Jason

Important letters which contain no errors will develop errors in the
mail.  Corresponding errors will show up in the duplicate while the
Boss is reading it.

dhcwg mailing list