Re: [Nolug] Radius & Tacacs+

From: Dennis J Harrison Jr <dennisharrison_at_gmail.com>
Date: Tue, 20 Jan 2009 12:12:21 -0600
Message-ID: <6e8b29e0901201012r2a054cb3r77aa9048c896cf7c@mail.gmail.com>

> Frankly, I'm not going to risk my networks with a product that even the
> developer says is "code is still alpha" with "core features are still
> missing." Yeah, using alpha quality software is great if you want to
> generate recurring income by using client production networks as lab rats,
> but I prefer that my production networks and clients have software that is
> certified by the developer as a release product. A network admin's job is
> busy and hard enough as it is without having to worry about alpha quality
> software possibly bringing you down at an inopportune time.

'The' Developer?

And there is nothing wrong with using aspects of already written code
to do your job. What core features are missing from samba4? When was
the faq posted? And did you know that samba4 has been in development
since 2002? The features of the code I use is very stable in my
testing... which I could help you reproduce to prove a point. I use
Samba4 as a pdc or sdc with folder redirection and gpos.

Anyway, you shouldn't be afraid to self certify the software you
use... since at the end of the day, the user is going to look to you,
or whoever you train. So if you have the responsibility to repair and
progress. Shouldn't you also have the knowledge? I am not saying use
every bit of new fangled 'gee wiz' code out there. Just that if you
wait for 'The' Developer (lol) to certify code before you even touch
it... that you will miss out on a lot of what open source (and
hopefully free) can bring to the table.

Don't we want to progress and solve new problems instead of rehashing
the same old problems over and over? And how can we as developers be
expected to do that when the majority of users are just hangers on
waiting for that special moment in time when the sun and moon and
stars all align and I make it easy for them to use my code to make
money without any thought / input of their own beyond following the
configuration templates?

I also take it personally that you think I would abuse a relationship
with anyone (customer or otherwise) to the point of absolute
dependence. That would be irresponsible, and something I stay very
far away from.

If you build a samba4 pdc and break it by doing things you should be
able to expect out of that role... I will help you understand how to
correct things.

On Tue, Jan 20, 2009 at 9:06 AM, Jeremy (mailing list box)
<listbox@unix-boy.com> wrote:
> Dennis J Harrison Jr wrote:
>>
>> And gmail is still in beta.
>>
>> you should come to your own conclusions instead of reading a blanket
>> faq from newbland.
>>
>> samba4 works fine for my customers. I don't mind supporting it though.
>>
>> You should know that unless forced to by circumstance no one with a
>> responsible mindset would want to say "Yes this will work 100% for you
>> I guarantee. If you have any problems feel free to whine away before
>> you follow any directions or read any disclaimers."
>>
>> What do you think though?
>>
>> What doesn't work in samba4 for the use case of applying GPOs?
>>
>
> Gmail is in perpetual beta. In five years, I wouldn't be surprised if it
> still is in beta.
>
> Frankly, I'm not going to risk my networks with a product that even the
> developer says is "code is still alpha" with "core features are still
> missing." Yeah, using alpha quality software is great if you want to
> generate recurring income by using client production networks as lab rats,
> but I prefer that my production networks and clients have software that is
> certified by the developer as a release product. A network admin's job is
> busy and hard enough as it is without having to worry about alpha quality
> software possibly bringing you down at an inopportune time.
>
> J
> ___________________
> Nolug mailing list
> nolug@nolug.org
>
___________________
Nolug mailing list
nolug@nolug.org
Received on 01/20/09

This archive was generated by hypermail 2.2.0 : 02/17/09 EST