Yet another bounce.Original CC: martin.langhoff@xxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx, peter@xxxxxxxxxxxxxxxx , mjscod@xxxxxx, melo@xxxxxxxxxxxxxxxx
On Jan 21, 2008, at 6:02 PM, Kevin Ballard wrote:
On Jan 21, 2008, at 5:56 PM, Martin Langhoff wrote:On Jan 22, 2008 11:46 AM, Kevin Ballard <kevin@xxxxxx> wrote:Again, I was talking about a system that used unicode top-to-bottom.On HFS+ you have to use UTF-8 for your filename or it simply won't work.Hmmm. I m pretty sure HFS+ has a lot of problems if you run OSX as anNFS server with clients in different encodings. It would never work in real life. The "envelope" OSs have to work in is hugely varied -- muchmore so than any other apps. You should try writing one someday ;-)I'd imagine writing an OS to be a horrifically complicated task. And yes, I can certainly imagine HFS+ might have issues when used to back an NFS server with other clients, but that still leads back to the original point, which is that all these problems stem from the differences between HFS+ and other filesystems, not any inherent problem with HFS+ itself.other words, I was trying to illustrate that HFS+ isn't wrong, it's just different, and the difference is causing the problem.Did you spot the rather nasty issues that Ted mentioned earlier in thethread? I would say HFS+ is a bit "special" rather than "different".IIRC, the biggest problem he talked about was the changing unicode standard, but since the technote appears to state that HFS+ will not be changing its normalization algorithms to preserve backwards compatibility with existing volumes, that doesn't appear to be a nasty issue after all. Is there another issue I've failed to address in this thread?-Kevin Ballard -- Kevin Ballard http://kevin.sb.org kevin@xxxxxx http://www.tildesoft.com
-- Kevin Ballard http://kevin.sb.org kevin@xxxxxx http://www.tildesoft.com
<<attachment: smime.p7s>>
