MaximumHoyt

Unreal is the first in a series of first-person shooters released by EPIC in 1998, It was followed by an add-on named Return to Na-Pali . The two games were combined into "Unreal Gold" and modified to run on the more modern Unreal Tournament game engine. The Windows version of the game is available from GOG for US$9.99 and is free of any Digital Rights Management restrictions. For my money, this is the best place to obtain the game. All four games in the series are available, often at a discount when purchased together. There are Linux installers available from Loki, but these are getting old and difficult to use . The game installs and plays well using PlayOnLinux  or Codeweaver's Crossover, both of which are a handy way of installing games when a native Linux game engine is not available or no longer works and using WINE and specially crafted installation scripts which not only select the best version of WINE to use, but also install any Windows apps that the ...

Quake3 Arena is a multiplayer online first-person shooter released in 1999. There is a Quake3 HOWTO written by Jonathan Bergknoff that should be your first stop for a general overview. It should be your first stop because even though dated, it provides useful details on how to launch mods and fix problems. There is also an interesting Wikipedia page for Quake3. It is quite amazing to me that this game was released way back in 1999 as the third installment to ID's Quake series. I've played it ever since the release; it has quite a following. Since id Software released the source code for the Quake3 game engine licensed under the GPL, there have been several projects that have attempted to make not only a better playing game, but a better looking game. You need a valid key to play Quake3, so if you don't already own the game, purchase the Windows version of the game from STEAM or Amazon to obtain the key code. There are several different game engines and...

There is a Quake2 HOWTO written by Bob Zimbinsky that should be your first stop. It should be your first stop because even though dated, it provides useful details on how to launch mods and fix problems. There is also an interesting Wikipedia page for Quake2. It is quite amazing to me that this game was released way back in 1997 as the second installment to ID's Quake series. I've played it ever since the release; it has quite a following. Since id Software released the source code for the Quake2 game engine, there have been several projects that have attempted to make not only a better playing game, but a better looking game. The game itself can be purchased from Amazon, GOG, eBay, or STEAM. There is no special code or password to unlock, run or install the game. In addition to the win32 game engine supplied with the original release as well as the GOG and STEAM releases, there are several different game engines and hi-res packs to choose from. What I'm prese...

There is a Linux Quake HOWTO written by Stevenuas that is extensive and should be your first stop. It provides guidance on how to run mods and fix problems. There is also an interesting Wikipedia page . It is quite amazing to me that this game was released in 1996 as the successor to id's Doom series. I've played it ever since the release. It has quite a following. Since id Software released the source code for the Quake game engine, there have been several projects that have attempted to make not only a better playing game, but a better looking game. There are several different game engines to choose from and several hi-res texture packs to choose from. What I'm presenting here is how I configure Quake on my Linux box. The game engine I chose is the DarkPlaces game engine built by LordHavoc . He last updated it in May of 2014 and his package provides binaries "for Windows (32bit, compatible with Windows XP/Vista x64/7 x64), Linux 686, Linux amd64, ...

All too often when installing a game, a problem occurs that halts the game and does not restore my desktop to the proper size. To look at what I started with and what I wound up with is simple. $ xrandr Screen 0: minimum 8 x 8, current 5120 x 1080, maximum 32767 x 32767 DVI-D-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm    1280x1024     60.02*+  75.02      1280x960      60.00      1152x864      75.00      1024x768      75.03    70.07    60.00      800x600       75.00    72.19    60.32    56.25      640x480       75.00    72.81    59.94   HDMI-0 connected primary 2560x1080+1280+0 (normal left inverted right x axis y axis) 798mm x 334mm   ...

I've been having trouble with occasional segfaults with my desktop workstation. It would be nice to look at the logs to see where the problem might be, but the logs show nothing. It might be easier, I thought, if I enabled remote logging. That way I would have a copy of the desktops' logs on a working computer, a Shuttle X35 I use as a http server running lighttpd , serving static pages for several hobby-related websites. Installing rsyslog was easy using urpmi . It was the configuration that was tricky. The configuration file for Mageia is kept in /etc/rsyslog.d and consists of a single file, 00_common.conf . The modules that can be called by rsyslog can be found in /usr/lib64/rsyslog . The man page states: The main configuration file /etc/rsyslog.conf or an alternative file, given with the -f option, is read at startup. Any  lines  that  begin  with the hash mark (``#'') and empty lines are ignored. If an error  occurs during parsing the error elem...

Occasionally, you may need to install something that is not included with Mageia. For instance, the x2x applications used to be included with Mageia, but has been dropped in Mageia 5. There are other packages, perhaps Ubuntu packages that I might want to use on my system. Or it's possible no package exists,  just a tarball. Why would you want to build a package from source if the binary is already available?  Let's begin with the Mageia Packagers RPM Tutorial as a reference. Create Your Build Environment It's always a good practice to build packages as a normal user, not as root. Still, it's handy to have sudo enabled for certain operations. Create you build environment. $ mkdir -p ~/rpmbuild/{SRPMS,SOURCES,SPECS,tmp} Using your favorite editor, create the .rpmmacros file to build Mageia packages.     # Only set %_topdir and %_tmppath if you want to ovveride the the default ~/rpmbuild # and ~/rpmbuild/tmp #%_topdir ...