Re: [Freedos-kernel] Kernel changes
You can release it, but I want to put it together with other updates and
finally generate v1.1.
Pat
On Fri, Apr 8, 2011 at 10:48 PM, Bart Oldeman
bartolde...@users.sourceforge.net wrote:
Hi,
thanks to Damien Guibouret the problem with file corruption in kernel
2039 finally seems to be resolved.
I collected some more changes and bug reports and fixed them. This
includes the problem with writes to write-protected disks failing
silently without error.
I think it might be a good idea to release a new 2040 kernel. If
nobody else does it within the coming 2 weeks I'll do it myself.
In the mean time:
An SVN source tarball can be obtained at:
http://freedos.svn.sourceforge.net/viewvc/freedos/kernel/trunk/?view=tar
An 8086/FAT32 OW1.9 compiled kernel.sys binary for testing at:
http://dosemu.org/bart/kernel.sys
2011 Apr xx - Build 2040
Jeremy Davis, Bart Oldeman
+ Changes Jeremy
* r1501 sys/sys.c: correct return value from NULL to FALSE -
fix compile with OW1.9
* r1500 docs/sys.txt, sys/sys.c:
handle case when source not specified but filename for boot
sector is given (sys X: bootfile.bin)
+ Changes Bart
* r1568 kernel/asmsupt.asm, mkfiles/owlinux.mak: Make sure the
DOS native and Linux cross-builds produce identical binaries.
* r1567 drivers/rdpcclk.asm,kernel/{asmsupt,entry,irqstack,kernel,
nls_hc}.asm, kernel/makefile:
Remove useless END from nls_hc.asm, add explicit byte
overrides for older versions of NASM for more compact code,
and adjust silent relocation segments.
* r1565 sys/sys.c: Change // to /* comments for Turbo C
compatibility.
* r1564 kernel/dosfns.c: If handle valid, close file in PSP
table before the low-level close + (perhaps) critical error.
Avoids closing the file twice (and hitting the critical
error twice) on abort/program termination.
Also, close can only return error 6 (DE_INVLDHNDL), not 5
(DE_ACCESS), see RBIL.
* r1563 kernel/task.c: From Christian Masloch:
set flags to 0x200 (IF set) when transferring to int22
termination address.
* r1562 kernel/fatfs.c: Check errors for callers of dir_write
and shrink_file. Fixes: Bug: File creation does not check
whether buffers are written correctly
(http://www.bttr-software.de/forum/forum_entry.php?id=9783)
* r1561 kernel/blockio.c, kernel/fatdir.c:
No longer force flush1() and dir_write_update() to return
TRUE if there were disk write errors. Part 1 for fixing
http://www.bttr-software.de/forum/forum_entry.php?id=9783
Bug: File creation does not check whether buffers are
written correctly
* r1560 kernel/kernel.asm:
Enlarge clock and block driver stacks. Thanks to Damien Guibouret
damien.guibou...@partition-saving.com.
* r1559 kernel/fatfs.c: Fix value that is used before being
initialised.
This lead to a drive to not be considered as FAT32 despite it is
(or vice-versa).
Thanks to Damien Guibouret damien.guibou...@partition-saving.com
.
* r1499 kernel/makefile:
With the stack changes the DOS segment has moved to 0x79.
* r1498 kernel/irqstack.asm:
New irqstack.asm: irq 2, 3, 4, 5, 6, 10, 11, 12, 14, 15 now
use the IBM interrupt sharing protocol for STACKS. Affect
int 2 too, but not IRQ 7 (INT 0fh) and IRQ 9 (INT 71h)
--
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
___
Freedos-kernel mailing list
Freedos-kernel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
--
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev___
Freedos-kernel mailing list
Freedos-kernel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] SourceForge.net Bug Tracker
Folks, Can you review the bug tracker at https://sourceforge.net/tracker/?group_id=5109atid=105109 and let me know what's valid. missing, etc.? I'm trying to plan/assign bug fixes. Pat Villani Project Coordinator -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Power management for Freedos kernel?
It's still active of sorts. I'm in the process of defining the road map, and input like this is very useful. We have FDAPM, but I'm not familiar with your GPU, and have no idea if it works with FDAPM. I don't know if there's anyone else that has an answer for you. Pat Project Coordinator On Mon, Jul 19, 2010 at 2:21 PM, Pekka Horttanainen pekka.horttanai...@gmail.com wrote: Hi! I used to use freedos in the past but then I upgraded my laptop to one that has a dedicated GPU, ATI Radeon Mobility X1600. Only now linux kernel (2.6.35rc) has come to the state that I can boot my computer to a text shell and keep it cool thanks to gpu power management in kernel. (And I used to have to use an old distro like Debian Lenny to be able to use the proprietary graphic driver for a legacy (=not supported anymore) card that has the best power management) I was wondering if the same could be implemented in Freedos kernel? You can see the code at the linux side, not having to reinvent the whole wheel. So far it is still Windows XP that keeps my computer coolest, keeping the CPU and GPU frequencies and voltages at their lowest, but I'd like to use other OS's as linux and Freedos without cooking my computer. Today's computers are so powerful that at their lowest setting they have still more than enough power to use a non-Windows OS. I hope someone's still reading this list since the archives show certain inactivity this year (I just joined). Best regards, Pekka Horttanainen aka piete -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] CRITICAL BUG - crosslinked files - 2039 unusable
There is work going on, but noe estimate to completion. I would tend to agree, use 2038 until it is fixed. Pat Project Coordinator On Fri, Jan 8, 2010 at 3:03 AM, dos386 dos...@gmail.com wrote: I have prepeared a new FreeDOS distribution for REAL USE in the field Is there anyone working on, o willing to work on this cross-linked files bug? If not, have to use 2038 :-| -- ~~~ wow ~~~ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] Distribution for REAL USE (was Re: CRITICAL BUG - crosslinked files - 2039 unusable)
Hello Alain, I probably missed it. What is different about your distribution? f it is a major imrpvement to what we have, why not distribute it as a FreeDOS distribution? Pat On Thu, Jan 7, 2010 at 7:54 AM, Alain Mouette ala...@pobox.com wrote: Hi all, first of all, Happy ne year :) Is there anyone working on, o willing to work on this cross-linked files bug? It seams to me that this can be very important for FreeDOS use, I allways assume that if a bug exists somewhere hidden, it could also atack under other circumstances, ie. not only on a 4Gb 99.9% full disk :( I have prepeared a new FreeDOS distribution for REAL USE in the field and this is holding me back. I never had problems with disks (older kernel), maybe even lass then with MS-DOS 7.10, and the latest kernel that I tested is even better (near to no lost cluster on reset). So this new version is very exciting :) Thanks for all, Alain Eric Auer escreveu: Hi dos386 :-) 1. No new details to the Crosslink-BUG ... cluster size is 4 KiB :-| However, it is very interesting that it involves broken high 16 bits on FAT32 on almost full disks. I hope this helped Bart to zoom in on potential causes for the bug :-). http://sourceforge.net/support/tracker.php?aid=2901916 www.mail-archive.com/freedos-kernel%40lists.sourceforge.net/msg02431.html To summarize your 19 Dec 2009 mail: Use kernel 2039 on a FAT32 (FAT28) disk, for example 6 GB with 4 kB/cluster and quite full, for example 95 p/c, with fragmented free space. Copy some files, delete some, copy some more files. Then, you say, many cross-links show up, mostly in the freshly copied two sets of files, also lost cluster chains. You are very right that the INTERESTING thing is that the broken files all have bad starting cluster numbers, all below 0x1, even though there were no free clusters in the first 65536 clusters before the experiment! 2. Discovered a NEW BUG: Half of it is not a bug, the other half is... 1. Get WDE or similar 2. Overwrite both entries in FS-info sector with $' 3. Reboot to FreeDOS 4. DIR - there is a massive delay at the end This is because DIR tells you how much space is used / free. For that, DOS has to count all used / free FAT clusters by reading the whole FAT, which is big in FAT32. The FS-Info sector caches the information, but by setting the values to the which you mention, you force a recalculation... 5. DIR - no delay anymore See above :-) 6. Try to brew a file or SUBDIR (MD) - expected result: should work - effective result: DOESN'T WORK Do you also get problems with file creation or growth, as far as those involve allocation of more clusters? If yes, which problems, just failure? Or creation of cross links? 7. Retry and it will work now Interesting! EDR-DOS doesn't have this bug. It probably also has the delay? I assume by bug you only mean the problem of creating a directory after invalidating FS-Info? Eric PS: I think 2039 got less publicity than 2038 and 2038 has more conservative updates. Combined, this means in 2039 you have more changes but (yet) fewer testers... -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] [SPAM] UNSUBSCRIBE
You need to go to https://lists.sourceforge.net/lists/listinfo/freedos-kernel, as shown on the bottom of the email, and follow instructions on that page. Pat On Mon, Nov 30, 2009 at 3:39 PM, m...@pixoled.com wrote: UNSUBSCRIBE -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] NOT PUBLIC DOMAIN (was Re: Possible size optimizations, kernel build 2039 bug in tracker)
Allow me to make this perfectly clear: the FreeDOS kernel * IS NOT PUBLIC DOMAIN* and will never be. Please do not spread such rumors. Just to make mys elf perfectly clear, the FreeDOS kernel *IS NOT PUBLIC DOMAIN*. In fact, unless a package has documentation that says it is public domain, make no assumptions of its copyright. Any package in FreeDOS, unless so deemed by its author, *IS NOT PUBLIC DOMAIN*. Pat On Fri, Nov 27, 2009 at 11:33 PM, ibid...@lavabit.com wrote: Hello all, 1. I saw a bug in the tracker ( http://sourceforge.net/tracker/index.php?func=detailaid=2901916group_id=5109atid=105109 ) regarding creation of cross-linked files on FAT32; this bug is new in 2039/not present in 2038. Seems to be very serious, but perhaps rare. 2. Size optimizations again Could nonls be re-enabled, since 2039 OW/UPX kernels seem to be about 2-4 kb larger than 2038.? Also, could the LFN helper api be commented out of the default build? The code in question is not current (reserves 3 fnodes, when only 2 are presently in use), and it is only a backend for an unwritten TSR. Would anyone be interested seeing the no-hd patches (and related stuff) merged into the tree as a build option (eg build fat16 nohd)? For what it's worth, this sounds like CD and _perhaps_ USB drivers would work, but not native USB boot (emulates HD), flash chips, or any bios drivers that don't use a floppy or floppy emulation. But we have two people who use it...Are there any more? Thanks, Ibidem PS- I looked up the Linux VFAT patent-avoidance patch (hack), and it seems to be less critical than I thought: It is a patch that enables a build configuration option (not identified). If the Linux kernel config does not show this option, it was not applied; if it shows the hack as not enabled, the code was not used. OFFTOPIC: JaguiD (Java with GUI for DOS) might be worth testing; the Ikon GUI, offered commercially this fall as an OS with some (unspecified) FreeDOS kernel, is now public domain/unmaintained--it should work with FreeDOS. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] NOT PUBLIC DOMAIN (was Re: Possible size optimizations, kernel build 2039 bug in tracker)
Thank you. I will follow through on that. Pat On Sat, Nov 28, 2009 at 8:26 AM, Eric Auer e.a...@jpberlin.de wrote: Hi Pat, Allow me to make this perfectly clear: the FreeDOS kernel *IS NOT PUBLIC DOMAIN* and will never be. Please do not spread such rumors. I do not see such rumors but... OFFTOPIC: JaguiD (Java with GUI for DOS) might be worth testing; the Ikon GUI, offered commercially this fall as an OS with some (unspecified) FreeDOS kernel, is now public domain/unmaintained --it should work with FreeDOS. Well only the GUI is public domain, but if their download still contains some unspecified FreeDOS kernel then you could ask them to make licensing clear on their page and in their download. If you sense a GPL violation, you can ask Shane for advice, he is an expert for handling that. Eric -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] A call for volunteers for 1.1 development
There's quite a bit of interest in producing version 1.1 on some of our other lists. As a result, I'm putting out a call for volunteers. I know when it comes to the kernel developers, there has been continual development activity and I'm hoping that you will continue to help with version 1.1. My personal goals for 1.1 in the kernel are more 32 bit support and better usb support/drivers/etc. Part of what I'd like to see from this group are suggestions on what features are possible that can be completed in the next six months. As project coordinator, I'll publish a list and start communications between activities as necessary. If you would simply like to help but don't know how, let me know. I'll check with the various developers and see how you can contribute. Thank you, in advance, to all who step up to make this happen. Pat -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] new kernel released
On Thu, Aug 6, 2009 at 12:01 PM, Tom Ehlert t...@drivesnapshot.de wrote: *** SNIP *** just wondering, why a) this wasn't advertised on this list and Oversight. b) why there isn't a 386-fat32 binary available (hardly anyone even knows where he might see a real 8086 machine), and the 386 resident code is ~1,5 KB smaller Point out the file(s) that were missed and I'll do an update. If, in the future, you or any other kernel developer would like to write up a better announcement, feel free to do so and give it to me. I'll follow through. Thanks. Pat -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] Fwd: [Freedos-user] Thanks for the new kernel, 2039
Just in case you missed it. Pat -- Forwarded message -- From: MegaBrutal megabru...@gmail.com Date: Wed, Aug 5, 2009 at 6:26 AM Subject: [Freedos-user] Thanks for the new kernel, 2039 To: freedos-u...@lists.sourceforge.net Dear FreeDOS developers, I'm a humble user (and fan) of FreeDOS, and I've just seen the Twitter message that announced the new kernel, built on 1st of August. :) I'd just like to thank you for the release! \o/ FreeDOS, and some folks here already helped me a lot in various projects of mine, including my thesis required by secondary school for the technician's certificate. Best regards, MegaBrutal -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-user mailing list freedos-u...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Building kernel 2038, compiles fine but hangs during boot.
On Sun, Aug 2, 2009 at 9:29 PM, Bart Oldemanbartolde...@users.sourceforge.net wrote: *** SNIP *** Or you can try the new 2039 release -- see sf.net/projects/freedos but not yet officially announced. Having trouble logging into ibiblio. When I get it uploaded there, I'll make the announcement. In the mean time, sourceforge is it. Pat -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] Freedos OS can't detect my cd-rom, or the cd driver cannot be loaded problem? - Yahoo! Answers
Hi Folks, Sonmeone is having trouble and it's up on one of the yahoo sites: http://answers.yahoo.com/question/index?qid=20090730064519AAdKTRN Can someone here have a look at the question and tell them about drivers and config.sys? Thanks. Pat -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Freedos OS can't detect my cd-rom, or the cd driver cannot be loaded problem? - Yahoo! Answers
Thank you. Pat On Fri, Jul 31, 2009 at 1:33 PM, Jackie McBride able...@gmail.com wrote: Pat, I'm taking care of it. It's the least I can do to help u guys. On 7/31/09, Pat Villani p...@monmouth.com wrote: Hi Folks, Sonmeone is having trouble and it's up on one of the yahoo sites: http://answers.yahoo.com/question/index?qid=20090730064519AAdKTRN Can someone here have a look at the question and tell them about drivers and config.sys? Thanks. Pat -- Change the world--1 deed at a time Jackie McBride Check out my homepage at: www.abletec.serverheaven.net please join my fight against breast cancer http://teamacs.acsevents.org/site/TR?px=1790196pg=personalfr_id=3489 -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] FYI
I've been seeing reports of FreeDOS crashing on machines it's installed on. I've also gotten some direct email from people about applications that ship with FreeDOS and then there are problems. I guess with the wider use of our little projects, we'll see and here more of these. What I'm doing personally is trying to get in touch with the HP folks who use our OS. I'd like to see if we can work more closely with them. Hopefully, we'll avoid some of the issues before the machines are shipped. I'll keep folks posted of any developments as they happen. Pat -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] new kernel release pending
Jeremy, Do you have a binary of what you will be tagging? I'd like to test it. Pat P.S., I can't build it because my development notebook is dying. On Wed, Jul 29, 2009 at 10:23 AM, Kenneth J. Davis jere...@fdos.org wrote: Assuming no objections, I will tag and make available kernel 2039 sometime at the end of this week. So if there are objections, please speak up! but include exactly what you feel needs to be done before the new release [that can not wait for a future release]. Thank you, Jeremy -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] new kernel release pending
On Wed, Jul 29, 2009 at 2:06 PM, Eric Auer e.a...@jpberlin.de wrote: *** SNIP *** Pat: Jeremy wrote earlier that current SVN binaries are always at: http://fdos.org/kernel/ke386f32.zip - 386+, FAT32 enabled kernel http://fdos.org/kernel/ke86f16.zip - 8086+, FAT16/12 only kernel now would be a good time to test for everyone else too! Sure :-) Maybe we could also mention the fdos.org auto builds on the webpage? Is there a way to include some automatic current build is from date X snippet...? What testing have you been doing on recent releases? Pat -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Copyright owners for kernel license
As FreeDOS project coordinator, just email here and you'll contact me. So you just did ;-) Way back in the dark ages, Jim and I had a discussion about licensing and we pretty much settled on GPL. These licensing discussions continue today as well. I won't bore you with the details, but we prefer GPL and related agreements for FreeDOS. Doesn't mean we'll turn away something that is not GPL but is open source for the distribution. That being said, my personal preference is GPL and don't want to change it for the kernel. I think it has served the purpose quite well over the years. Now a nit. I am of Italian origin and my first name is Pasquale, not Patrick. I use Pat as a nickname. Long story ... Pat On Mon, Jul 27, 2009 at 8:26 PM, Kenneth J. Davis jere...@fdos.org wrote: On Mon, Jul 27, 2009 at 10:44 PM, ibid...@lavabit.com wrote: ... In the discussion I refer to, relicensing was mentioned. I am curious who should be contacted for such requests, or if relicensing would be allowed, etc. The kernel source says Portions copyright Patrick J. Villani. Would that mean that Pat should be contacted? ... It would be very difficult; at minimal one would have to find all the people listed in contrib.txt (within the docs directory in the kernel source) and each of them would have to agree or the corresponding contribution determined and replaced. Pat of course would be the starting point as the kernel as a whole is derived from his work; in recent years Bart and Tom have contributed the most. Assuming this was achievable, it would only get you a version of the kernel relicensed; the majority of FreeDOS [the associated shell utilities] would still be GPL licensed. Jeremy -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] Web site ISP problems
Over the weekend, the ISP that handles our DNS did an upgrade and unfortunately it didn't happen smoothly, so they are effectively down right now. Based on what we know, this may take some time before they can correct it. Until this is fixed, www.freedos.org will not be resolvable in DNS, so it will appear as though the FreeDOS site is down. Instead, developers and users can visit the FreeDOS web site at its alternate address: http://freedos.sourceforge.net/ . Sorry for any inconvenience this may cause. Special thanks to Jim Hall for all the work he's done with respect to this issue. Pat -- ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] Thank you to kernel developers for new kernel 2038
I would like to thank all the folks who have worked very hard to produce this latest kernel. Their effort is very much appreciated by myself and all the people who continue to use FreeDOS in various applications. I am looking forward to using this new kernel and updating the distribution. Pat -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
Folks, I am not as up to date on the changes as you may be. I'm looking for a volunteer (or volunteers) to update history.txt for 2038 and 2039. When I get the updated files, I'll follow through and get them on the web sites. Pat On Sun, May 31, 2009 at 9:05 AM, Eric Auer e.a...@jpberlin.de wrote: *** SNIP *** Pat, Jeremy: Please FIRST update history txt BEFORE we make a sourceforge file release of kernel 2038. Thank you :-). Eric -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, Big Spaceship. http://p.sf.net/sfu/creativitycat-com ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Hello again
If half as much effort went into the code that has gone into this thread, we'd have rewritten the kernel several times over. Since I'm wrong about the kernel(?), let me put it to you this way. I want to put out a new release, FreeDOS v1.1 and get a plan in place. In 50 words or less, who is going to tell me which kernel is going with 1.1? Pat -- Amateur Radio Station: WB2GBF U.S. Army MARS station: AAR2BY/T -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Which kernel
This sounds liuke a good strategy. Pat On Mon, May 18, 2009 at 8:07 PM, ibid...@lavabit.com wrote: Hi Pat, I would say 2038 as default, 2037 (including winkrnl) as option--unless 2039 shows up first (doesn't look likely). If 2039 gets something worthwhile, 1.11 is an option. Thank you, ibidem -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel -- Amateur Radio Station: WB2GBF U.S. Army MARS station: AAR2BY/T -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038
I'll take care of it tomorrow. Pat On Sun, May 17, 2009 at 11:11 PM, Kenneth J. Davis jere...@fdos.org wrote: Kernel 2038 tagged and available at http://www.fdos.org/kernel/latest/ Someone with access, please upload to ibiblio and release on SF. Please test and report any new issues to the mailing list. Depending on any reported issues, 2039 scheduled to be released in about a month. Comments about new or existing bugs to focus on for next release welcome. Thank you, Jeremy -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel -- Amateur Radio Station: WB2GBF U.S. Army MARS station: AAR2BY/T -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Hello again
OK, let me chime in on this. Jim and I had several conversations on topics like this before I took over. I want to share the current thinking. We, as a group, have made a significant impact on the open source community and computing in general. This is something we need to keep in mind as we move forward, because there are people out there who depend on good ol' DOS functionality. On the other hand, we can't stand still because if we do, the project dies. Let me present the broad road map that exists at this time. The current release will continue along with better compatibility, possibly including running pre Win2K Windows, a new installer, formalizing a FreeDOS GUI, and of course bug fixes. We will start a new development branch that will remove the 8086 restriction, expand processor coverage, file systems, etc., and allow us to move FreeDOS forward. We will be developing this road map over the next couple of weeks. It is for this reason that I started this thread. I ask that all of you continue to provide constructive input so that we can start working on new stuff and have some fun while we're doing it. Pat -- Amateur Radio Station: WB2GBF U.S. Army MARS station: AAR2BY/T -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Hello again
Nope, I'm not doing anything other than trying to gather enough information with respect to project status to try to come up with a road map and possibly plan release 1.1. I have made *NO* decisions. Pat On Thu, May 14, 2009 at 4:26 PM, Eric Auer e.a...@jpberlin.de wrote: Hi Jeremy, *** SNIP *** Ohhh I smell a misunderstanding :-) I had assumed you or Pat were planning to make a fresh minimalistic start with a DOS kernel that can only RUN OW. This is partly because there is another DOS clone which was actually made to be good enough to RUN Borland compilers, too :-). *** SNIP *** Eric -- Amateur Radio Station: WB2GBF U.S. Army MARS station: AAR2BY/T -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] What is what?
Thanks all for the information. As everyone probably already knows, I have a similar background to Jeremy, with similar constraints. Here at HP, I now work on Linux clusters and we've been delivering products at an unprecedented rate. The cost is employee free time, as I typically put in 60+ hours per week all last summer in oder to meet schedule commitments. I'd love to be more active. Instead, best I can do is the occasional comment. *Sigh* Pat Interim FreeDOS Kernel Maintainer wrote: Arkady V.Belousov wrote: Hi! 11--2005 12:19 [EMAIL PROTECTED] (Pat Villani) wrote to freedos-kernel@lists.sourceforge.net: PV With all the unstable versions and private branches going around, 1. official 2035. 2. tom's stable fork (not very known). 3. Mine/Lucho unstable fork. 4. Kenneth tree, which is compomise between 2035 and (3) (development?). PV what is the official kernel? 2035. To clarify a little, The latest release kernel is 2035 (1 above), that Bart released, I hope to have a 2035a released in a few weeks, but largely depends on if I continue having free time or not. Tom maintains his own tree, which presently is very similar to 2035, it is available from his site. (2 above) The official kernel is the sourceforge 'freedos' project 'kernel' cvs. It has two branches, HEAD and UNSTABLE. The UNSTABLE (3 above) branch is what I refer to as the development kernel (kernels with w suffix). This is where Arkady's, Lucho's, and my work is done. It is for those wanting to make major changes or otherwise controversial changes. The unstable is because the changes here are less tested and there may occasionally be regressions or bugs that hopefully will not show in a stable release. The HEAD (4 above) branch is where released versions are made from. It follows a development model similar to what Bart and Tom have been doing. Fixes and changes from the UNSTABLE branch will be merged into here as I review them and/or they are decently tested. Some changes may not be merged or merged slower than necessary to avoid the fun [read unwanted banter] that would occur. Head is meant to remain as a stable branch for those needing a stable kernel for their product [personal or commercial] or those not wanting to help improve the kernel. The dev branch is meant for those who are willing to help improve the kernel (or simply have a program that needs a fix yet to be merged). Patches are accepted for both branches, but those to the dev series may be applied quicker or with less rigorous review than patches to the stable series. compiled cvs kernels (updated daily) are available as: (they correspond to OW compiled for 8086 with Fat32) www.fdos.org/kernel/kernel.sys for stable www.fdos.org/kernel/kernel.dev.sys for dev series (ren to kernel.sys) If it is still not clear, please ask and I will try to clear up any confusion remaining. [In case you missed it, I am presently the acting kernel maintainer, at least until someone speaks up and indicates they would like the role.] I do have plans for what I would like to do, but I make no commitments, only say that if something needs fixing, then bug me til its fixed, least I get side tracked. As an aside, I have an M.S. in computer science, and do this for fun, not related to professional activity, so user/developer feedback tends to spur what I work on. I think it is great that that you still read these lists (even if only occasionally) and value your input (along with Bart's, Tom's, Jim's, Arkady's, Lucho's, and the others that have worked on the kernel). You may find I tend to be quiet, but I do read all the messages on the list (when my email isn't being too flaky). Jeremy :-) --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] What is what?
With all the unstable versions and private branches going around, what is the official kernel? Pat --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: [Freedos-cvs] kernel/kernel inthndlr.c,1.87.2.12,1.87.2.13
That's really bad practice. The reason that it's there is so if, by reason of a bug or hardware failure of any sort, return_user() does really return, you will have bug that will be a nightmare to find. For the savings of less than 10 bytes, it's not worth the risk. Pat Arkady V.Belousov wrote: ! 31--2004 12:46 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to [EMAIL PROTECTED]: +++ inthndlr.c31 Dec 2004 12:46:21 - 1.87.2.13 @@ -752,7 +752,6 @@ return_user(); - break; @@ -1025,7 +1027,6 @@ return_user(); - break; I think, for readability purposes (to make understanding by new developers easier) `break' should be remained as comment. Something like: /* return_user() never returns, so break not need */ --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: [Freedos-cvs] kernel/kernel inthndlr.c,1.87.2.12,1.87.2.13
Hi Arkady, The - in the diff says that the break is removed entirely. Did you actually mean this, given your reply? I think you do save 2 or 3 bytes per break, depending on the compiler. However, I can relate to you an amusing experience. At one time, I did some consulting for Bell Labs. A few years after I left, ATT had a major network failure in the northeast US. A friend who was still with ATT told me that the failure was the result of a hardware problem that took the code into an untested branch of code. It was a function call inside a case that should have never returned and had no break at the end. The code fell into the next case and the system fell like a set dominoes. I'm not maintaining the kernel, so just my $0.02 -- which is worth less in Euros ;-) Pat Arkady V.Belousov wrote: Hi! 5--2005 08:30 [EMAIL PROTECTED] (Pat Villani) wrote to freedos-kernel@lists.sourceforge.net: +++ inthndlr.c31 Dec 2004 12:46:21 - 1.87.2.13 return_user(); - break; I think, for readability purposes (to make understanding by new developers easier) `break' should be remained as comment. Something like: /* return_user() never returns, so break not need */ PV That's really bad practice. The reason that it's there is so if, by PV reason of a bug or hardware failure of any sort, return_user() does PV really return, you will have bug that will be a nightmare to find. No, I say not this (that `break' should be present): I say, that new kernel developer may not know (yet) that return_user() never returns, so [s]he may wonder, why there is no `break' and why this is not a bug. So, commenting this trick may ease the understanding of this code. PV For the savings of less than 10 bytes, it's not worth the risk. BTW, `break' here really (may) save some bytes, because tails merging. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] unused SFT fields - f_nodes not needed???
The simple fact is that the f_nodes structure is not needed at all. Before I left the group several years ago, I was planning to rewrite the kernel specifically to eliminate f_nodes and move to SFT. The reason was precisely the incompatibility between this kernel and other programs such as windoze. The f_nodes structure is a leftover from the original family of DOS API compatible RTOS that the kernel is derived from. Those operating systems used the f_nodes structure for file system switches and as locking objects for fine grain locking necessary in an RTOS. You don't need them. Pat Eric Auer wrote: Hi, I tried to check SFT compatibility of FreeDOS, quick conclusion: sft_dcb is never accessed sft_stclust is never accessed sft_relclust is never accessed sft_cuclust is never accessed sft_dirdlust (sic!) is never accessed sft_diridx is never accessed sft_bshare is never accessed sft_ifsptr is never accessed (nor initialized to 0?) Is that correct? I think SFT-messing programs like Windoze will not be happy in particular about all those uninitialized cluster values, the missing DCB pointer, and missing dir entry info. The share / ifs stuff is probably less interesting or set by SHARE / IFSdrivers directly, without kernel interaction. Each SFT uses some header with size info and link pointer, and tools like FILES.COM or Windoze will just search for the last SFT and add extra SFTs - how will FreeDOS react? I think this will create SFT slots for which no fnodes exist. Next point are the fnodes themselves: f_count, f_mode, f_flags, f_diroff, f_dirstart, f_offset, f_cluster and f_cluster_offset all seem to have exact equivalents in the SFT slot structure. Am I misunderstanding something here or could we just throw away half of the f_node fields by using the SFT slot fields instead??? There would be still some remaining f_node fields, but they would be not much more than a copy of the raw directory image data (f_dir) and a pointer to the DPB for the file (f_dpb). I must be misunderstanding something here - if removing f_nodes would be so easy (in terms of: replace fields by very equivalent SFT fields), then why did we have that big project with near fnodes instead of just throwing away the fnodes altogether? So please tell me where the big hidden caveat is lurking. Thanks for reading this maso mail ;-). Eric PS: If a DCB and a DPB are the same (?), the only left over f_node purpose would be holding a copy of the raw directory entry of the file. That could be guarded by something like storing a checksum of the starting cluster and filename in the fnode, and re-read the directory entry if the SFT slot has changed unexpectedly (a warning could be shown if the SFT slot has changed unexpectedly when FreeDOS would like to write back the directory entry to disk). PPS: A few bits of f_flags might differ from sft_flags bits. [This mail is based on browsing the SF.net 2035 sources, no CVS updates...] --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] unused SFT fields - f_nodes not needed???
It's the original data structure used for file systems. It was designed originally as a structure that contained a semaphore, file system type identifier, and a union for file system data. It was simplified for the original DOS-C/FreeDOS kernel, and changes have been made by myself and others to map it into the SFT, so that it now shares this role with the SFT. Pat Roberto Mariottini wrote: Hi Eric, I don't know what an f_node is, but you have received 4 replies from: - James (former kernel maintainer) - Bart (former kernel maintainer) - Tom (former kernel maintainer) - Pat (former kernel maintainer and original kernel author) I just wanted to add myself :-)) Ciao P.S.: If you still have no clue, you are in big troubles... :-) --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
