I can't be sure that 2.0.24 was the cause, but maelstrom won't
run right now because it claims that it cannot allocate 'X shared
memory' or some such thing. Lately, I upgraded many things including
libc5 and 2.0.6 -> 2.0.24 before I noticed this. Anyway, when
I can spare a few hours of modem time
On Thu, 7 Nov 1996, Bruce Perens wrote:
> It currently has 2.0.23 (although I have not released a boot disk, the
> kernel package is there).
>
> I'd like to hear more about what breaks with 2.0.24 .
>
How about hearing what has been fixed in 2.0.24? ;-) There was a bug
introduced via a bugfix for
On Thu, 7 Nov 1996, Bruce Perens wrote:
> I'd like to hear more about what breaks with 2.0.24 .
Some people have reported that X is slower in 2.0.24. Linus is looking
into the cause.
Gerry
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-
Bruce Perens wrote:
>
> > Any chance that 1.2 will have a recent kernel (like 2.0.23 or 2.0.24)?
> > 2.0.24 has the big ping fix which I consider important, however I've
> > heard some applications have problems with .24 due to a change in a
> > network struct.
>
> It currently has 2.0.23 (althou
In your email to me, Bruce Perens, you wrote:
>
> > Any chance that 1.2 will have a recent kernel (like 2.0.23 or 2.0.24)?
> > 2.0.24 has the big ping fix which I consider important, however I've
> > heard some applications have problems with .24 due to a change in a
> > network struct.
>
> It
> Any chance that 1.2 will have a recent kernel (like 2.0.23 or 2.0.24)?
> 2.0.24 has the big ping fix which I consider important, however I've
> heard some applications have problems with .24 due to a change in a
> network struct.
It currently has 2.0.23 (although I have not released a boot di
On Mon, 4 Nov 1996, Bruce Perens wrote:
> The code-freeze for 1.2 happens today.
Any chance that 1.2 will have a recent kernel (like 2.0.23 or 2.0.24)?
2.0.24 has the big ping fix which I consider important, however I've
heard some applications have problems with .24 due to a change in a
netwo
The person who is building X is expecting to upload them within the
next two weeks - he says sooner, I'm being conservative. The hold-up is
due to our packaging system going through some changes that require
editing of installation scripts. The X source builds 27 binary packages,
no surprise that s
8 matches
Mail list logo