| |||||||||||||
That would appear to workThat would appear to workPosted Mar 3, 2009 16:56 UTC (Tue) by jamesh (guest, #1159)In reply to: That would appear to work by jmorris42 Parent article: Third time is the charm?
With Rock Ridge CDs, don't you have separate name spaces for the long and short names? That is, you either use the full file names or the legacy short names, but not both.
The patent talks of a "common name space", so RR might not apply.
(Log in to post comments)
That would appear to work Posted Mar 5, 2009 1:14 UTC (Thu) by JoeBuck (subscriber, #2330) [Link] With VFAT you also use either one or the other. Non-VFAT-aware systems see only the short names; VFAT-aware systems see the long names. It would appear that Rock Ridge works the same way.
That would appear to work Posted Mar 5, 2009 2:39 UTC (Thu) by jamesh (guest, #1159) [Link]
On Windows, both the long and short path names are available concurrently for VFAT. You can even mix the long and short names in a single path (e.g. "c:\Progra~1\Microsoft Office"). It really is exposed as a single name space for both types of file names.
That would appear to work Posted Mar 5, 2009 2:51 UTC (Thu) by jmorris42 (subscriber, #2203) [Link]
> It really is exposed as a single name space for both types of file names.
It is in the Windows implementation but there isn't a requirement that other implementations follow their example. I don't think the Linux vfat does, haven't used fat volumes much lately to really say. Matters not though since if doing that would work around the patent it wouldn't be a loss of usability for vfat under linux to only show/accept the long file names.
|
|||||||||||||