> Can you check again? I think I solved at least Lucho's problem during > the init phase -- when fnodes could overlap disk buffers! Weird things > could happen indeed. > > After booting I haven't seen the message you quote though, so please > let me know how to reproduce if it still occurs for you. > > I made an intermediate kernel tarball just in case the cronjob fails.
Just read your mail and also the word from Lucho that it indeed fixed his fnodes so I checked right away and my test-machines are still panicing over the "more than 2 near fnodes ..." :-/ It goes wrong on extract.exe that is used with the modboot boot-system to unpack the cab-archives to ramdisk. On my boot disks I normally redirect output from extract.exe to file to only show that upon error. By setting an ENV-var this redirection can be disbled thus showing all extracting console output. With redirected-extract.exe it allways fails on the second call to extract.exe. With non-redirected-extract.exe it fails on the x-th (somewehere between the 5th and 10th) call to extract.exe. I used the daily tar.gz where the latest mod-time/date is 27-03-2004 01:35 for inthndlr.c So the current kernel is still panicing on fnodes ... Erwin -- Erwin Veermans <[EMAIL PROTECTED]> Psychiatry RuG, PO Box 30001, 9700 RB Groningen, Netherlands ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
