<< >>
justin = { main feed , music , code , askjf , social , pubkey };recent comments
It seems you are looking at this page. Would you like to hear some music?

yes | no
November 20, 2017
macOS High Sierra Gatekeeper malfunction and repair

I'm posting this so that google will find it in case anybody runs into this issue:

I installed macOS 10.13 fresh on a laptop, then migrated my 10.12 system (which had been updated from a 10.10 install previously) using the migration assistant to the new computer. Everything was great, except when I tried to mount downloaded .dmg files, I would get this:

"(disk image name)" is damaged and can't be opened. You should move it to the Trash.
My immediate response was: noooo what happened to our build process? Then I realized it was just this computer.

I found this article, tried using "sudo spctl --disable-master", which was a workaround, so apparently it was GateKeeper. I also tried replacing /var/db/SystemPolicy as described, with no luck.

After some hours of debugging I found that /var/db/gkopaque.bundle was invalid, and by replacing it with the contents of a working system's copy, and executing "sudo killall syspolicyd", the issue was resolved.

There you go. Also: apple -- Migration Assistant maybe should correctly copy that? Or the code that reads the gkopaque.bundle sqlite database in Security.framework should at least gracefully handle the error, rather than throwing an exception which causes assessments to all fail with an error?

Oh also I tweeted with more detail during the last part of this, but not really worth reading.


November 15, 2017
super8 lengthy


Nov 11 2017
no straw to draw

November 8, 2017
super8 sore


Nov 07 2017
the tadzios all hail the homunculus demo

Nov 06 2017
the tadzios fit me on your tongue demo v2

November 2, 2017
super8 rehearsal [or something]

1 Comment

Nov 01 2017
the tadzios silly boy demo v2

Oct 23 2017
record it later

October 20, 2017
super8 improv rehearsal

(these rehearsals are for a show in January, woohoo)


Oct 19 2017
say goodbye to yourself
cant be left alone

October 19, 2017
super8 improv rehearsal


October 16, 2017
super8 improv rehearsal


Oct 12 2017
oh the bios

September 28, 2017
super8 improv rehearsal


Sep 17 2017
user error with chris supervision

September 13, 2017
super8 improv rehearsal


September 7 2017
super8 improv rehearsal


Sep 05 2017
haunting something

September 4, 2017
super8 improv rehearsal


September 3, 2017
super8 improv rehearsal


Aug 31 2017
im invisible

Aug 23 2017
kiss goodbye
broken horse

Aug 07 2017
this is windows update

Aug 04 2017
another day another template

Jul 21 2017
you think im crazy
river of sorrow
no news

July 20, 2017
super8 improv rehearsal (flashing lights warning, oops)


Jul 18 2017
no business

Jul 17 2017

July 13, 2017
the lowest end

To follow up on my last article about Linux on the ASUS T100TA, I recently acquired (for about $150) an ASUS C201 Chromebook, with a quad-core (1.8ghz?) ARM processor, 4GB RAM, and a tiny 16GB SSD. This is the first time I've used a Chromebook, and ChromeOS feels not-so-bad. I wish we could target it directly!

...but we can't! At least, not without going through Javascript/WebAssembly/whatever. Having said that, one can put it in developer mode (which isn't difficult but also is sort of a pain in the ass, especially when it prompts you whenever it boots to switch out of developer mode, which if you do will wipe out all of your data, ugh). In developer mode, you can use Crouton to install Linux distributions in a chroot environment (ChromeOS uses a version of the Linux kernel, but then has its own special userland environment that is no fun).

I installed Ubuntu 16.04 (xenial) on my C201, and it is working fine for the most part! It's really too bad there's no easy way to install Ubuntu completely native, rather than having to run it alongside ChromeOS. ChromeOS has great support for the hardware (including sleeping), whereas when you're in the Ubuntu view, it doesn't seem you can sleep. So you have to remember to switch back to ChromeOS before closing the lid.

So I built REAPER on this thing, fun! And I still have a few GB of disk left, amazingly. Found a few bugs in EEL2/ARM when building with gcc5, fixed those (I'm now aware of __attribute__((naked)), and __clear_cache()).

Some interesting performance comparisons, compiling REAPER:

  • C201 (gcc 5.4): 9m 7s
  • T100TA (gcc 6.3): 8m 45s
  • Raspberry Pi 3 w/ slow MicroSD (gcc 4.7): 28m
REAPER v5.50rc6 (48khz, 256 spls, stock settings), "BradSucks_MakingMeNervous.rpp" from old REAPER installers -- OGG Vorbis audio at low samplerates, a few FX here and there, not a whole lot else:
  • C201: 28% CPU, 13% RT CPU, 15% FX CPU, longest block: 1.5ms
  • T100TA: 22% CPU, 9% RT CPU, 10% FX CPU, longest block 0.9ms
(The T100TA's ALSA drivers are rough, can't do samplerates other than 48khz, can't do full duplex...)

Overall both of these cheapo laptops are really quite nice, reasonably usable for things, nice screens, outstanding battery life. If only the C201 could run Linux directly without the ugly ChromeOS developer-mode kludge (and if it had a 64GB SSD instead of 16GB...). Also, I do miss the T100TA's charge-from-microUSB (the C201 has a small 12V power supply, but charging via USB is better even if it is slow).

I'll probably use the T100TA more than the C201 -- not because it's slightly faster, but because I feel like I own it, whereas on the C201 I feel like I'm a guest of Google's (as a side note, apparently you can install a fully native Debian, but I haven't gotten there yet.. The fact that you have to use the kernel blob from ChromeOS makes me hesitate more, but one of these days I might give it a shot).


Jul 03 2017
oil (wip)

1 Comment

[ present 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ... past ]
search : rss : recent comments : Copyright © 2017 Justin Frankel : 1499224