# Content tagged Linux

Our Bodies, Our Hearts, Our Software
posted on 2016-08-23 22:10:04

I don't really keep up with the various Linux conferences that happen now and then, but I certainly follow various free software planets, which generally filter the good stuff out for me anyway.  Something that slowly made it through my filters recently was Karen Sandler's keynote address at the Australian Linux Conference, where she, unsurprisingly, talked about the importance of FOSS software.  The part that was surprising, though, and really hit home for me, was when she started talking about her internal defibrillator.

Apparently, Karen has an abnormally large heart, in the physical sense.  She is at risk of suffering what her doctors called "sudden death," which means she could simply die with no warning.  Luckily for her, there is a great treatment in the form of the internal defibrillator - a small device that can be wired directly into her heart that will issue a shock to restart her it if she suddenly, well, dies.

I'm going to take this moment to urge you to go watch the video, it's a bit long, but listening to her talk about her own heart is going to do more for you than I can manage.

For those of you not watching the video, there are two scary parts.  First - when she talks about being at risk of sudden death.  The second is the sequence building from her cardiologist not knowing much about the device he was offering to implant to the point where he hangs up on her in frustration.  His frustration came from her desire to see the code running on the device he wanted to put in her, the company's unwillingness to show her the code, and his lack of understanding about why that's important.  If you're wondering why this sort of thing is important at all, it's because this machine is wired to her heart.

## What we put into our bodies...

When we go out to dinner somewhere, we expect to be told what's in our food if we ask, we expect to know what's in the drugs we take, so why shouldn't we expect access to what's in the devices implanted in our bodies?

Let me phrase it another way.  A company makes an electric heart that you need because yours was stabbed like Jean-Luc Picard was in Star Trek.  You get it and want to know what makes you tick, and they tell you that your heart is their intellectual property and you're not allowed to know how it works. Furthermore, you're not allowed to modify it, open it up, or see its source code.  There's a well-known bug in it?  There's a firmware update?  You might not get it if it doesn't make money for the company.  You want to install it yourself?  That might be illegal depending on the time of year and what phase the moon is in.

When Karen told her story, her concerns were that she couldn't check the logic of her device, herself, nor could she have a friend or consumer-advocacy group do it.  Four years ago, when I started writing this, that was where the story ended.

## Things that come out of our bodies

A few weeks ago, I came across this article, which I thought might be a bout Karen, again.  I opened it, hoping to read more about her and, hopefully, what progress she had made.  Instead, I learned about a brave, new person taking up this baton, because the same problems were still around.  It turned out that, on top of Karen's original concerns, people were now taking data from Marie Moe's device and refusing to give her access to it.

At first, as I read that they were collecting the data, I hoped it was available to her.  Wouldn't that be cool?  I could make graphs of my heart rate, if I had that data.  But they seemed to think that the data was theirs.  Her doctor seemed to be too busy to help her get at it either, which isn't surprising.  To me, this feels like going into the doctor to get the results of your blood work and being told, "I can't show you the numbers, but your cholesterol is fine.  The company owns your iron levels, but you aren't anemic."

There's an old maxim that is often forgotten or ignored that you don't own anything you can't take apart.  Warranties are nice, but when farmers can't repair their own tractors you start to see why user serviceable parts, even skilled- or trained-user serviceable parts are important.  In a world where any data that's collected is often sold and firmware updates come twice a year and stop as soon as the new model comes out.  People with implants are at an ever greater risk of losing control of their body parts RoboCop-style.  Malfunctions happen, and a thriving, open community is a great way of keeping the process more transparent and hopeful for everyone.  I would hate to have a malfunctioning defibrilator in my chest and have nowhere to turn, once the company tells me it's outside warranty or the like.

Yet Another DeDRM afternoon
posted on 2015-02-12 22:12:00
Today, I agreed to my first programming job! More on that another time. To celebrate, I got myself a copy of "Effective Javascript" by David Herman.

I decided to give Kobo a try, having been repeatedly disappointed by Barnes and Noble, and not having a Kindle. I thought Kobo was supposed to be DRM-free. I'm not entirely sure how I thought they were doing that when everyone else is trying to lock you into a books-as-a-service ecosystem, but I did.

In any event, it came wrapped in gross Adobe Digital Editions DRM. So, I just spent the last hour stripping it off and then deleting my Kobo account. To save any of you the trouble I went through, here's some links that were useful in a sea of not-useful stuff.
Clearing up some free space
posted on 2015-01-13 18:28:00
Every now and then, I get notifications on my laptop that the root partition is running out of space. That's because I made a rather small root partition for Fedora to run on when I upgraded to a SSD 1 that was smaller than my older, spinning disk drive.

One of the fist places I look for wasted space is /var, because I know that yum/dnf keep caches there and systemd keeps the system log there, too.

Usually, there's a rather large log sitting in there, for some reason. Today, there was about 950MB of log sitting there. I searched around a little and found that you can edit the configuration for the system log daemon at /etc/systemd/journalctl.conf. There's a configuration option called SystemMaxUse that you can set to something small, like 16M or 100M, depending on how generous you're feeling and how much you like logs, and it should max out at that much space.

Sources: A blog post and a stackexchange post.

## Footnotes:

1Solid State Drive

Multiple Cursor Mode
posted on 2013-09-26 15:35:00
In case you haven't already tried it, Multiple Cursor Mode for emacs is awesome. I actually got chills the first time I used it to edit multiples lines of work on a physics problem. All those repeated lines of LaTeX code, and now I can change them all at once!

It's in Marmalade, so go try it out!
No Gods, No Bosses
posted on 2013-06-14 00:17:17
Andy Wingo from Igalia has started writing about the company and their cooperatively run organization on his blog.  It's interesting both because of the exciting way they organize and run themselves, but also in the language Andy chose to use to talk about them.

Nobody likes to talk about Anarchism these days, and people who use its lexicon are usually buried in the media, as the recent Occupy movement was.  It's an immediate red-flag, and I know I intentionally avoid using words like "revolution" and even calling Anarchism by its name because I think people will just shut off and stop listening to me if I say them.  I find this sad, and I'm sadder still that I self-censor in this way, because there are important things to say, that I care dearly about, which use these words.

What I mean to say is that I really appreciate both the content of Andy's posts and how he chose to write them.  it makes me feel a little braver, a little more comfortable with something that is part of who I am and what I believe, and safer bringing it up in public.

You can find the introduction here and the first part here.

And for something fun and related, here's some Chumbawamba!
Unbricking a Buffalo WZR-HP-G300NH
posted on 2012-08-21 22:12:00
This general thing has been posted around a fair bit, including here and here.  I don't recommend going to them, because they are long and rambly, but they did help me fix my problem.  I'm going to include the instructions for flashing firmware on linux with tftp, as much so I can remember next time I brick the router.
Rooting the nook color
posted on 2011-10-01 15:55:35
When I graduated recently, I got a nook color as a present from a thoughtful family member who saw an article about rooting them in the paper and realized that was something I would probably enjoy. While I do very much enjoy the rooted nook, I the actual rooting process has been a bit of a pain for me. A few days ago, my nook started boot-looping, and I was forced to reset and re-root it yet again.

Instructions for rooting the nook with the 1.2 version of its software can be found here.

When flashing the clockwork recovery to an sd card, I need to use my phone as a card reader. This is annoying because it works best with my phone in recovery mode, and therefore takes my phoneout of comission  while I'm flashing the disk image. The other annoying thing is that I've found I need to flash the image to the raw device with dd, which goes slower than flashing to a partition. I assume this is to get some boot flag on the base partition. This means I flash the image with
dd if=1gb_clockwork.img of=/dev/sdb