Hi,
I'm working slowly towards using SFTs in the kernel using a series of
patches (so we can backtrack in case somebody finds a filesystem bug).
The idea is to still use the near fnodes for internal use but to use
only SFTs (no more far fnodes) for the file data.
First the two had to be made comp
2009/5/21 Eric Auer :
> Not really - I think it would be tricky to put the config
> variables in something that all used MAKE versions can deal
> with directly, as opposed to having both a BAT and a MAK?
There used to be (a long time ago) both a config.bat and a config.mak
(for DOS!), where config
Hi Bart,
>> svn diff -r1386:1388
>> gives a diff of 14 kilobytes, 12 files modified,
>> 46 lines changed, 170 lines added. Quite a lot.
> Do you think the change is too big?
Too big to say "read the diff" instead of explaining
what and how you changed, but not too big as patch :-)
Many of your
2009/5/21 Eric Auer :
> That is the point...
>
> svn diff -r1386:1388
>
> gives a diff of 14 kilobytes, 12 files modified,
> 46 lines changed, 170 lines added. Quite a lot.
> Okay okay I can analyze the patch myself... :-( Some explanations
> from the author would have saved some time here, of cou
Hi, I found another patch on my disk which probably has not
been applied to the stable kernel yet - please have a look
and comment :-)
- handle unusual floppy types
- change some initdisk messages
- re-enable DF_NOACCESS flag (correctly, I hope?)
- change InitializeAllBPBs to avoid "FAT16 FAT32 a
Hi Bart,
> Can you be more specific? Did you look at the svn diff at all?
That is the point...
svn diff -r1386:1388
gives a diff of 14 kilobytes, 12 files modified,
46 lines changed, 170 lines added. Quite a lot.
Okay okay I can analyze the patch myself... :-( Some explanations
from the auth
Hi Eric,
> Interesting :-) How does it work (in other words, what was the
> trick to make it possible) and how do the "config bat" settings
> work in this context? :-)
Can you be more specific? Did you look at the svn diff at all?
Bart
--
> Does anyone have any information or Idea about this problem?
> Would any of Jack's driver help?
Maybe __removing__ drivers and avoidable memory managers would be the
more promising approach ...
YES, a ramdisk (I use SRDISK) is a way to avoid the HD and possibly
bugged INT $13 support.
Also, a
Tested and didn't find anything eclatantly evil so far :-)
- It works mostly, see shot: http://img211.imageshack.us/img211/4611/ker2038.png
- "my" GetDiskFreeSpaceEx bug seems fixed
- "history.txt" neglects any development, oops Eric already pointed it, also,
the filename should be "HISTORY.T
Hi Bart :-)
> Jim reinstated SVN write access so I committed a patch that I have
> used internally in a not so clean fashion for a long time:
> cross-compiling from Linux using Open Watcom. The reason why: well it
> is more convenient and quicker (less than 2 vs. 20+ seconds here) to
> cross-comp
10 matches
Mail list logo
