Re: Some considerations about the Wine FUSE project for GSoC
On Monday 31 March 2008 16:08:00 Kai Blin wrote: On Monday 31 March 2008 15:30:17 Marc Andre Tanner wrote: First, I haven't yet applied for the project mainly because i will probably not be able to work full time on a GSoC project due to real life issues (part time job, family related things etc). On the other hand I doubt that it will require ~3 months to implement, I have done my prototype over more or less a weekend. That's why there's more than one FUSE file systems on the list ;) I miss the technical discussion on how the problem should be solved. I think the idea of keeping the original filename in an extended attribute and storing everything in lower case is a pretty good one. Andrew Tridgell also listed it on one of his slides from WineConf05 [1]. The tricky part is convincing Alexandre Julliard, as always when working on Wine. I prototyped something and thought this way I would at least get some feedback (after all Talk is cheap. Show me the code. is common practice in the open source world). But this wasn't really the case, so i am still wondering what should be done differently? Whoops, I didn't see that url. Sorry, but things were a bit busy recently. I'll give that a whirl later today. I'm seeing some funny behaviour in a directory containing the files foo.txt, Foo.txt and bAr.tXt After mounting, I can only see a foo.txt in the directory, containing the Foo.txt contents. Cheers, Kai -- Kai Blin WorldForge developer http://www.worldforge.org/ Wine developerhttp://wiki.winehq.org/KaiBlin Samba team member http://www.samba.org/samba/team/ -- Will code for cotton. signature.asc Description: This is a digitally signed message part.
Re: Some considerations about the Wine FUSE project for GSoC
Kai Blin wrote: On Monday 31 March 2008 16:08:00 Kai Blin wrote: On Monday 31 March 2008 15:30:17 Marc Andre Tanner wrote: I prototyped something and thought this way I would at least get some feedback (after all Talk is cheap. Show me the code. is common practice in the open source world). But this wasn't really the case, so i am still wondering what should be done differently? Whoops, I didn't see that url. Sorry, but things were a bit busy recently. I'll give that a whirl later today. Thanks for testing btw. I'm seeing some funny behaviour in a directory containing the files foo.txt, Foo.txt and bAr.tXt After mounting, I can only see a foo.txt in the directory, That's intended, filenames which aren't all lower case are ignored. This makes sure that there won't be conflicts. Ideally you should start with an empty directory mount the fs and then untar your actual content in mountpoint. containing the Foo.txt contents. This would be a bug, are you really sure you are getting the contents of Foo.txt and not foo.txt? I ask because i can't reproduce it here. If so could you please compile in debug support make debug and then run ciopfs with option -d. This should print some debug information to stderr. Thanks, Marc -- Marc Andre Tanner http://www.brain-dump.org/ GPG key: CF7D56C0
Re: Some considerations about the Wine FUSE project for GSoC
On Wednesday 02 April 2008 17:18:27 Marc Andre Tanner wrote: containing the Foo.txt contents. This would be a bug, are you really sure you are getting the contents of Foo.txt and not foo.txt? My bad, I must have misread. It's the contents of the lower case file. Cheers, Kai -- Kai Blin WorldForge developer http://www.worldforge.org/ Wine developerhttp://wiki.winehq.org/KaiBlin Samba team member http://www.samba.org/samba/team/ -- Will code for cotton. signature.asc Description: This is a digitally signed message part.
Re: Some considerations about the Wine FUSE project for GSoC
Kai Blin wrote: Hi folks, after another chat about Wine's goals in respect to FUSE file systems on IRC, I just wanted to point the students who applied for this project already (I've Bcced them) at the goals Wine has for this GSoC project. For Wine, the goal is to create prototype FUSE file systems so we can figure out if this approach is useful to Wine at all. There is no immediate goal to include the file systems into Wine in the near future, we first want to know if they're what we need. First, I haven't yet applied for the project mainly because i will probably not be able to work full time on a GSoC project due to real life issues (part time job, family related things etc). On the other hand I doubt that it will require ~3 months to implement, I have done my prototype over more or less a weekend. I miss the technical discussion on how the problem should be solved. I think the idea of keeping the original filename in an extended attribute and storing everything in lower case is a pretty good one. Andrew Tridgell also listed it on one of his slides from WineConf05 [1]. I prototyped something and thought this way I would at least get some feedback (after all Talk is cheap. Show me the code. is common practice in the open source world). But this wasn't really the case, so i am still wondering what should be done differently? Regards, Marc [1]http://us5.samba.org/samba/ftp/slides/tridge_wineconf05.pdf (page 18) -- Marc Andre Tanner http://www.brain-dump.org/ GPG key: CF7D56C0
Re: Some considerations about the Wine FUSE project for GSoC
On Monday 31 March 2008 15:30:17 Marc Andre Tanner wrote: First, I haven't yet applied for the project mainly because i will probably not be able to work full time on a GSoC project due to real life issues (part time job, family related things etc). On the other hand I doubt that it will require ~3 months to implement, I have done my prototype over more or less a weekend. That's why there's more than one FUSE file systems on the list ;) I miss the technical discussion on how the problem should be solved. I think the idea of keeping the original filename in an extended attribute and storing everything in lower case is a pretty good one. Andrew Tridgell also listed it on one of his slides from WineConf05 [1]. The tricky part is convincing Alexandre Julliard, as always when working on Wine. I prototyped something and thought this way I would at least get some feedback (after all Talk is cheap. Show me the code. is common practice in the open source world). But this wasn't really the case, so i am still wondering what should be done differently? Whoops, I didn't see that url. Sorry, but things were a bit busy recently. I'll give that a whirl later today. Cheers, Kai -- Kai Blin WorldForge developer http://www.worldforge.org/ Wine developerhttp://wiki.winehq.org/KaiBlin Samba team member http://www.samba.org/samba/team/ -- Will code for cotton. signature.asc Description: This is a digitally signed message part.
Re: Some considerations about the Wine FUSE project for GSoC
On Mon, Mar 31, 2008 at 04:08:00PM +0200, Kai Blin wrote: On Monday 31 March 2008 15:30:17 Marc Andre Tanner wrote: I prototyped something and thought this way I would at least get some feedback (after all Talk is cheap. Show me the code. is common practice in the open source world). But this wasn't really the case, so i am still wondering what should be done differently? Whoops, I didn't see that url. Sorry, but things were a bit busy recently. I'll give that a whirl later today. I just pushed some primarily unicode based case mapping code implemented with help of http://www.icu-project.org/ to the git repository. I am not yet sure whether the transformation works as i think it should, but at least it translates some german umlauts correctly. On Debian system the required package is called libicu-dev. Fetch the latest code from: git://repo.or.cz/ciopfs.git Regards, Marc -- Marc Andre Tanner http://www.brain-dump.org/ GPG key: CF7D56C0
