At 07:13 26.09.2002 +1000, Andrew Bartlett wrote:
Stefan (metze) Metzmacher wrote:
Hi Jerry,
please don't kick 3.0alpha20 before this is fixed. Andrew B. optimizes my
patch...
metze, I want to get that patch 'right', so I may take some time...
In particular, you changed the parsing
Stefan Metzmacher wrote:
At 07:13 26.09.2002 +1000, Andrew Bartlett wrote:
Stefan (metze) Metzmacher wrote:
Hi Jerry,
please don't kick 3.0alpha20 before this is fixed. Andrew B. optimizes my
patch...
metze, I want to get that patch 'right', so I may take some time...
In
At 10:01 23.09.2002 -0500, Gerald Carter wrote:
Everyone,
I would like to do another alpha snapshot release of the 3.0
code base later this week. Does anyone know of any code that
is too unstable for a release (seg faults, etc...)?
domain master = Auto is broken...
metze
At 10:01 23.09.2002 -0500, Gerald Carter wrote:
Everyone,
I would like to do another alpha snapshot release of the 3.0
code base later this week. Does anyone know of any code that
is too unstable for a release (seg faults, etc...)?
metze there's a bug in pdb_interface.c: in context_setsampwent
On Wed, Sep 25, 2002 at 01:32:16PM +0200, Stefan (metze) Metzmacher wrote about 'Re:
approaching release of 3.0alpha20':
At 10:01 23.09.2002 -0500, Gerald Carter wrote:
Everyone,
I would like to do another alpha snapshot release of the 3.0
code base later this week. Does anyone know of any
I think we should never put a NULL value in function handlers, but
always a stub function !!
Simo.
On Wed, 2002-09-25 at 13:32, Stefan (metze) Metzmacher wrote:
At 10:01 23.09.2002 -0500, Gerald Carter wrote:
Everyone,
I would like to do another alpha snapshot release of the 3.0
code base
Then that would be a function that always returns False /
NT_STATUS_NOT_IMPLEMENTED - I think the system can figure that out as
well...
On Wed, Sep 25, 2002 at 03:14:18PM +0200, Simo Sorce wrote about 'Re: approaching
release of 3.0alpha20':
I think we should never put a NULL value in function
Simo Sorce wrote:
This way to fix, without any DEBUG in is obscure and may hide
implementation errors imho.
A crash is much more easier to understand while developing.
We (ctrlsoft and I) had decided that implementing those functions was
optinal - I think we had the stub functions before,
at 03:14:18PM +0200, Simo Sorce wrote about 'Re: approaching
release of 3.0alpha20':
I think we should never put a NULL value in function handlers, but
always a stub function !!
Simo.
On Wed, 2002-09-25 at 13:32, Stefan (metze) Metzmacher wrote:
At 10:01 23.09.2002 -0500, Gerald Carter
Simo Sorce wrote:
It's not so difficult to change pdb code to NTSTATUS errors ..
I'll do it.
On the inside interface it's OK - if you change the external interface
then it's a big search/replace job. (But a job I would *love* to see
picked up, becouse it makes later conversions to other
On Wed, 2002-09-25 at 15:48, Stefan (metze) Metzmacher wrote:
At 23:34 25.09.2002 +1000, Andrew Bartlett wrote:
Simo Sorce wrote:
Yes, returning always NT_STATUS_NOT_IMPLEMENTED is the way to go imho.
This is in the old pdb code, so we don't have NTSTATUS there yet - so
for there I
Stefan (metze) Metzmacher wrote:
Hi Jerry,
please don't kick 3.0alpha20 before this is fixed. Andrew B. optimizes my
patch...
metze, I want to get that patch 'right', so I may take some time...
In particular, you changed the parsing for the info21, but not info23,
and I want to track the
On Thu, 26 Sep 2002, Andrew Bartlett wrote:
Stefan (metze) Metzmacher wrote:
Hi Jerry,
please don't kick 3.0alpha20 before this is fixed. Andrew B. optimizes my
patch...
metze, I want to get that patch 'right', so I may take some time...
It's not going to happen today, but I
Everyone,
I would like to do another alpha snapshot release of the 3.0
code base later this week. Does anyone know of any code that
is too unstable for a release (seg faults, etc...)?
My plans are to begin actively maintaining the SAMBA_3_0 branch
following this release.
cheers, jerry
I would like to do another alpha snapshot release of the 3.0
code base later this week. Does anyone know of any code that
is too unstable for a release (seg faults, etc...)?
I have not heard of any reports of FreeBSD users having any problems,
but I am also not sure how many people use
On Mon, Sep 23, 2002 at 10:01:53AM -0500, Gerald Carter wrote:
Everyone,
I would like to do another alpha snapshot release of the 3.0
code base later this week. Does anyone know of any code that
is too unstable for a release (seg faults, etc...)?
I've noticed just a few segfaults in
On Mon, 23 Sep 2002, Rafal Szczesniak wrote:
On Mon, Sep 23, 2002 at 10:01:53AM -0500, Gerald Carter wrote:
Everyone,
I would like to do another alpha snapshot release of the 3.0
code base later this week. Does anyone know of any code that
is too unstable for a release (seg faults,
On Tue, Sep 24, 2002 at 04:15:21AM +0930, Richard Sharpe wrote about 'Re: approaching
release of 3.0alpha20':
On Mon, 23 Sep 2002, Rafal Szczesniak wrote:
I would like to do another alpha snapshot release of the 3.0
code base later this week. Does anyone know of any code that
is too
On Tue, Sep 24, 2002 at 04:15:21AM +0930, Richard Sharpe wrote:
On Mon, 23 Sep 2002, Rafal Szczesniak wrote:
On Mon, Sep 23, 2002 at 10:01:53AM -0500, Gerald Carter wrote:
Everyone,
I would like to do another alpha snapshot release of the 3.0
code base later this week. Does
On Mon, 23 Sep 2002, Rafal Szczesniak wrote:
I've noticed just a few segfaults in utils like smbpasswd or net. I
don't remember now, where exactly, but I can look for it. Other than
that, I see no serious issues.
OK. Good. What I'm looking for anyone to scream, No! I'm halfway
through a
On Mon, Sep 23, 2002 at 10:01:53AM -0500, Gerald Carter wrote:
Everyone,
I would like to do another alpha snapshot release of the 3.0
code base later this week. Does anyone know of any code that
is too unstable for a release (seg faults, etc...)?
Apparently we ignore non-primary groups
21 matches
Mail list logo
