Knowledge Base (Posts about software)

Dosbox-X: run Signing Exact English

bgstack15 — Thu, 11 Jun 2026 12:43:00 GMT

I did a deep-dive for running a long-gone Windows 95-era program in modern desktop Linux. A user needed to run "Signing Exact English," which was the old desktop version rather than their web app. Here's how I did it.

Requirements

Run the program with all features
Print to pdf

Steps to reproduce

These steps assume the username is public. I previously tried the application in Wine, but Wine didn't play nicely with the Adobe Director plugin PrintOMatic.x32, due to some problem listing a default printer.

Explode SEE.zip to /home/public/.wine/drive_c/SEE2

mkdir -p ~/.wine/drive_c/SEE2 ; cd ~/.wine/drive_c/SEE2
7za x /mnt/public/Support/Programs/Signing-Exact-English/SEE.zip

Adjust Dosbox-X win98.conf with [autoexec] entry:

MOUNT -t dir G "/home/public/.wine/drive_c/SEE2" -label SEE

Prepare the pdf995 files.

cp -pi ~/Downloads/pdf995s-9.5.exe ~/Downloads/ps2pdf995.exe ~/.wine/drive_c/SEE2

Install ps2pdf995

Read more… (3 min remaining to read)

Useful Dosbox-X config values

bgstack15 — Sun, 07 Jun 2026 12:55:00 GMT

I've recently had to switch even my Windows 3.1 Dosbox guest to Dosbox-X. I was getting weird display glitches even just loading Windows 3.1, not even any of the games yet.

I've come across some very useful settings that I want to use for any DOSBox-X instances.

[sdl]
# Capture the mouse
autolock  = true
# Hide the KRNL386 garbage data in the titlebar
showbasic = false
[dosbox]
# Show this in the titlebar
title     = win31games
[render]
# Keep the 4:3 aspect ratio at all times, which makes full-screening the application still look nice.
aspect    = true

On a Devuan system, the useful document files are these.

/usr/share/dosbox-x/dosbox-x.reference.conf
/usr/share/dosbox-x/dosbox-x.reference.full.conf

Xbright: adjust X11 brightness

bgstack15 — Wed, 03 Jun 2026 12:47:00 GMT

Years ago I found a small program on the Internet that makes it easier to adjust screen brightness within X11. You can of course use xrandr, but this makes it easier when you're not thinking that deeply.

It isn't sufficient for adjusting gamma. I need to adjust gamma for playing games like Portal that are just too dark.

xgamma -gamma 1.5

Maybe I should add it as a slider, but I haven't bothered to do that yet.

Drag-and-drop to sign code

bgstack15 — Sat, 02 May 2026 13:02:00 GMT

I set up a simpler hands-on process for signing binary assets of various kinds. There are apparently still people in the world who don't want to "sign every rubbish binary blob the software developers produce." (Read: give developers a CI/CD with automatic signing, so that they can produce whatever malware they want and get a company signature on it.) For small-scale operations, this suffices to manually sign assets.

The Windows world calls this "Authenticode." There is no direct equivalent in the Free Software world, because official software comes from gpg-signed rpm or apt repositories. Additional installation assets are usually published with checksums on https pages.

The solution involves the signing process with a specific certificate identified by thumbprint. Windows really wants to identify certificates by thumbprint rather than by serial number. Sometimes that means you can get a new certificate with the exact same thumbprint, which I'm sure is useful somewhere. (It also means you're using the same private key, which may or may not be within your certificate policy to allow.)

Yes, this is partially vibecoded. It's my standard format of a library that can be loaded into the current shell (I forgot how and why to use modules.)

