There's been a few discussions in the past about that in the past.
I actually looked at starting to write some code but ran into a couple things
and
also lack of time.
I would be happy to donate some time (not much for now) if there woudl be a
couple people with the knowledge of the subject to hel
On Fri, 6 Dec 2002, Octavian Hornoiu wrote:
> I have been doing a lot of research into integrating FreeBSD into my
> company's network recently and we have been converting our servers to
> FreeBSD gradually but one of the hurdles to overcome is the login issue.
> In order to make logins seamless
Quoting Brooks Davis <[EMAIL PROTECTED]>:
> On Fri, Dec 06, 2002 at 09:31:00AM -0800, Octavian Hornoiu wrote:
> > Winbind requires nsswitch to work properly and I know that FreeBSD
> > does not support it currently but why is this not a top priority at
> > the moment? I would much rather have nss
On Fri, Dec 06, 2002 at 09:31:00AM -0800, Octavian Hornoiu wrote:
> I have been doing a lot of research into integrating FreeBSD into my company's
> network recently and we have been converting our servers to FreeBSD gradually
> but one of the hurdles to overcome is the login issue. In order to
On Fri, Dec 06, 2002 at 09:31:00AM -0800, Octavian Hornoiu wrote:
> Winbind requires nsswitch to work properly and I know that FreeBSD
> does not support it currently but why is this not a top priority at
> the moment? I would much rather have nsswitch working than some of
> the minor features int
I have been doing a lot of research into integrating FreeBSD into my company's
network recently and we have been converting our servers to FreeBSD gradually
but one of the hurdles to overcome is the login issue. In order to make logins
seamless across our network I **MUST** use NT logins which
6 matches
Mail list logo
