Major FUD (was Re: Add root drive mapping to default config file)B

Jeff Smith whydoubt at yahoo.com
Tue Jun 3 14:24:29 CDT 2003


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 opinions
expressed in that article were by any means my own.  Perhaps I should have
made a disclaimer. :-/

As for using it in the wine config tool, I thought it was going to be a
winelib app, as opposed to pure win32.  With a winelib app, wouldn't you be
able to read the file in with *nix calls?  I haven't written any winelib apps
myself, so maybe I'll shut up now about that.

Finally, on the security (non) issue, a virus designed with wine in mind (that
phrase is fun to say) could get privileges to / if ${HOME} is already mapped.
Try this: 'notepad "F:\.wine\config"', where F is what ${HOME} is mapped to,
and then use your imagination.

 -- Jeff Smith


--- "Dimitrie O. Paun" <dimi at intelliware.ca> wrote:
> On Tue, 3 Jun 2003, Lionel Ulmer wrote:
> 
> > 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 not have been started at all :-)
> 
> Not quite. I, for one, (and I think I'm not in a minority) would like to
> have such a Z: drive in normal/correct/proper configuration. In which case 
> we have to deal with it being there anyway. And once we do, we might as well 
> have it present by default :)
> 
> -- 
> Dimi.


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com



More information about the wine-devel mailing list