"The Java Archive offers access to some of our historical Java releases. WARNING: These older versions of the JRE and JDK are provided to help developers debug issues in older systems. They are not updated with the latest security patches and are not recommended for use in production."
Personal notes and recipes, views and opinions.
If it must run, it runs on Solaris!
Thursday, May 24, 2018
The Java Archive
One may get to the official The Java Archive (as I call it) download page which link is found to the bottom of the official Java SE Downloads page. As dully warned by Oracle the legacy artifacts are unsupported and security flawed:
Updating Java via IPS
The world knows Java, for the good, and for the bad, whatever. Bottom line is one way or the other you're gonna need to handle its existence and pervasiveness. Fortunately, Java is Oracle's as well as Solaris is and thus there's an easier way of handling it via IPS, even if one doesn't have an agreement for having access to an IPS support repository. This post is about a more streamlined way of how to do it based on the article: How to Update Only Java on Your Oracle Solaris 11 System. For this post I assume just a publicly available Solaris 11.3 GA system.
Saturday, May 12, 2018
Terminator
Terminator (by Chris Jones) is a very convenient command-line GUI middleware. That's because it excels on multiplexing a single GUI window for multiple GNOME terminals. One could try to achieve similar results by simply running GNU screen with multiple (split terminal) regions within a single GNOME terminal but in the end it can't keep up with all the features of a specialized GUI software as Terminator. The main focus of GNU screen is not the GUI thing, but the underlying shell process thing.
Under Solaris 11.3, Terminator is dependent on Python 2 and GTK+ 2:
Under Solaris 11.3, Terminator is dependent on Python 2 and GTK+ 2:
The command-line GUI
To achieve an efficient and functional UNIX command-line interface should be easy, but that's not always the case, because of the myriad of options and personal tastes, needless to say the many specific scenarios with unique requirements that may come into play.
On the seek for the "perfect terminal" I actually like to combine three things:
On the seek for the "perfect terminal" I actually like to combine three things:
- GNOME terminals
The fundamental underlying GUI terminal.
- Terminator
The fundamental GUI window multiplexer.
- GNU screen
The fundamental underlying shell process preserver.
Wednesday, April 11, 2018
Building zlib 1.2.11
The basic building strategy and general assumptions have been detailed on a previous post: Staged Building.
$ pwd
/stage/build
$ ./gnu-build-preparation ../source/.../zlib-1.2.11.tar.xz
...
$ cd zlib/zlib-1.2.11-64
$ source ../setenv 64
CONFIG_SHELL=/usr/bin/bash
CC=/usr/bin/gcc CFLAGS=-m64 -march=core2 -std=gnu89
CXX=/usr/bin/g++ CXXFLAGS=-m64 -march=core2 -std=gnu++03
LD=/usr/bin/ld LDFLAGS=-m64 -march=core2
PATH=/opt/gnu/bin:/usr/gnu/bin:/usr/bin:/usr/sbin
PKG_CONFIG_PATH=
Suggested build sequence:
Fine-tune/fix config.h.in, Makefile.in and others...
$ ./configure \
--build=x86_64-pc-solaris2.11 \
--prefix=/opt/... \
...
$ gmake -j3
For IPS package:
$ gmake DESTDIR=/stage/prototype/zlib/1.2.11/64 install
For immediate use:
$ sudo gmake install
$ sudo zfs snapshot -r .../opt/...@zlib-1.2.11
$ pwd
/stage/build
$ ./gnu-build-preparation ../source/.../zlib-1.2.11.tar.xz
...
$ cd zlib/zlib-1.2.11-64
$ source ../setenv 64
CONFIG_SHELL=/usr/bin/bash
CC=/usr/bin/gcc CFLAGS=-m64 -march=core2 -std=gnu89
CXX=/usr/bin/g++ CXXFLAGS=-m64 -march=core2 -std=gnu++03
LD=/usr/bin/ld LDFLAGS=-m64 -march=core2
PATH=/opt/gnu/bin:/usr/gnu/bin:/usr/bin:/usr/sbin
PKG_CONFIG_PATH=
Suggested build sequence:
Fine-tune/fix config.h.in, Makefile.in and others...
$ ./configure \
--build=x86_64-pc-solaris2.11 \
--prefix=/opt/... \
...
$ gmake -j3
For IPS package:
$ gmake DESTDIR=/stage/prototype/zlib/1.2.11/64 install
For immediate use:
$ sudo gmake install
$ sudo zfs snapshot -r .../opt/...@zlib-1.2.11
Subscribe to:
Posts (Atom)