Here are some FAQs for starter of BlueQuartz developing.

About us.

We, Cobalt Users Group is non profit group for enthusiasts of Cobalt Microserver, since spring of 1998. Based in Japan. Please check our website Go for Cobalt!.
In 2003, we were starting up the project BlueQuartz and it is going on with Go for BlueQuartz! website. How we started this project, see stories archive.

[ 2004.03.06 by Yutaka Yasuda ]

BlueQuartz

BlueQuartz is the name of the project for porting Cobalt management software which has been released as open source software to PC white box. This project has started in June of 2003, by Cobalt Users Group.

[ 2004.03.06 by Yutaka Yasuda ]

Current status and plan

Currently, our development is based on RaQ550 source code, BlueQuartz Hosting Edition (product code 5100R) is. The target platform of 5100R is CentOS4.
BlueQuartz Workgroup Edition (5100WG) is also exist but the updating had been suspended while. Because the version of Sausalito code base of 550 is relatively higher than Qube3's. We are not able to work for two different development concurrently by our limited human resourece.
We distributes BlueQuartz in two methods, an install CD image and through Subversion repository. See more deatil in Source Code and Binary Distribution page.
You can check the progress of this project through our mailing list.
After we move to stable phase of development, we might consider about merging Qube3 features. DHCP/NAT/Firewall/File Printer sharing/etc.. These features are possible to merge to 5100R as a module, so if you may try to port them to 5100R, please let us know.

[ 2007.05.06 by Yutaka Yasuda ]

Why RedHat Linux 9? (obsoleted)

We chose RHL9 for the basement of the first BlueQuartz platform because it close to original Cobalt. We know RHL9 is not perfect solution for all people but we have to choose one at July of 2003 when Qube3 code had been released.
Which distribution is the best? We think it is not a big issue now. It is better to do make stable BlueQuartz system up first.
And actually, the important issue for the appliance is how we can provide updates/patches continuously. At this viewpoint, the best answer is well knowned. We should have a special distribution of our own, such as Cobalt did so, in actuality.
Of course, please try to port to another platform if you are intersted. Multiformity and freedom are the essence of open source.
(this FAQ is obsoleted because we moved to FC1 then CentOS.)

[ 2004.03.06 by Yutaka Yasuda ]

Why Fedora Core 1? (obsoleted)

As you can see the above FAQ, we have choose RHL9 as a first platform for BlueQuartz. Then after the ends of support RHL9, we have moved to FC1 as the second platform and in April of 2004, we succeed to release the first BlueQuartz which was based on FC1.
Now, November 2004, FC1 development had been closed and there is no clear future support. So there are some opinions to move FC2 or 3. But we keep continue to use FC1 a while.
(this FAQ is obsoleted because we moved to FC1 then CentOS.)

[ 2004.11.17 by Yutaka Yasuda ]

What is different between Qube3 and RaQ550?

Qube3 is a product for SOHO or workgroup environment and RaQ 550 is focuced on the hosting service. In functionally, Qube3 has various features which is useful on intranet, for example DHCP/NAT/Firewall/VPN/File+Printer sharing/etc... RaQ550 has no feature but it is able to handle the virtual sites. Of course primary services are common such as WWW/SMTP/POP/IMAP/DNS.
Both of Qube3 and RaQ550 are based on Sausalito architechture but 550 modules version are ahead of Qube3's.
So we chose the target for porting to BlueQuartz Hosting Edition which is derived RaQ550. It is better to merge various features of Qube3 after the porting works will be completed the first stage.
Some features might not merge if the verification proceess will be too difficult, such as VPN.

[ 2004.03.06 by Yutaka Yasuda ]