At 06:53 PM 8/13/00 +0200, Neil Blakey-Milner wrote:
>On Sun 2000-08-13 (09:20), Kurt D. Zeilenga wrote:
>> >A make.conf knob to use a userinstalled library may create problems with
>> >different versions of Cysus-SASL. I had some problems with that when
>> >uppgrad
At 01:49 PM 8/13/00 +0200, Johan Granlund wrote:
>I think we have to support rfc2554 autenthication (With MECH LOGIN for
>Outlook) out of the box if we are serius about mailserver and security.
If you're serious about security, you shouldn't support LOGIN (or PLAIN)
unless adequate privacy protec
Note that there should be no need to cron the job. You
only need to save one set of bits to be used as a seed
for the next startup. And one set of bits SHOULD be
as good as any other.
I suggest you (at boot time):
1: open seed file for read
unlink seed file
use seed file +
At 11:08 PM 1/8/00 +, David Malone wrote:
>On Sat, Jan 08, 2000 at 02:14:10PM -0800, Kurt D. Zeilenga wrote:
>> At 04:43 PM 1/8/00 -0500, Garrett Wollman wrote:
>> >Hmmm. I don't see any such module. Or are you proposing to write
>> >one?
>>
>&g
At 04:43 PM 1/8/00 -0500, Garrett Wollman wrote:
>Hmmm. I don't see any such module. Or are you proposing to write
>one?
No. I'd just pull the pam_wheel from the Attic.
Kurt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
At 02:32 PM 1/8/00 -0500, Garrett wrote:
>< said:
>
>> I've noticed that su(1) is not yet PAM'ized. Is anybody
>> working on this? If so, I'm willing to test. If not
>> and time permits, I'll see if I can whip up an appropriate
>> patch.
>
>If you do this, please take care not to break WHEELSU
I've noticed that su(1) is not yet PAM'ized. Is anybody
working on this? If so, I'm willing to test. If not
and time permits, I'll see if I can whip up an appropriate
patch.
Kurt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the mess
I provided a patch for the USR2030 that likely could be
committed at the same time. See kern/13983.
Kurt
At 07:34 PM 10/3/99 +0100, Doug Rabson wrote:
>diff -u -r1.268 sio.c
>--- sio.c 1999/09/25 18:24:21 1.268
>+++ sio.c 1999/10/03 18:32:10
>@@ -567,7 +567,9 @@
> {0
At 11:50 AM 9/24/99 -0700, Jonathan M. Bresler wrote:
> insert plug for the FreeBSDcon talk "Stopping Spam--Five Years
>in the Trenches" by Jonathan M Bresler ;P
But what about "Stopping chat on technical mailing lists..." by ?. :-)
Kurt
To Unsubscribe: send mail to [EMAIL PROTE
This discussion is diverging a bit from this list's charter. Hence,
I'll be brief.
Amancio Hasty wrote:
> True LDAP (v2 or v3) does not provide record locking . Now the question is
> does Novell's NDS 8 -- a native LDAP v3 -- , Oracle's Directory
> Server or Microsoft Active Directory does if th
At 02:29 PM 7/4/99 -0700, Amancio Hasty wrote:
>Record locking and batch requests is a bit more difficult to solve perhaps
>someone in the list can shed light into this problem for instance does
>LDAPv3 provide such mechanism?
LDAP (v2 or v3) does not provide record locking, client/server
transac
At 07:56 PM 6/4/99 +0200, Poul-Henning Kamp wrote:
>I still think the right thing is:
>
> default to keepalives.
> set the timeout to a week.
OpenLDAP slapd, like may other daemons, relies on timeouts being a
reasonably short (a few hours) to deal with dead streams. Dead
streams occur
To facilate auto detection of the local threading environment,
it would be nice if the -?thread options set all the necessary
compiler/linker flags. It is a common practace for such
options to specify both compilation and link options.
I suggest the EGCS specs be adjusted to:
-pthread => -D_THRE
At 10:49 AM 4/3/99 -0600, Jacques Vidrine wrote:
>On 3 April 1999 at 7:49, "Kurt D. Zeilenga" wrote:
>[snip]
>> If you mean a version of regex included in the LGPL'ed libc,
>> yes, then this point might be mute. However, if you mean
>> the regex/rx distribu
At 03:32 PM 4/2/99 -0600, Jacques Vidrine wrote:
>On 2 April 1999 at 22:25, Doug Rabson wrote:
>> We should also consider installing libbfd. If and when we bring in a newer
>> version of gdb, it would be a good idea to avoid importing yet another
>> version of libiberty and libbfd.
>
>... and GNU
I had a hoard of problems upgrading a 3.0-current a.out
system circa ~12/7/98 to RELENG_3. After CVSuping,
running make aout-to-elf-build would complain about
OBJFORMAT previously being set in /etc/make.conf
(which I don't think it was) and suggested I override it.
Setting OBJFORMAT to elf, the a
At 05:47 PM 1/23/99 +0100, Alexander Sanda wrote:
>Even most recent versions of libtool (1.2e imho) fail to check for
>freebsd4* (as expected). As a result, they set can_build_shared to "no"
>which disables building of shared libraries.
Here is a simple patch (which I'll forward this to the libtoo
"Richard Seaman, Jr." wrote:
>
> On Fri, Jan 22, 1999 at 09:49:23AM -0800, Kurt D. Zeilenga wrote:
> > "Richard Seaman, Jr." wrote:
> > > _THREAD_SAFE is only used in stdio.h. Looking at what's there, it could
> > > be rewritte
"Richard Seaman, Jr." wrote:
>
> On Thu, Jan 21, 1999 at 02:00:53PM -0800, Kurt D. Zeilenga wrote:
>
> > > For kernel threading you just use libc. Whether or not libc generates
> > > thread safe (re-entrant) calls depends on whether its also linked with
>
"Richard Seaman, Jr." wrote:
> > BTW, why does FreeBSD use -D_THREAD_SAFE AND -D_REENTRANT (math.h)
> > while most other PThread (final) implementations use -D_REENTRANT?
> Don't know. Using _REENTRANT would be preferable, IMO.
Now if only a committer would agree... (I'll send patches if needed)
At 06:12 PM 1/21/99 +0200, Jeremy Lea wrote:
>On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote:
>> Actually, the new version, in FreeBSD "ports" form, doesn't require
>> -DLINUXTHREADS anymore, but it does require -I/usr/local/include to
>> pick up the right header, since it ins
21 matches
Mail list logo
