Just a bit of background. Some BALUG sites may be impacted soon, but *not*
www.balug.org or balug.org itself.
See:
http://lists.balug.org/pipermail/balug-admin-balug.org/2014-July/002233.html
for *which* sites will (and won't) be impacted
As to some background and why, have a look at:
http://linuxmafia.com/pipermail/sf-lug/2015q3/011330.html
And, for the BALUG specific bits I left out of the above:
> From: "Michael Paoli" <Michael.Paoli(a)cal.berkeley.edu>
> Subject: Re: vicki (exodus) & GoGrid/Datapipe
> Date: Thu, 23 Jul 2015 03:14:08 -0700
> BALUG: what balug has on the virtual machine atop vicki is certainly
> highly useful and convenient, and would be relative pain to be without,
> but we could survive without, at least for a bit, and have in fact
> relocated it (temporarily) elsewhere in past.
>
> What BALUG does *not* have atop the (VM on the) vicki host:
> www.balug.org, and balug.org itself aren't on that host, but other
> sites/subdomains are, e.g. [www.]{archive,wiki}.balug.org, among others.
>
> DNS - only for some subdomains, again not balug.org. itself.
For those that may have been wondering ...
the BALUG logo:
http://www.balug.org/images/balug/logo.gif
The apparently binary data shown on bottom towards left:
01100010 01100001 01101100 01110101 01100111
What is that data? Interpreted as ASCII data in binary, it's:
balug
references/excerpts:
http://www.balug.org/images/balug/logo.gif
$ perl -e 'print(pack(q(B*),join(q(),qw(
> 01100010 01100001 01101100 01110101 01100111
> ))),"\n");'
balug
$
