Oracle Solaris Download – Softpedia Linux #oracle #solaris, #download #oracle #solaris, #oracle


Oracle Solaris (formerly SunOS) is a commercial product that provides users with an integrated and full featured server-oriented platform that combines the powerful OpenStack open source cloud computing software with a stable and reliable enterprise-class operating system.

Availability, supported platforms, boot options, and a little bit of history

First of all, we want to remind the reader that this is not a Linux distribution! Solaris OS is a UNIX operating system initially developed by Sun Microsystems, and now maintained by Oracle Corporation under the name of Oracle Solaris.

It is available for download as installable and live ISO images that can be burned onto blank CD discs using any CD/DVD burning software, as well as USB images that allows users to write the operating system to portable USB flash drives.

Supported architectures include x86 (32-bit) and SPARC (Scalable Processor Architecture). Recommended system requirements include at least 2GB or RAM (system memory) and at least 15GB of free hard disk space.

The Live CD ISO/USB images provide users with a modern boot prompt powered by GRUB2, from where users can start the live environment with default settings, using the VESA framebuffer, with SSH enabled, with screen reader, with magnifier, or in text mode. It is also possible to boot an existing operating system installed on the first disk.

State-of-the-art UNIX technologies for both server and desktop platforms

Before entering the live environment, users will need to select a keyboard layout and the language they want to use. The graphical session is powered by the traditional GNOME desktop environment, which comprises of two panels, a top one for accessing the main menu and launching apps, and a bottom one for interacting with running apps and switching between virtual workspaces.

Using the highly acclaimed ZFS filesystem, it includes powerful applications like the Mozilla Firefox web browser, Mozilla Thunderbird email and news client, Glade interface designer, Pidgin instant messenger, Rhythmbox music player, Totem video player, Orca screen reader and magnifier, and GParted partition editor.

Bottom line

All in all, Oracle Solaris is a decent server operating system that has been redesigned from the ground up and engineered for cloud computing. It supports the x86 and SPARC architectures, and features the award winning OpenStack software.

New in Oracle Solaris 11.2:

  • Now available, Oracle Solaris 11.2 is engineered to deliver an efficient, secure, compliant, open and affordable path to enterprise cloud computing for organizations seeking to simplify and modernize their data centers.
  • Oracle Solaris 11.2 is a complete, integrated and open cloud platform engineered for large-scale enterprise cloud environments. It combines OpenStack, application-driven SDN technology, clustering, and zero-overhead virtualization with a proven enterprise-class OS.
  • With its application compatibility guarantee program, Oracle Solaris is designed to make IT’s transformation to enterprise-grade cloud simple, fast, and affordable.
  • Customers can get a cloud up and running in as few as 10 minutes using Oracle Solaris 11.2’s Unified Archive template and OpenStack distribution.

Read the full changelog

Cheyenne Web Server #server #cfg, #cheyenne #web #server #rebol #free #open #source


14-Sep-2013 – Cheyenne sources moved to git/Github [0032 ]

The Cheyenne codebase has been moved from svn/Googlecode to git/Github. The change was made to simplify contributions to Cheyenne, and to regroup my open source projects at the same place (like Red and CureCode ).

In the process of changing the backend building scripts to support git, we also extended the supported platforms for automated builds, we now supports Windows and Mac OSX. in addition to Linux. The new builds are generated twice a day, if new commits are found in the master branch.

Thanks very much to Tamas Herman for helping with the scripts coding and providing the Mac OSX machine, and thanks to the HackJam hackerspace group from Hong-Kong for the hosting!

Please find the latest Cheyenne builds on the updated Download page.

12-Aug-2013 – CORS support added [0031 ]

Thanks to the kind sponsoring of Alan Macleod, Cheyenne now has a module for handling Cross Origin Resource Sharing protocol, basically allowing Javascript to make requests to another domain than the one the script originated from.

In order to use the new mod-cors module, you need to:

  1. Uncomment the cors module line in global section of the httpd.cfg config file.
  2. Add at least one allow-cors directive in a virtual host settings block.

28-Nov-2011 – Websocket support upgraded to hybi-10 [0030 ]

The websocket communication protocol is quite a moving target, it changes several times a year, sometimes breaking compatibility with previous revisions. Cheyenne is now up-to-date and supports the last RFC revision (named “hybi-10”), starting from Cheyenne revision 155.

