Mailing List Archive

I sent this guy a couple of suggestions, and asked for a couple of things,
does anyone want a cc of the messages?


At 10:25 AM 8/22/95 MDT, you wrote:
>
>Do we need to have a set of pre-compiled binaries for each platform ?
>
>I can't see any problem doing this, so unless there's an object, can
>we agree on what options to compile with then upload our binaries ?
>
>BTW, for this to work well, common features such as XBITHACK should be
>made a config option (assuming it hasn't already) so that we don't
>need multiple versions of binaries (basic/dbm auth could cause trouble).
>
>
>Here's a Linux user in need of assistance. If anyone wants to help him,
>please contact him directly, having me as the middle man only introduces
>confusion and delay.
>
>> Date: Tue, 22 Aug 1995 23:58:12 +0800
>> Message-Id: <199508221558.XAA00287@who.overseas.com.tw>
>> X-Sender: lizard@overseas.com.tw
>> X-Mailer: Windows Eudora Version 2.1.1
>> Mime-Version: 1.0
>> Content-Type: text/plain; charset="us-ascii"
>> To: hartill@lanl.gov
>> From: Steven Fox <lizard@overseas.com.tw>
>> Subject: Re: (fwd) for our Linux gurus (fwd)
>> Status: RO
>>
>> I am sorry to report that reinstalling LINUX kernel v1.2.7, & recompiling
>> Apache 0.8.10 did not solve the problem, look:
>>
>> [Tue Aug 22 23:43:18 1995] socket error: accept failed
>> [Tue Aug 22 23:46:37 1995] socket error: accept failed
>> [Tue Aug 22 23:48:59 1995] socket error: accept failed
>> [Tue Aug 22 23:49:01 1995] socket error: accept failed
>>
>> -Steven Fox
>
>> >> ---------- Forwarded message ----------
>> >> Date: Mon, 21 Aug 1995 13:25:52 -0400
>> >> From: "Aram W. Mirzadeh" <awm@qosina.com>
>> >> Subject: Re: (fwd) for our Linux gurus
>> >>
>> >> I had the same problem, I downgraded the linux kernel to 1.2.8 and problem
>> >> went away. Haven't had time to investigate the problem, but I'll look
>> into it.
>> >>
>> >> BTW, after the downgrade, you'll need to recompile the apache code.
>> >>
>> >> <Aram>
>
>
--
Aram W. Mirzadeh, MIS Manager, Qosina Corporation
http://www.qosina.com/~awm/, awm@qosina.com

>
> Do we need to have a set of pre-compiled binaries for each platform ?
>
> I can't see any problem doing this, so unless there's an object, can
> we agree on what options to compile with then upload our binaries ?

I think this is a good idea.

I feel that we should compile with *every* distributed module loaded.
If we don't put the features in, someone will just report that it
doesn't work.

I can supply NetBSD, BSDI_1.1 (and 2.0 if needed), and SunOS 4.1.x (who can't)


> BTW, for this to work well, common features such as XBITHACK should be
> made a config option (assuming it hasn't already) so that we don't
> need multiple versions of binaries (basic/dbm auth could cause trouble).
>

At 08:27 AM 8/23/95 -0500, you wrote:
>>
>> Do we need to have a set of pre-compiled binaries for each platform ?
>>
>> I can't see any problem doing this, so unless there's an object, can
>> we agree on what options to compile with then upload our binaries ?
>
>I think this is a good idea.
>
>I feel that we should compile with *every* distributed module loaded.
>If we don't put the features in, someone will just report that it
>doesn't work.
>
>I can supply NetBSD, BSDI_1.1 (and 2.0 if needed), and SunOS 4.1.x (who can't)

Linux 1.2 ( lib 4.6) here.
--
Aram W. Mirzadeh, MIS Manager, Qosina Corporation
http://www.qosina.com/~awm/, awm@qosina.com

X-Uri: http://www.zyzzyva.com/
Date: Wed, 23 Aug 1995 08:27:34 -0500
From: Randy Terbush <randy@zyzzyva.com>

I think this is a good idea.

I feel that we should compile with *every* distributed module loaded.
If we don't put the features in, someone will just report that it
doesn't work.

Would this include the experimental modules, and the NCSA
miscellaneous-log compatibility stuff? (NB that if that stuff's
compiled in, it does become active, logging to its default filenames).

[. The DBM auth stuff is also optional, but that's only because not
everyone has the necessary libraries; so long as we do, it's not
a problem for putting distributions together. However, it's
possible that knottier issues like this might arise with other
interfaces to third-party libraries or products in the future... ]

rst