How do we plan to get rid of having default config files? Where would the default registry go?
Chris
From: Alexandre Julliard julliard@winehq.org Date: 2004/01/05 Mon PM 03:19:54 EST To: Chris Morgan cmorgan@alum.wpi.edu CC: wine-devel@winehq.com Subject: Re: install default config files to $PREFIX/share/wine
Chris Morgan cmorgan@alum.wpi.edu writes:
- configure.ac, Makefile.in, documentation/Makefile.in, documentation/samples/
Makefile.in Chris Morgan cmorgan@alum.wpi.edu Install default wine configuration files to $PREFIX/share/wine for use by packages and by future changes to create a default configuration if none is present.
I don't think we want that. Future changes are supposed to get rid of the need for a config file, so we don't want to give the impression that external apps can depend on finding a sample config file.
-- Alexandre Julliard julliard@winehq.com
chmorgan@charter.net writes:
How do we plan to get rid of having default config files? Where would the default registry go?
It will be created on the fly by registering the various dlls and creating the remaining needed keys, most likely through a setupapi .inf script.
On Mon, Jan 05, 2004 at 01:46:59PM -0800, Alexandre Julliard wrote:
chmorgan@charter.net writes:
How do we plan to get rid of having default config files? Where would the default registry go?
It will be created on the fly by registering the various dlls and creating the remaining needed keys, most likely through a setupapi .inf script.
But how will we get rid of the drive config?
Ciao, Marcus
Marcus Meissner marcus@jet.franken.de writes:
But how will we get rid of the drive config?
We will need a tool (maybe wineboot) to setup the initial drive config according to the machine setup. A default config file is not going to help with that anyway.
On January 5, 2004 05:27 pm, Alexandre Julliard wrote:
We will need a tool (maybe wineboot) to setup the initial drive config according to the machine setup. A default config file is not going to help with that anyway.
I'd say we just have a C: drive pointing to / (root). This setup is definitely the most user friendly, and the one most in the spirit of Unix (one large tree). A user of a Unix system will be most confortable with it, and it will create the least unexpected behavior.
Thinking about this, I'm not even sure why we encourage people to define drives (by having a nice UI in winecfg)... What's wrong with only a C: drive by default? Power users have regedit :)
On Tue, Jan 06, 2004 at 09:44:05AM -0500, Dimitrie O. Paun wrote:
On January 5, 2004 05:27 pm, Alexandre Julliard wrote:
We will need a tool (maybe wineboot) to setup the initial drive config according to the machine setup. A default config file is not going to help with that anyway.
I'd say we just have a C: drive pointing to / (root). This setup is definitely the most user friendly, and the one most in the spirit of Unix (one large tree). A user of a Unix system will be most confortable with it, and it will create the least unexpected behavior.
Thinking about this, I'm not even sure why we encourage people to define drives (by having a nice UI in winecfg)... What's wrong with only a C: drive by default? Power users have regedit :)
Well, no.
Where do you want to have windows/ and windows/system/ directory? In / of the UNIX filesystem, world writeable? :)
For SuSE, I have: A: /media/floppy/
C: %HOME/.wine/fake_windows/ ...some cd drives...
X: /tmp/ Y: %HOME% Z: /
But this is case for endless discussion I guess.
We could just make "C:" redefineable and leave the rest as default for instance.
Ciao, Marcus
Marcus Meissner wrote:
[snip]
Where do you want to have windows/ and windows/system/ directory? In / of the UNIX filesystem, world writeable? :)
For SuSE, I have: A: /media/floppy/
C: %HOME/.wine/fake_windows/ ...some cd drives...
X: /tmp/ Y: %HOME% Z: /
[snip]
What are the common attack vectors of viruses and trojans and what can I do to prevent them?
regards, Jakob
Le mar 06/01/2004 à 09:44, Dimitrie O. Paun a écrit :
On January 5, 2004 05:27 pm, Alexandre Julliard wrote:
We will need a tool (maybe wineboot) to setup the initial drive config according to the machine setup. A default config file is not going to help with that anyway.
I'd say we just have a C: drive pointing to / (root). This setup is definitely the most user friendly, and the one most in the spirit of Unix (one large tree). A user of a Unix system will be most confortable with it, and it will create the least unexpected behavior.
Thinking about this, I'm not even sure why we encourage people to define drives (by having a nice UI in winecfg)... What's wrong with only a C: drive by default? Power users have regedit :)
Are you thinking that all installers (CD-based) are able to cope with the data not at the root of a drive? What about those which just know that C:\Windows or C:\Program Files are always present and valid?
My small experience (mostly second-hand, I must say) is that's not always the case.
Vincent
--- Alexandre Julliard julliard@winehq.org wrote:
It will be created on the fly by registering the various dlls and creating the remaining needed keys, most likely through a setupapi .inf script.
We have already added a bunch of stuff from winedefault.reg to a inf script in ReactOS. If you wanted to try and test adding support to WINE for this here is the script:
http://cvs.reactos.com/cvsweb.cgi/reactos/bootdata/hivesft.inf?rev=1.17&...
Thanks Steven
__________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus
-
Alexandre Julliard -
chmorgan＠charter.net -
Dimitrie O. Paun -
Jakob Eriksson -
Marcus Meissner -
Steven Edwards -
Vincent Béron