One of the things coming in Go 1.11 is (experimental) support for 'vgo' package versioning ; youcan read some (in-progress) documentation here and here .One of the reasons I'm looking forward to projects adopting it isthat it holds great promise for cleaning up my $HOME/go/src tree.

The problem with my $HOME/go/src currently is that it minglestogether programs (and sometimes packages) that I'm actively usingand tracking along with

In theory today (July 24th) is the start of a HTTP apocalypse,because Google has launched Chrome 68 and Chrome 68 labels allHTTP sites as 'not secure' .More exactly, it adds a 'not secure' label to the URL bar (oromnibox, if you prefer that term). It's possible that Firefox willfollow now that Chrome has led the way on this and in any caseChrome apparently has about 60% of the browser market, so itsdecision

We have a set of Python programs that are the core of our ZFSspares handling system . Theproduction versions are written in Python 2 and run on OmniOS on our ZFS fileservers , but we'removing to ZFS-based Linux fileservers, so this code needed a tune-upto cope with the change in environment. As part of our decisionto use Python 3 for future tools ,I decided to change this code over to Python 3 (partly because Ineeded to write some completely new Python code to handle

So I tweeted :

It's impressive how many different executable file formats Windowshas.

(I care because our email system wants to reject top-level attachmentsthat are Windows 'executables' and boy is the list getting long.)

I put 'executables' into quotes in this tweet because many of thesefile formats (or more exactly file types) are not binaries; insteadthey're text files that Windows will feed to various things thatwill interpret them in ways that you don't want. Typical

I tweeted :

One problem with a HiDPI monitor is the occasional application thatabsolutely doesn't upscale. For example, the Java that I need toaccess the KVM-over-IP console of this locked up NFS fileserver.

Our current fileservers are oldenough Supermicro machines that their onboard IPMIs only supportKVM-over-IP through a Java Web Start application. Today,I needed to use it from home, and I was only a little bit surprisedwhen the resulting virtual console was, well, tiny on my

If you have ZFS based NFS fileservers you're normally supposed tohandle setting up NFS export/sharing permissions through ZFS bysetting and updating the sharenfs property on ZFS filesystems.ZFS then worries about keeping the system's NFS export permissionsin sync with what (ZFS) filesystems you have mounted, where youhave them mounted, and what their sharenfs settings are. Thereare all sort of convenient aspects of this and it's what we've donefor years on our current fileservers .Unfortunately this is not

As part of our move from OmniOS based fileservers to ones based on Linux, I'verecently been looking into how to map our current NFS exportpermissions into Linux's NFS export permissions . As part ofthis I've been looking into the similarities and differences betweenthe Linux model of NFS export permissions and the Illumos one . The end results you can getare mostly similar (with one difference that may matter for ussomeday), but Linux gets there in a significantly different way.

To simplify a bit

For my sins, I use a number of third party 'out of kernel' kernelmodules in my Fedora kernels, especially on my office workstation . I don't use a binary GPU driver, but there's thelatest git tip of ZFS on Linux , VMWare 's kernel modules, and an out of tree it87module in order to support mymotherboard's sensors ( for as long as that keeps working ).Usually this works fine. Usually. For the past few days, my

Perhaps at one point I fully understood Solaris and thus Illumos NFS export permissions (but I suspect not). If so, that understanding fell out of my mindat some point over the years since then, and just now I had theinteresting experience of discovering that our NFS export permissionshave sort of been working by accident.

I'll start with a ZFS sharenfs setting and then break it down.The two most ornate ones we have look like this:

sec=sys,rw=nfs_ssh,ro