I’m having trouble installing WINE from the WineHQ website could someone help direct me trough the process.
No need
Open a terminal and do this
su -
zypper in wine
On 07/24/2011 06:06 PM, Firelord301 wrote:
>
> I’m having trouble installing WINE from the WineHQ website could someone
> help direct me trough the process.
>
>
remove everything you you downloaded, and everything you unpacked from
WineHQ, then use YaST…
-open YaST
-click on Software Management
-type wine in search box
-press “Search”
-find “wine” in right pane
-single left click on the box next to wine
-a green arrow will appear in that box and some others
-single click “Accept”
-YaST will (probably) find some other packages that must be installed
for wine to work (those are called “dependencies”)
-to approve the install of the dependencies, click “Continue”
-watch YaST work…patiently, it might take a minute or two…do NOT
touch the keyboard…just watch…do not get tired of watching and
press “Abort”…there is LOTs of stuff going on in the background! lots!!
-let YaST finish
-read the wine docs to learn how to use it (i do not know how)
–
DD
Caveat-Hardware-Software
openSUSE®, the “German Engineered Automobiles” of operating systems!
When installing from the site you must take in consideration that you are installing wine using the source code. Here is what you do:
- download the archive from the wine hq site
- open a console and login as root
- open the software management window from Yast, because is possible that some dependencies are not installed
- unzip the archive using the comand tar -xvf archive-name.bz2
- ./configure here the installer will tell you if you are missing any packages; run ./configure untill no more warnings appear(dev packages). At the end be aware to install the packages that wine complains it can create support for(again dev packages)
- after step 5 is completed run the command make this will compile wine; this is an long step because compiling can last on average 45 minutes so grab a beer, coffee or something
- after the compile process is done, use make install to install wine
8(keep it in mind). to uninstall wine simply run make uninstall from the same directory you build wine in the first place; a good ideea is to keep the wine directory after you install it.
I hope this solve your issue, but i recommend using Yast to install wine since it will take a couple of seconds or maximum a minute. Your decision 
On 07/24/2011 10:26 PM, creatura85 wrote:
>
> Firelord301;2367855 Wrote:
>> I’m having trouble installing WINE from the WineHQ website could someone
>> help direct me trough the process.
> When installing from the site you must take in consideration that you
> are installing wine using the source code. Here is what you do:
> 1. download the archive from the wine hq site
> 2. open a console and login as root
please! no…do not log in as root at this point in the process
> 3. open the software management window from Yast, because is possible
> that some dependencies are not installed
> 4. unzip the archive using the comand tar -xvf archive-name.bz2
do not unzip as root
> 5. ./configure here the installer will tell you if you are missing
> any packages; run ./configure untill no more warnings appear. At the end
> be aware to install the packages that wine complains it can create
> support for
do not run configure as root
> 6. after step 5 is completed run the command make this will compile
> wine; this is an long step because compiling can last on average 45
> minutes so grab a beer, coffee or something 
do not run make as root
> 7. after the compile process is done, use make install to install
> wine
NOW, become root by using “su -”
> 8(keep it in mind). to uninstall wine simply run make uninstall
>
> I hope this solve your issue, but i recommend using Yast to install
> wine since it will take a couple of seconds or maximum a minute. Your
> decision 
agree…YaST is so much more simple
–
DD Caveat
openSUSE®, the “German Engineered Automobiles” of operating systems!
doing all that AS ROOT !!!
no wonder people ARE GETTING ROOTKITS installed !!!
NEVER EVER extract a archive as root
NEVER EVER run ./configure as root
NEVER EVER run make as root
if you are going to do that then REMOVE ALL installs of linux and run Windows AS ADMINISTRATOR and go get a virus !!!
i have NO sympathy for idiots that run everything as root !!!
DenverD: And why not ./configure and make as root? This is paranoia you know. Yes i agree never login as root at the login prompt, but running a compilation as root from time to time is not a crime(i know people that login as root to do a task and logout after they get it done, same thing with wine in the console). Is like saying that the firewall is useless when is not.
JohnVV: chill and relax, the world will not end today.
On 07/25/2011 08:46 AM, creatura85 wrote:
>
> DenverD: And why not ./configure and make as root?
just to begin…read the instructions in most READMEs (packed within the
tar ball)…i say most, because i agree that (unfortunately) not all
are correctly written…
or, read some of the millions of hits here: http://tinyurl.com/3hm7oyf
> This is paranoia you know. Yes i agree never login as root at the login prompt, but
> running a compilation as root is not a crime.
we are not talking either crime nor paranoia…simply talking about
system security and the proven administrative practices which either
enhance it, or destroy it…
now, i freely admit i’ve never seen the potential ills of running either
configure or make as root…and, i don’t quite remember what any of
those ills might be…well, because i read the big three inch thick
admin book back in the '90s and followed it…and, therefore have not
seen first hand any of the problems said to occur…
so, i’ll leave those details to others here, or findable via google…
i’m not sure but i think one (or both)
http://tinyurl.com/ydbwssh
http://tinyurl.com/665h5ek
> Is like saying that the firewall is useless
who said that? (i’m behind two)
and, by the way: I wouldn’t be paranoid if ‘they’ would just stop
following me! – actually, it the world today it is a very thin line
between “paranoia” and “prudent security”…
if you don’t believe me, ask the cracked, pwn’ed, rooted and sad.
–
DD
Caveat-Hardware-Software
openSUSE®, the “German Engineered Automobiles” of operating systems!
DenverD:in the world today it is a very thin line between “paranoia” and “prudent security”
Yes the line is thin, but as i said i don`t think that running from time to time a compilation as root can lead to a hacked linux-box. You must admit that all comes down to the security of the linux-box, firewall and services settings.
“(i’m behind two)”
What a coincidence i`m behind two as well; one from openSUSE and the other from my router
“now, i freely admit i’ve never seen the potential ills of running either configure or make as root…and, i don’t quite remember what any of those ills might be…well, because i read the big three inch thick admin book back in the '90s and followed it…and, therefore have not seen first hand any of the problems said to occur…”
That sounds like a “holly bible for linux” . In most cases people get hacked due to weak passwords or incorrect adjusted services(with opened ports) and firewall settings i suppose. Would you agree with that ?
Now, i say lets stop the off-topic here and wait for an answer from the topic starter to help him if needed.
caf4926 wrote:
> No need
>
> Open a terminal and do this
>
> Code:
> --------------------
> su -
> zypper in wine
> --------------------
One step missed here and in DenverD’s YaST instructions is to first add
the correct repository. Choose from the list at:
<http://en.opensuse.org/Additional_package_repositories#Wine>
The reason is that Wine is updated quite frequently and the standard
repository is usually behind the times. The updates are normally for
functionality & compatibility rather than security.
On 07/25/2011 11:28 AM, Dave Howorth wrote:
> The updates are normally for
> functionality & compatibility rather than security.
so therefore they don’t get pushed though the update repo??
and, THANKs for the added info (since i don’t have wine installed–never
use it, how could i know)
–
DD Software
On 07/25/2011 10:46 AM, creatura85 wrote:
>
> In most cases people
> get hacked due to weak passwords or incorrect adjusted services(with
> opened ports) and firewall settings i suppose. Would you agree with that
> ?
sorry, i do not know the way most Linux boxes are compromised…but, i
would agree the machines of individuals, international organizations and
governments should have strong passwords, minimum services/ports and
sane firewalls as a beginning, and then a daily practice of security to
keep things secure (like running configure & make as user)…
> Now, i say lets stop the off-topic here and wait for an answer from the
> topic starter to help him if needed.
call it off topic as you wish, but i find it very on topic to correct
posts which give bad/incorrect advice…
–
DD
openSUSE®, the “German Engineered Automobiles” of operating systems!
Dear @creatura85,
I think you miss an important point in the discussion about using the root user when not stricktly needed. It is not about what you do with your system, being responsible most probably to yourself only. It is about propagating bad practises in a forum where all kind of people, many of them real newcomers, try to learn about Linux and good practises.
Thus many people on the forums here react immediatly when they see something that could encourage people unknowlingly doing things as root that they shouldn’t. People will get the feeling that doing things as root is quite normal and they will soon end up in not only using it for compiling Wine, but doing the weirdest things with it.
I hope you understand.
Maybe I missed it but there is of course the special wine repositor which
contains more recent versions of wine and receives regular updates.
Can be added with yast via the community repos.
–
PC: oS 11.4 64 bit | Intel Core i7-2600@3.40GHz | KDE 4.6.0 | GeForce GT 420
| 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.5 | nVidia
ION | 3GB Ram
On Mon, 25 Jul 2011 06:46:02 +0000, creatura85 wrote:
> And why not ./configure and make as root? This is paranoia you know. Yes
> i agree never login as root at the login prompt, but running a
> compilation as root is not a crime. Is like saying that the firewall is
> useless
Because a Makefile is basically a batch file that can be set up to do
anything. Unless you do a full analysis of each and every Makefile, you
won’t know what it’s doing.
One could argue the same with regards to the source code you’re building,
but every recommendation I’ve ever seen on compiling your own software is
that you should only run ‘make install’ as root.
I usually run that as a non-root user as well to see what it’s going to
do, and then if I’m satisfied about what it’s going to do (and where it’s
going to put files), I’ll run it as root.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Jim Henderson wrote:
> On Mon, 25 Jul 2011 06:46:02 +0000, creatura85 wrote:
>
>> And why not ./configure and make as root? This is paranoia you know. Yes
>> i agree never login as root at the login prompt, but running a
>> compilation as root is not a crime. Is like saying that the firewall is
>> useless
>
> Because a Makefile is basically a batch file that can be set up to do
> anything. Unless you do a full analysis of each and every Makefile, you
> won’t know what it’s doing.
>
> One could argue the same with regards to the source code you’re building,
> but every recommendation I’ve ever seen on compiling your own software is
> that you should only run ‘make install’ as root.
>
> I usually run that as a non-root user as well to see what it’s going to
> do, and then if I’m satisfied about what it’s going to do (and where it’s
> going to put files), I’ll run it as root.
Just to be more direct, I read what you write to mean that running as root
opens one up to self-inflected damage which is one of the best reasons for
NOT running as root unless required.
I have done far more damage to my systems due to fat finger mistakes or
poorly designed programs of my own than I have ever suffered from an
external attack - even pulling the network cable won’t protect you from
that!
–
WHonea
On Mon, 25 Jul 2011 17:51:15 +0000, Will Honea wrote:
> Just to be more direct, I read what you write to mean that running as
> root opens one up to self-inflected damage which is one of the best
> reasons for NOT running as root unless required.
That’s a very succinct way of putting it, yes.
My general rule of thumb when running systems is to use no more privilege
than absolutely necessary for the task at hand.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Exactly, but there are allways people that say they are faultless (until they prove themselves being wrong).
Dont worry i do; like any other user involved in this forum im here learn from other peoples experience and adjust it to my needs(when in doubt, trouble or just learning) and of course to leave something good behind that could help others that will come after me. It is not wrong to say that from mistakes we learn how to avoid them.
“People will get the feeling that doing things as root is quite normal and they will soon end up in not only using it for compiling Wine, but doing the weirdest things with it.”
That would be weird; i find it hard to belive but hey the world is big and has over 6 bilion ideas…
On Mon, 25 Jul 2011 18:16:02 +0000, hcvv wrote:
> Exactly, but there are allways people that say they are faultless (until
> they prove themselves being wrong).
Those people tend to be excellent at self-deception. 
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C