files/2026/listings/Sign-Code.ps1 (Source)

	`#!/bin/pwsh`
	`# File: Sign-Code.ps1`
	`# Last-Modified: 2026-04-01T11:07:34-0400`
	`# Locations:`
	`# \\utility5\e$\CodeSign\Scripts`
	`# Author: bgstack15`
	`# Startdate: 2026-03-31`
	`# Title: Sign-Code`
	`# Project: Codesign`
	`# Purpose: Functions for easily signing binaries on utility5`
	`# History:`
	`# Usage:`
	`# As a library, . .\Sign-Code.ps1`
	`# Or directly, ".\Sign-Code.ps1"`
	`# References:`
	`# https://www.scriptinglibrary.com/languages/powershell/how-to-modify-your-proxy-settings-with-powershell/`
	`# https://4sysops.com/archives/how-to-create-an-open-file-folder-dialog-box-with-powershell/`
	`# Improve:`
	`# Dependencies:`
	`# Cert loaded in Cert:\LocalMachine\My`
	`# Documentation:`
	`<#`
	`.SYNOPSIS`
	`Functions for easily signing binaries on the utility server.`

	`.DESCRIPTION`
	`This script provides functions to configure proxy settings, select files via a dialog,`
	`sign binaries using signtool.exe, and move signed files to a destination folder.`
	`It supports being dot-sourced as a library or run directly to invoke the signing process.`

	`.NOTES`
	`.USAGE`
	`As a library (import functions for manual use):`
	`. .\Sign-Code.ps1`

	`Run directly (sign files from default or specified folders):`
	`.\Sign-Code.ps1`

	`.PARAMETER Set-Proxy`
	`Configures the user's system proxy settings by modifying registry keys.`

	`.PARAMETER Get-File-Dialog`
	`Opens a Windows File Open dialog to select one or more files.`

	`.PARAMETER Sign-File`
	`Signs each file using signtool.exe and moves successfully signed files to a destination folder.`

	`.PARAMETER Ask-Sign-Files`
	`Main function to select files, and sign them.`

	`.DEPENDENCIES`
	`- Windows signtool.exe located at the specified path.`
	`- Code signing certificate loaded in Cert:\LocalMachine\My.`
	`- User has write permissions to destination folders.`

	`.REFERENCES`
	`- https://www.scriptinglibrary.com/languages/powershell/how-to-modify-your-proxy-settings-with-powershell/`
	`- https://4sysops.com/archives/how-to-create-an-open-file-folder-dialog-box-with-powershell/`
	`#>`

	`#region Proxy Configuration Function`

	`Function Set-Proxy {`
	`<#`
	`.SYNOPSIS`
	`Sets the system proxy server and port for the current user.`

	`.PARAMETER Server`
	`The proxy server address (e.g., proxy.example.com).`

	`.PARAMETER Port`
	`The proxy server port number (e.g., 8080).`

	`.EXAMPLE`
	`Set-Proxy -Server proxy.example.com -Port 8080`
	`#>`
	`[CmdletBinding()]`
	`[Alias('proxy')]`
	`[OutputType([string])]`
	`Param`
	`(`
	`[Parameter(Mandatory = $true,`
	`ValueFromPipelineByPropertyName = $true,`
	`Position = 0)]`
	`[string]$Server,`

	`[Parameter(Mandatory = $true,`
	`ValueFromPipelineByPropertyName = $true,`
	`Position = 1)]`
	`[int]$Port`
	`)`

	`# Set proxy server address and enable proxy in the user's registry`
	`Set-ItemProperty -Path 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings' -Name ProxyServer -Value "$($Server):$($Port)"`
	`Set-ItemProperty -Path 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings' -Name ProxyEnable -Value 1`

	`# (Optional) Display the current proxy settings`
	`# Get-ItemProperty -Path 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings' \| Select-Object ProxyServer, ProxyEnable`
	`}`

	`#endregion Proxy Configuration Function`

	`#region File Selection Function`
	`Function Get-File-Dialog {`
	`<#`
	`.SYNOPSIS`
	`Opens a file open dialog for the user to select one or multiple files.`

	`.PARAMETER InitialFolder`
	`The folder that the dialog will open initially.`

	`.OUTPUTS`
	`String[] - Full paths of the selected files.`

	`.EXAMPLE`
	`$files = Get-File-Dialog -InitialFolder "E:\CodeSign\ToBeSigned"`
	`#>`
	`[CmdletBinding()]`
	`Param(`
	`[Parameter(Mandatory = $false)]`
	`[string]$InitialFolder = "E:\CodeSign\ToBeSigned"`
	`)`

	`# Load Windows Forms assembly for GUI dialog`
	`Add-Type -AssemblyName System.Windows.Forms`

	`# Configure and show OpenFileDialog allowing multi-selection`
	`$FileBrowser = New-Object System.Windows.Forms.OpenFileDialog -Property @{`
	`InitialDirectory = $InitialFolder;`
	`Title = "Choose file(s) to sign";`
	`MultiSelect = $true`
	`}`
	`$null = $FileBrowser.ShowDialog()`

	`# Return array of selected file paths`
	`return $FileBrowser.FileNames`
	`}`

	`#endregion File Selection Function`

	`#region File Signing Function`

	`Function Sign-File {`
	`<#`
	`.SYNOPSIS`
	`Signs one or more files using signtool.exe and moves successfully signed files.`

	`.PARAMETER FilePath`
	`One or more full file paths to sign. Supports pipeline input.`

	`.PARAMETER DestinationFolder`
	`Directory where successfully signed files will be moved.`

	`.NOTES`
	`Requires signtool.exe at specified path and appropriate certificates installed.`

	`.EXAMPLE`
	`$files \| Sign-File -DestinationFolder "E:\CodeSign\SignedCode"`
	`#>`
	`[CmdletBinding()]`
	`Param(`
	`[Parameter(Mandatory = $true,`
	`ValueFromPipeline = $true,`
	`ValueFromPipelineByPropertyName = $true,`
	`Position = 0)]`
	`[string[]]$FilePath,`

	`[Parameter(Mandatory = $true)]`
	`[string]$DestinationFolder`
	`)`

	`Process {`
	`foreach ($file in $FilePath) {`
	`Write-Host "Signing file: $file"`

	`# Execute signtool.exe with specified options`
	& "C:\Program Files (x86)\Windows Kits\10\bin\10.0.26100.0\x64\signtool.exe" sign `
	/fd sha256 /td sha256 /v `
	/f "E:\CodeSign\cert2025\example.cer" `
	/sha1 B38EXAMPLE17340436A80B0A2FDC3BEC9352250F `
	/kc CodeSignExample2025 `
	/csp "Safenet Key Storage Provider" `
	/tr http://timestamp.digicert.com `
	`$file`

	`$exitCode = $LASTEXITCODE`

	`if ($exitCode -eq 0) {`
	`# Signing succeeded; ensure destination folder exists`
	`if (-not (Test-Path -Path $DestinationFolder)) {`
	`New-Item -Path $DestinationFolder -ItemType Directory -Force \| Out-Null`
	`}`

	`# Move signed file to destination folder`
	`$destinationPath = Join-Path -Path $DestinationFolder -ChildPath (Split-Path $file -Leaf)`
	`try {`
	`Move-Item -Path $file -Destination $destinationPath -Force`
	`Write-Host "Moved file to $destinationPath"`
	`}`
	`catch {`
	`Write-Warning "Failed to move file $file to ${destinationPath}: $_"`
	`}`
	`}`
	`else {`
	`Write-Warning "Signing failed for $file with exit code $exitCode. File not moved."`
	`}`
	`}`
	`}`
	`}`

	`#endregion File Signing Function`

	`#region Main Orchestration Function`

	`Function Ask-Sign-Files {`
	`<#`
	`.SYNOPSIS`
	`Orchestrates proxy setup, file selection, and signing of files.`

	`.PARAMETER DestinationFolder`
	`Optional. Destination folder for signed files. Defaults to "E:\CodeSign\SignedCode".`

	`.PARAMETER InitialFolder`
	`Optional. Initial folder for the file selection dialog.`

	`.EXAMPLE`
	`Ask-Sign-Files -InitialFolder "E:\CodeSign\ToBeSigned" -DestinationFolder "E:\CodeSign\SignedCode"`
	`#>`
	`[CmdletBinding()]`
	`Param(`
	`[Parameter(Mandatory = $false)]`
	`[string]$DestinationFolder = "E:\CodeSign\SignedCode",`

	`[Parameter(Mandatory = $false)]`
	`[string]$InitialFolder`
	`)`

	`# Configure proxy settings for the user environment`
	`Set-Proxy -Server proxy.example.com -Port 8080`

	`# Get files to sign via file dialog`
	`$Infiles = Get-File-Dialog -InitialFolder $InitialFolder`

	`# Pass files and destination folder to signing function`
	`$Infiles \| Sign-File -DestinationFolder $DestinationFolder`
	`}`

	`#endregion Main Orchestration Function`

	`#region Script Execution Control`

	`# Check if script is being run directly or dot-sourced/imported`
	`# If called directly, with more than 0 arguments`

	`if ($args.Count -gt 0) {`
	`# Files were dropped onto the script or shortcut, process them directly`
	`# Assuming the DestinationFolder is set or can be defaulted`
	`$destinationFolder = "E:\CodeSign\SignedCode"`

	`# Validate that all args are files`
	`$filesToSign = $args \| Where-Object { Test-Path $_ -PathType Leaf }`
	`if ($filesToSign.Count -eq 0) {`
	`Write-Warning "No valid files passed as arguments."`
	`exit 1`
	`}`

	`# Call Sign-File with the files from args`
	`$filesToSign \| Sign-File -DestinationFolder $destinationFolder`
	`}`
	`elseif ($MyInvocation.InvocationName.Contains($MyInvocation.MyCommand.Name) -or`
	`$MyInvocation.InvocationName -eq $PSCommandPath) {`
	`# Script is being run directly; invoke main function with default folders`
	`Ask-Sign-Files -InitialFolder "E:\CodeSign\ToBeSigned" -DestinationFolder "E:\CodeSign\SignedCode"`
	`}`

	`#endregion Script Execution Control`

