>> > I've just installed a new box running Debian 2.0 (hamm) and I'm having a
>> > slight problem. I can't get it working properly on the network (this is
>> > my fourth hamm install and all others are fine...).
>> > nics# ping 192.168.1.1
>> > PING 192.168.1.1 (192.168.1.1): 56 data bytes
>> > p
> > Every Linux production server I work on is 2.0.29. Not one single 2.0.30
> > in the bunch...
> what's wrong with 2.0.30? am i missing something?
I've accidentally deleted the message that talked about ip_masq being
fixed in 2.0.30. I think it is fixed by applying a patch to 2.0.30, n
> I agree with jon here. A few weeks ago i tried to compile and run a
> pre-release of 2.0.31 and had all kinds of problems. I went back to
> 2.0.30 and everything has been peachy so far.
There were two different threads of development for 2.0.31. For a few
months David Miller was doing the de
> I have been just WAINTING for someone to bring this up. In my personal
> opinion, Linus is making a mistake by introducing new features in the
> release tree and it results in having two development trees going at the
> same time. Somehow the old way of releasing bug-fixes only in the stable
> When is 31 going to be finished? There are already pre-31 patches out..
> all the way up to 5.
They are up to pre-7 now. Looks like there's still a few problems to be
worked out, to be sure we have a nice stable kernel. The best thing you
can do at this point is to install pre-7 on all your
5 matches
Mail list logo
