Free FAT12/FAT16/FAT32 filesystem (C)
in [Embedded]
|
Prev: Sed1335 with LPC2294
Next: SD Card - boot sector
From: Jonathan Kirwan on 9 Jan 2006 23:10 On Tue, 10 Jan 2006 03:21:18 GMT, Jonathan Kirwan <jkirwan(a)easystreet.com> wrote: > So maybe I'll use this as >incentive to try and re-establish Lynx. I found a Win32, version 2.8.5rel1 of Lynx at: http://keihanna.dl.sourceforge.jp/lynx-win32-pata/17942/Lynx285rel1THg.exe It an installer for Win32 and you just run it and tolerate the crazy Japanese stuff as you proceed. Then, once installed, you've got one more problem -- it's configured for Japanese. So I went in, killed the existing LYNX.CFG file in the main directory and copied in the LYNX.CFG file that is in the org_docs subdir. Fixed. Jon
From: Jonathan Kirwan on 9 Jan 2006 23:28 On Mon, 9 Jan 2006 17:57:33 +0100, "Sagaert Johan" <sagaert.j AT belgacom.net> wrote: >have a look here > >http://sourceforge.net/projects/efsl Docs for it can be had at: http://puzzle.dl.sourceforge.net/sourceforge/efsl/manual-0.2.5.pdf or http://internap.dl.sourceforge.net/sourceforge/efsl/manual-0.2.5.pdf I note that it says that a minimum of 1k RAM is required. Better performance with more. Jon
From: Anton Erasmus on 10 Jan 2006 03:02 On Tue, 10 Jan 2006 03:35:46 GMT, Jonathan Kirwan <jkirwan(a)easystreet.com> wrote: >On 9 Jan 2006 19:03:46 -0800, "larwe" <zwsdotcom(a)gmail.com> wrote: > >>Oh, the initial URL appears. You can't use any of the links, though. > >By the way, the "About" on that sourceforge site says: > >"Library for filesystems intended to be used in embedded projects. The >library currently supports FAT12/16/32 reading & writing on SD-cards, >and is easily expandable for use with other devices on any platform." > >It's in C. Just so you know. > The license is LGPL though. AFAICR this means that a user of one's embedded system must have some way of replacing the LGPL'd library with a newer version of the same library. I think providing a linkable object file of everything without the library code is acceptable. Regards Anton Erasmus
From: larwe on 12 Jan 2006 22:01 Hi Steve, > filesystem file which I can also mount on FC3. (I used mkdosfs). Anyway > for some reason when the file is mounted as a loopback device, I can > only create names in lower case. Your test program in main.c has > strings in upper case. So I change your memcmp calls with strncasecmp. Not sure what this will achieve. The directory entry should contain uppercase characters. There is an oddity about the vfat driver in Linux, that it tries to prettify directory output by silently lowercasing 8.3 names when you list dir contents. IIRC if a filename you create COULD be represented as 8.3, it is stored on disk as the 8.3 uppercase version. Even if you specified lowercase when you created it, there will be no LFN entry containing this information. This fact is however semi-invisible under both Windows and Linux because of the magic translation in vfat and the case-agnosticism of Windows. However, if you do this: echo something > /mnt/vfat-device/OUTPUT.TXT cat /mnt/vfat-device/OUTPUT.TXT (no such file) cat /mnt/vfat-device/output.txt (shows output) In other words, you can't trust the output of ls on Linux when looking at MSDOS volumes. The 8.3 alias for your filename will be stored in uppercase in the directory entry. It is a "kinda" spec violation to have lowercase letters in the 8.3 name (it will break many DOS programs). By "kinda" I mean that as far as I'm aware it isn't specifically disallowed, but under Microsoft OSs it is impossible to create such a directory entry without poking around with a sector editor. I'll study your patch when I'm awake (I'm hallucinatingly tired at the moment) and see what else it addresses. Thanks for your feedback, much appreciated.
From: Anton Hadinger on 13 Jan 2006 04:18
larwe schrieb: > Hi Steve, > > >>filesystem file which I can also mount on FC3. (I used mkdosfs). Anyway >>for some reason when the file is mounted as a loopback device, I can >>only create names in lower case. Your test program in main.c has >>strings in upper case. So I change your memcmp calls with strncasecmp. > > > Not sure what this will achieve. The directory entry should contain > uppercase characters. > > There is an oddity about the vfat driver in Linux, that it tries to > prettify directory output by silently lowercasing 8.3 names when you > list dir contents. IIRC if a filename you create COULD be represented > as 8.3, it is stored on disk as the 8.3 uppercase version. Even if you > specified lowercase when you created it, there will be no LFN entry > containing this information. This fact is however semi-invisible under > both Windows and Linux because of the magic translation in vfat and the > case-agnosticism of Windows. > Look at the chapter 'Mount options for vfat' in the MOUNT(8) manual page. shortname=[lower|win95|winnt|mixed] Defines the behaviour for creation and display of filenames which fit into 8.3 characters. If a long name for a file exists, it will always be preferred display. There are four modes: ... Anton |