Hello, I read the README and the man pages and the User Guide. They only say to run ./tools/wineinstall but it can't be found anywhere on my system! I downloaded the package and used tar to extract it to my home directory (/root). I do not find "./tools" anywhere. Nothing in the documentation mentions the directory from which to install at all.
Do not run wine as root! Create regular user and then you can follow this example: o Optional: download compile and install latest fontforge from sourceforge.net o Download wine sources from http://ibiblio.org/pub/linux/system/emulators/wine/wine-0.9.57.tar.bz2 to some directory o Extract wine sources with Code: tar jxf wine-0.9.57.tar.bz2 o Enter the extracted sources directory: Code: cd wine-0.9.57 o Execute Code: ./configure --with-x && make depend && make o If everything went fine do a Code: make install as root, or run wine from the directory where you created it. o Optional: run Code: wineprefixcreate Hope that helps. Plamen P.S. Did I mentioned NOT to run wine as root?
ShellyCat wrote:> Hello, > > I read the README and the man pages and the User Guide. > > They only say to run ./tools/wineinstall but it can't be found anywhere on my system! > > I downloaded the package and used tar to extract it to my home directory (/root). I do not find "./tools" anywhere. Nothing in the documentation mentions the directory from which to install at all. > >Shelly: You are going to read this again and again but here goes. NEVER RUN WINE AS ROOT. You leave your system open to viruses (which is one reason to switch to Linux in the first place) and if something bad were to happen, your entire system may be damaged... James McKenzie
Dan Kegel wrote:> <jjmckenzie51 at sprintpcs.com> wrote: > > > You are going to read this again and again but here goes. > > > > NEVER RUN WINE AS ROOT. You leave your system open to viruses (which is > > one reason to switch to Linux in the first place) and if something bad > > were to happen, your entire system may be damaged... > > > > We're saying this so many times a day ... time to automate the > warning. I'll send a patch.I am sorry to resurrect a dead thread, but just out of curiosity, Dan, what you think is the preferred behaviour when wine gets started by root? Should wine just print warning and then run, or probably it should die unless there is a special option on the command line like --yeah-I-know-I-am-root or --allow-root or something like that. Most users are running their applications via desktop/menu shortcuts so they won't see the warning (that's if they are running their graphic environment as root too). Maybe it should print a warning, then die. The warning should inform the user about the risks involved in running wine as root, and if they absolutely need to run wine as root then they should consult the documentation (where this option will be mentioned). If the warning itself contains option then it's almost guaranteed that the user will just set it and run wine again. On the other hand this is too restrictive... What do you think? regards Plamen
Ah yes, I see that a discussion is already on. Thank you Austin ;)
OK, I had an error message when I ran "wineprefixcreate" (as a regular user). I did a search and found only 1 post, and tried to do what it said. I will cut there and paste here in just a sec. Original post:>The new problem is, when I tried to run "sh winetricks gecko" I got this error: Code: Executing cabextract /home/myuser/.winetrickscache/wine_gecko-0.1.0.cab winetricks: line 234: cabextract: command not found Note: command 'cabextract /home/myuser/.winetrickscache/wine_gecko-0.1.0.cab' returned status 127. Aborting. So, I still wonder...will I not be able to view HTML in any applications I run in Wine? Why does it insist on Mozilla?
Plamen.Vassilev wrote:> > o Optional: download compile and install latest fontforge from sourceforge.net > o Download wine sources from http://ibiblio.org/pub/linux/system/emulators/wine/wine-0.9.57.tar.bz2 to some directory > o Extract wine sources with...I should not have been so impatient, and asked the purpose of fontforge...OK, its because Wine installs Windows fonts, and you need "fontforge" to do so, correct? After starting "wine winefile" and seeing that the interface defaulted to some horrible fantasy-type text on me (though I could change the font used for file-browsing), I went back and installed fontforge. I verified the install by running "fontforge", which bought up the font-browsing GUI window. Question: The fantasy font is still used in the "winefile" file browser...do I need to re-configure wine? Uninstall wine and compile and install all over again?[/b]