CrunchBang Linux

^ The WD USB enclosures were the only ones that failed that quickly (I have seen it happen to three different people), they had the most delicate USB ports I have ever seen.
They may be better now, I have not used a WD enclosure in years so I can't comment on the current quality.
I don't recommend them based on their poor reliability in the past for me and others.
Their drives are not bad (though they run hot in my experience) but I have found their enclosures to be fragile.

The "failed after 10 plugs/unplugs" actually happened to me after six months with a WD enclosure (I think a My Book).
I was a backup drive that was only moved if it had to be and was treated delicately.
I cracked the enclosure open (literally since it needed a special tool) and put the drive in a new enclosure and it still works six years later.
Other brands lasted longer but they did break eventually, I still use one of them because it is my only PATA enclosure and the Firewire ports work.

I always buy enclosures with more than one type of data port (USB/Firewire, USB/eSATA, etc.) now anyway so there is a backup if one fails.

^^ After less than 2 years, though under 1 year is not uncommon in my experience.
These drives were not moved or unplugged more than 10 times so I think the problem is really just the poor quality of the usb ports or the way they are mounted in the enclosure that causes them to fail in normal use.

In my experience Western Digital enclosures are the most likely to have usb port problems.
In my house we have had three fail that way (only one mine) and several of my friends have had it happen as well over the years.
The cable (one of those cheap looking thin ones) itself failed (the head broke free of the cable and insulator) for one of my friends first and the port failed a couple of months later.
None of these drives had any problems once they were put in a new external enclosure.

No, cmake is an alternative to autotools for automated build configuration.
It can produce makefiles for multiple compilers (Linux, Windows, Mac ones for sure, possibly more) which is why it sees use on a lot of cross-platform programs like mplayer.
Some projects use it just because their developers prefer it though.

^ "X11/extensions/XShm.h" is in the "libxext-dev" package.

^ I don't think you can make windows without 90 degree corners in X.
I know conky does not support that.
You could shade the background with other angles to the corners to simulate that effect though with a Lua script.

Post your whole "~/.config/openbox/autostart" file to see if there is anything that could cause it not to work in there.

I would need to see your script as it is now to help you with that.

This is only a warning message and won't cause any problems if you ignore it.

You have to run

/usr/bin/gnome-keyring-daemon --start --components=pkcs11

with your window managers "run command at login" function to get rid of that warning.
There are more options that may need to be added to the "--components=" section (as a comma separated list) if you use programs that need them but conky wants the "pkcs11" option.

The ".*" is a multiple character wildcard so it will match any command that ends in "/conky/test2.conkyrc".
pgrep accepts a type of regular expression in its argument, you can look at "man pgrep" to see which one specifically.

In network manager the way you do it is to set the metric value for each connection.
To get to that setting go to the IPv4 Settings tab when editing the connection settings and click the "Routes" button.
This will open a new window where you can set routes for that connection.
If you need to add a entry here use the same values for "Address", "Netmask", and "Gateway" as are shown on the first edit Window.
Set a lower metric value here for the connection you want to give priority over the other.
If your local network has no connection to the Internet check the "Use this connection only for resources on its network" box in its routes Window.
If you use IPv6 you may need to repeat these steps on the IPv6 tab.

If both your networks connect to the Internet I don't know how well this will work since I have never had a setup like that.

I recently started building my own kernels with the Liquorix kernel as a base.
The main reason I do it is I need some non-standard build options to be able to set some of my wireless cards firmware options to get it to work correctly.

CONFIG_MAC80211_DEBUGFS=y
CONFIG_ATH9K_DEBUGFS=y
CONFIG_ATH_DEBUG=y

That lets me turn of "ANI (Adaptive Noise Immunity)" with

echo 1 > /sys/kernel/debug/ieee80211/phy0/ath9k/disable_ani

which stops my network speed from dropping to zero every 30 seconds.

I set some compile options to optimize for my processor (Intel specific settings with "-march=native") and turned off the GPU (Non Intel and Nvidia) and CPU modules (Non Intel) I will never use.
This helps some with load (~0.2 lower) on my old Core2 media server, much less so on my i7.
I also set

CONFIG_NR_TTY_DEVICES=12

because I don't need 63 possible ttys.
I might go through and turn off all the other wireless card stuff I don't need some other time.

I don't turn anything else off since I don't want to have to recompile if I need to plug some random piece of hardware in.

^ They are working for me.

window.frame.focusColor:             #CC9900
window.frame.unfocusColor:           #8B0000

Try this then, it might be a current working directory problem.

cd "/home/surfino/.wine/drive_c/Program Files/GOG.com/Fallout" && env WINEPREFIX="/home/surfino/.wine" wine "/home/surfino/.wine/drive_c/Program Files/GOG.com/Fallout/falloutw.exe"