told ya so… 8P
it doesn’t completely work the way i want it to, yet, but it was 2% working yesterday, and today it’s back to 95%
while i’ve got my email back, it’s not completely working yet, and i’m still having to deal with peculiarities with which i’m not exactly familiar. they’re peculiar enough that, it’s my professional opinion that they may be caused by demons, and may work themself out on their own eventually… one of my email accounts apparently uses a password i don’t remember. gramps works, but it still thinks the media is on the non-existent disk… i still don’t have the fonts straightened out…
but it’s one hell of a lot closer than it was yesterday, when i didn’t have the task bar icons that i usually have, and the K-menu icons that i usually have, and my email didn’t work… and i didn’t even have to convince it to mount the big hard disk, which wasn’t even showing up as being capable of mounting until i jumped through a 3-step hoop in order to mount it, yesterday…
it’s fixed enough that i am not even worried about going to bellingharm tomorrow, but i probably won’t spend the night.
UPDATE 10:30 pm i got email working. it was a combination of trying things in a new way, and demons in the pipes. i’ve even got my sigrot working, although i don’t know whether cron is taking care of running it every 5 minutes. also i got dropbox working again. now all i gotta do is figure out where my fonts went to…
for a couple of years now the fan in my computer has been making an evil buzzing noise when i first turn on the machine. i discovered that if i take a bottle of canned air and squirt it into the fan, it stops… after a while…
fast forward a couple of years, and multiple cases of canned air from costco (i.e. at least 10), and it’s actually been taking longer and longer to get the fan to quit buzzing, and the buzzing has been getting more loud and evil sounding, especially since i re-oriented the box, so i finally decided to open it up and see if i could fix it.
i found a lot of dust… which i cleaned out outside, because i’ve had previous experience with trying to clean dust out of a computer while inside, and it results in making everything taste like the inside of a computer for a couple of weeks… 😛
but it didn’t stop the buzzing, so i broke down and bought a new fan.
it cost me $9.00. 😐
i don’t know why i don’t just put my computer in a place where it’s relatively easy to disconnect and clean, apart from general laziness and lack of caring, and i wonder about the habit i have of stacking stuff on top of the computer, and/or putting it in obscure, difficult to remove places even more when the solution to my problem ALL ALONG cost me less than $10.00… 😐
i’ve been working in the computer industry long enough that i should have known it was going to turn out that way… 😐
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
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) 😐
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