Show newer

mild vent 

My home's 'Net service is randomly disconnecting again, and now Mastodon is freezing & crashing. I guess I should be thankful it isn't eating enough load to overheat my CPU like TweetDeck does.

Show thread

mild vent 

I've been irritable all day, & I have no idea why. It wasn't just programmer news, but that didn't help. I think most of it was seeing a brand new error during a support call, on site in a hot room. It was so hot that stepping outside into the Summer sun actually cooled me down.

@softgoat Sounds like just X crashed, but I can't see how an almost-drained battery would cause that.

BRB, making illegal copies of the software sheriff. (wrt lb)

@squirrel Sounds like the state of typewriters: When the instructions become separated, locked away, or lost, collective knowledge of how to use them is forgotten.

iliana's linux pro tips 

put a directory named aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa in /home that just has 250000 empty inodes in it

that way, when you accidentally run "rm -rf *" in your home directory, you have a chance to ctrl-C it before it deletes anything important

Microsoft announces first new feature to be added to github after their acquisition

This won't shake the programming world to its very core at all, no-sir-ee! Microsoft and GitHub are talking about selling GitHub to Microsoft. businessinsider.com/2-billion-

pda 

@squirrel without nearly as much retro win as your night is going. That's awesome. :3

Hmmm. This is a shortcoming of Mastodon: If a profile spammer follows you from another instance, then when the other instance's admin deletes the account, no unfollow propagates. I have a spammer ghost following me.

How? Well, FreeBSD's chown(8) manpage says this about -R:

Change the user ID and/or the group ID of the file hierarchies rooted in the files, instead of just the files themselves. Beware of unintentionally matching the ``..'' hard link to the parent directory when using wildcards like ``.*''.

Guess what matched & why it took so long.

Show thread

Remembering that time I discovered an upward directory traversal bug in a NextStep version of the chown command & wound up owning several dozen user accounts without ever touching a keyboard.

Somehow, my home dir wasn't owned by me anymore, so a sysadmin got root & ran `chown -R arielmt *` in my home dir, but the other user still owned dotfiles, so the sysadmin ran `chown -R arielmt .*` & took a long time to notice it was taking too long to run.

LB reminds me of the customers who wanted me to repair their desktop PC after they pulled straight out on the CPU heat sink with so much force that, when the CPU pins finally gave, the still-locked ZIF socket came part-way off the motherboard.

Show older
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!