1. 6
  1.  

  2. 7

    Am I crazy? I thought Oracle killed off Solaris? Or did they just lay off a bunch of folks?

    1. 8

      They definitely sacked a lot of people, which presumably did nothing for the morale of the folks left behind either. We picked up some of the people jumping ship at Joyent when it happened.

      You can only fire or terrorise so many of the people in an organisation who know how something works before there won’t be a critical mass left to maintain it. Because of the long pipeline of work that was already underway at the time of the event (including the most recent line of SPARC microprocessors) they had a lot of stuff they could release just after the firing – “See, of course we’re not dead!” – but I wouldn’t hold out much hope for anything else.

      1. 1

        Oracle killed OpenSolaris, not Solaris.

      2. 1

        Privileged Command Execution History

        A new command, admhist, was included in Solaris 11.4 to show successful system administration related commands which are likely to have modified the system state, in human readable form. This is similar to the shell builtin “history”.

        That’s a curious one. It’s a shame the solaris manpages don’t appear to be public. I wonder if they’re logging the use of system() or exec*() in their libc.

        What’s worse is I immediately started thinking about how this workaround could be useful. Naughty Hales! Fix the shell configs on the servers instead. Stop imagining libc level hacks to see what coworkers have been up to.

        1. 4

          I have no idea how it’s implemented, but I would note that Solaris and illumos systems have an auditing system with kernel involvement that can capture, amongst other things, all command execution. Perhaps this is a set of filters for displaying information gathered by the existing auditing mechanism.