© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
(In reply to comment #42)
> I like the virtualized filesystem idea, but its probably not practical for wine
> itself to implement, moreso something for a separate project (winetricks?)
Thinking further about the virtualized filesystem idea, it should, in theory, be possible to virtualize the filesystem without needing a fuse driver, if the user were to setup a single file that were to hold the filesystem, sort of like a VHD or an ISO. I like the ISO idea better, but perhaps something that's not associated with a read-only media would be more appropriate.
That way it could be mounted with the loopback driver already in the kernel and reads/writes would just take place to the mount point. It would make managing things easier because the user could create an fstab-like file for wine to read (or just do it in winecfg) to specify the mount point and path to the file containing wine's filesystem -- That's the one thing I've always disliked about wine was having the filesystem default to being under my home directory.