Category Archives: geek links

if it ain’t broke, don’t fix it

a wise old linux guru told me this, a few years ago, and i’ve found myself smack in the middle of what happens when you follow that maxim… and it doesn’t feel entirely comfortable, at this point.

i have been happily running kubuntu trusty since 2014, which means that, now, there are TWO LTS releases to bring me up to date… Bionic Beaver, and the interim release, Xenial Xerus, which had some notable problems that were notable enough that i decided that… IF IT AIN’T BROKE, DON’T FIX IT.

now, i’ve actually heard some good things about the new LTS release, and, strangely enough, Amarok broke about two weeks ago (and the amarok user list has gone quiet the past few months, which makes me wonder who to contact), so i’ve been having to resort to qmmp to play music… so i decided to upgrade.

i’ve had some AWFUL experiences upgrading operating systems, and linux is no exception. the last time i upgraded linux, it took me three days to get my computer back. in an attempt to avoid that possibility this time, i have finished uploading my ENTIRE /home directory to the cloud, and am in the process of uploading my ENTIRE music collection to the cloud.

then, on the advice of the linux gurus over at Kubuntu Forums (who have saved my ass more than once), i’m going to go out and get a 2TB SSD on which to install bionic.

the only problem is that i still am not completely sure that my email is going to transfer, because i know that kontact was one of the notable problems i read about with xenial that made me want to avoid upgrading… and i’m not sure the standard “back up everything including the hidden directories from /home” is going to work this time, because i’ve heard that bionic uses something other than akonadi, which was, apparently, the source of the problems with xenial… which would mean that potentially i could lose 7 years worth of email and contact information. 😒

so, we’ll just have to see how it goes… 😐

unicode geekery

the most current version of UNICODE, (v.7.0) has an emoticons block, which has, predictably, been incorporated into the most recent versions of your most popular operating systems in your most popular “mobile devices” (i.e. cell phones, tablets, etc.)…

but, because of the fact that they’re emoticons, i.e. pictures, rather than words, the interpretation of the emoticons in this block is, apparently, open to wild speculation about what they actually “mean” or “represent”…

which makes things A LOT more confusing, rather than clearing things up, as emoticons were intended to do…

for example, U+1F624 FACE WITH LOOK OF TRIUMPH looks like this, according to UNICODE:

U+1F624

looks like this in Mac OsX and iOS:

U+1F624

and, honestly, to me it looks like a “haughty” face rather than a “triumphant” one… either that, or it’s someone with an outrageous mustache…

another one that is even more confusing is U+1F632 ASTONISHED FACE, which looks like this, according to UNICODE:

U+1F632

and looks like this in Mac OsX and iOS:

U+1F632

which looks to me like a DEAD face… seriously, why don’t they make his eyes OPEN and not X-ed out… 😐

and then we get into non-real (for people in the west, anyway) glyphs, such as U+1F472 MAN WITH GUA PI MAO, which is in the “Miscellaneous Symbols and Pictographs” block and NOT the “Emoticons” block — a confusing aspect that is shared by a lot of the other “emoticons” in the version of unicode that the general public uses — which looks like this:

U+1F472

and in iOS it looks like this

U+1F472

i guess it is somewhat more understandable if you know that GUA PI MAO is a type of Chinese skullcap, but even knowing that doesn’t make it particularly useful to a western person…

and a lot of the things that pass for emoticons, but are something else, according to the UNICODE standard, are weirder than that… for example, the world-famous U+1F4A9 PILE OF POO, which, according to UNICODE, looks like this:

U+1F4A9

and, according to apple, looks like this:

U+1F4A9

i can think of a few select circumstances where the PILE OF POO glyph might be actually useful, and a whole bunch more that would definitely be silly, but why it got included in UNICODE is so far beyond my understanding that i am totally baffled.

SHELLSHOCK UPDATE

Shellshock: ‘Larger scale attack’ on its way, warn securo-bods

Apple FINALLY patches the ‘don’t worry’ Bash Shellshock vuln

Apple Releases Patches for Shellshock Bug


Every Mac Is Vulnerable to the Shellshock Bash Exploit: Here’s How to Patch OS X
— i upgraded from v.3.2.51(1) to v.3.2.53(1) according to their directions for pre-mavericks computers, and, according to the test i posted last week the system is no longer “vulnerable”, but, because of the fact that it doesn’t actually give a response other than “this is a test”, i can’t tell for sure whether or not they’ve actually patched shellshock, or whether they have just turned off the error message… it would be really nice if i could just upgrade to the current GNU release, which is v.4.3… this is why i am no longer a mac-head… 😐

Apple patches "Shellshock" Bash bug in OS X 10.9, 10.8, and 10.7

SHELLSHOCK UPDATE

Firms BASH Bash bug with new round of Shellshock patches

Cisco splats Bash bug in busy swatting season

i’ve run three rounds of security updates in the past three days, and bash was updated in every one of ’em… eventually they’re gonna fix it for real… maybe i’ll just revert to using csh… or zsh (which was written by paul falstad, my former manager and coworker at openwave) 😐

SHELLSHOCK UPDATE

UPDATE: Bash Vulnerability AKA SHELLSHOCK

The ‘Shellshock’ Bash vulnerability and what it means for OS X

Apple: Most OS X users safe from ‘Shellshock’ exploit, patch coming quickly for advanced Unix users — which, of course, is a blatant falsehood… all macs are as much at risk as -x was, and -x had a patch yesterday… this is why i am no longer a mac-head… 😐

Apple working on “Shellshock” fix, says most users not at risk [Updated] — which includes the following information:

Mac OS X uses version 3.2.51.(1) of GNU bash, released in 2007; the current GNU release of the shell is bash 4.3. However, the current version is released under the GNU Public License version 3 (GPLv3). Apple has avoided bundling GPLv3-licensed software because of its stricter license terms, even dropping the open-source Windows networking service Samba from OS X server in 2011 because Samba had shifted to a GPLv3 license. Therefore, although patches for the vulnerability have now been pushed out for most open-source operating systems, Apple executives may feel they have to have their own developers make modifications to the bash code.

this is the explanation why i haven’t been able to get SAMBA to work on my mac… grumble, mutter… 😐

Still more vulnerabilities in bash? Shellshock becomes whack-a-mole