Re: traceroute breaks with 2.4.4

David Konerding wrote: > As far as I can tell, somewhere between 2.4.2 and 2.4.4, traceroute > stopped working. > I see the problem on RH7.x. Regular kernel compile with near-defaults > for networking, > no firewalling is enabled. Rebootiing to a similar config under 2.4.2 >

traceroute breaks with 2.4.4

As far as I can tell, somewhere between 2.4.2 and 2.4.4, traceroute stopped working. I see the problem on RH7.x. Regular kernel compile with near-defaults for networking, no firewalling is enabled. Rebootiing to a similar config under 2.4.2 works OK. - To unsubscribe from this list: send the li

Re: BUG: Global FPU corruption in 2.2

Ulrich Drepper wrote: > "Richard B. Johnson" <[EMAIL PROTECTED]> writes: > > > The kernel doesn't know if a process is going to use the FPU when > > a new process is created. Only the user's code, i.e., the 'C' runtime > > library knows. > > Maybe you should try to understand the kernel code and

Re: OOM killer???

I would tend to agree, I'm not a fan of the OOM killer's behavior. The OOM is forced because of the policy of overcommitting of memory. The reason for that policy is based on an observation: many programs allocate far more memory than they ever use, and most people don't want their program to cr

Re: "mount -o loop" lockup issue

Joerg Pommnitz wrote: > David Konerding <[EMAIL PROTECTED]> wrote: > > > But the attitude that "many eyes make all bugs shallow" and "let the > > users test the code for us" just don't hold up. For the former, > > clearly, many ey

Re: "mount -o loop" lockup issue

Alan Cox wrote: > > It's a bug in Linux 2.4.2, fixed in later versions. Regression/quality control > > testing would > > have caught this, but the developers usually just break things and wait for people > > to complain > > as their "Regression" testers. > > Hardly. We knew it was broken since w

Re: "mount -o loop" lockup issue

Rik van Riel wrote: > On Mon, 26 Mar 2001, David Konerding wrote: > > > It's a bug in Linux 2.4.2, fixed in later versions. > > Regression/quality control testing would have caught this, but the > > developers usually just break things and wait for people to comp

Re: "mount -o loop" lockup issue

It's a bug in Linux 2.4.2, fixed in later versions. Regression/quality control testing would have caught this, but the developers usually just break things and wait for people to complain as their "Regression" testers. Jason Madden wrote: > On Mon, 26 Mar 2001, David E. Weekly wrote: > > > On L