You are here

Feed aggregator

SFE is Running on Backup Site

SFE Articles - Mon, 04/30/2018 - 13:12

(Article will be updated once new status is know) last updated: 20180430-1300GMT

Dear SFE Users!

Once a service goes down, you recognize how important the service is to people.

The backup site and _ALL_ IPS Repositories are online and operational. The domain name points to this new IP-Address, so no changes needed on your side.

The original machine serving is broken, but the service is *online* as usual from the backup site.
You do not need to change anything on your side, the DNS entry for has been changed to point to my own servers. The SFE package repositories are fully available.

Only limitation: Please do _not_ mirror the IPS repositories with pkgrecv right now. The available connection bandwidth doesn't allow this. The replacement machine will be strong enough to let you mirror if you really think so.

Current status is the following:
Friday 20180420 1300 UTC the blog site is back again on backup site No 1.
Saturday 20180422 2100 UTC _all_ IPS Repositories are running on backup site No 2 with 10MBit bandwidth
Saturday 20180428 new machine is up, zone created, now the real work begins :). I think it will take until mid of may to do a clean new setup, includes a trial concept for automatic failover to backup site. I don't want to get you and me into troubles.

One day I hope there will be volunteers helping to setup a "release repository" where packages are promoted from the development repos (those you currently know: localhost*** publishers9.
The task is to create a website with the packages listes and a mechanism to "vote" on those packages. Once a package receives two +1 and no -1 it gets promoted to the "release repo" (including dependencies).

If you had the publisher "disabled", then it time to enable them again: (choose your publisher)

pkg set-publisher --enable localhosts11
pkg set-publisher --enable localhosts12
pkg set-publisher --enable localhostoih
pkg set-publisher --enable localhostomnios

Thank you for your patience!

Thank you for using SFE packages!

And thank you for sending comments on SFE packages!
I would really like to know what you are doing with SFE packages! Waht do you need next?
(email: sfepackages at g mail dot com - or write a comment here - or write an articel on your blog site - or write on the mailing list)


Tags: outagSFE repositorysfe.opencsw.orgbackupbackup site
Categories: SFE

OpenIndiana Hipster 2018.04 is here

OpenIndiana Announcements - Sat, 04/28/2018 - 15:37

We have released a new OpenIndiana Hipster snapshot 2018.04. The noticeable changes:

  • Userland software is rebuilt with GCC 6.
  • KPTI was enabled to mitigate recent security issues in Intel CPUs.
  • Support of Gnome 2 desktop was removed.
  • Linked images now support zoneproxy service.
  • Mate desktop applications are delivered as 64-bit-only.
  • Upower support was integrated.
  • IIIM was removed.

More information can be found in 2018.04 Release notes and new medias can be downloaded from

Categories: OpenIndiana


Josef Sipek - Mon, 04/23/2018 - 19:59

This post is part of a series named “Europe 2017” where I share photos from my adventures in Europe during the summer 2017.

In late June 2017, Holly and I did a day trip to  Tallinn. This wasn’t the first time I was in Tallinn, so I knew what the interesting parts of the old town were. As always, there is a gallery with more photos.

Tallinn’s old town is a medieval pocket in a otherwise modern city. In some of the photos you can see the modern civilization right behind a medieval tower.

A view of the  Alexander Nevsky Cathedral from the tower of  St. Mary’s Cathedral:

The tower of St. Mary’s Cathedral:

A section of the fortification wall that remains:

I’ve been to Tallinn twice and all my time there was spent in the old town. This makes me far from an expert about what there is to do. With that said, I enjoyed my time there and I recommend a day trip to anyone visiting nearby.

Categories: illumos


Josef Sipek - Wed, 04/18/2018 - 18:17

This post is part of a series named “Europe 2017” where I share photos from my adventures in Europe during the summer 2017.

When I attended the Kaivopuisto Air Show in early June last year, I learned about the existence of the Finnish Aviation Museum. It took me a month and a half, but eventually I found a free day to go check it out.

The museum itself is packed with all sorts of aircraft on static display. While they were interesting (and I certainly took plenty of photos of them), they aren’t what this post is about. This post is about Lokki—a retired  DC-3 (registration OH-LCD) on display outside of the museum.

As luck would have it, the folks from the DC Association were there that day trying to see if they could start up Lokki’s engines—after 12 years of inactivity. After a lot of preparation, they managed to start them!

Without further ado, here are a few photos of Lokki (more photos can be found in the gallery).

 Aero OY was the original name of Finnair:

One of the mechanics working on the left engine:

One of the people from the DC Association, seeing that I was obviously excited about the plane, asked me if I’d like to climb inside. I said yes, of course.

The inside was pretty bare-bones (which is to be expected of a static display that’s normally closed to public). I took a couple of photos inside, but most weren’t that interesting.

Throttle quadrant (note: most of the instrument panel was removed long ago):

It runs!

The livery is pretty simple—polished aluminum with dark blue lettering and a stripe:

I’m not really sure why they wanted to see if they could start the engines, but I’m happy that it worked out. Radial engines just have a unique roar to them.

Anyway, that’s it about Lokki. Hopefully I’ll get around to post processing the photos from the museum itself soon.

Categories: illumos

Modern Mercurial - Phases

Josef Sipek - Sun, 04/15/2018 - 16:51

This post is part of a series named “Modern Mercurial” where I share my realizations about how much Mercurial has advanced since 2005 without me noticing.

Last year, I had a realization that I haven’t been using Mercurial to its full potential. In this post, I’d like to share my thoughts about and usage of Mercurial Phases.

Phases are not a new feature. They made their first appearance back in 2012 as part of Mercurial 2.1, which makes them a little over 6 years old.

What are phases?

While there is a description of phases on the Mercurial wiki, I’ll take a stab at a short intro.

Each commit belongs to one of three phases (public, draft, or secret) which implies a set of allowed operations on the commit. Furthermore, the phase dictates which other phase or phases the commit can transition to.

You can think of the phases as totally ordered (secretdraftpublic) and a commit’s phase can only move in that direction. That is, a secret commit can become either a draft or a public commit, a draft commit can become a public commit, and a public commit is “stuck” being public. (Of course if you really want to, Mercurial allows you to force a commit to any phase via hg phase -f.)

The allowed operations on a commit of a particular phase are pretty self-explanatory:

Public commits are deemed immutable and sharable—meaning that if you try to perform an operation on a commit that would modify it (e.g., hg commit –amend), Mercurial will error out. All read-only operations as well as pushing and pulling are allowed.

Secret commits are mutable and not sharable—meaning that all modifications are allowed, but the commits are not pullable or pushable. In other words, a hg pull will not see secret commits in the remote repository, and a hg push will not push secret commits to the remote repository.

Draft commits are mutable and sharable—a phase between public and secret. Like secret commits, changes to commits are allowed, and like public commits, pushing and pulling is allowed.

Or in tabular form:

Phase Commits Sharing public immutable allowed draft mutable allowed secret mutable prevented

By default, all new commits are automatically marked as draft, and when a draft commit is pushed it becomes public on both ends.

Note that these descriptions ignore the amazing changeset evolution features making their way into current Mercurial since they can blur the “not yet shared” nature of draft commits. (Perhaps I should have titled this post Modern Mercurial (2012 edition) — Phases.)

A note about hg log

Unfortunately, the default hg log output does not display phases at all. I think this is rather unfortunate (but understandable from a backwards compatibility point of view).

Last year, I dedicated a whole post to how I template hg log information including my reasoning for why I display phases the way I do.

How do I use phases?

Now that we have the basic introduction to phases out of the way, let me describe how I mapped them to my workflow.

First of all, I make all new commits start in the secret phase (instead of the default draft) with a quick addition to .hgrc:

[phases] new-commit = secret

This immediately prevents an accidental hg push from pushing commits that I’m still working on. (Recall that secret commits cannot be pushed.) In at least one repository, this allowed me to regularly have more than 6 heads with various work-in-progress feature ideas without the fear of accidentally messing up a public repository. Before I started using phases, I used separate clones to get similar (but not as thorough) protections.

Now, I work on a commit for a while (keeping it in the secret phase), and when I feel like I’m done, I transition it to the draft phase (via hg phase -d). At that point, I’m basically telling Mercurial (and myself when I later look at hg log) that I’m happy enough with the commit to push it.

Depending on what I’m working on, I may or may not push it immediately after (which would transition the commit to the public phase). Usually, I hold off pushing the commit if it is part of a series, but I haven’t done the last-chance sanity checks of the other commits.

Note: I like to run hg push without specifying a revision to push. I find this natural (and less to type). If I always specified a revision, then phases wouldn’t help me as much.

“Ugly” repos

I have a couple of repositories that I use for managing assorted data like my car’s gasoline utilization. In these repositories, the commits are simple data point additions to a CSV file and the commit messages are repetitive one-liners. (These one-liners create a rather “ugly” commit history.)

In essence, the workflow these repositories see can be summarized as:

$ echo "2018-04-05,12345,17.231," >> data.csv $ hg commit -m "more gas" $ hg push

In these repositories, I’ve found that defaulting to the secret phase was rather annoying because every commit was immediately followed by a phase change to allow the push to work. So, for these repos I changed new-commit back to draft.

Edit: I reworded the sentence about Mercurial giving you a way to force a commit to any phase based on feedback on

Categories: illumos

Kaivopuisto Air Show 2017

Josef Sipek - Thu, 04/12/2018 - 17:55

This post is part of a series named “Europe 2017” where I share photos from my adventures in Europe during the summer 2017.

In early June 2017, we attended an air show in  Kaivopuisto. Unfortunately, we found out about it last minute, and so we missed the beginning which included a Finnair Airbus A350 flyby. Pity.

The show included a number of trainers and combat aircraft performing various maneuvers. Here are the highlights (for more photos visit the gallery).

 Red Arrows:

A seagull joining in:

 Finnish Coast Guard’s  Turva nearby with  Suomenlinna visible behind it:

 Eurofighter Typhoon:

 Saab 35 Draken:

 Saab Gripen:

During one of the passes, I took a burst of images and then assembled them into a Southwest 737 “Airportrait”-style image.

Finnish Air Force  F-18 Hornet:

A Finnish aerobatics team  Midnight Hawks flying  BAE Systems Hawk:

Even though this post has more photos than I typically share, there are many more in the gallery. So, if you are into airplanes, I suggest you peruse it.

Categories: illumos

The Workbench 2018-04

SFE Articles - Mon, 04/09/2018 - 12:32

Quick note, more updates on this article will appear soon.

Now available: pdftk for Solaris 11!

pdftk 2.02 from ist now available for Solaris 11 (version 11.3)!

You can merge, split or watermark PDFs from the command line.
To build the package it was necessary to enhance the GCC 4.9.4 package with the Java compiler "gcj".
For OpenIndiana Hipster the compile run is is not yet clean (iconv symbols missing).


Tags: workbench20182018-04pdftk
Categories: SFE

Juhannus 2017

Josef Sipek - Fri, 04/06/2018 - 19:17

You may have noticed that I was a bit quiet during the last summer. I have a really good reason for it: I spent five months in Helsinki for work. On weekends, Holly and I got to explore, which led me to accumulate approximately 12000 photos. Sadly, I am quite behind on post processing them all, but I will get through them eventually.

This post is about how I spent  Juhannus last year.

Juhannus is the name of the Finnish summer solstice holiday. It is a time to relax, spend time with friends and family, and enjoy oneself. Every year, a nearby island,  Seurasaari, has an afternoon and evening with an assortment of traditional events and bonfires.

There is of course a gallery of my photos.

Every year, one couple is selected to have their wedding on Seurasaari during Juhannus. Here is 2017’s lucky couple:

Before about half a dozen bonfires are set ablaze, a number of “can fires” is lit:

The largest bonfire gets lit by the newlyweds—from a boat:

I’m not sure how exactly the big bonfire pile was constructed, but it didn’t take long for it to grow:

So, that was Juhannus on Seurasaari in 2017. It was a nice and relaxing afternoon and evening, and if I happen to be in Helsinki around Juhannus in the future, I’ll likely spend the day on Seurasaari.

I’m going to end this post with a bit of Finnish (from because languages can be fun:

– Kokoo koko kokko kokoon!
– Koko kokkoko?
– Koko kokko.


– Assemble the Midsummer bonfire!
– The whole Midsummer bonfire?
– Yes, the whole Midsummer bonfire.

(I’m told that kokoo is a dialect form of kokoa.)

Categories: illumos

libvncserver: fix CVE-2018-7225

github/OpenIndiana/oi-userland - Thu, 04/05/2018 - 16:23
libvncserver: fix CVE-2018-7225
Categories: oi-userland

nodejs-6: update to 6.14.0

github/OpenIndiana/oi-userland - Fri, 03/30/2018 - 22:30
nodejs-6: update to 6.14.0
Categories: oi-userland

nodejs-8: update to 8.11.1

github/OpenIndiana/oi-userland - Fri, 03/30/2018 - 16:03
nodejs-8: update to 8.11.1
Categories: oi-userland

openssl-1.0.2: update to 1.0.2o

github/OpenIndiana/oi-userland - Thu, 03/29/2018 - 19:12
openssl-1.0.2: update to 1.0.2o
Categories: oi-userland

icu: fix CVE-2017-15422

github/OpenIndiana/oi-userland - Thu, 03/29/2018 - 16:00
icu: fix CVE-2017-15422
Categories: oi-userland

Remove gnome-desktop

github/OpenIndiana/oi-userland - Thu, 03/29/2018 - 08:38
Remove gnome-desktop
Categories: oi-userland

Remove gnome-python

github/OpenIndiana/oi-userland - Thu, 03/29/2018 - 08:38
Remove gnome-python
Categories: oi-userland

Remove gnome-python-extras

github/OpenIndiana/oi-userland - Thu, 03/29/2018 - 08:38
Remove gnome-python-extras
Categories: oi-userland

Remove cheese

github/OpenIndiana/oi-userland - Thu, 03/29/2018 - 08:38
Remove cheese
Categories: oi-userland

Remove gdesklets

github/OpenIndiana/oi-userland - Thu, 03/29/2018 - 08:38
Remove gdesklets
Categories: oi-userland

Remove WorldTime gdesklet widget

github/OpenIndiana/oi-userland - Thu, 03/29/2018 - 08:38
Remove WorldTime gdesklet widget
Categories: oi-userland

terminator: update to 1.91

github/OpenIndiana/oi-userland - Thu, 03/29/2018 - 07:53
terminator: update to 1.91
Categories: oi-userland


Subscribe to OpenIndiana Ninja aggregator