linux

I spent a good amount of time learning Golang (Go, but since using two letters in any form of a search usually is an exercise in futility). My goal was fairly simple, I wanted to display some system statistics via HTTP by reading them directly from /proc. I saw that Golang had a module in the standard library call "syscall" and I decided that it might be fun to give that a try.

I’m very excited that GNUTLS has support for ed25519 keys, these keys are faster, smaller, and more secure than RSA keys. I found this out from a developer’s blog while doing research and messing around with CA’s in December. The reason I’m writing this is that GNUTLS 3.6 has been made available in Fedora 28, therefore can all use this. Additionally and perhaps more importantly we gain the the ability to use TLS 1.

I have a workstation that I have built, it contains a multi-disk Large Form Factor ZFS array. There have been multiple posts in the past about some of my disk related problems that I’ve handled, you should be able to find them with a ‘zfs’ or ‘disk’ tag. Well I had several issues, that I hope should be calming down; going back to January, where I decided to move from 4x3TB RAID-Z (software RAID 5) to 4x4TB 7200RPM RAID 10 setup.

====== urxvt vs Eterm ====== So I was trying different terminals so that I can keep on terminal just for a screencast sessions. I want to keep screencasting clean and partitioned. Additionally I have admitted to myself (now everyone else) that I need to know more about profiling the system, I got [http://www.brendangregg.com/books.html](Breddan Gregg’s book ) on system performance, so far its very through. One complaint is that as a Solaris guy and even regarding many of his Linux presentations and writings is that he really favors dtrace, for obvious reasons; its a fantastic tracing tool.

As rain falls from Hurricane Matthew, I can’t split wood or I have started to work on some items, and have recorded various thoughts. I started to look at the failure of the btrfs volume, this truly appears that the failure was not hardware related; instead it is just corrupt checksums. I ran two SMART tests on all of my hard drives, none of them (I paid particular attention to the drives mentioned that were corrupt) had failed any tests.

====== options, arguments, or parameters ====== Where I am currently employed there has been, in my opinion, an over application of the term “parameter”. Or at least from where I have been in the past. I have always thought that for example: example -x test.txt -x would be a switch, and the option after -x, test.txt, would be argument. But it seems here or recently we apply the term parameter to everything.

====== Standardization ====== I am sure many of us have seen the xkcd comic “Standrads", if not check it out, its kinda funny. I have been thinking about the debate and later burden that we seem to impose on ourselves through well intended standardization. This came around when there was a discussion at my full time employer about standardizing a spaces around the text and brackets only_if {node.fqdn.upcase =~ 'PROD'} compared to only_if { node.

Powershell Linux debut I began to experiment with Powershell. I feel that Microsoft has to follow through on showing the community that it meant what it said, that Microsoft Loves Linux. Perhaps I can lump myself into that group too, because I remember the October Document, and the utter frustration in trying to get Linux to work in a mostly Windows environment. I think Microsoft senses that the game is changing, and is changing with it.