Re: DOSFS_FindUnixName and "unix" filesystem (was: Re: (HELP) ...)
Martin Wilck wrote:
In any case this is relatively minor and we can live without. If we don't patch, we need to be prepared that other people stumble into the problem I had, though. I am still feeling dumb - my wine development was practically stuck for 2 months because of that "wine" file.
Since I also was stumbled for a long period on a similar problem, due to specifying a "unix" filesystem, perhaps it would be appropriate in the documentation to put some large warnings on that option.
On Thu, Aug 29, 2002 at 09:37:13AM -0700, Duane Clark wrote:
Martin Wilck wrote:
In any case this is relatively minor and we can live without. If we don't patch, we need to be prepared that other people stumble into the problem I had, though. I am still feeling dumb - my wine development was practically stuck for 2 months because of that "wine" file.
Since I also was stumbled for a long period on a similar problem, due to specifying a "unix" filesystem, perhaps it would be appropriate in the documentation to put some large warnings on that option. Well, uh, where have you been recently ? ;-) That's exactly what we've been doing in several docu places for two years now. OK, it may not be specified in every relevant docu, but I'd say that at least 40% of all docs tell this story.
-- The Declaration of Software Freedom: http://freedevelopers.net/freedomdec/index.php
Andreas Mohr wrote:
On Thu, Aug 29, 2002 at 09:37:13AM -0700, Duane Clark wrote:
Martin Wilck wrote:
In any case this is relatively minor and we can live without. If we don't patch, we need to be prepared that other people stumble into the problem I had, though. I am still feeling dumb - my wine development was practically stuck for 2 months because of that "wine" file.
Since I also was stumbled for a long period on a similar problem, due to specifying a "unix" filesystem, perhaps it would be appropriate in the documentation to put some large warnings on that option.
Well, uh, where have you been recently ? ;-) That's exactly what we've been doing in several docu places for two years now. OK, it may not be specified in every relevant docu, but I'd say that at least 40% of all docs tell this story.
Obviously I should have actually looked at the docs before posting that. It is clearly spelled out in the important spots. Oh well, now that I think about it, it was more than two years ago that I had created the config file that had caused the problem for me.
Am Don, 2002-08-29 um 18.37 schrieb Duane Clark:
Since I also was stumbled for a long period on a similar problem, due to specifying a "unix" filesystem, perhaps it would be appropriate in the documentation to put some large warnings on that option.
Wait a bit - the usual suspect is not guilty here. My FS used to be "win95" all the time. I just reckoned "unix" might come as a friend here. For "win95", it is inherently clear that "wine" and "Wine" can't be distinguished. For "unix", that shouldn't be so. Thus I suggest improving "unix" and make it work nicely in cases where "win95" cannot possibly do the job, rather than deprecating it. Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck(a)Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy
participants (3)
-
Andreas Mohr -
Duane Clark -
Martin Wilck