User Tools

Site Tools


info:about

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
info:about [2014/06/21 16:29]
101.164.104.241 [Sausalito]
info:about [2015/03/07 14:08] (current)
Line 1: Line 1:
-NOTE: This page is a google translation of an old wikipedia page. It is old, outdated, and missing lots of information. Eventually, it should be a general "​about"​ page for BlueOnyx, showing the history of how we got to the community we are all part of today. Please feel free to update/​contribute to this page. 
- 
-The original non-english source for this page is located at http://​de.wikipedia.org/​wiki/​BlueQuartz 
-  
- 
 ====== BlueOnyx ====== ====== BlueOnyx ======
-BlueOnyx is an open source User Interface for virtual Webservers. BlueOnyx is built on top of the free CentOS or ScientificLinux ​operating system, which is binary compatible with Red Hat Enterprise Linux.+BlueOnyx is an open source User Interface for virtual Webservers. BlueOnyx is built on top of the free CentOS or Scientific Linux operating system, which is binary compatible with Red Hat Enterprise Linux (EL). Over the years different versions of BlueOnyx were made for different versions of said OS's: EL5, EL6 and EL7.
  
 BlueOnyx allows a Linux novice to install, administer, and manage a Linux-based Web server. ​ BlueOnyx allows a Linux novice to install, administer, and manage a Linux-based Web server. ​
 The administrator will use a browser to use configure the server, virtual websites, users, DNS, FTP, and email accounts. ​ The administrator will use a browser to use configure the server, virtual websites, users, DNS, FTP, and email accounts. ​
-The user interface is available in English, German, Danish and Japanese.+ 
 +The user interface is available in the following languages: ​English, German, Danish, Spanish, French, Dutch, Italian. Portuguese ​and Japanese.
  
 ===== History ===== ===== History =====
Line 24: Line 20:
  
 ==== Sun Cobalt ==== ==== Sun Cobalt ====
