In article <linux.kernel.UTC199905092118.XAA02192.aeb@eland.cwi.nl>,
 <Andries.Brouwer@cwi.nl> wrote:

>2.0.36 has
>	#define LPSTRICT    0x060f
>2.1.131 (and 2.2.*) has
>	#define LPTRUSTIRQ  0x060f
>
>
>This is a bug. It makes it a bit awkward to release an improved
>tunelp, entirely regardless of who does the releasing, since
>tunelp would have to check for the version of the running kernel,
>and the man page would need a lengthy explanation.
   .
   .
   .

  [patch]
>-#define LPSTRICT    0x060f  /* enable/disable strict compliance */
>+#define LPSTRICT    0x0610  /* enable/disable strict compliance */

     No, no, this is wrong, and bad software design.

     If LPSTRICT is defined as 0x60f in 2.0.36, it should also be
     0x60f in 2.2.*  -- if you define it as anything different,
     tunelp has to do run-time checks to see what kernel version
     it's running on.

                   ____
     david parsons \bi/ Or do the "The kernel is the wrong version for
                    \/  this program" message that MS-DOS is so loved for.

-
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/