Flutterby™! : FAT filesystem

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

FAT filesystem

2007-05-10 01:47:42.605453+00 by Dan Lyke 5 comments

Silly question for you embedded developers out there? Anyone know of a DOS/FAT filesystem library that reads and writes and is free for redistribution (not GPL)? I see a number of commercial products, which are an option, and free source for reading, but everything that allows writing is either for pay, or bundled in to the rest of an OS (like Linux).

[ related topics: Free Software Embedded Devices ]

comments in ascending chronological order (reverse):

#Comment Re: made: 2007-05-10 22:33:02.740256+00 by: ziffle

http://www.freedos.org/

#Comment Re: made: 2007-05-10 22:58:34.973539+00 by: dexev

looks like it fails the 'not GPL' test...

#Comment Re: made: 2007-05-11 01:16:22.146254+00 by: Dan Lyke

Yeah, my hope was that I could find something I could statically link. One of the assorted free operating systems might be okay, heck, Linux might work for that matter, but if I can get around without using an OS I'd be happier.

#Comment Re: made: 2007-05-11 13:31:43.180004+00 by: ziffle

hmm I read that as GPL - sorry. Why not GPL? Why FAT?

Documentation and source code (171K) for a Re-entrant DOS-compatible file system. This package handles all file operations for a DOS-compatible file system on a diskette or hard disk partition no larger than 32M. A simple but useful diskette file utility (21K) is included to illustrate the use of the package. Also includes a simple buffer cache package.

http://alumnus.caltech.edu/~pje/rdcf2.txt http://alumnus.caltech.edu/~pje/software.html

Maybe he will allow redistribution.

#Comment Re: made: 2007-05-11 13:43:03.003426+00 by: Dan Lyke

Hmmm... I'll check that out, although we'll likely be in the 1-2 gig range.

FAT in case we want interop with Windows or Macs, not GPL because if we statically link with the library (as would likely be the case in a lightweight embedded system) then the application would have to fall under the GPL as well, and at least one entity in the chain wouldn't be amenable to that.

But GPL is okay if we end up running another operating system or something with dynamic library capability, because then I can just push changes into that module back upstream and keep the main app closed.