-After Sun purchased Cobalt Networks Inc. for two billion dollars (( press release: [{http://www.pressetext.com/pte.mc?​pte=000919053|Sun purchase of Cobalt networks ])), development of the former cobalt Networks server products almost came to a complete standstill. ​+After Sun purchased Cobalt Networks Inc. for two billion dollars (( Sun: [[https://​web.archive.org/​web/​20070222051020/​http://www.sun.com/smi/​Press/​sunflash/​2000-09/​sunflash.20000919.2.xml|Sun purchase of Cobalt networks ​]])), development of the former cobalt Networks server products almost came to a complete standstill. ​
  
-Despite statistics (( Netcraft: [[http://​news.netcraft.com/​archives/​2004/​06/​24/​cobalt_shows_gains_after_source_is_opened.html|Cobalt Shows Gains After Source is Opened]] )) that indicate over 3 million hostnames were hosted on cobalt servers in August 2002, Sun announced end of sale of cobalt RAQ and Qube in 2003 (( theregister:. [[http:// www.theregister.co.uk/​2003/​12/​18/​sun_drives_the_final_nail/​|Sun drives the final nail in Cobalt'​s coffin]] ))+Despite statistics (( Netcraft: [[http://​news.netcraft.com/​archives/​2004/​06/​24/​cobalt_shows_gains_after_source_is_opened.html|Cobalt Shows Gains After Source is Opened]] )) that indicate over 3 million hostnames were hosted on cobalt servers in August 2002, Sun announced end of sale of cobalt RAQ and Qube in 2003 (( TheRegister:. [[http:// www.theregister.co.uk/​2003/​12/​18/​sun_drives_the_final_nail/​|Sun drives the final nail in Cobalt'​s coffin]] ))
  
  
Line 35: Line 31:
 Immediately after the publication of the source code under the BSD License, we saw the launch of Project Blue Quartz. The objective was to provide both for the very popular in Japan Qube 3, and for the RaQ550 alternatives on the basis of the now free source code. Immediately after the publication of the source code under the BSD License, we saw the launch of Project Blue Quartz. The objective was to provide both for the very popular in Japan Qube 3, and for the RaQ550 alternatives on the basis of the now free source code.
  
-BlueQuartz initially used Fedora. In early 2004, the project changed to CentOS. During the  early days, BlueQuartz had to deal with some problems, as the underlying architecture was sometimes quite poorly documented ​((BlueQuartz mailing list: [[http://​www.bluequartz.us/​phpBB2/​viewtopic.php?​p=246524|complaints about inadequate documentation]] )) had been, or detailed documentation later by former employees of [[Sun Microsystems | Sun]] could be provided. ​**TRANSLATION - CHECK ME**+BlueQuartz initially used Fedora. In early 2004, the project changed to CentOS. During the  early days, BlueQuartz had to deal with some problems, as the underlying architecture was sometimes quite poorly documented. ​Later on former employees of [[Sun Microsystems | Sun]] provided ​some extra documentation beyond what was already in circulation. However, that documentation also had many shortcomings or was more oriented towards marketing than technically minded developers.
  
 +In addition, some commercial developers also used the combined source code of Sun and BlueQuartz, creating competing platforms for users to choose from. 
  
- +Added to this was the somewhat cumbersome procedure for installing ​BlueQuartz ​in its early phase. To do this, first had to install and customize the operating system. Then you launched an installer, the reconfigured the operating system, and conformed the components of the browser-based user interface installed.
-In addition, some commercial developers also used the combined source code of Sun and Blue Quartz, creating a competitive battle for users. +
- +
-Added to this was the somewhat cumbersome procedure for installing ​Blue Quartz ​in its early phase. To do this, first had to install and customize the operating system. Then you launched an installer, the reconfigured the operating system, and conformed the components of the browser-based user interface installed.+
  
 In early 2005 Brian N. Smith of NuOnce Networks published a free Boot CD, providing both the configured operating system and BlueQuartz installed. Only then became BlueQuartz an increasingly growing acceptance and came first for all those in question, which had to replace a RaQ550 by more modern server hardware. In early 2005 Brian N. Smith of NuOnce Networks published a free Boot CD, providing both the configured operating system and BlueQuartz installed. Only then became BlueQuartz an increasingly growing acceptance and came first for all those in question, which had to replace a RaQ550 by more modern server hardware.
Line 47: Line 41:
  
 ==== Commercial interaction during the development of BlueQuartz ==== ==== Commercial interaction during the development of BlueQuartz ====
-In mid-2005 ​began the project of Project ​Blue Quartz (Hisao Shibuyaas the lead developer at Turbolinux, Inc. - a Japanese Linux distributor. There they developed on the basis of the published source code for the Sun RaQ550 ​and from the sources of the Blue Quartz ​Turbolinux Appliance Server 2.0, also called TLAS. TLAS 2.0 was released in March 2006 (( Turbolinux, Inc.:[[Http://​www.turbolinux.com/​cgi-bin/​newsrelease/​index.cgi?​date2=20060222131514&​mode=syosai|press release publication of TLAS 2.0]] ))+In mid-2005 Project ​BlueQuartz started. It was initiated by Hisao Shibuya as the lead developer at Turbolinux, Inc. - a Japanese Linux distributor. There they developed ​a commercial product ​on the basis of the published source code for the Sun RaQ550, which got called ​the Turbolinux Appliance Server 2.0. Which was als called TLAS in short. TLAS 2.0 was released in March 2006 (( Turbolinux, Inc: [[Http://​www.turbolinux.com/​cgi-bin/​newsrelease/​index.cgi?​date2=20060222131514&​mode=syosai|press release publication of TLAS 2.0]] )) 
 + 
 +Just as BlueQuartz had accelerated the development of TLAS there was also a constant flow of development in the reverse direction, benefitting BlueQuartz itself. Improvements to the commercial TLAS also found their way into the source code of BlueQuartz. More often so BlueQuartz had fixes and new features earlier than TLAS, as the commercial product had slower release cycles than the Open Source project BlueQuartz. This eventually caused a conflict of interest, as the freely available BlueQuartz offered the same functionality as the 950 U.S. dollar priced TLAS 2.0 (( Turbolinux, Inc: [[Http://​www.turbolinux.com| Product page of TLAS]] )). 
 + 
 +==== BlueQuartz ==== 
 +BlueQuartz was mostly adopted among former operators of RaQ550 servers, who needed compatible replacements for their aging Sun Cobalt RaQs with more modern hardware. However, over time BlueQuartz also attracted new users that had no prior Sun Cobalt experience. According to statistics <- evaluation of server log files of the central YUM repositories of BlueQuartz.org April 2008 -.> (04/2008) of Project Blue Quartz run more than 135,000 Web servers worldwide with Blue Quartz (the numbers were counting Update operations collected and that may be representative). 
 + 
 +==== The developers ==== 
 +The original Blue Quartz developers <ref> BlueQuartz: [http://​bluequartz.org/​aboutus.html The Team] </ ref> were Hisao Shibuya, Yutaka Yasuda and Makoto Oda. In the end of 2006 Brian N. Smith of NuOnce Networks, Inc. and Michael Stauber from Solarspeed.net joined the team. Both had (since 2000) provided add-on software and services for Sun Cobalt server and its successor systems. The team was further strengtened by Taco Scargo, a former Sun Cobalt employees.
  
-Just as BlueQuartz had accelerated the development of TLAS, also an information flow in the reverse direction took place. Improvements to the commercial TLAS also found in the source code of Blue Quartz collection. This eventually drew a conflict of interest from, because the available free BlueQuartz was also fully developed and offered a similar functionality as the about 950 U.S. dollar TLAS 2.0 (( Turbolinux, Inc.. [[Http://​www.turbolinux.com|/​ products / server / tlas /  product page of TLAS 2.0]] )) 
-Dissemination of BlueQuartz ==== ====  
-First BlueQuartz has occurred mostly among former operators of RaQ550 servers spread - especially when it came to replace outdated Sun Cobalt hardware with new ones. However, over the time also met new users to that had been used no RaQ550 server. According to statistics <- evaluation of server log files of the central YUM repositories of BlueQuartz.org April 2008 -.> (04/2008) of Project Blue Quartz run more than 135,000 Web servers worldwide with Blue Quartz (the numbers were counting Update operations collected and that may be representative). 
-The developers ==== ====  
-The original Blue Quartz developers <ref> BlueQuartz: [http://​bluequartz.org/​aboutus.html The Team] </ ref> Hisao Shibuya, Yutaka Yasuda and Makoto Oda end of 2006 joined Brian N. Smith of NuOnce Networks, Inc. and Michael Stauber from solar speed Ltd.. which will both offered since 2000 add-on software and services for Sun Cobalt server and its successor systems. The team by Taco Scargo, a former Sun Cobalt employees was further strengthened. 
 ==== Further development ==== ==== Further development ====
-Although CentOS 5 was published in April 2007, found the part of the project management team BlueQuartz ​no serious efforts instead ​(( BlueOnyx: [http://​www.blueonyx.it/​index.php?​mact=News,​cntnt01,​detail,​0&​cntnt01articleid=10&​cntnt01returnid=54|BlueQuartz on CentOS 5]]))BlueQuartz ​CentOS ​CentOS 4 according to port 5. Separate ​single developer advances in this direction ​found no support ​and little support ​(( BlueOnyx: [http://​www.blueonyx.it/​index.php?​mact=News,​cntnt01,​detail,​0&​cntnt01articleid=13&​cntnt01returnid=54|Split the development teams] ))+Although CentOS 5 was published in April 2007 the project management team of BlueQuartz ​did not appear to make any push to transition BlueQuartz to CentOS 5 (( BlueOnyx: ​[[http://​www.blueonyx.it/​index.php?​mact=News,​cntnt01,​detail,​0&​cntnt01articleid=10&​cntnt01returnid=54|BlueQuartz on CentOS 5]])) and BlueQuartz ​so far was only available for CentOS 4 instead. Separate ​efforts of individual developers towards porting BlueQuartz to CentOS 5 found no support ​among the rest of the developers ​(( BlueOnyx: ​[[http://​www.blueonyx.it/​index.php?​mact=News,​cntnt01,​detail,​0&​cntnt01articleid=13&​cntnt01returnid=54|Split the development teams]] )). 
 + 
 +Eventually Brian N. Smith and Michael Stauber (( BlueOnyx: [[http://​www.blueonyx.it/​index.php?​page=development|The Team]] )) decided to leave the BlueQuartz development team to create Project BlueOnyx [[BlueOnyx|http://​www.blueonyx.it]] with a fork of the BlueQuartz code . The first release of BlueOnyx 5106R on CentOS 5 included many new features and was released on 31 December 2008 (( BlueOnyx: [[http://​www.blueonyx.it/​index.php?​mact=News,​cntnt01,​detail,​0&​cntnt01articleid=20&​cntnt01returnid=54|Notice of BlueOnyx 5106R release]] ))
  
-Then split (( BlueOnyx: [[http://​www.blueonyx.it/​index.php?​page=development|The Team]] )) the development team of Blue Quartz ​and under new line was an offshoot of the code - developed ​on CentOS 5 Base - under the name [[BlueOnyx|http://​www.blueonyx.it]]. BlueOnyx includes many new features ​and was released on 31 December 2008 (( BlueOnyx: [[Http://​www.bluequartz.us/​phpBB2/​viewtopic.php?​t=75392|notice of BlueOnyx]] ))+Hisao Shibuya, Yutaka Yasuda and Makoto Oda continued to maintain BlueQuartzHowever, ​the newer BlueOnyx and the departure ​of important developers didn't make their task any easier. Years later BlueQuartz managed another major release ​and published BlueQuartz 5200R, which was based on CentOS 5 as OS, but it was soemwhat rough around ​the edges and lacked an ISO install method.
  
-While Hisao Shibuya, Yutaka Yasuda and Makoto Oda continue BlueQuartz maintain BlueQuartz by the departure ​has important developer and by competition ​with the successor BlueOnyx an increasingly heavier stand ((BlueOnyx: [[http://​www.bluequartz.us/​phpBB2/​viewtopic.php?​t=75703|notice Blue Quartz 2.0]]))+The project BlueQuartz has falled more or less dormant in recent years and Team BlueOnyx is happy that Hisao Shibuya has joined us to aid with his amazing expertise in the platform.
 ===== Basic Architecture ===== ===== Basic Architecture =====
  
 ==== Sausalito ==== ==== Sausalito ====
-Developed by Cobalt Networks Inc. architecture called Sausalito. Essentially,​ Sausalito is modular and functions can be retrofitted via modules (eg third party) (( Solar Speed ​​Ltd: [[Http://data.smd.net/cobalt.docs/​SSDK.pdf|Sausalito Developer'​s Guide (PDF)]])) (( Solar Speed Ltd: [[http://data.smd.net/cobalt.docs/​DevGuide.pdf|The Qube 3 software Architecture Developer'​s Guide (PDF)]] ))+Developed by Cobalt Networks Inc. architecture called Sausalito. Essentially,​ Sausalito is modular and functions can be retrofitted via modules (eg third party) (( BlueOnyx Developer Archive: [[http://devel.blueonyx.it/pub/Cobalt/​SSDK.pdf|Sausalito Developer'​s Guide (PDF)]])) (( BlueOnyx Developer Archive: [[http://devel.blueonyx.it/pub/Cobalt/​DevGuide.pdf|The Qube 3 software Architecture Developer'​s Guide (PDF)]] )). Other Sun Cobalt related original documentation can be found in the (( BlueOnyx Developer Archive [[http://​devel.blueonyx.it/​pub/​Cobalt/​|BlueOnyx Developer Archive]] )) as well.
  
  
 Sausalito consists of the following components: Sausalito consists of the following components:
 ==== The user interface (UI) ====  ==== The user interface (UI) ==== 
-The administration interface of Blue Quartz ​is programmed in [[PHP]]. Via so-called Skins or Themes ​Improve ​the look of the admin interface ​to customize. The UI runs on a customized Apache web server that is bound to a specific port (Port 81 - HTTP / Port 444 - HTTPS). This web server is running as an unprivileged user '​apache'​. However, it allows authenticated users and privileged, ​certain narrowly defined functions on the underlying operating system with superuser (root) to run+The administration interface of BlueQuartz and BlueOnyx ​is programmed in [[PHP]]. Via so-called Skins or Themes the look of the admin interface ​could be customized, although the template architecture of the original GUI is by now somewhat antiquated. The UI runs on a customized Apache web server that is bound to a specific port (Port 81 - HTTP / Port 444 - HTTPS). This web server is running as an unprivileged user '​apache' ​(or '​admserv'​ in newer versions). However, it allows authenticated users to execute ​certain narrowly defined functions on the underlying operating system with superuser (root) ​rights. The level of privileges each user has is defined by Access Control Lists (ACL'​s) that operate on a per Group basis. Serveral levels of privileges exist. 
 + 
 +If an authenticated user - provided he has sufficient privileges ​to do so - runs a transaction (such as creating a virtual site or user), then Sausalito writes an entry in an internal database. This database is called CODB. Which is short for "​Cobalt Object Database"​.
  
-If an authenticated user - provided it has the appropriate rights - a change to the system before (for example, creates a new virtual website on), so Sausalito writes an entry in an internal database. This database is called CODB - or Cobalt Object Database. 
 ==== CODB: Cobalt Object Database ====  ==== CODB: Cobalt Object Database ==== 
  
 The Cobalt Object Database is an object-oriented database for storing parameters, settings and data of the web server. ​ The Cobalt Object Database is an object-oriented database for storing parameters, settings and data of the web server. ​
-Stored ​in the database objects belong to classeswithin ​which one can define namespaces and content ​of XML schemas freeCan also be configured directly via XML schemas, what type of content in a particular namespace may be written within the class, and which group of users has write access to this class + 
-A namespace for the type 'email address' ​has been defined may, for example, receive only content that matches ​valid e-mail address.  +Data stored ​in the database objects belong to Classes, which themselves ​can have separate NameSpaces. The format ​of Classes and their Namespaces is defined via XML Schema filesSuch Schema files define the key/value pairs that a Class or NameSpace has. They also define which type of data can be stored into a "​value"​ fieldThis immediately provides input validation as well. For example: If a database value is configured to only accept an email address, then data that doesn't appear to be an email address ​won't be accepted. Additionally the access controls ​for each key/value pair (or the entire Class or Namespace) can be defined in those Schema files. Here is one example ​of Schema file [[http://​devel.blueonyx.it/​trac/​browser/​BlueOnyx/​5209R/​platform/​base-apache.mod/​glue/​schemas/​apache.schema|BlueOnyx 5209R Apache Schema file]])). 
-CODB takes the content storage for an examination ​of the data transmitted. So on the one hand checked whether ​the user is authorized for write access, ​and on the other hand, if the data to be saved corresponds to the expected type.+ 
 +When CODB is tasked with the database manipulation (creating ​of Objects, modification of Objects or deletion of Objects - and their Namespaces) it always checks if the transmitted ​data is valid, if the user is authenticated ​and has the proper access control rights ​to perform this transaction 
 ==== CCE: Cobalt Configuration Engine ==== ==== CCE: Cobalt Configuration Engine ====
  
-CCE (Cobalt Configuration Engine) is the interface between the admin interface and CODB (Cobalt Object Database). It handles the authentication of users and compares them with the mechanisms for user management of the operating system. ​Also managed ​CCE database requests from the UI to read and write.+CCE (Cobalt Configuration Engine) is the interface between the admin interface and CODB (Cobalt Object Database). It handles the authentication of users and compares them with the mechanisms for user management of the operating system. ​It also manages ​CCE database requests from the UI to readwrite and delete Objects.
  
-CCE consists of a [[demon]], which constantly runs in the background, as well as a [[Client]], which can be used as needed from the command line to perform administrative functions.+CCE consists of a [[Daemon]], which constantly runs in the background, as well as a [[Client]], which can be used as needed from the command line to perform administrative functions. CCE also runs certain scripts (Handlers and Constructors),​ which perform administrative tasks with superuser privileges based on startup events (Constructors:​ Run on CCE startup) or CODB database events (Handlers: Run on specific CODB transactions).
  
 === Configuration files === === Configuration files ===
  
-About configuration files to CCE can be configured ​so that it performs certain operations with superuser privileges when certain database fields created, changed or deleted. ​To perform such privileged operationsCCE starts ​by checking ​the authorization of the user a handler that performs this operation.+Via configuration files CCE can be configured ​to performs certain operations with superuser privileges when certain database fields ​are created, changed or deleted. ​For example it can be defined that if a certain Class is created or deletedthen a certain Handler should be run to modify config files. Or if a certain database field in CODB gets modified, then a Handler should run to publish these changes to the OS config files. In all cases these Handler runs can only be triggered ​by users with the proper access levels and after successful authentication
  
 === Handler === === Handler ===
-A handler is in [[Perl (programming language) | Perl]] ​or programmed PHP script that can perform certain narrowly defined tasks on the file system of the server with superuser privileges. These scripts can be triggered for safety reasons ​only by CCE itself. +A handler is typically a [[Perl (programming language) | Perl]] script that can perform certain narrowly defined tasks on the file system of the server with superuser privileges. These scripts can only be triggered ​by CCE itself - for safety reasons. Handlers are for example ​used to create ​users or virtual ​sites, or to adjust configuration files of the server.
-Handlers are used, for exampleto create ​a user or virtual ​websites, or adjust configuration files of the server.+
  
 === Constructors === === Constructors ===
-Much like handler ​Constructor is programmed in Perl or PHP script, which performs certain tasks on the file system with superuser privileges. However, a constructor ​usually runs only once when starting the server, or at the start of the CCE daemon. +Like Handlers ​a Constructor is typically ​programmed in Perl and performs certain tasks on the file system with superuser privileges. However, a Constructor ​usually runs only once when the CCE daemon ​is started 
-Constructors are used for example ​to read and save these in the Cobalt Object Database information about the operating system and its configuration.+ 
 +Constructors are typically ​used to read configuration files and to inform CODB of the state of the server by writing that data into CODB. Or values stored ​in CODB are published to the OS to make sure that the server operates on a known configuration. ​ 
 ==== PHP and i18n ==== ==== PHP and i18n ====
-Since the communication between UI and CCE on custom i18n module ​version ​of PHP is done, PHP is one of the few components ​on a Blue Quartz, ​that can only be conditionally update ​or replace them with newer versionsOtherwise, ​the communication between UI and CCE is interrupted under certain ​circumstances.  +Since the Cobalt days the communication between UI and CCE is done via Zend API PHP module ​called cce.so. This extends the basic PHP interpreter ​of the server with special functions to communicate with CCE and CODB. This cce.so ​PHP module ​is only loaded on the separate webserver (AdmServ) that runs the GUI.  
-If you want to still PHP version update a few jumps, a more recent installation of PHP in a separate directory is recommended.+ 
 +Additionally another Zend API PHP module (i18n.so) ​is loaded to provide PHP with the internationalization support needed to display the GUI in different languages. The i18n.so module provides an interface between PHP and the GetText locales ​on the server. 
 + 
 +Naturally this creates ​problem as far as the upgradeability of PHP on the servers OS is concerned: These two mandatory PHP modules are specially compiled against the PHP that BlueQuartz ​or BlueOnyx ships with. In order to work with a different PHP version they need to be recompiled. If the PHP version ​is drastically different, then these modules might no longer be compatible. For this reason upgrading (or replacing) PHP has always required ​certain ​"​special"​ procedures. Or an install of the updated PHP into a separate directory
 + 
 +BlueOnyx 5207R and BlueOnyx 5208R still use the PHP modules cce.so and i18n.sobut have fallback mechanism ​in place. If these modules are no longer loaded (due to PHP compatability issues) the GUI will fall back to native PHP Classes that provide the same functionality. However, this comes at small performance impact, as the PHP modules are faster than the PHP Classes. 
 + 
 +BlueOnyx 5209R no longer uses the PHP modules cce.so and i18n.so, as we couldn'​t get them to work with PHP-5.4 due to API changes within PHP. BlueOnyx 5209R uses the supplementing PHP Classes instead by default. 
 ==== Operating system ==== ==== Operating system ====
-Generallythe source of Blue Quartz ​can easily be adapted so that it can run on any Linux or Unix derivative. For this purposeonly minor adjustments to the source code necessary to compile ​the source code as well as for the new platform. Since all the advanced features of the Blue Quartz surface ​are modular, you can not leave for managing virtual websites for example on their own based on BlueQuartz Projects Modules such as the mailing list management, user management ​or the module.  + 
-This gives you carefully planned ​and well framework for its own administration interface.+Generally the source of BlueQuartz or BlueOnyx ​can easily be adapted so that it can run on any Linux or Unix derivative. For this purpose only minor adjustments to the source code and a recompilation of the sources might be necessary. Since all the advanced features of the BlueQuartz or BlueOnyx GUI are all modular ​it would be trivial to use it as a GUI framework for entirely different purposes.  
 + 
 +In practical terms the adaption of BlueQuartz ​or BlueOnyx to different OS's (than the ones already supported) requires ​wide range of skills ​and expertise and the lack of thorough documentation creates certain challengesWe are working on making it easier, though and this Wiki is one step into that direction. 
 ==== PKGs ==== ==== PKGs ====
-PKGs are special packages that allow - regardless of the update mechanism ​of the operating system ​equip BlueQuartz with additional software. PKGs consist of files that have been packed with tar and gzip. Within a PKGs are RPMs, a list of files to be installed, as well as scripts that run when installing or uninstalling the PKGs.+PKGs are special packages that allow the installation ​of pre-packaged ​additional software. PKGs consist of files that have been packed with tar and gzip. Within a PKGs are RPMs, a list of files to be installed ​and scripts that run when installing or uninstalling the PKGs. Additionally PKGs can display license information and information about the included software that is presented in the GUI upon installation. A PKG has mechanisms to make sure that it can only be installed on versions of BlueQuartz or BlueOnyx that the PKG was designed for. 
 + 
 +There is also a server implementation for the distribution of PKGs, which can be used to distribute PKGs (and their updates) to servers that are tied into this update channel. This distribution method is called NewLinQ and is used by the [[http://​shop.blueonyx.it/​|BlueOnyx Shop]])). 
 ===== Related Projects ===== ===== Related Projects =====
 After the release of the source code of the Qube 3 and the RaQ550 efforts were made from different companies and groups to build a similar solution based on this code. Not all were successful. After the release of the source code of the Qube 3 and the RaQ550 efforts were made from different companies and groups to build a similar solution based on this code. Not all were successful.
 +
 ==== Active ==== ==== Active ====
-  * BlueOnyx ​development ​of BlueQuartz  +  * BlueOnyx, successor ​of BlueQuartz ​and the RaQ550 
-  * Aventurine {e} Linux virtualization solution based on BlueQuartz. ​+  * Aventurine {e} Linux virtualization solution based on an evolved BlueOnyx versions.  
 + 
 +==== Inactive/​Discontinued ==== 
 +  * BlueQuartz 
 +  * Renamed argon TLAS 2.0 pre-installed on Hardware.  
 +  * Efinity F-560 RaQ to the FreeBSD base.  
 +  * RaQDevil RaQ to the FreeBSD base.
   * Strongbolt Linux BlueQuartz + CentOS distribution for installation on original Sun Cobalt hardware. ​   * Strongbolt Linux BlueQuartz + CentOS distribution for installation on original Sun Cobalt hardware. ​
   * Turbolinux Appliance Server 2.0 RaQ on Turbo Linux. ​   * Turbolinux Appliance Server 2.0 RaQ on Turbo Linux. ​
Line 112: Line 136:
   * ClassCat Cute Server Appliance / ClassCat, Inc. Japanese, based on the RaQ550 code.    * ClassCat Cute Server Appliance / ClassCat, Inc. Japanese, based on the RaQ550 code. 
   * [[NetBSD]] on Cobalt servers, English, completely independent of the Linux project.   * [[NetBSD]] on Cobalt servers, English, completely independent of the Linux project.
-==== Submitted ==== +
-  * Renamed argon TLAS 2.0 pre-installed on Hardware.  +
-  * Efinity F-560 RaQ to the FreeBSD base.  +
-  * RaQDevil RaQ to the FreeBSD base.+
 ===== Weblinks ===== ===== Weblinks =====
-  * [http://www.bluequartz.orgBluequartz-Website(englisch) +  * [http://devel.blueonyx.itBlueOnyx Source Code
-  * [http://bluequartz.org/trac/​browser BlueQuartz-Quellcode(englisch) +  * [http://www.blueonyx.itBlueOnyx Website
-  * [http://​www.solarspeed.net/category.php?​id_category=12 Bluequartz Boot-CD ISO(englisch) +  * [http://​www.bluequartz.orgBlueQuartz Website
-  * [http://www.wiki.csoft.at/index.php/Kategorie:​Bluequartz Bluequartz-Tipps]+  * [http://bluequartz.org/trac/browser BlueQuartz Source Code ] 
info/about.1403332159.txt.gz · Last modified: 2014/06/21 16:29 by 101.164.104.241