9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Paweł Lasek" <pawel.lasek@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] authentication by LDAP?
Date: Thu, 29 Dec 2005 23:32:37 +0100	[thread overview]
Message-ID: <9f3897940512291432h677a5793y2f758ae927c02c1c@mail.gmail.com> (raw)

Hi.

I'm in following situation:

We want to have a plan9 machine in school, however, it must share it's
users database (usernames, passwords, privs and so on) with NetBSD and
Linux. Not only that, we need shared home directories and texmf tree
(we don't have much space so why waste it)

network is made of 3 virtual machines:

nexus: Linux Xen 2.0 host, main server, stores all files
devil: NetBSD 3.0/xen-guest
usagi: Plan9, xen-guest

What I am looking for is a way to hook plan9's databases into LDAP or
something similar, so I could change only the global repository.

Even better if it would be possible to set the rest, like ndb by it :-)

And what about DHCP? For some reason I can't get ISC DHCPD to give
valid info about auth servers and so on, would it work to use
plan9port and plan9's dhcp server?


--
Paweł Lasek
"Once a hitokiri, always a hitokiri. This will never change" - Jine-Ei
http://plasek.jogger.pl [in polish]

             reply	other threads:[~2005-12-29 22:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-29 22:32 Paweł Lasek [this message]
2006-01-02 12:35 ` Steve Simon
2006-01-03  1:12   ` erik quanstrom
2006-01-03  1:15     ` Russ Cox
2006-01-03  2:13       ` erik quanstrom
2006-01-03  2:34         ` Russ Cox
2006-01-03  2:53           ` erik quanstrom
2006-01-03 14:20   ` Paweł Lasek
2006-01-03 17:20     ` Dan Cross
2006-01-04 22:13       ` Paweł Lasek
2006-01-07  3:13     ` erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9f3897940512291432h677a5793y2f758ae927c02c1c@mail.gmail.com \
    --to=pawel.lasek@gmail.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).