All protocol features have been implemented but some are not tested yet, as they require a custom-made client (the Javascript websocket API does not support those features yet AFAICT):

  • Ping/pong frames
  • Fragmented frames

The server-side user API has been left untouched, a ping command might be added later though. The websocket chat demo has been upgraded too and now supports Chrome 14+, FF8+ and IE10.

27-Nov-2011 – Cheyenne at PHP Tour 2011 [0029 ]

I have been invited a couple of days ago at PHP Tour 2011 event in Lille (France) to make a presentation of Cheyenne to the PHP community and demonstrate Cheyenne ability to interface with a PHP FastCGI server and serve PHP generated content. I had a great time with developers from PHP community and enjoyed great presentations from Zend engineers about their famous framework and cryptography support in PHP.

Here are my presentation slides (in french):

If you are experiencing issues seeing the slides in flash format, here’s a PDF version .

If you are wondering what slide 4 is about, it is just a warning for people confusing this Cheyenne server with the one embedded in the ADSL box of one of french ISP (which is just an Apache instance renamed, and that name used to appear when an internal error occured in the box).

8-Jun-2011 – Cheyenne at Chti’RUG2011 [0028 ]

I was at Chti’RUG2011 french event at Lille a week ago and did a presentation of Cheyenne. This is the same presentation I did at ReBorCon2011, just translated in french (available in PDF format ).

There is a french blog article by Olivier Auverlot talking about this meeting.

Routing Messages to SYSLOG on a UNIX System #syslog #unix


Routing Messages to SYSLOG on a UNIX System


This topic discusses how to set up an IBM i (i5/OS) running on IBM Power Systems (System i, iSeries) to route messages to SYSLOG on a remote UNIX system. This is done by using programs supplied as part of the IBM i that run in the PASE environment. The PASE environment is a standard free component of the IBM i that runs a subset of AIX with binary compatibility.

The path of a message is:

logger: This AIX command sends a message to the SYSLOG daemon on the local system.

syslogd: This is the SYSLOG daemon, and it routes log messages for the entire system. One of the options is to forward the message to another system, which is the one we will be using for this exercise.

We have assumed for this topic that SYSLOG is not currently configured or being used.

Initial Setup


Check that PASE is installed on your system. This is IBM i option 33, and is distributed free of charge with the operating system.


The first thing to do is to configure the SYSLOG daemon to route selected messages to the remote UNIX system. This is done using the file QOpenSys/etc/syslog.conf .

It is important that you use a UNIX editor or a Windows-based editor that is able to write ASCII files in UNIX format to create this file. UNIX terminates lines with a Line Feed character; Windows uses Carriage Return and Line Feed, which will not work with SYSLOG. The people running the system you intend to route the message to might be the best people to speak to about creating this file.

The file should contain one line, which tells SYSLOG to route messages from a particular facility to a remote server. We suggest using facility local0, or the administrator for your target system may have another suggestion. The following line will route all messages for local0 of severity debug and above (which means all messages) to a server called SyslogTarget:

Note that a tab character must be used between the facility name and the server name; a space will not work. The line must end with a newline (LF) character. Once the file has been created, use FTP to move it into the IFS:

ftp host
cd /QOpenSys/etc
put syslog.conf

SYSLOG will use the IBM i DNS configuration to resolve the host name, so no further configuration is required. The name can be resolved from the system’s hosts table (CFGTCP option 10), or from the corporate DNS server. A dotted decimal address (such as could be used instead, but it’s recommended that a symbolic name be used for ease of maintenance.

SYSLOG Start-up

The SYSLOG daemon will need to be started; this should be added to the system initial start-up routine. The following command starts the SYSLOG daemon in subsystem QSYSWRK, the SYSLOG profile is one we have created for this purpose:

The user name must have *ALLOBJ authority, as only a super user can start the daemon.

Sending a Message

The following MMSNDSLM command will send a message to be routed by syslogd:

This command can be added to an auto-reply rule to provide the ability to route messages through to SYSLOG on a UNIX platform.

This example shows any changes to the system values being forwarded:

Pressing F10 shows the previously mentioned MMSNDSLM command with some variables being passed from the message:

This is the type of view as it would appear on the UNIX platform: