Re: [lkml]2.2.19pre13: Are there network problem with a low-bandwidthlink?

On Tue, 20 Feb 2001, Alan Cox wrote: > > Its normal tcp behaviour. Its something called the capture effect. You can > mitigate it to an extent by using less buffers, but the buffer count in question > is at the ISP end for a download, or by using smaller windows > Some dumb questions. Does th

2.2.19pre13: Are there network problem with a low-bandwidth link?

When I am a) using modem ppp connection and b) downloading a file from a reasonably fast server so that the incoming connection is saturated, then attempting to open a new network tcp connection while this is going on fails quite regularly. The user app gets a ECONNRESET error. Investigation show

Re: 2.2.19pre6 change in /proc behavior

On Sat, 6 Jan 2001, Thiago Rondon wrote: > > At 2.4 too, but the status of file is o+r. Do see any > problem about this? > > -Thiago Rondon > Yes. /proc//environ is now unreadable by the owner; similarly for /proc//fd/ . It makes debugging harder. It is also a major change in a supposedly st

2.2.19pre6 change in /proc behavior

Let's say a normal user has started a process with pid = 12345. /proc/12345 owner and group is the same as the user but /proc/12345/* are all owned by root so the normal user can't read most of the entries there. In 2.2.18 everything is owned by the user. Is this supposed to be happening? Thanks

2.2.18pre18: many calls to kwhich

I noticed that kwhich is called a lot: make oldconfig:10 make dep: 65 make bzImage modules: 142 Assuming that this is unintentional, this patch helps a lot. --- Makefile.orig Sun Oct 29 09:09:16 2000 +++ MakefileTue Oct 31 11:39:11 2000 @@ -28,7 +28,7 @@ # k

Re: 2.2.18pre14 msdos mounted filesystems now in uppercase?

On Mon, 2 Oct 2000, Andries Brouwer wrote: > [omitted] > > so I suppose that if you try the "small" mount option > you should get the old behaviour back. > Yes, that works. I'm impressed that even old mounts handle this correctly. > [Clearly not a bug, although I don't know whether it is > a

2.2.18pre14 msdos mounted filesystems now in uppercase?

I have some fat16 partitions which I mount as msdos, intentionally not vfat. With 2.2.18pre14, the listings are now in uppercase which is a big change from previous kernels. A bug or a feature? Thanks. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a me