On Thursday 05 June 2003 04:04 am, Mike Hearn wrote:
We have that, this is what MESSAGE is meant to do.
OK, cool, I guess routing that into a GUI should be on somebodies mental
if not marked up todo list.
just another note (hmm, by speaking on this, I fear I am getting dangerously
close to
On June 5, 2003 01:40 am, Gregory M. Turner wrote:
Really... I didn't know that. Then, should we slap a gui into this as
discussed previously?
Sure... We just need a volunteer to do it! :)
--
Dimi.
Mike Hearn writes:
Basically I think the Wine output should be hidden by default as it's
essentially meaningless to anybody but developers (and often, anybody
but wine developers).
PMFJI, I'm basically a Wine newbie as of 11/01/02 and a Linux newbie as of a
year before that, but it was
On 04 Jun 2003 19:57:57 +0200, you wrote:
(However, the latest generation of users seem to start their wine
experience by point-an-click on an .exe in some filemanager. They won't
see the messages sent to stderr.
Perhaps we should instead of error message blabla.exe not accessible
from
On Wednesday 04 June 2003 09:59 pm, Dimitrie O. Paun wrote:
On June 4, 2003 05:16 am, Mike Hearn wrote:
I would also propose a new class of logging message, or logging macro,
USERMSG, which is *only* to be used for things that directly help or
inform the user, as opposed to developers.
We
All this FUD is getting me hungry. bad pun
On Tue, 3 Jun 2003, PETREOLLE Sylvain wrote:
: please dont add / to the default config.
: - its insecure, since you can write everywhere you want
: and some filesystem corruption still exist today.
Bullshit. Wine can't corrupt your filesystem,
I am not voting for or against the / config because I
have not tested security and viruses but if the / is
so controversial why not get the /mnt a default config
since most users problems are with removable media.
Just a tought,
Hatky.
__
Do you Yahoo!?
Yahoo!
And this assumes that /mnt is where Arbitrary Unix
OS mounts removable
media. For one, I know mine doesn't. 8-)
I assume someone could get something more generic, I
was just rising an idea that more people could agree
on
Hatky.
__
Do you Yahoo!?
Yahoo!
Now, if someone would like to offer a *technically competent* argument as to
why mapping a drive letter to / is bad, I'd love to hear it.
Basically, adding '/' as a drive is to help people which are not able to
properly configure / install Wine (and who do not understand the 'Drive'
error
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
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
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
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
through to
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
On Tue, 3 Jun 2003, Lionel Ulmer wrote:
: Now, if someone would like to offer a *technically competent* argument as to
: why mapping a drive letter to / is bad, I'd love to hear it.
:
: Basically, adding '/' as a drive is to help people which are not able to
: properly configure / install Wine
I see mapping a drive to `/' as `proper' configuration. (i.e. If Wine is
meant to integrate apps to the Unix environment, it shold be able to see
the full Unix environment.)
Ah, there is where my opinion diverges the most from most of the people here
(and why I advocate a lot for the Desktop
On Tue, 3 Jun 2003, puoti wrote:
: 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
El mar, 03 de jun de 2003, a las 13:22, Todd Vierling escribio:
On Tue, 3 Jun 2003, Carlos Lozano wrote:
: Besides it shouldn't be possible enable ShowDotFiles when your home
: is mapped, because it could read your private ssh keys.
Now you're getting into serious FUD. If I install
El mar, 03 de jun de 2003, a las 13:22, Todd Vierling escribio:
On Tue, 3 Jun 2003, Carlos Lozano wrote:
: Even with read-only, i don't like the idea of window programs
: reading in /dev and /proc.
Why not? You can read //./PhysicalDrive0 in Windows. And winelib
programs that choose to
You're not the only one.
I didnt write it explicitely on my mails,
but this is what make me react on this subject.
Ah, there is where my opinion diverges the most from most of the
people here
(and why I advocate a lot for the Desktop option).
I do *NOT* want to have my Windows and my Linux
I agree with Lionel, wine should ideally have a explorer reimplementation, so
one would have a wine desktop that looked like a hardware emulator, but with the
speed of wine, and I think that a Correct wine configuration should look like
this (If one has a temp directory in fake windows, why use
I agree with Lionel too.
Couldnt winefile used in this way ?
-Message d'origine-
De : puoti [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 4 juin 2003 00:00
À : wine-devel
Objet : Re: Major FUD (was Re: Add root drive mapping to default config
file)
I agree with Lionel, wine should ideally
On Tue, 3 Jun 2003 22:57:52 +0200, you wrote:
I see mapping a drive to `/' as `proper' configuration. (i.e. If Wine is
meant to integrate apps to the Unix environment, it shold be able to see
the full Unix environment.)
Ah, there is where my opinion diverges the most from most of the
On June 4, 2003 05:16 am, Mike Hearn wrote:
I would also propose a new class of logging message, or logging macro,
USERMSG, which is *only* to be used for things that directly help or
inform the user, as opposed to developers.
We have that, this is what MESSAGE is meant to do.
--
Dimi.
24 matches
Mail list logo
