nobody is saying eliminate it from the source code, they are just saying change
the default so that it is not compiled it. It is already part of an IFDEF but
the current source left it enabled.
David Lang
On Tue, 7 Jul 1998, Rogier Wolff wrote:
> Date: Tue, 7 Jul 1998 13:33:16 +0200 (MET DST)
> From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
> To: dalecki <dalecki@cs.net.pl>
> Cc: tytso@MIT.EDU, mj@atrey.karlin.mff.cuni.cz,
> linux-kernel@vger.rutgers.edu
> Subject: Re: OBSOLETE STUFF
>
> dalecki wrote:
> > > understand how to judge an OS based on such aesthetic qualities, I don't
> > > mind catering to their little obsessions if it doesn't take much
> > > effort. In this particular case the code has gone through enough
> > > testing that I'm reasonably certain it won't cause a problem, which is
> > > why I submitted a bug to Linus to disable it by default.
> >
> > ;-))) Ted ted. That was exactly my point. After some time, like years in
> > this case, the code should be in a state where the debugging code should
> > be just obsolete and removed. It was just a remainder what I did. And btw.
> > is't not my obsession it's my hobby :-))))))).
>
> I hold the opinion that unless it is really hindering your "movements"
> in the code, debugging code should remain in place. At some point in
> the future, you're going to get a problem, where enabeling the
> debugging code leads you to the problem quickly, while having to redo
> the debugging stuff takes a while.
>
> Linux also has a lot of stuff that checks for stuff that "usually
> doesn't go wrong". For example pushing data on skbuffs check if that
> space is available. You could argue that Linux has been debugged
> enough that this is no longer neccesary, but I tell you that it is
> much nicer to get a reproducable kernel panic while developing a
> driver than it is to have clients wine about unstable software.
>
> And I bet I'd have forgotten to turn that debugging on before starting
> developing, as well as I'd think stuff was stable before shipping, so
> the field would see "unstable behaviour" instead of the reliable
> panic. So Linux indeed has some debugging code, that remains enabled
> even in production kernels. This means that the cause for problems is
> more easily traced. This is a feature.
>
> Roger.
>
>
> --
> Actor asks a collegue: "To what do you owe your success in acting?"
> Answer: "Honesty. Once you've learned how to fake that, you've got it made."
> -------- Custom Linux device drivers for sale! Call for a quote. ----------
> Email: R.E.Wolff@BitWizard.nl || Tel: +31-15-2137555 || FAX: +31-15-2138217
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
>
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv
iQEVAwUBNaI6XD7msCGEppcbAQFqcQgAkYCCa2RObJCesqX4k3tMnddZ4KZM3MWM
G5ycBr8NwWHLAeOp6JlFuGNTLIn57p123hQNAxe3S0ZwuFf5hzxqDCMc5x90/jSD
B4ZJcm9Dby4kogyrAUFRM2D8C65D2lNaxe3pMDDncwXipe8jzZDOG8UaaCNV09cy
iQnRhx2AoebTB09aB4jBDmKvL64/NzxpScCYMtygXc/9pGAVl43Nm8/VxOCAqpLh
Cyc6KNVyUZfGRQrUv8QDzGmP90fpi2UeXEwR6vykjoCGG7girHVeuKBLweX6Aqxn
cBrDflCcXa/STkEwFS8IK5AakyALgZxaohp0X8dKk8OItILu41i7+w==
=N347
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu