**** Cyborg Central ****

Old Androids Never Die, They Just Have A Few Screws Loose

Same Shit, Different Environment

September 21, 2016

If I worked the way I am being expected to vote, I wouldn't have a job, since #1 and #2 both are horrible choices.
Actually, it's pretty similar: #1 is horrifically corporate, very susceptible to viruses, sloppy, easily hacked, and most people hate how it works, but think supporting it should be mandatory.

#2 is all flash and no substance, self-aggrandizement and ego, paired with one-sided draconian policies resting on top of exploitation of other people's work. Moreover, take the fancy plastic off and inside is exactly the same shit as #1.

Don't expect me to fix your computer, or your government, if you can't admit that you willingly picked something broken.
I've been third party for DECADES and it's worked just fine for me so far. I don't need to support you.

So I won’t Forget

September 5, 2016

Need to run the Windows plugins for Flash or Silverlight on Ubuntu?

Try Pipelight. I used this to watch the 2016 Olympics and it worked really well, just don't have more than one going at once. ;)

Sharing Files In Snaps

August 30, 2016

Since I figured part of this out, I felt like I'd share it.

To use the 'content' interface to share files, you need to have special YAML in both the consuming snap and the producing snap. These dictate which paths are shared, and where they show up in the consuming snap's file space.

In the producing snap's yaml, add:

        interface: content
        read: [ path1, path2 ]

This goes in the TOP LEVEL of the yaml. Then, in the consuming snap, you have to add a similar block to the top level there:

        interface: content
        target: producer-mount

Note that the consuming snap MUST have a directory to serve as a mount point for the producer's files, and you have to create this yourself. I have just been using a directory containing a directory, and this yaml at the bottom of the parts list:

    plugin: dump
    source: mountpoints

Then, just have mountpoints/producer-mount in there, and it should all just work.

My Olympic Taekwondo Cheering List

August 18, 2016

I'll be updating this post all weekend.


Jade Jones - 12-4, 7-2, 9-4, 16-7 GOLD medal!!! :D
Lee Dae Hun - 6-W, lost in QF 8-11, Repechage 14-6
BRONZE medal!


Lutalo Muhammed - 14-0, 9-2, 12-7, 6-8 Silver! (Ouch though!)
Paige McPherson - 5-6 :(


Mahama Cho 12-6, 3-3 GP, 1-4 loss, 4-5 :(
Jackie Galloway 5-0, 0-0 Decision, 0-0 Decision loss, 2-1 BRONZE medal!
Bianca Walkden 14-1, 5-0, 1-1 GP loss, 7-1 BRONZE medal!

How to handle ST partitions on Ubuntu

July 22, 2016

If you are using an SD-based hard drive with your Atari ST, it is very easy to move files back and forth from Ubuntu using the mformat/mcopy/mdelete/etc series of commands. The magic option is -i; this allows you to specify an image to be used as a FAT disk, and is smart enough to understand the Atari ST disk format.

In my case, when I attached my SD card to my workstation, it appears as /dev/sdc, with four 256mb partitions. Mounting these is difficult if you are using a TOS 1.0 compatible disk format, which is the only thing my first-run Atari 1040 STF understands. It was easy to copy files, though:

$ sudo mcopy -s -i /dev/sdc1 * ::

The command must be used under sudo to write to the device. the :: represents the root of the FAT filesystem; if you want to copy files to a subdirectory, or copy from the Atari back to Ubuntu, just format your paths like this:

::/folder/file <-- is DISK:/FOLDER/FILE

Ubuntu makes it incredibly easy to sling ST files around, too. Want to extract the files from an image? Just do:

$ mcopy -s -i IMAGE.ST :: .

It will pull the files right out.

July 10, 2016

I'm fed up with talking about this on Facebook, but I need to vent, so I am going to post here instead.

DNC voters, and more specifically, Hillary Clinton supporters, must thrive on cognitive dissonance. How anyone can support someone so completely careless with classified information, who so strongly condemned people who've exposed illegal acts on the part of the government, is just beyond me. It's willful ignorance, and arrogance to expect people to just go along with it because Trump is soooooo scary to them.

ESPECIALLY when there has been a much better candidate all along.

The last thing I am going to do is reward a bunch of self-serving baby boomers and their toadies with my vote.

She damn well knew she was breaking the law.  I can point you to the fucking email where she did it. Willful. Ignorance. There is literally no other reason.

And yet, these kneebiting idiots will stand there and defend her while she lies through her teeth, saying that "the alternative is too scary."

There's more than one alternative, dipshits!!!!!!


June 28, 2016


linux (4.2.0-42.49) wily; urgency=low

[ Ben Romer ]

* Release Tracking Bug
- LP: #1597053


That feels pretty good.


June 11, 2016

I really don't like flying. Or being dependent on someone else for my safety.

Oh the things I do for Ubuntu....


May 17, 2016

Is multitasking really that hard?

One of the things I've been thinking about a lot is how we've gone from single-program 8-bit computers to these huge, powerful multiprocessor systems, but the method of working with them has gone full-circle back to the single-program interface.

Phones, tablets, and even the ugly but commonplace Windows UI have all thrown up their hands and given up on windowing and moved to a simpler, one-screen-one-task interface. For someone like me who finds it easy to multitask, the UI is incredibly frustrating, but for the average person, it seems like this is about what they can handle, so they like it.

What happened?

Back in the 90s, the PC and Mac were taking tentative steps out into true multiprogramming, the NeXT and Amiga were already there, but only NeXT had realized that screen real estate was essential to having a good multiprogram GUI. At some point we hit the line where more resolution didn't help.

The same went for OS isolation - we were doing pretty good with multiprogramming, then virtualization came, and we gave up on that. Then even that was too heavy and containers came.

We just can't get away from the one computer per app model. It's just TOO HARD. Apparently.

So I wonder: at what point do we throw away everything but hardware-provided multiprogramming and just go the fuck back to the actual one-computer-per-app setup? Do we strip Xen down to the bare bones and just run DOS? or EFI?

How shit is that?