From: Sam M. <pa...@gm...> - 2005-01-14 01:09:58
|
But there are options to work around this, for example Samba or NFS. If there is a fully working coLinux installation with networking, both Samba (for Windows and Linux) or NFS (mostly for Linux, but Windows clients and servers do exist, the Cygwin nfsd appears to be stable) are available to access partitions from either side of the gate, just requires a bit of setting up. On Fri, 14 Jan 2005 00:31:24 +0000, Nuno Lucas <li...@xp...> wrote: > Charles Duffy, dando pulos de alegria, escreveu : > > Until this issue is resolved, folks using coLinux to access raw partitions > > should probably avoid ext2fsd. > > Note that this issue will never be solved. > > The only way to fix it would be to make ext2fsd to coop with colinux and > that means patching both (meaning a special version of ext2fsd just for > use with colinux). > > All ext2fs windows programs out there assume they are the only ones > working with the image files/partitions. This leads to corruption of > the fs if used concurrently. > > This is also why the linux NTFS driver will never work with colinux (can > work, but with high corruption risk) and we need things like the > experimental cofuse module, which use the host OS API to "talk" to the > file system, avoiding so any corruption issues. > > Regards, > ~Nuno Lucas > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |