tom ehlert wrote:
Hello Kenneth,
With several of my changes/additions the size of the
kernel has grown
just a few cents:
a) are human beings like me supposed to locate kernel sources ?
how about a link where one can download it without knowing where it
is ?
they are in the same place they have been, on sourceforge cvs. However,
most of the commits I make are in the dev (aka UNSTABLE) branch, because
they may very well (such as currently) unstablize the kernel. However,
anyone who wishes to get the kernel sources without going through
sourceforge (either via cvs or the online cvs viewing page) can download
an archive or binary (compiled with OW or Borland, updated daily) from
www.fdos.org/kernel/ (which contains both the stable kernel, which is
not too different from 2035a and I consider a stable kernel for users to
use anytime, and the dev kernel, which may occasionally not be for
public use (present week due to a bug I know about and am working on
fixing -- but that I've already mentioned the easy workaround).
b) anyone knows who in hell is 'perditionc' (or 'ror4') ?
me, it is my username on sourceforge (I figured you would have known
that by now?), also my web site (www.pchasm.org/www.perditionschasm.org).
I thought ror's commits were prior to even Bart being maintainer?
c) a while back, when changing things, they were discussed ;
either between Bart and me, or by posting changes to this list.
what happened to this praxis ?
what happened is no one responds when I post things or make available
online a patch for testing/reviewing, so now I commit my changes to get
a reaction. However, any major change or items I have questions about I
do try to discuss on list, and other various changes I do sometimes
discuss offlist with Lucho/Arkady/Bernd/Eric/Aitor since they have had
the most active participation in work for the last year or so. The
whole reason for the development kernel is to provide an implementation
that can change, be tested, and otherwise discussed prior to committing
to the stable kernel. Soon (when time, that thing I have little of,
permits) I will be merging changes from the dev kernel into the stable
kernel, and I will be using the comments I've received both on and off
list and bug reports to help determine what gets added -- anyone is
welcome at anytime to help me by either discussing changes (preferably
on the kernel mailing list) or someone such as you are Bart by going
ahead and committing the changes to stable if deemed useful/correct.
tom
I hope you don't feel I'm taking over the kernel and trying to keep the
discussions/decisions about changes to the kernel private or simply
excluding you. I really do value and strongly consider/review the
opinions and remarks of all the previous kernel maintainers (you, Bart,
Lucho, Arkady, ...); that said I'm not perfect and am doing the best I
can to fix user's bug reports and make the kernel more MS compatible.
I actually have 3 dev cvs trees (and then the stable cvs tree) that I'm
working on; my current primary one is the one I've been committing from
which currently only contains changes for debugging the fnode in use
message/panic and work towards the kernel missing floppy change-line
detection [kinda a pain for me to test well since my primary test
computer has an Award BIOS with the bug that doesn't clear changeline
until a read/write/? occurs]; another tree I haven't touched in while
but already merged the most important parts (most as conditional chunks)
is my win3 compatible tree (the remaining parts are simply the removal
of fnodes -- something I've decided against for now as I think for
future work I'd like to do (additional filesystem support) they may be
useful, and it didn't really bring anything useful that the
xltfd/savefnode functions couldn't do --- populate/validate SFT
entries); and a third where I'm working on MS/FD compatible menuing in
config.sys processing and additional sys/bootsector work. Periodically
I may make patch sets or test binaries available at
http://www.fdos.org/kernel/test/ (or for short descriptions use
http://www.fdos.org/AuoIndex/index?dir=kernel/test/ )
:-)
Jeremy
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
