Nope. Cinch is the installer. I wrote it from scratch because that was easier for me to port and manage then Anaconda (not all Python is easy to maintain).
With that said, Cinch is just an simple installer. If you require a system provisioning tool (which I think is what you are asking about), I would recommend SystemImager and/or Warewulf (while it is generally a cluster tool, it is very capable of provisioning thousands of systems in parallel). Both come with cAos-2.
Lastly, Cinch is actually driven by a series of ASH scripts. It is very easy to modify and customize.
What exactly do you mean by "managed by the community"?
I see your point and you bring up a good question. Here is how I (and Webster) define that statement:
Managed: To have under control and direction; to conduct; to guide; to administer; to treat; to handle.
Community: Common possession or enjoyment; participation; as, a community of goods. (2) A body of people having common rights, privileges, or interests... (3) Society at large; a commonwealth or state; a body politic; the public, or people in general.
I think you are very right. BSD fits very accuratly, and we have based some of our models from the success of that project (as you noticed).
Our choice to use RPM was a major factor that drove us to build a new distro. Religion aside, people use RPM, and many developers and organizations have standardized on them. Yet there was no RPM based solutions managed by the community itself.
The lifecycle statement is actually very important when comparing this project to Fedora. For instance, Fedora is basically impossiable to standardize an infrastructure on because it is constantly changing. There is not always a clean upgrade path (which is by design).
By stating that cAos actually has a life longer then 6 months, we are commiting to its long term viability as a solution.
I'm getting a little tired of all these distros popping up every two weeks claiming to be the latest and greatest since sliced bread.
Claiming what? Actually the cAos Foundation has been very quitely doing their thing for about 2 years now. There is no hype about it, and the mentality is that we are doing this because this is what we need. If someone else can get value from it, then great! Appearantly you have the wrong idea about the developers of the cAos Foundation. I for one can tell you that we are rather modest, and just trying to share our work with the community.
I don't even thing the facade of community based means a whole lot these days. There's been a few good ones with a fundamental approach that's different, but not a lot.
I am unclear what you mean the "facade" of community. We have multiple developers and contributors in the project. We welcome members of the community to actually maintain packages in the distro. We are completly open in our build methods and CVS tree... Decisions are made via the package maintainers and core developers themselves. I see it as reality, not a facade.
If you evaluate our approach, you might see that we are doing somethings that are in fact different. Like the use of RPM in a community maintained distro, also our build system, community involvement ideologies, and segreation of a core static ABI from the extended OS package maintainers.
Slashdot Mirror
Nope. Cinch is the installer. I wrote it from scratch because that was easier for me to port and manage then Anaconda (not all Python is easy to maintain).
With that said, Cinch is just an simple installer. If you require a system provisioning tool (which I think is what you are asking about), I would recommend SystemImager and/or Warewulf (while it is generally a cluster tool, it is very capable of provisioning thousands of systems in parallel). Both come with cAos-2.
Lastly, Cinch is actually driven by a series of ASH scripts. It is very easy to modify and customize.
I see your point and you bring up a good question. Here is how I (and Webster) define that statement:
Managed: To have under control and direction; to conduct; to guide; to administer; to treat; to handle.
Community: Common possession or enjoyment; participation; as, a community of goods. (2) A body of people having common rights, privileges, or interests... (3) Society at large; a commonwealth or state; a body politic; the public, or people in general.
I think you are very right. BSD fits very accuratly, and we have based some of our models from the success of that project (as you noticed).
Our choice to use RPM was a major factor that drove us to build a new distro. Religion aside, people use RPM, and many developers and organizations have standardized on them. Yet there was no RPM based solutions managed by the community itself.
The lifecycle statement is actually very important when comparing this project to Fedora. For instance, Fedora is basically impossiable to standardize an infrastructure on because it is constantly changing. There is not always a clean upgrade path (which is by design).
By stating that cAos actually has a life longer then 6 months, we are commiting to its long term viability as a solution.
Claiming what? Actually the cAos Foundation has been very quitely doing their thing for about 2 years now. There is no hype about it, and the mentality is that we are doing this because this is what we need. If someone else can get value from it, then great! Appearantly you have the wrong idea about the developers of the cAos Foundation. I for one can tell you that we are rather modest, and just trying to share our work with the community.
I don't even thing the facade of community based means a whole lot these days. There's been a few good ones with a fundamental approach that's different, but not a lot.
I am unclear what you mean the "facade" of community. We have multiple developers and contributors in the project. We welcome members of the community to actually maintain packages in the distro. We are completly open in our build methods and CVS tree... Decisions are made via the package maintainers and core developers themselves. I see it as reality, not a facade.
If you evaluate our approach, you might see that we are doing somethings that are in fact different. Like the use of RPM in a community maintained distro, also our build system, community involvement ideologies, and segreation of a core static ABI from the extended OS package maintainers.