Hi all, Alain mentioned that it is hard to keep an overview which kernel file is which version, for example if you want to report a problem or want to compare kernels. For that it would be a great help to put for example the SVN release number in there. SYS CONFIG can then be used to show it for any kernel file without having to boot with the file.
Example: Current SVN version of the kernel is 1499 since 22 Aug 2009, or if you include SYS: 1500 since 13 Nov. The latter calls itself version 3.6e by the way, but SYS can easily show a version of itself, a kernel cannot :-). The SYS update is for handling "SYS X: bootsect.bin" runs. You can get automated builds from fdos.org/kernel/ which also has http://fdos.org/kernel/latest/ which is the most recent SF.net file release, FreeDOS 2039, SVN 1494 if the history.txt in there did not miss any :-). Looks good! The config would still be less than 16 bytes with version number in it. I think it would be a valuable small extra. Putting the SVN release number will only add a 16 bit int. Opinions? Comments? Eric PS: FD Changes since 1494: 1495 update history.txt itself, 1497 update LSM to have only placeholders instead of real version/date and add BAT to fill in data, 1498 support IBM int sharing for STACKS, 1499 adjust RAM layout build. PPS: Sorry for my big silence in the last few months, I should really make some time free to read more DOS mail! ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
