Re: [Freedos-kernel] Versions and builds, conservatism
Hi! 8-Авг-2004 11:39 [EMAIL PROTECTED] (Bart Oldeman) wrote to [EMAIL PROTECTED]: BO> FreeDOS could, say, show the full message if you press a certain F key(as BO> it waits for F5/F8 anyway), like this BO> FreeDOS kernel build 2035a-WHATEVER. Copyright... BO> This kernel comes with ABSOLUTELY NO WARRANTY and you are welcome to BO> redistribute it under certain conditions; press F1 for details. Nice idea and very easy to implement. :) I think, this is even _should_ be implemented, as startup screen should be cleaned. --- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Versions and builds, conservatism
Hi! 7-Авг-2004 17:22 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to [EMAIL PROTECTED]: LG> Arkady, please respond if you read this. How are you? Fine, thank you. --- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Versions and builds, conservatism
> >> nor removal of phrases like "All Rights Reserved." that are useless now > > Pat sent an email to this list -- here's your chance if you really care > > about this! > > The Buenos Aires Convention (1911) that required this was superseded by > the Universal Copyright and Berne conventions. More on this at > http://www.cni.org/Hforums/cni-copyright/1999-01/0196.html Honestly I believe you're right here -- the issue is that changing copyright messages without agreement of the original author is a bit shaky IMHO. If you just get Pat's go ahead for the change then I'm all for it. Note that the GPL doesn't use "all rights reserved", it gives an example like Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. FreeDOS could, say, show the full message if you press a certain F key(as it waits for F5/F8 anyway), like this FreeDOS kernel build 2035a-WHATEVER. Copyright... This kernel comes with ABSOLUTELY NO WARRANTY and you are welcome to redistribute it under certain conditions; press F1 for details. > > It's more difficult than a simple "removal". If you'd simply replace all > > fnode references with SFT's you'll see a substantial increase in code > > size (because SFT's are "FAR"). Also fnodes are used in situations where > > SFTs can't do the job (dir operations). > > You're right - there are for example cluster fields that must be 32 bit > and not 16 bit for FAT32. Well those can be dealt with, a bit awkward though. IIRC Win98 stores these clusters in the various "SHARE" related fields. Not sure how many DOS programs (if any) depend on these on FAT32 though. Maybe SMARTDRV and DOSLFN or LFNDOS? > > However -- replacing the use of the persistent fnodes that are now in > > the HMA by SFTs is a good idea IMHO. This is just a question of time, it > > may never happen but it can happen if somebody does it and it works well. > > I see. What about including the SFT in the F-node structure and removing > all duplicating fields? As all SFTs are pointed to by a linked list, I > think that this is possible. What do you think? IMHO easiest to copy those fields across that matter, and then then delete them from the persistent fnodes. i.e. the far fnodes would be able to become different from the near ones, and xlt_fd() and save_far_fnode() would no longer use "fmemcpy" but copy individual fields. Another difference is the way that directory entries are addressed: SFT's use (sector number, entry in sector), where fnodes use (starting cluster number of dir, entry in directory). And if you don't keep the whole directory entry in memory then dir_write would have to become read/modify/write instead of simply "write". Takes a fair bit of time of course, it just depends how motivated one is. Bart --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Versions and builds, conservatism
Luchezar Georgiev wrote: Hallo Bart, ... #define BUILD "2035a" #define SUB_BUILD "-UNSTABLE" oops, I see it should be BUILD 2035 with SUB_BUILD a-UNSTABLE I don't know why some people started calling 2035a-UNSTABLE plain 2035a... perhaps just too lazy to type "-UNSTABLE". But it reports that on the screen right? Any conversation regarding UNSTABLE should refer to it as UNSTABLE or 'development branch' and optionally the cvs (may equal build) date if not the latest sources. Stable series should be refered to either by its version (only valid for released ones) or also by its cvs date if not latest. Sure. It reports quite a lot of things. But if BUILD is defined as 2035 (Bart) and 2035a (Arkady),it may be used for identification too. I hate the build & version dualism (e. g. version should be 2.0.35), but I know There is not a Bart and Arkady kernel, there is only a stable and development branch. Because Arkady likes to change lots, his patches are most easily worked into the dev branch, and because Tom/Bart like fewer changes, there's are more easily worked with the stable branch. As soon as I get time (maybe next week, this week I haven't even had time for sleep) I will sync in some of Arkady's fixes into to stable and bump both up to 2035b. ... By the way, how is Arkady? Has anybody heard of him recently? I begin to worry about him! No, I had to check sourceforge archives to make sure I was still getting Kernel mailings, its been so quiet. Hopefully all's well and he is just taking a break to work on other things. Regards, Lucho (as for patch starting this discussion, I'll look at it when I get home from work tommorrow afternoon; anyway I've got to get ready ...) Jeremy --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Versions and builds, conservatism
Bart Oldeman escribió: By the way, how is Arkady? Has anybody heard of him recently? I begin to worry about him! No idea. A bit silent here indeed. True. Maybe he is on a vacation? Aitor --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Versions and builds, conservatism
Hello Luchezar, > OK, long live the holy conservatism that saves the FreeDOS world > from the Arkadifying hell ;-G By 100% agreed tom --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Versions and builds, conservatism
Hello Bart, Actually a couple of years ago it was build 1937 for version 1.0.2 ;) Wow! Well, I hope that it can be 2.0.60 for build 2060 in just a couple of years ;-) nor removal of phrases like "All Rights Reserved." that are useless now Pat sent an email to this list -- here's your chance if you really care about this! The Buenos Aires Convention (1911) that required this was superseded by the Universal Copyright and Berne conventions. More on this at http://www.cni.org/Hforums/cni-copyright/1999-01/0196.html It's more difficult than a simple "removal". If you'd simply replace all fnode references with SFT's you'll see a substantial increase in code size (because SFT's are "FAR"). Also fnodes are used in situations where SFTs can't do the job (dir operations). You're right - there are for example cluster fields that must be 32 bit and not 16 bit for FAT32. However -- replacing the use of the persistent fnodes that are now in the HMA by SFTs is a good idea IMHO. This is just a question of time, it may never happen but it can happen if somebody does it and it works well. I see. What about including the SFT in the F-node structure and removing all duplicating fields? As all SFTs are pointed to by a linked list, I think that this is possible. What do you think? An altogether different subject, and you know very well why. You've made plenty of patches yourself and most of them went in. For which I thank you, and I hope that in time, more Arkady's patches will be accepted too. No idea. A bit silent here indeed. Arkady, please respond if you read this. How are you? Regards, Lucho --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Versions and builds, conservatism
Hello Lucho, > the build & version dualism (e. g. version should be 2.0.35), but I know > that neither this, Actually a couple of years ago it was build 1937 for version 1.0.2 ;) > nor removal of phrases like "All Rights Reserved." that > are useless now, Pat sent an email to this list -- here's your chance if you really care about this! > nor removal of the f-nodes that prevent programs which > modify SFTs from working, will ever happen. It's more difficult than a simple "removal". If you'd simply replace all fnode references with SFT's you'll see a substantial increase in code size (because SFT's are "FAR"). Also fnodes are used in situations where SFTs can't do the job (dir operations). However -- replacing the use of the persistent fnodes that are now in the HMA by SFTs is a good idea IMHO. This is just a question of time, it may never happen but it can happen if somebody does it and it works well. > OK, long live the holy > conservatism that saves the FreeDOS world from the Arkadifying hell ;-G An altogether different subject, and you know very well why. You've made plenty of patches yourself and most of them went in. > By the way, how is Arkady? Has anybody heard of him recently? I begin to > worry about him! No idea. A bit silent here indeed. Bart --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Versions and builds, conservatism
Hallo Bart, #define BUILD "2035" #define SUB_BUILD "a" #define KERNEL_VERSION_STRING "1.1.35" /*#REVISION_MAJOR "." #REVISION_MINOR "." #REVISION_SEQ */ #define KERNEL_BUILD_STRING "2035a" /*#BUILD SUB_BUILD */ #define BUILD "2035a" #define SUB_BUILD "-UNSTABLE" #define KERNEL_VERSION_STRING "1.1.35a" /*#REVISION_MAJOR "." #REVISION_MINOR "." #REVISION_SEQ */ #define KERNEL_BUILD_STRING "2035a-UNSTABLE" /*#BUILD SUB_BUILD */ I don't know why some people started calling 2035a-UNSTABLE plain 2035a... perhaps just too lazy to type "-UNSTABLE". But it reports that on the screen right? Sure. It reports quite a lot of things. But if BUILD is defined as 2035 (Bart) and 2035a (Arkady),it may be used for identification too. I hate the build & version dualism (e. g. version should be 2.0.35), but I know that neither this, nor removal of phrases like "All Rights Reserved." that are useless now, nor removal of the f-nodes that prevent programs which modify SFTs from working, will ever happen. OK, long live the holy conservatism that saves the FreeDOS world from the Arkadifying hell ;-G By the way, how is Arkady? Has anybody heard of him recently? I begin to worry about him! Regards, Lucho --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel