Re: 2.1.X and its separation from the Linux User base

linux kernel account (linker@nightshade.z.ml.org)
Thu, 5 Feb 1998 17:31:54 -0500 (EST)


The freeze refered to is a feature freeze (more like a 'slush' right now)
and existing code will be fixed.

On Thu, 5 Feb 1998, A.N.Kuznetsov wrote:

> In article <m0y0BCs-0005FsC@lightning.swansea.linux.org.uk> you wrote:
> : > For 2.2: Freeze, fix the bugs and get things out ASAP before trying any
>
> : Linus has already announced the first stage of freezing stuff.
>
> Opla.. I missed this moment... I'm playing quake2 and cannot stop it :-)
>
> Alan, how much time I have? There are several important things to do
> before releasing 2.2. I even do not say about QoS, there are the things
> crying about solution:
>
> * Transparent proxy. It is broken both at socket level (after new socket
> hashing) and in routing part (by me). Seems, it is the only thing, which
> really deserves to be blamed by 2.0 users.
> * IPv6. Well, though this stuff is still experimental, it would be shame
> to freeze it in its current state. To be honest, it is one big bug now,
> and if it would go to a stable kernel it is unlikely to make good reputation
> to linux. Fixing is not easy and will require some intellectual exerts.
> Well, I can make it, but I need know how much time we have to schedule
> this work and to decide what we will manage to make cleanly and what
> is deemed to be plugged with temporary patches.
> * Routing API needs garbage collection. It is not a big problem,
> because all the applications using it are under my control at the moment,
> but I need a time to be sure that something looking as garbage was not
> really an organ important for life :-)
>
> Alexey Kuznetsov
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu