Getting Arch installed on a prgmr.com VPS is not
insanely complex, but I wanted to make sure my method is documented
somewhere I could find it again. The goal of this is to document the
steps taken, then flesh it out into a full set of scripts to install
Arch on a VM. Ideally this would be relatively simple, and provide an
installation with two separate partitions for the file systems
(/boot and /). Having /boot in a separate partition will allow
me to upgrade / to btrfs when prgmr.com upgrades to grub2 in a
few months.
Every time I install Arch Linux I am surprised when XFCE insists on
running gpg-agent when I log on. When it further doesn't work
properly with ssh-keys (admittedly, probably because I don't know how
to use it properly) and invokes pinentry to input another passphrase
so Gnome Keyring can protect the key the agent is supposed to
protect... well... that's when I start to get irritated. Irritation
leads to anger, and anger to research, and research to a solution.
Luckily the solution is easy to find every time, but this time I'm
making it easier to find. This makes XFCE use ssh-agent even if
gpg-agent is …continue.
In working with Hakyll the biggest problem was my lack of familiarity with
Haskell, and my lack of time to learn it sufficiently to feel comfortable
with the software. After a while I started to get irritated by my lack of
understanding, and decided that (unless I dedicated more time to learning
Haskell) I needed to move over to something in a language I was more familiar
with (Python)... thus the move to Acrylamid.
Installing on FreeBSD turned out to be relatively simple, given that the
software is available for install using easy_install or pip. I chose pip
because I have an issue with software that …continue.
Although the method of serving an APT repository I discovered when setting up
Debian on MacBook Pro 5.2 is sufficient, it is not very robust. Thus
I began looking for something more useful for multiple repositories, and which
is packaged for debian itself.
The search led me to a post that demonstrated how to configure a
private repository using reprepro. Although that gave me almost
everything I needed, one final bit was required: permission adjustment. As I
use Mathopd, the easiest way to prevent visitors from accessing the conf and
db directories was to restrict their permissions to that of my user alone.
I experienced a problem for years on FreeBSD, but have never been motivated to
solve it until now. The problem presents when attempting to set FQDN of the
system (nastie.weller-fahy.com). I set hostname to the proper value in
/etc/rc.conf.
hostname="nastie.weller-fahy.com"
When I type hostname at the prompt, I am given the unqualified hostname,
nastie. When it bit me tonight, I finally tried to find a solution, and
(shock of all shocks) found one!
So, to sum up, create an executable file /etc/dhclient-enter-hooks with the
following content.
One of the things I wanted most in my conversion to Hakyll was a way to show the
location breadcrumbs of the current page. For those unfamiliar with the
concept, these do not show the actual path the user took to get to the page, but
they do show the location of the current page in the website hierarchy. For
example, if I were on a post called "Having my bread crumbs and eating them
too!", then the bread crumb URLs on the page would be as follows.
It is considered good practice to set an expiration date on your GPG/PGP keys.
Setting the expiration date prevents the possibility of losing the private key
leaving a valid, non-expired, key out on the key servers that you cannot revoke.
Revocation certificates may be one solution, but I found it more useful to
simply set the expiration date.
It is useful if one can also remember how to extend the expiration date of the
GPG key in question when the expiration date sneaks up without warning.
Luckily, I was able to find an article by George Notaras on How to change the
expiration date of a GPG key, …continue.
Ikiwiki is a great idea in theory. For those unfamiliar with the concept,
it is basically a fully functional wiki integrated with a version control system
(VCS), all done in such a way that the pages are served statically unless you
are modifying the configuration or one of the pages.
An excellent solution for those who need that level of interactivity, but it is
a bit much for my purposes. …continue.
Just came across this excellent example of WebGL programming, and lost
some productive time playing with it. This is a superb demonstration of what
the web could become, or, at least, could aspire to become... plus, it is fun!