My thoughts on the "new development model"
Quoted 4 lines · On Tue, 26 Oct 2004 at 10:37:06 -0700 William Lee Irwin III wrote:
Quoted 1 line
"It works for me" doesn't cut it in the OS world.
It's an existence proof spanning a wide swath of architectures. If you are not seeing similar results, send bugreports.
I don't neeed to send in bug reports, there are plenty on l-k
right now:
- LVM is currently broken in 2.6.9-mm1
- the RTC and NMI code have a race condition between them
- NFS mount won't accept a FQDN over 50 bytes (patch was sent and utterly ignored, then recently reposted)
- cdrom driver thinks non-mt. rainier drives are capable
Quoted 2 lines
Point releases are in fact updated and maintained. Those updates are given the name of the next point release.
Are you saying people who encounter bugs in 2.6.9 should wait for
2.6.10? ...and when they find bugs in _that_ release they should keep waiting? In other words, Zeno was right after all?
--Chuck Ebbert 26-Oct-04 17:23:57
Quoted 3 lines · Chuck Ebbert
Are you saying people who encounter bugs in 2.6.9 should wait for 2.6.10? ...and when they find bugs in _that_ release they should keep waiting?
Hmm, what people do when they find a bug in 2.4.27 release? Wait for 2.4.28? Oh, horror!
Signature · 1 line
Dmitry
Quoted 3 lines · Chuck Ebbert
Quoted 3 lines
? Are you saying people who encounter bugs in 2.6.9 should wait for 2.6.10? ?...and when they find bugs in _that_ release they should keep waiting?
Quoted 2 lines · Dmitry Torokhov
Hmm, what people do when they find a bug in 2.4.27 release? Wait for 2.4.28? Oh, horror!
Apply a patch for the bugfix once it comes out. This is not news.
-- wli
Quoted 2 lines · On Tue, 26 Oct 2004 at 10:37:06 -0700 William Lee Irwin III wrote:
Quoted 2 lines
It's an existence proof spanning a wide swath of architectures. If you are not seeing similar results, send bugreports.
Quoted 7 lines · Chuck Ebbert
I don't neeed to send in bug reports, there are plenty on l-k
right now:
- LVM is currently broken in 2.6.9-mm1
- the RTC and NMI code have a race condition between them
- NFS mount won't accept a FQDN over 50 bytes (patch was sent and utterly ignored, then recently reposted)
- cdrom driver thinks non-mt. rainier drives are capable
None of the bugs you cite were recently introduced.
Quoted 2 lines · On Tue, 26 Oct 2004 at 10:37:06 -0700 William Lee Irwin III wrote:
Quoted 2 lines
Point releases are in fact updated and maintained. Those updates are given the name of the next point release.
Quoted 3 lines · Chuck Ebbert
Are you saying people who encounter bugs in 2.6.9 should wait for
2.6.10? ...and when they find bugs in _that_ release they should keep waiting? In other words, Zeno was right after all?
Bad idea to try this kind of argument with someone from a domain such as holomorphy.com. Zeno's mischaracterization of limit arguments was erroneous and furthermore is irrelevant to discrete models of phenomena, which don't have indefinite divisibility. In fact, these quantities of bugs correspond to natural numbers, which yield to infinite descent arguments, and satisfy descending chain conditions of various kinds. These are of the form "every descending chain stabilizes", a fortuitous choice of wording on Artin's part. =)
Upgrade to the later release to get fixes for a given release. This is not difficult to understand. No point release is "orphaned". The results of maintaining a point release are the subsequent point releases.
You may also have to face the fact of life that you may actually have to apply a patch to fix a bug if there's no release to move to yet.
-- wli
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 11 lines · William Lee Irwin III
Quoted 10 lines
Quoted 2 lines
It's an existence proof spanning a wide swath of architectures. If you are not seeing similar results, send bugreports.
I don't neeed to send in bug reports, there are plenty on l-k
right now:
- LVM is currently broken in 2.6.9-mm1
- the RTC and NMI code have a race condition between them
- NFS mount won't accept a FQDN over 50 bytes (patch was sent and utterly ignored, then recently reposted)
- cdrom driver thinks non-mt. rainier drives are capable
Quoted 1 line
None of the bugs you cite were recently introduced.
Is it relevant?
They exist, they must be fixed. If there is relevancy in this issue, the matter is "why do we care more about recently introduced bugs (that can be avoided by using a not-so-recent kernel) instead of caring about those well-known long-dated bugs?".
Mind Booster Noori
- -- /* *************************************************************** */
Marcos Daniel Marado Torres AKA Mind Booster Noori
http://student.dei.uc.pt/~marado - [email protected]
() Join the ASCII ribbon campaign against html email, Microsoft
/\ attachments and Software patents. They endanger the World.
Sign a petition against patents: http://petition.eurolinux.org
/* *************************************************************** */ -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFBfwvCmNlq8m+oD34RAo55AJ9cOHkhxYnA21anwlWkDj34V51KNACg48Pt yqOQ1GX/Xgszr6yNft/2BL4=
=VeDx
-----END PGP SIGNATURE-----
Quoted 1 line · William Lee Irwin III
Quoted 1 line
None of the bugs you cite were recently introduced.
Quoted 4 lines · Marcos D. Marado Torres
Is it relevant? They exist, they must be fixed. If there is relevancy in this issue, the matter is "why do we care more about recently introduced bugs (that can be avoided by using a not-so-recent kernel) instead of caring about those well-known long-dated bugs?".
It is highly relevant. The argument against the development process is on the basis of regressions introduced in subsequent versions.
When I point this out, the examples of "regressions" are invalidated, because they are in fact not introduced or reintroduced by new releases, and therefore not regressions at all.
Your "point", as it were, is different and incorrect on different grounds. Waiting to fix all known bugs to issue a release will fail to make forward progress of any kind, at the very least from "WONTFIX" bugs, and more commonly from bugs so hard they require extended periods of time to make progress in fixing, e.g. my current sun4d woes.
Perhaps the myth of utopias where all bugs are trivially fixable must be dispelled. I'm not a specialist in communicating with laymen, so my take on it is this:
Not all bugs are trivially fixable. The longstanding bugs you're complaining about are not getting fixed because they are so hard to fix the entire kernel programmer population of the Linux community can't solve them in a timely fashion. They are being worked on. We can't stop the world because of this because the kernel is so big there are hundreds or more of these unsolved bugs in the kernel at any given time and many of them last for years. So we have to continue doing other things while these bugs are open.
-- wli
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 7 lines · Chuck Ebbert
Quoted 4 lines
Quoted 1 line
"It works for me" doesn't cut it in the OS world.
It's an existence proof spanning a wide swath of architectures. If you are not seeing similar results, send bugreports.
I don't neeed to send in bug reports, there are plenty on l-k
right now:
If there are bugs not yet reported, you should report them. The number of yet-to-be-fixed bugs shouldn't make you not to report the others...
Mind Booster Noori
- -- /* *************************************************************** */
Marcos Daniel Marado Torres AKA Mind Booster Noori
http://student.dei.uc.pt/~marado - [email protected]
() Join the ASCII ribbon campaign against html email, Microsoft
/\ attachments and Software patents. They endanger the World.
Sign a petition against patents: http://petition.eurolinux.org
/* *************************************************************** */ -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFBfwxCmNlq8m+oD34RAl9jAJ9FWzkM96WUJks443s258iyhY0vgACfRyvh rQ+cm7HPeHKvtzqAOv7Ulso=
=e9Uc
-----END PGP SIGNATURE-----