MaximumHoyt

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    2560x1080     60.00*+    1920x1080     60.00    59.94    50.00    29.97    60.05    60.00    50.04      1680x1050     59.95      1600x900      60.00      1280x1024     75.02    60.02      1280x720      60.00    59.94    50.00      1152x864      75.00      1024x768      75.03    60.00      800x

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 element is i

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  %(echo $HOM