Diablo 3: Keeping Your Work

Ok… so… you bought Diablo 3, you are running Gentoo, the files aren’t updating… The installer isn’t working… The launcher isn’t working either… Sure you can copy the files from your Windows computer, if you have one, but every time there is a patch you’d

need to do this.

This was the problem I was facing. Fortunately there are some really cool people on the internet who have written patches for Wine to over come these issues and Wine almost fully supports Diablo 3 right out of the box. Now it’s just our job to apply these patches. The problem is the pesky ebuild files. We want to apply 4 patch files to make this work. If we just compile from source, then portage is going to think we didn’t install here.

Here is what I did to accomplish getting Diablo 3 installed and running on Gentoo. All of my steps are adapted from the WineHQ entry for Diablo 3. The patches are provided by third parties whom I don’t know and not affiliated.

Step one) Diablo 3 required some Microsoft C++ package. There is a really awesome program called winetricks that will install a plethora of Wine related items. You have to unmask the package in portage and emerge winetricks first.

• winetricks vcrun2008

Step two) I didn’t want to mess with creating an ebuild or installing Wine from source. To do this, I added the keepwork feature in /etc/make.conf. Afterward I started the Wine emerge and control-C’ed the install just after it started to configure the source. With keepwork there, all I had to do was go to the work directory of Wine

to proceed to the next step. The work directory will be in the output of the emerge.

Step three) The patches are listed at the end of the this thread. They are the works of other people and they are third party patches to Wine. Wine has not yet accepted or declined them in to the source tree. They are obviously at your own risk. The first three patch

files are part of a greater patch. I also synlinked the wine-1.5.4 directory to b so I could copy and paste the file paths. There is likely a better way to do this, but I was just wanting the job done. After the first three files are patched, you just run the make_requests script in the tools folder to update the server source. The first patch (three patch files) addresses the inability to install or update Diablo. The second patch addresses the game crashing when altering the video settings.

• patch < 86263.txt
• patch < 86264.txt
• patch < 86265.txt
• ./tools/make_requests
• patch < reset.patch

Step four) Emerge Wine as you normally would. The keepwork feature will not overwrite your work directory and install Wine the usual Gentoo way. Obviously you want to disable this feature as it’s horrible and should never be used. I don’t really condone using this feature, but until a permanent solution is found, this should do the trick.

SMBD: No I’m Not Talking About Samba

Let’s say you need high

availability. You can’t afford to have a switch go down or have a network card go bad. You need uptime and you need it now. Now let’s make this even more complicated. Let’s add non native vlans to this ordeal. My weapons of choice are bonding and Gentoo. We need a few things.

1. Linux bonding module – Device Drives > Network device support > <M> Bonding drive support (you can make this a module or build it in but my howto only covers the module)
2. VLAN support – Networking support > Network options > 802.1Q VLAN Support
3. net-misc/vconfig
4. net-misc/ifenslave

After building the modules in your Linux kernel, emerge net-misc/vconfig net-misc/ifenslave . Next you want to setup the bonding module to auto load with your settings. Note that you may have more modules in your autoload file.

# cat /etc/modules.autoload.d/kernel-2.6
…
bonding miimon=100 mode=1

…

Remember to run update-modules. The miimon setting is how often, in milliseconds, the link state of the interface is checked. If it does not have link it will remove the link from the pool. The mode setting indicates the way the interfaces are balanced. There are several modes, but most require that your switch also be configured to use them. In this howto’s case mode 1 is set. Mode 1 is active/backup where you may have one active link up and one or more backups or standbys. If the active fails a backup will take its place.

Next you need to configure the network. The network

configuration file for Gentoo is /etc/conf.d/net . Here is how to setup bonding.

config_eth0=( “null” )
config_eth1=( “null” )

slaves_bond0=”eth0 eth1″

config_bond0=( “192.168.0.1/24” )
routes_bond0=( “default via 192.168.0.254/24” )

Basically you set eth0 and eth1 to have no configuration. This allows the ethernets to be brought up to use, but not configured to do anything or assumed to be dhcp. The slaves_bond0 directive sets which

interfaces are members of the pool of available interfaces. Finally config_ and route_ sets the ip and gateway for your interface.

Now, let’s say you are going to add non native VLANs. The config_ and route_ lines won’t work now. Here is the new config.

config_eth0=( “null” )
config_eth1=( “null” )

slaves_bond0=”eth0 eth1″

config_bond0=( “null” )

vlans_bond0=”100 200″
mtu_bond0=”1496″
vconfig_bond0=( “set_name_type VLAN_PLUS_VID_NO_PAD” )

config_vlan100=( “192.168.0.1/24” )
routes_vlan100=( “default via 192.168.0.254” )
config_vlan200=( “10.0.0.123/24” )

Basically the only difference is the removal of routes_bond0 and setting config_bond0 to null. The vlans_bond0 sets which VLANS to attach the interface to, mtu_bond0 sets the MTU size, and vconfig_bond0 sets VLAN options. Finally it’s time to setup the actual VLAN interfaces, those are config_<vlanid>. In our case we’ve already set them with vlans_bond0, so we have config_vlan100 and config_vlan200. Our default route goes out vlan100, so routes_vlan100 is used and vlan200 is our private interface.

That concludes our bondage training. I hope you all enjoyed and found this informational.