Hi Tom,

> now it would be interesting to hear about these 'heavy' updates, that
> happened completely in the dark for FreeDOS developers.
> 
> what do they do? fix bugs? improve compatibility? where are they
> documented?
> 
> it would be cool to let the freedos kernel developers decide if these
> changes are out of scope, or if cherry picking might be possible and
> worth the effort.

Well, have a look: https://github.com/dosemu2/fdpp/

My impression was that there are many changes related to pulling
the whole thing over into the dosemu2 Linux space and changing
the structure mixed with a variety of changes to improve for
example compatibility with apps. The new structure and style
has enabled some Valgrind checking, so potential bugs found by
that also have led to patches. The number of commits was too
high to even start looking at which of them are cherries, alas.

Apparently a few patches have already been backported, maybe by
Jeremy or Andrew, but as you know, Jeremy rarely talks about the
kernel work so I know very little about such plans and successes.

You can probably check https://github.com/FDOS/kernel

One example is changing how int 2f.1217 deals with pending CDS:

https://github.com/FDOS/kernel/commit/0dc6a02450ff170101ce911cf9f628187d17fe2f

This makes the kernel work with lredir drives in dosemu2 even
when no fake FAT "seed" is used (dosemu2 provides a FAT illusion
for C: during boot so you can boot from a Linux directory). In
dosemu1, there was a workaround in the emulator, but that had
to keep track of (potentially moving) data structures of DOS,
which was problematic. The patched kernel no longer needs that
FreeDOS-only workaround. Commercial DOS versions always worked.

You can also get automated builds, updated on commit here:

http://kernel.fdos.org/ which links to

https://github.com/FDOS/kernel/zipball/master
https://github.com/FDOS/kernel/tarball/master

That in turn makes me wonder whether it would be possible to
extract last-changed timestamps from the commit logs to stamp
every file in the ZIP or TAR with their respective change date.

At the moment, ALL files in the ZIP have the same timestamp
as the ZIP itself, which I find rather inconvenient.

Regards, Eric



_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to