Solaris / OpenSolarisThis forum is for the discussion of Solaris and OpenSolaris.
General Sun, SunOS and Sparc related questions also go here.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Big projects like OpenIndiana need dedicated teams when it comes to maintaining packages, patching security bugs, and even then ensuring all the projects work completely.
My thoughts in this...
Downsize the project.
The entire project could be stripped down to the bare minimum for a complete working system... like a Slackware Linux approach. Bare minimums with the most functionality, commonly used build tools, and then reside everything else to community maintained build scripts.
This way fewer people are required to maintain the project and keep it working.
However, this would also mean the killing off of dependency resolution, but it wouldn't be needed anyway if everything completely optional went assigned to the community and lists of dependencies would be named. Just as Slackware has SlackBuilds, OpenIndiana could have OIBuilds.
Patrick Volkerding who maintains Slackware even quoted Lao Tzu that said, "In order to lead, one must follow."
It's a sound option if there ever was one, and it would not only help out OI with maintaining itself, but it would allow for OI to become more community involved.
Note that there are already stripped down projects concurrently to OpenIndiana, like SmartOS, EON and Omnios. They all share the same core (illumos kernel and utilities) but are targeted to specialized platforms instead of a general purpose desktop, like OpenIndiana.
One fairly trivial thing that could have a big return is some pizazz on the OpenIndiana website. I check back every once-in-a-while and see the same intro page that's always been there. It makes it look like it's dead and no one pulled the plug yet. The July 29 news was the first difference I remember seeing in years.