https://wiki.archlinux.org/api.php?action=feedcontributions&user=Prune&feedformat=atomArchWiki - User contributions [en]2024-03-28T15:17:25ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Active_Directory_integration&diff=41774Active Directory integration2008-05-23T09:06:19Z<p>Prune: Spelling</p>
<hr />
<div>[[Category:Networking (English)]]<br />
[[Category:HOWTOs (English)]]<br />
= HowTo Arch Linux as Active Directory Member =<br />
<br />
This guide explains how to include Archlinux into an existing Windows Active Directory.<br />
<br />
== WARNING ==<br />
<br />
Although I have tested this HowTo many times, there may still be bugs. This procedure worked this week, who knows if it will do tomorrow. Any update in glibc, samba, heimdal could break this HowTo in pieces.<br />
<br />
Having Backups of all modified files is recommended, as well as testing login before any rebooting. In the worst case, login will be broken for all users, including root - so be warned: Don't reboot or logout as root until you checked everything.<br />
<br />
DO NOT RELY UPON ANY INFORMATION FOUND IN THIS HOWTO WITHOUT INDEPENDENT VERIFICATION. USE AT OWN RISK.<br />
<br />
=== General ===<br />
<br />
* What you get:<br />
** Windows AD users & archlinux users are accepted archlinux box users, at the console or gdm<br />
** Windows AD users can use Samba shares like Windows Shares.<br />
<br />
* What you won't get<br />
** Windows users are simply users on your machine. Possibly you can have Windows AD Admins to be linux admins, too. But this is not worked out so far in this HowTo.<br />
** Several other apps use authentication - like sudo, f.e. As far as they use PAM, it should be able to let them check against AD user accounts, too. But this is not worked out so far.<br />
<br />
=== Requirements ===<br />
<br />
*Have a Windows Active Directory (AD)<br />
*Be a Windows Admin.<br />
*Be root.<br />
*Be able to work with linux without X.<br />
*Be able to edit files.<br />
*Note: There is NO need to taint the AD with linux schemes.<br />
<br />
== Preparation of the Windows AD Policy ==<br />
<br />
It is necessary to disable "Digital Sign Communication (Always)" in the AD group policies. Dive into<p><br />
'Local policies'<br><br />
'Security policies'<br><br />
'Microsoft Network Server'<br><br />
'Digital sign communication (Always)'<br><br />
and<br />
* activate "define this policy" and<br />
* use the "disable" radio button</p><br />
<br />
This is all you have to do in Windows. Let's go on with Archlinux.<br />
<br />
= Installation =<br />
<p>These packages are needed on the Archlinux machine:<br><br />
* Samba <br />
* Heimdal<br />
* NTP<br />
* pam_krb5.so<br />
</p><br />
Most of the packages can be installed by using pacman:<br />
<pre>pacman -Sy samba ntp heimdal</pre><br />
<br />
To install pam_krb5.so, you have to download pam_krb5-1.60.1-css1_linux.tar.Z for RedHat / Linux from http://www.css-security.com/. Untar it, move into the extracted folder and run:<br />
<pre>./install.sh</pre><br />
Now, pam_krb5.so is installed into /lib/security/cssi/, with a symlink into /lib/security.<br />
<br />
'''Note: There is now a pam_krb5 in AUR'''<br />
<br />
= Configuration =<br />
Please check your /etc/hosts file! It is important for it to be correctly configured. If you have a dual boot system on a machine, you have to use a different hostname and netbios name for the linux configuration, or the protected connection between windows and the domain controller will result broken.<br />
<br />
In our example:<br><br />
127.0.0.1 MACHINE-NAME.PARADISE.COM MACHINE-NAME<br><br />
192.168.0.1 ADAM.PARADISE.COM ADAM<br><br />
192.168.0.2 EVE.PARADISE.COM EVE<br><br />
<br />
=== Samba / Winbindd Startup===<br />
<br />
Arch Linux implements samba and winbind as a single script in /etc/rc.d/samba<br />
<br />
The daemons started by /etc/rc.d/samba are configured in the file /etc/conf.d/samba.<br />
<br />
<pre><br />
##### /etc/conf.d/samba #####<br />
SAMBA_DAEMONS=(smbd nmbd winbindd)<br />
</pre><br />
<br />
=== Heimdal / Kerberos - /etc/krb5.conf ===<br />
<p> Let's assume that your AD is named paradise.com. Let's further assume your AD is ruled by two domain controllers, the primary and secondary one, which are named adam and eve, adam.paradise.com and eve.paradise.com respectively. Their IP adresses will be 192.168.0.1 and 192.168.0.2 in this example.</p><br />
<pre><br />
##### /etc/krb5.conf ####<br />
[libdefaults]<br />
default_realm = PARADISE.COM<br />
clockskew = 300<br />
ticket_lifetime = 1d<br />
<br />
[realms]<br />
PARADISE.COM = {<br />
kdc = 192.168.0.1<br />
kdc = 192.168.0.2<br />
default_domain = PARADISE.COM<br />
}<br />
<br />
<br />
[domain_realm]<br />
.paradise.com = PARADISE.COM<br />
paradise.com = PARADISE.COM<br />
paradise = PARADISE.COM<br />
<br />
[appdefaults]<br />
pam = {<br />
ticket_lifetime = 1d<br />
renew_lifetime = 1d<br />
forwardable = true<br />
proxiable = false<br />
retain_after_close = false<br />
minimum_uid = 0<br />
debug = false<br />
}<br />
<br />
[logging]<br />
default = SYSLOG:NOTICE:DAEMON<br />
kdc = FILE:/var/log/kdc.log <br />
</pre><br />
<br />
Inside an AD, it is important that all machines run the same system time. To synchronize the time run:<br />
<pre><br />
/usr/bin/ntpdate adam.paradise.com<br />
</pre><br />
<br />
Now you can query the AD domain controllers for a ticket with the following commands (uppercase is necessary):<br />
<pre># kinit ADMINISTRATOR@PARADISE.COM</pre><br />
<br />
<p>You´ll now be asked for the password. In case it matches, you'll be returned to the console.</p><br />
<br />
=== PAM Configuration for Login ===<br />
<p>Now we have to change /etc/pam.d/login so it sends its request to the AD controllers. In case of logins, PAM should first ask for AD accounts, and for local accounts if no matching AD account was found. Therefore, we add entries to include pam_winbindd.so into the authentication process. Furthermore, we include pam_mkhomedir.so. If an AD user logs in, /home/paradise/user will be created automatically.</p><br />
<pre><br />
#### /etc/pam.d/login ####<br />
#%PAM-1.0<br />
auth sufficient pam_unix2.so<br />
auth required pam_winbind.so use_first_pass use_authtok<br />
auth required pam_securetty.so<br />
auth required pam_nologin.so<br />
auth required pam_mail.so<br />
account sufficient pam_unix2.so<br />
account sufficient pam_winbind.so use_first_pass use_authtok<br />
password required pam_pwcheck.so<br />
password sufficient pam_unix2.so<br />
password sufficient pam_winbind.so use_first_pass use_authtok<br />
session required pam_mkhomedir.so skel=/etc/skel/ umask=0022<br />
session sufficient pam_unix2.so<br />
session sufficient pam_winbind.so use_first_pass use_authtok<br />
session required pam_limits.so<br />
</pre><br />
<p>If you like to allow AD users to login into GDM, you have to do the same for /etc/pam.d/gdm. You may try to change other /etc/pam.d/ rules for other apps, to allow them to authenticate AD users.</p><br />
<br />
=== Samba Configuration for Shares===<br />
<p> Samba is highly configurable. Take this example only as a rough idea, hardly polished. Here is what my /etc/samba/smb.conf looks like:</p><br />
<pre><br />
#### /etc/samba/smb.conf ####<br />
[Global]<br />
netbios name = archlinux<br />
workgroup = PARADISE<br />
realm = PARADISE.COM<br />
server string = archlinux<br />
map to guest = Bad User<br />
idmap uid = 10000-20000<br />
idmap gid = 10000-20000<br />
winbind enum users = yes<br />
winbind enum groups = yes<br />
winbind gid = 10000-20000<br />
winbind use default domain = Yes<br />
winbind separator =+<br />
os level = 20<br />
<br />
# Theres no shell defined for users in AD, so I define a default shell to use<br />
# Not sure if its even possible to define a shell in AD<br />
template shell = /bin/bash<br />
<br />
encrypt passwords = yes<br />
security = ads<br />
password server = adam.paradise.com<br />
preferred master = no<br />
dns proxy = no<br />
wins server = eve.paradise.com<br />
wins proxy = no<br />
<br />
admin users = @"NET+domain admins"<br />
force group = "PARADISE+domain admins"<br />
inherit acls = Yes<br />
map acl inherit = Yes<br />
acl group control = yes<br />
<br />
load printers = no<br />
debug level = 3<br />
use sendfile = no<br />
<br />
[homes]<br />
comment = User´s homedirs<br />
path =/home/%U<br />
valid users = %S NET+%S<br />
browseable = no<br />
read only = no<br />
<br />
[data] <br />
comment = Data<br />
valid users = %S net+%S<br />
path = /data<br />
read only = no<br />
browseable = yes<br />
<br />
[Back-up]<br />
comment = Backup filer<br />
path = /backup<br />
read only = no<br />
browseable = yes<br />
valid users = @"NET+Domain Admins"<br />
</pre><br />
<br />
We shall now explain to Samba that it shall use the PDC´s database for authentication queries. Again, we use winbindd which is a part of the samba package. Winbind maps the UID and GID of the AD to our Linux-machine. Winbind uses a Unix-implementation of RPC-calls, Pluggable Authentication Modules (aka PAM) and Name Service Switch (NSS) to allow Windows AD and users accessing and to grant permissions on the Linux-machine. The best part of winbindd is, that you don´t have to define the mapping yourself, but only define a range of UID and GID. That´s what we defined in smb.conf.<br />
To include Winbindd into NSS calls, edit /etc/nsswitch.conf. Add winbind to the lines as shown here:<br />
<pre><br />
#### /etc/nsswitch.conf ####<br />
passwd: files winbind<br />
shadow: files winbind<br />
group: files winbind<br />
</pre><br />
<br />
= Starting and testing services =<br />
<br />
=== Starting Samba ===<br />
<br />
Hopefully, you have not rebooted yet! Fine. If you are in an X-session, quit it, so you can test login into another console, while you are still logged in.<br />
<br />
Start Samba (including smbd, nmbd and winbindd:<br />
<pre><br />
/etc/rc.d/samba restart<br />
</pre><br />
<br />
=== Testing Winbind ===<br />
Let's check if winbind is able to query the AD. The following command should return a list of AD users:<br />
<br />
<pre><br />
wbinfo -u<br />
</pre><br />
<br />
We can do the same for AD groups:<br />
<br />
<pre><br />
wbinfo -g<br />
</pre><br />
<br />
=== Testing Login ===<br />
Now, start a new console session and try to login with an AD account. As we told winbind to use default_realms, it should not be necessary to add the AD name.<br />
Lets assume there is an AD user named kain. Try to login as<br />
<br />
<pre><br />
kain<br />
PARADISE+kain<br />
</pre><br />
<br />
Both should work. You should notice that /home/paradise/kain will be created.<br />
'''Log into another session using an linux account. Check that you still be able to log in as root - but keep in mind to be logged in as root in at least one session!''' <br />
<br />
=== Testing Samba Commands ===<br />
<br />
Try out some net commands to see if samba can address the AD:<br />
<br />
<pre><br />
net ads info<br />
net ads lookup<br />
net ads status<br />
</pre><br />
<br />
The commands return several AD related information.<br />
<br />
= Archlinux becomes an AD member =<br />
<br />
You need an AD Administrator account to do this. Let's assume this is named Administrator. The command is 'net ads join'<br />
<pre><br />
# net ads join -U Administrator<br />
Administrator's password: xxx<br />
Using short domain name -- PARADISE<br />
Joined 'MACHINE-NAME' to realm 'PARADISE.COM'<br />
</pre><br />
<br />
= When to Reboot? =<br />
<br />
Everything checked? OK. Pray and reboot.<br />
<br />
= More INFO:<br> =<br />
<br />
[http://us3.samba.org/samba/ Everything there is to know about Samba]<br />
<br />
Please feel free to comment this article - but if your edit this - PLEASE LET ME KNOW</div>Prunehttps://wiki.archlinux.org/index.php?title=World_of_Warcraft&diff=39513World of Warcraft2008-04-03T22:21:14Z<p>Prune: Fixed spelling errors</p>
<hr />
<div>[[Category:Games and entertainment (English)]]<br />
[[Category:Wine (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|World of Warcraft}}<br />
{{i18n_links_end}}<br />
<br />
World of Warcraft (WoW) is a Massively Multiplayer Online Role-Playing Game (MMORPG) by Blizzard Entertainment taking place in the fictional world of Azeroth, the world that previous Blizzard titles in the Realtime Stategy (RTS) Warcraft series. For more information about the game itself, visit [http://www.worldofwarcraft.com/ the Official World of Warcraft website].<br />
<br />
This article will describe how install and run in on Arch Linux using [http://winehq.org/ Wine].<br />
<br />
Some of this information was provided by http://www.wowwiki.com/Linux/Wine which is the best general source of information on WoW on Wine.<br />
<br />
==Introduction==<br />
As Blizzard so kindly created World of Warcraft with OpenGL support, we don't need [http://www.transgaming.com/products_linux.php Transgaming's Cedega], which is a non-free version of Wine with better DirectX support. Wine has as good, or better, OpenGL support than Cedega, and doesn't cost you a penny. <br />
<br />
Running WoW is slightly more difficult than some other games with Wine, but still relatively easy. It's quite possible that you will need to patch Wine to work with WoW, however, even this process is rather simple with Arch. The following guide will explain it all, step by step.<br />
<br />
If you do choose to purchase Cedega, which runs some games that Wine does not, for example, Guild Wars, the process is almost identical. I use Cedega myself because Wine currently doesn't cope with my Wireless USB keyboard well.<br />
<br />
==Installing Wine==<br />
<br />
Wine now no longer requires it's own special "World of Warcraft" version. The one in the repositories works fine (currently 0.9.38.1). Install both wine and unzip, which you will need later.<br />
<br />
pacman -S unzip wine<br />
<br />
==Installing Cedega==<br />
<br />
Cedega 6.01 is available in the AUR. To get the cedega program you will need to subscribe to Transgaming ; this currently costs about £3 per month. <br />
<br />
You also need dbus-python, which isn't a dependency of Cedega.<br />
<br />
pacman -S dbus-python<br />
<br />
==Installing the Game==<br />
There are four options for installing World of Warcraft. <br />
<br />
===Copying the CDs to a folder===<br />
<br />
My preferred method is to copy the 5 install CDs to a folder. This seems to solve problems with deciding whether a CD is mounted and needs changing or not ; I think this is a fundamental problem because Windows doesn't have the basic concept of mounting and unmounting drives.<br />
<br />
mkdir /mnt/temp<br />
cd /mnt/temp<br />
<br />
mount /mnt/cdrom<br />
cp -R /mnt/cdrom/* /mnt/temp<br />
umount /mnt/cdrom<br />
(repeat above for each of the 5 CDs)<br />
<br />
Then run the World of Warcraft Installer with :<br />
<br />
wine Installer.exe<br />
<br />
===Copying an Existing Installation===<br />
<br />
The second is to simply copy an exisiting WoW installation from a Windows drive to Linux. <br />
<br />
'''NOTE:''' If you do not alreay have Wine installed, or have not run World of Warcraft with Wine before, you should skip down to [[#Installing Wine]], then come back to this section. ''Please DO NOT SKIP this section unless you are absolutely sure you know what you are doing.''<br />
<br />
Copy the C:\Program Files\World of Warcraft directory from Windows to ~/.wine/drive_c/Program Files/World of Warcraft.<br />
<br />
Example (assuming your windows partition is mounted at <tt>/mnt/windows</tt> and you are in your home directory) (Quotes are needed because of the spaces in the file names):<br />
<br />
cp -R "/mnt/windows/Program Files/World of Warcraft" ".wine/drive_c/Program Files/World of Warcraft"<br />
<br />
This will ensure that Wine knows about your WoW and will be able to configure it properly, and also ensures that WoW won't notice it has even been moved at all.<br />
<br />
Now that you have WoW installed, skip down to [[#Post-Installation]].<br />
<br />
===New Installation from CD===<br />
'''NOTE:''' We will assume that your Wine CD-ROM drive is "D:\" for this guide. Please use the correct letter as set up in the [[#Installing Wine]] section.<br />
<br />
Insert the first CD, mount it, and start the installation with:<br />
<br />
wine "D:\Installer.exe"<br />
<br />
When it asks for the next cd, simply unmount your CD drive and mount the next CD. Make absolutely sure that you mount the CD before telling the installer to load the CD, or it may make the installation fail. If you have any issues installing using the CDs, please read the next section.<br />
<br />
The WoW installation uses all 5 CDs, so it will take a while. Go outside and get some fresh air while the CD loads, because soon you won't have any "free time". :P<br />
<br />
===New Installation from DVD===<br />
'''NOTE:''' Note that on some WoW DVD's the installer executable is hidden and you need to mount the disc with the 'unhide' option. To do this type in a terminal:<br />
mount -t iso9660 -o ro,unhide /dev/cdrom /media/cdrom/<br />
<br />
Insert first the DVD. If it will be mounted automatically - just unmount.<br />
<br />
# umount /media/dvd<br />
<br />
Now mount manually<br />
<br />
# mount -t iso9660 /dev/dvd0 /mnt/dvd<br />
<br />
Now you will find the Install.exe on the DVD<br />
<br />
~ wine /mnt/dvd/Installer.exe<br />
<br />
==Installing Patches==<br />
Now we will need to update WoW. As of today (1st July 2007), the latest version of WoW is 2.1.2.6803 . This will change over time, of course. The best place I have found to access the latest patches is http://www.wowwiki.com/Patch_mirrors<br />
<br />
I think the simplest way of updating World of Warcraft is to download the patches (links are at the Patch Wiki) and copy them into the working directory for World of Warcraft. I have had problems with the Blizzard Downloaders either not working at all, or working very slowly. If you download them, you can reuse them if you reinstall or have an accident.<br />
<br />
The current patches which are needed for 2.1.2.6803 are listed below <br />
<br />
WoW-1.12.0-enGB-patch.exe<br />
wow-1.12.x-to-2.0.1-engb-patch-3.zip<br />
WoW-2.1.0-enGB-patch.exe<br />
WoW-2.1.0.6692-to-2.1.0.6729-enGB-patch.exe<br />
WoW-2.1.0.6729-to-2.1.1.6739-enGB-patch.exe<br />
WoW-2.1.1.6739-to-2.1.2.6803-enGB-patch.exe<br />
<br />
I am British (pauses to sing "God Save the Queen"), so I use the enGB patches. There exist other patches for other versions of the game in the USA, France, Germany and Spain.<br />
<br />
When you have downloaded the files into their own folder for neatness, copy these patches into the World of Warcraft working directory (paulr is my user name, you will need to use yours)<br />
<br />
cp * /home/paulr/.wine/drive_c/Program\ Files/World\ of\ Warcraft/<br />
<br />
The 1.12.x patch needs to be unzipped into the working directory<br />
<br />
cd /home/paulr/.wine/drive_c/Program\ Files/World\ of\ Warcraft/<br />
unzip wow-1.12.x-to-2.0.1-engb-patch-3.zip<br />
<br />
The simplest way to install the patches seems to be to run World of Warcraft. It detects that you have downloaded the patches and doesn't do it again.<br />
<br />
cd /home/paulr/.wine/drive_c/Program\ Files/World\ of\ Warcraft/<br />
wine WoW.exe<br />
<br />
You have to keep going round 5 times, it does get a bit dull, but it's fairly reliable. Accept the offer to Install the Gecko renderer when it comes up on your first patch install.<br />
<br />
The original Wiki says you can install patches with Wine as follows:<br />
<br />
wine wow-VERSION-LANG-patch.exe<br />
<br />
I haven't tried this, so I can't say if this works, and I don't know how to install the zip file this way :) <br />
<br />
If the Launcher (it displays a little box with News and Play) seems to stop when downloading, close its window and re-run WoW.exe<br />
<br />
==Installing in Cedega==<br />
<br />
Installing in Cedega is done by running the program from the menus, selecting Install, typing "World of Warcraft" in the Game name, selecting the WoW profile, navigating to the Installer.exe file using browse, and then clicking continue.<br />
<br />
===Fixes for Cedega===<br />
<br />
On my Gnome system, Cedega will not run using Alsa, it is necessary to switch to OSS. <br />
<br />
The current version of Cedega requires you to edit the following file<br />
<br />
gedit .cedega/configuration_profiles/cedega_6.0.1 <br />
<br />
and add the following line to the [d3dgl] section<br />
<br />
"VertexShadersLevel" = "1.1" <br />
<br />
==Configuration==<br />
<br />
The World of Warcraft configuration file is kept in the WTF directory (do Blizzard have a sense of humour ?)<br />
<br />
Edit it with<br />
<br />
gedit WTF/Config.wtf<br />
<br />
===Using OpenGL===<br />
<br />
Add the following line which makes WoW run in OpenGL (hurrah !) instead of grotty old DirectX Mode (boo). <br />
<br />
SET gxApi "opengl"<br />
<br />
This is a REQUIREMENT for Wine, but is not required for Cedega.<br />
<br />
===Resolution and Colour depth===<br />
<br />
You can change the following two lines to set the default WoW resolution. I have a 19" Monitor so I can use the following.<br />
<br />
SET gxColorBits "24"<br />
SET gxResolution "1440x900"<br />
<br />
===Windowing===<br />
<br />
You can run in a Window by setting this, but I haven't tried it.<br />
<br />
SET gxWindow "1" <br />
<br />
===Sound Issues===<br />
<br />
====Configuring the Buffer====<br />
If the sound makes a horrendous racket with squeaks and white noise try :<br />
<br />
SET SoundOutputSystem "1" <br />
SET SoundBufferSize "100"<br />
<br />
====Stuttering or Static Sound====<br />
Run <tt>winecfg</tt>, and in the "Audio" tab, selected "OSS" as the sound driver, using "Standard" hardware acceleration and driver emulation enabled.<br />
<br />
You can also set WoW to run at a higher "nice level", which will usually improve sound performance (<tt>renice</tt> must be run as root):<br />
<br />
sudo renice -15 `pidof WoW.exe`<br />
<br />
==A customised version of Wine==<br />
If you wish to compile wine from source yourself, you will need to edit the Wine PKGBUILD.<br />
(Note that patching Wine with fixes for WoW is no longer necessary)<br />
<br />
First, update your ABS with this command:<br />
<br />
pacman -S cvsup<br />
abs<br />
<br />
Next, copy the Wine PKGBUILD to <tt>/var/abs/local/wine</tt>:<br />
<br />
cp -R /var/abs/extra/x11/wine /var/abs/local<br />
<br />
and edit the PKGBUILD so that it looks something like this:<br />
<br />
<pre># $Id: PKGBUILD,v 1.12 2006/04/04 17:10:07 tpowa Exp $<br />
# Maintainer: Dale Blount <dale@archlinux.org><br />
# Contributor: Matt Smith (Majik) <darkknight@helpdesk.zaz.net><br />
pkgname=wine<br />
pkgver=0.9.12<br />
pkgrel=1<br />
pkgdesc="Emulator of the Windows 3.x and Win32 APIs"<br />
url="http://www.winehq.com"<br />
# don't add arts, it's only a dep if configured<br />
depends=('x-server' 'libjpeg' 'libungif' 'alsa-lib' 'glut' 'openldap' 'libxslt' 'lcms' 'libxxf86dga' 'freeglut')<br />
makedepends=('alsa-lib' 'arts' 'sane')<br />
install=<br />
source=(http://ibiblio.org/pub/linux/system/emulators/wine/wine-$pkgver.tar.bz2 \<br />
wine-$pkgver-wow_fixes.patch)<br />
<br />
build() {<br />
cd $startdir/src/$pkgname-$pkgver<br />
msg "Patching Wine..."<br />
patch -Np0 ../$pkgname-0.9.11-wow-fixes.patch<br />
<br />
msg "Done patching, starting build..."<br />
./configure --prefix=/usr --sysconfdir=/etc --enable-opengl --with-x<br />
make depend || return 1<br />
make || return 1<br />
make prefix=$startdir/pkg/usr install || return 1<br />
# expand conflicts with textutils ( doesn't exist anymore ? )<br />
# mv $startdir/pkg/usr/bin/expand $startdir/pkg/usr/bin/wine-expand || return 1<br />
mkdir -p $startdir/pkg/etc/wine<br />
# mkdir -p $startdir/pkg/etc/profile.d<br />
# cp -r $startdir/src/$pkgname-$pkgver/documentation/samples $startdir/pkg/etc/wine<br />
}<br />
#md5sums=('b21d359b75f07255bb5cd34384bdc3cf' 'a65f6f2d422e5ee50af8492ebd38470f')<br />
</pre><br />
<br />
'''NOTE:''' You can get the <tt>wine-$pkgver-wow_fixes.patch</tt> from here: http://appdb.winehq.org/appview.php?versionId=4031<br />
<br />
Now execute the following commands to build and install your custom wine:<br />
<br />
cd /var/abs/local/wine<br />
makepkg -w `pwd`<br />
pacman -U wine-*.pkg.tar.gz<br />
<br />
You now have a working version of Wine!<br />
<br />
==Performance Tweaks==<br />
<br />
1. Here is a performance tweak that can boost your FPS significantly (everything without quotes):<br />
<br />
- Open wine's version of the registry editor by running "regedit"<br />
- Navigate to HKEY_CURRENT_USER\Software\Wine\ <br />
- Select the "Wine" folder, right-click onto the folder symbol and select New-> Key and rename it to "OpenGL"<br />
- Select the OpenGL-Key, then right-click into the right-hand pane, chose New-> String Value and hit enter<br />
- Rename "New Value #1" to "DisabledExtensions"<br />
- Double-Click on the renamed Key and enter "GL_ARB_vertex_buffer_object" into the "value" field<br />
<br />
That was it, close the registry editor again, your changes will be saved automatically.<br />
<br />
2. If you are finding it annoying that turning your character by let's say 90 degree takes n seconds normally, but n+m seconds in pupolated areas (in other words: that the polygon count of your surroundings affects the camera turning speed), apply something to "GL_ARB_vertex_buffer_object", like let's say a "2", so it looks like this: "GL_ARB_vertex_buffer_object2". You will still have the performance boost of the above tweak, but with a smoother feeling.<br />
<br />
==Links==<br />
<br />
[http://appdb.winehq.org/appview.php?iVersionId=6482 World of Warcraft in the wine APPDB]<br />
<br />
[http://www.wowwiki.com/Main_Page WoWWiki]<br />
<br />
[http://www.wowwiki.com/Patch_mirrors Patch Mirrors]</div>Prune