Well, the best solution would be to forget about a default config file and force
people to configure wine correctly. If / mapping is so important for wine cfg
lets have it. But I do think the best solution would be to force people to
configure wine correctly, with winesetuptk that can't be consid
> My understanding is rather weak here, as well. I've been using a call
> to fopen("/etc/fstab",...) and it works fine. However, I'm unsure as to
> why this works: is it because winecfg is a winelib app so fopen is
> actually coming out of the normal glibc? or does wine pass the name
> thro
On Tue, 3 Jun 2003, Jeff Smith wrote:
: BTW, Todd, I hope when I posted the URL to the article puoti had
: mentioned, that you did not think the opinions expressed in that article
: were by any means my own. Perhaps I should have made a disclaimer. :-/
Heh, I didn't imply that at all. When I re
After further consideration, I have come to believe that we might as well have
the root mapping. Enough people seem to want it that, as Dimi say, we need
to deal with the possibility anyway. BTW, Todd, I hope when I posted the URL
to the article puoti had mentioned, that you did not think the opi
> This seems like a different issue. In fact, this will be solved if we also
> had a proper definition for the CDROM, wouldn't it?
Of course.
But if the user had a correct Wine configuration, he would not have had the
problem that made Mike add '/' as a drive path... And all this discussion
would
