Linked by Jordan Spencer Cunningham on Tue 22nd Sep 2009 16:50 UTC
Thread beginning with comment 385535
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2005-07-06
FAT32, of course, does away with that 65536-overhead number of files, but it also doesn't use extents (HFS does) and as such, has a horrible amount of overhead required to handle the number of files in the housekeeping department, because like FAT16 and FAT12, the File Allocation Table is a series of intersnarled singly-linked lists that snake through (possibly) the entire FAT. Oh, yes: HFS also supported long file names far before FAT ever did
You forget the Amiga. The filesystem - simply called the AmigaDOS FileSystem (FS) until the Fast FileSystem (FFS) came out, at which point it was called the Old FileSystem (OFS) - had no limit on files beyond what would fit on the media. The root directory started in the middle of the volume and kept expanding until you ran out of space. You also weren't limited to 8.3 filenames - you could have up to 30 characters (a limitation of Workbench - AmigaDOS supported up to 102 characters... monstrous at the time).