Re: [PATCH] putting old-style lock handling back into 2.2.10

david parsons (o.r.c@p.e.l.l.p.o.r.t.l.a.n.d.o.r.u.s)
5 Jul 1999 17:11:02 -0700

In article <linux.kernel.19990705213918.A3030@loth.demon.co.uk>,
Steve Dodd <dirk@loth.demon.co.uk> wrote:
>On Sun, Jul 04, 1999 at 04:08:59PM -0700, david parsons wrote:
>
>> I noticed (when it made one of my test machines blow up and die) that
>> 2.2 doesn't support the old-style F_EXLCK locking anymore. This little
>> patch (against 2.2.10) puts that locking back, so that people using a.out
>> gdbm programs won't have them blow up on them.
>
>Uhhuh. I can quite understand not wanting to upgrade from libc4 / a.out
>binaries, but I can't understand sticking with libc4 & a.out, and then chucking
>the 2.2 / 2.3 kernel on it.

Because 2.2
* has devfs
* has reiserfs
* supports more devices
* is supposed to be faster
* corrects some bugs
* has better support for IDE

I don't feel that Linux should emulate the more unsavoury aspects of
Microsoft Windows -- in that when you update the kernel you have to
willy-nilly update everything else so that it would work. Of course
2.2.x is basically obsolete now that the 2.3 branch is active, but
it will make an adequate placeholder until 2.4 is released.

____
david parsons \bi/ And if I don't upgrade to 2.2, I'll be really unpleasantly
\/ surprised when 2.4 comes along.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/