I wonder if the upcoming 10.5.3 SP has a fix for this bug??

NickK · 12 May 2008 at 10:38

He found this bug in all other versions of BSD and BSD derivatives -- such as Mac OS/X -- that he checked. He found it in 4.4BSD Lite 2 and a helpful Samba developer also found it in 4.2BSD, which says the bug was about 25 years old.

knowledge123 · 12 May 2008 at 19:51

I'd much rather they fix the 4GB FAT32 bug; massively annoying

lloydsj · 12 May 2008 at 20:16

knowledge123 said:
I'd much rather they fix the 4GB FAT32 bug; massively annoying

Is that a bug? I thought 4GB was inherent to FAT32, and not something to do with Apple? or is the 4GB limit not what you're referring to

knowledge123 · 12 May 2008 at 20:23

lloydsj said:
Is that a bug? I thought 4GB was inherent to FAT32, and not something to do with Apple? or is the 4GB limit not what you're referring to

It is a bug, iirc, they fixed it and it came back again. :confused:

Not 100% sure, but afaik, that's what happened.

Fillado · 12 May 2008 at 22:04

FAT32 has a file size limit of 4GB, that isn't anything to do with Windows or Mac OS X - it's the limit of the actual filesystem.

If you're talking about something else ignore me

Sic · 13 May 2008 at 13:58

that's pretty mad. Surely there's enough BSD/Samba users to have discovered that sooner!!

knowledge123 said:
I'd much rather they fix the 4GB FAT32 bug; massively annoying

I was always under the impression that that's a limit of FAT32, not a bug.

titchard · 13 May 2008 at 14:35

Yeah 4GB is the largest filesize of FAT32.

Rich

NickK · 26 May 2008 at 09:12

*drums fingers* I'm tired of the Core memory leaks.. there's fixes for those in it too..