Hi Bernd,
>> Am 27.05.2025 um 16:17 schrieb tom ehlert via Freedos-devel >> <freedos-devel@lists.sourceforge.net>: >> >> I don't have any secret information. >> I'm just worried that there might be a reason PerditionC hasn't released >> *any* kernels over the last few years, while there has been so much >> added/fixed. >> And I have asked *often*. Nothing. I'm not sure taking the kernel "as is" >> from GitHub anyway is such a great idea. > I fully agree with you that the kernel should be thoroughly tested. I just > think that including it in a test release is a good way of having it tested > before some serious bugs propagate to a FreeDOS release. As the next FreeDOS release is probably a couple of years ahead, there is no hurry to throw it at a bunch of unsuspecting "testers". > My point of view on this is that the current master branch kernel is in a > better shape than the release kernel. I don't doubt that. > It fixes quite some serious bugs. +1 However not really "serious" as they existed for MANY years. > So I strongly suggest that we try getting these fixes into the distribution. I strongly disagree. I'm afraid of a kernel 2037 2.0 disaster. As you weren't around (neither was Willi): We had a perfect stable kernel 2036. 2037 had a couple of useful features/bug fixes, but someone declared "odd numbered kernels are unstable". So it happened that all bug fixing/feature enhancement went into the "better" kernel 2037. Reasonable so far. It only happened that 2037 crashed/halted/got stuck after a while. "Randomly". The reason was never discovered. In the end, 2037 (+ most of the effort) was discarded, and development restarted at 2036. BTW: the guy at the steering wheel was PerditionC. Just my 2 cents. Tom _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
