[linuxdc-dev] VMU filesystem question

[Adrian M. <ad...@mc...>]

I have a thorny problem with vmufs design.....

The vmu directory is designed to save games files from a dreamcast and 
contains game specific information (eg header offsets). This means nothing to 
Linux.

Thus if one executed the command...

cp old_vmu/OLD_FILE new_vmu/NEW_FILE the copy would not be perfect - the data 
in the file itself would be copied and a basic directory entry created, but 
not all the directory information would be copied over fully.

There seem to be two ways to solve this:

(a) Ban all interaction between vmufs and any other filesystem (ie assume that 
all an any file is a vmufs file)

(b) Ignore the problem because it is probably not too serious in any case


(a) seems overly restrictive and I doubt whether it is practible in any case. 
I won't know about (b) until I've actually done an implementation and tested 
it.

Have I missed anything? Any thoughts?

Adrian

PS Today is my birthday... all together now....