And somehow in the loss of progress, you cannot set up a shortcut to run powershell, and have it accept parameters. (Or I never learned. I'm sure the comments will correct me shortly.) So you can do that with the following batch script.

files/2026/listings/Sign-Code.bat (Source)

	`@echo off`
	`REM File: Sign-Code.bat`
	`REM Purpose: make it possible to drop files onto this`
	`:: Check for admin rights by trying to create a folder in %windir%`
	`>nul 2>&1 "%SYSTEMROOT%\system32\cacls.exe" "%SYSTEMROOT%\system32\config\system"`

	`if '%errorlevel%' NEQ '0' (`
	`echo Requesting administrative privileges...`
	`powershell.exe -Command "Start-Process -FilePath '%~f0' -ArgumentList '%*' -Verb RunAs"`
	`exit /b`
	`)`

	`:: If we get here, we have admin rights`
	`powershell.exe -NoProfile -ExecutionPolicy Bypass -File "E:\CodeSign\Scripts\Sign-Code.ps1" %*`
	`pause`

Set up a shortcut to the script. You don't need to customize parameters; it will already handle them correctly. Set up your .lnk to point to C:\Path\Sign-Code.bat and that is all.

The non-free software I use

bgstack15 — Fri, 14 Jul 2023 13:16:21 GMT

Here's what I can think of for the non-free software I use, and why. It's my walk of shame.

Steam and Age of Empires 2: Definitive Edition

I play AoE2DE because I've been playing Age of Empires 2 ever since the Conquerors Expansion in 2004. I remember the fun days of Voobly. The current scene is on the Microsoft services-centric AoE2 Definitive Edition, so I have to use it.

Discord

I use Discord for my AoE2 group.

Nvidia graphics

I have some hand-me-down Nvidia card that is enough to run Age of Empires 2. That's it. I don't care about anything else it can or cannot run.

Old computer games

There are many old computer games from before my free-software days, like kids' games, that I still have the original disc or materials for. I play through some of them on occasion. I'd say most of them are edutainment titles like from The Learning Company. Maybe this category doesn't count, because it's all old stuff.

I use Telegram for communicating with family. You have to make a stand somewhere, and apparently I was way too late with my self-hosted Matrix idea (which still isn't implemented). I'm sure the NSA or FSB or whoever my threat model is can read anything I choose to send anyways.

Compile Pale Moon 28 on Fedora 27

bgstack15 — Sat, 18 Aug 2018 01:23:16 GMT

Introduction

Pale Moon 28 was released on August 16, 2018. I package it myself on Fedora because I don't see it in the fedora repositories, and plus I like the experience of assembling packages myself. For a basic compile (not in an rpm), you can follow these instructions.

Install dependencies

Install the whole set of packages listed on the Pale Moon site (reference 2) or CentOS7

sudo dnf -y install gtk2-devel dbus-glib-devel autoconf213 yasm mesa-libGL-devel alsa-lib-devel libXt-devel zlib-devel openssl-devel sqlite-devel bzip2-devel pulseaudio-libs-devel
sudo dnf -y groupinstall 'Development Tools'

Install the dependencies I found.

sudo dnf -y install GConf2-devel notification-daemon

Use autoconf 2.13

Pale Moon depends on autoconf 2.13. Thankfully, it's in the Fedora repos, but changing the main autoconf link to point to this specific version will save a bunch of headache later. Be aware that this step exactly as shown will change your system's default autoconf. I'm sure this is a crude way to do it, but aren't build systems throwaway systems nowadays?

autoconfver="$( autoconf --version 2>/dev/null | awk 'NR==1 {print $NF*100;} END {print "0";}' | head -n1 )"
test ${autoconfver} -ne 213 &&amp test ${autoconfver} -gt 0 && sudo mv /usr/bin/autoconf /usr/bin/autoconf-${autoconver} 2>/dev/null ; sudo ln -sf autoconf-2.13 /usr/bin/autoconf

Fetch source

Pale Moon likes to compile in ~/pmsrc. Don't change it. It just makes it easier.

mkdir ~/pmsrc ~/pmbuild
cd ~/pmsrc
git clone https://github.com/MoonchildProductions/UXP .

Prepare to compile

Use the recommended .mozconfig from the Pale Moon site (reference 2)

tf=~/pmsrc/.mozconfig
touch "${tf}"
cat <<'EOFMOZCONFIG' > "${tf}"
mk_add_options AUTOCLOBBER=1
mk_add_options MOZ_OBJDIR=/home/$USER/pmbuild/
ac_add_options --enable-application=palemoon

ac_add_options --enable-optimize="-O2"

# Please see https://www.palemoon.org/redist.shtml for restrictions when using the official branding.
ac_add_options --enable-official-branding
export MOZILLA_OFFICIAL=1

ac_add_options --enable-default-toolkit=cairo-gtk2
ac_add_options --enable-jemalloc
ac_add_options --enable-strip
ac_add_options --with-pthreads

ac_add_options --disable-tests
ac_add_options --disable-eme
ac_add_options --disable-parental-controls
ac_add_options --disable-accessibility
ac_add_options --disable-webrtc
ac_add_options --disable-gamepad
ac_add_options --disable-necko-wifi
ac_add_options --disable-updater

ac_add_options --x-libraries=/usr/lib
EOFMOZCONFIG

Compile

These instructions include saving the output to a log file, but that's not necessary.

mkdir ~/log
cd ~/pmsrc
{ time ./mach build && time ./mach package ; } | tee -a ~/log/pmsrc.$( date "+%F-%H%M%S" ).log
echo done

References

Weblinks

Compiling Pale Moon web browser on Fedora 27

bgstack15 — Fri, 09 Feb 2018 13:31:27 GMT

Story

I like the traditional model of Firefox. This is easily represented in the current project Pale Moon. The upstream project does not currently provide instructions for compiling on Fedora 27. All the options they have documented are on their developer site: https://developer.palemoon.org/Developer_Guide:Build_Instructions/Pale_Moon/Linux. You might think it is no big deal to download and compile an application. But when the application is still targeted for gcc4.9, it's a little tricky to compile on the current Fedora which uses gcc7. After consulting the Internet, I have assembled my instructions for compiling Palemoon on Fedora.

Compile palemoon on Fedora 27

# Install the whole set of packages listed on (primary ref 1) for CentOS7
sudo dnf -y install gtk2-devel dbus-glib-devel autoconf213 yasm mesa-libGL-devel alsa-lib-devel libXt-devel zlib-devel openssl-devel sqlite-devel bzip2-devel pulseaudio-libs-devel
sudo dnf -y groupinstall 'Development Tools'

# Install additional dependencies I found
sudo dnf -y install nspr-devel

# Use autoconf 2.13
autoconfver="$( autoconf --version 2>/dev/null | awk 'NR==1 {print $NF*100;} END {print "0";}' | head -n1 )"
test ${autoconfver} -ne 213 && test ${autoconfver} -gt 0 && sudo mv /usr/bin/autoconf /usr/bin/autoconf-${autoconver} 2>/dev/null ; sudo ln -sf autoconf-2.13 /usr/bin/autoconf

# Use the copr davidva/gcc49
sudo dnf -y copr enable davidva/gcc49
# fix the $releasever variable in the repo
sudo sed -i -r -e 's/-\$releasever-/-23-/;' /etc/yum.repos.d/_copr_davidva-gcc49.repo
sudo dnf -y install gcc49
# fix a minor library problem (primary ref 2)
pushd /opt/gcc-4.9.3/lib64/gcc/x86_64-fedoraunited-linux-gnu/4.9.3
sudo cp -p ../lib64/libgcc_s.so.1 .
sudo ln -s libgcc_s.so.1 libgcc_s.so
popd

# Fetch palemoon source
mkdir ~/pmsrc ~/pmbuild
cd ~/pmsrc
git clone https://github.com/MoonchildProductions/Pale-Moon.git .

# Prepare to compile
# use .mozconfig from (primary ref 1)
tf=~/pmsrc/.mozconfig
touch "${tf}"
cat <<'EOFMOZCONFIG' > "${tf}"
# Please see https://www.palemoon.org/redist.shtml for restrictions when using the official branding.
ac_add_options --enable-official-branding
export MOZILLA_OFFICIAL=1

mk_add_options MOZ_CO_PROJECT=browser
ac_add_options --enable-application=browser

mk_add_options MOZ_OBJDIR=/home/$USER/pmbuild/

ac_add_options --enable-optimize="-O2 -msse2 -mfpmath=sse"
ac_add_options --with-pthreads

ac_add_options --disable-installer
ac_add_options --disable-updater

ac_add_options --enable-release
ac_add_options --enable-devtools
ac_add_options --enable-jemalloc
ac_add_options --enable-shared-js

ac_add_options --enable-strip

ac_add_options --x-libraries=/usr/lib
EOFMOZCONFIG

# Compile:
mkdir ~/log
cd ~/pmsrc
source /usr/bin/gcc49
{ time ./mach build ; } | tee -a ~/log/pmsrc.$( date "+%Y-%m-%d-%H%M%S" ).log
echo done

Future steps

Post these instructions on the fedora and palemoon fora. Ask Pale Moon devs if these can be adapted and shared on Reference 1.

References

Weblinks

primary

http://developer.palemoon.org/Developer_Guide:Build_Instructions/Pale_Moon/Linux
ensure lib files are in right dir: https://serverfault.com/questions/266138/cannot-find-lgcc-s-from-gcc-3-4-on-unbuntu-11-04/266141#266141

auxiliary

A great example and future reference http://ftp.nluug.nl/pub/os/Linux/distr/pclinuxos/pclinuxos/srpms/SRPMS.pclos/palemoon-27.0.3-1pclos2017.src.rpm
https://build.opensuse.org/package/show/network/palemoon

gcc 4.9 for Fedora 27

bgstack15 — Thu, 01 Feb 2018 14:26:50 GMT

If you want gcc 4.9 (the GNU Compiler Collection) on the current version of Fedora, which is Fedora 27, there is an easy option for you! You can use the Cool Other Packages Repo, or copr, written by the user davidva. The easiest way to use his gcc49 copr is this:

sudo dnf -y copr enable davidva/gcc49
sudo sed -i -r -e 's/-\$releasever-/-23-/;' /etc/yum.repos.d/_copr_davidva-gcc49.repo
sudo dnf -y install gcc49

There is a weakness in the repo file delivered by the copr, where it uses the $releasever instead of a static number 23 used by the repo. Davidva compiled the package without a specific fedora version number tied to it, so it will install on any version of Fedora, as long as you can get to the rpm package. There is also a weakness with a particular library. It's in the wrong directory, so it cannot be found. You might find an error when trying to compile a project:

/usr/bin/ld: cannot find -lgcc_s

Use these steps to fix it (Weblink 2).

pushd /opt/gcc-4.9.3/lib64/gcc/x86_64-fedoraunited-linux-gnu/4.9.3
sudo cp -p ../lib64/libgcc_s.so.1 .
sudo ln -s libgcc_s.so.1 libgcc_s.so
popd

As the copr page (Weblink 1) indicates, this installation of gcc 4.9 can be present concurrently with the main gcc installation. To use version 4.9, you need to run:

source /usr/bin/gcc49

Which sets a few variables, notably $CC and $CXX to be the specific binaries from this package.

References

https://copr.fedorainfracloud.org/coprs/davidva/gcc49/
ensure lib files are in right dir: https://serverfault.com/questions/266138/cannot-find-lgcc-s-from-gcc-3-4-on-unbuntu-11-04/266141#266141

Moving the application installation directory for bgscripts

bgstack15 — Wed, 11 Jan 2017 15:15:42 GMT

Overview

My bgscripts package in version 1.1-27 and before was installed in /usr/bgscripts. The more I thought about it, and the more I read the spec for FHS 3.0 (filesystem hierarchy standard) (PDF), the more I realized it should actually be in /usr/share/bgscripts. Moving the files in the build directory was easy.

Wrapper script

But despite my symlinks in /usr/bin, which were easy to update, I have many, many hard-coded pathname calls of my scripts everywhere. So to mitigate the problem, I wrote a fancy wrapper script for regular scripts, including bup, send, bgscripts.bashrc, rdp, and treesize. I needed to send myself a message with the various information about what script called the old location. I picked send.sh because that's what it's for-- sending emails. I slapped in a bunch of diagnostic information and wrote a call to the new location. `

!/bin/bash # Wrapper at legacy location for bgscripts. Sends alert and then

continues the process. # DETERMINE LOCATION OF FRAMEWORK while read flocation; do if test -x ${flocation} && test "$( ${flocation} --fcheck )" -ge 20161212; then frameworkscript="${flocation}"; break; fi; done <&2 && exit 4 . ${frameworkscript} || echo "$0: framework did not run properly. Aborted." 1>&2 ### CUSTOM WRAPPER BEGINS HERE pwd="$( pwd )" psout="$( ps -ef )" parentprocess="$( ps -ef | grep -iE -- "${thisppid}" | grep -viE -- "grep.-iE.--" )" /usr/share/bgscripts/send.sh -hs "bgscripts alert ${server}: ${scriptfile}" bgstack15@gmail.com <<EOF ----- Description ----- This alert means that script "${scriptfile}" was called, and you need to fix it because /usr/bgscripts/* has been deprecated and will be removed in a future version. ----- Debug info----- pwd: ${pwd} Scriptdir: ${scriptdir} Scriptfile: ${scriptfile} All parameters: $@ Server: ${server} Now: ${now} Thisos: ${thisos} Thisflavor: ${thisflavor} Thisppid: ${thisppid} Parent process: ${parentprocess} ----- Process list ----- ${psout} EOF ### CALL NEW LOCATION /usr/share/bgscripts/${scriptfile} "${@}" ` So if something of mine calls /usr/bgscripts/bgscripts.bashrc, this wrapper script will throw an email alert, and then redirect the script call so workflows are not interrupted! The very first production use of the wrapper script was when I logged onto my test Ubuntu box to conduct a deep-dive search (more on that in the next heading) of scripts that call framework.sh. I got an email right away, saying I had dot- sourced the bashrc script. Looking at the diagnostic info, I was reminded that I tended to hardcode into my ~/.bashrc the call to /usr/bgscripts/bgscripts.bashrc. I have now updated that to point to /usr/bin/bp, so in the future it will point to wherever I want it to. However, I seriously doubt the location will change now. My package is now FHS 3.0 compliant, and I don't want to break that.

Deep dive search

So, I wanted to conduct a deep-dive search of all shell scripts (defined by me as everything ending in .sh, because I almost always use the extension) on all systems that refer to framework.sh, which is going to be the big hangup. So I whipped up this oneliner. sudo updatedb; locate .sh | grep -iE "\.sh$" | grep -viE "\/usr\/src|\/usr\/share|\/usr\/lib|\/home\/.*\/rpmbuild/|\/home\/work\/.*clean" | xargs grep -iE "framework\.sh" Now, an reading of my code shows that many of my scripts do a lookup for framework.sh in various locations, including ./framework.sh, ~/framework.sh, /usr/local/bin/framework.sh, and so on. You can observe this pattern in my wrapper script in this post. So the serach will catch those, but I will recognize those blocks of code because they are just the filename on a separate line (in a here- doc) and as long as I see the /usr/libexec/bgscripts/framework.sh final resting place of framework, I'll be satisfied.

References

Weblinks

Filesystem hierarchy standard 3.0 http://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html
FHS 3.0 in pdf http://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf
Here document https://en.wikipedia.org/wiki/Here_document