Released: 31 July 2015
ClearOS 7.1.0 Beta 3 is here! This release contains major improvements and insight to the eventual release of ClearOS 7 and replaces ClearOS 7.1.0 Beta 2 as the current running beta.
We are excited to add Samba Directory to the mix. Samba Directory allows for Active Directory equivalent functionality using ClearOS as your Directory Server. Simple user and group administration is available for Samba Directory in the usual places in ClearOS' Webconfig. If you comply with Microsoft's EULA for the tool, you can use Microsoft®'s Server administration tools to modify additional aspects of your Samba Directory including Group Policy Objects.
This beta is built using the new Koji build system. The change to this build system is needed now since it fundamentally changes some structure that we will need to have working smoothly throughout the 7.x release cycle. This new build system should be much more automated and integrated than the past system. As a consequence of this change, updates from Beta 2 to Beta 3 will require a change in the yum repo data and a performance of a dist-upgrade.
ClearOS version 7.1 introduces:
New Upstream Features Include:
ClearOS 7 will feature a Community, Home, and Business version. All versions of ClearOS will install from the same install image. You will be required to select your version at the time of installation in the wizard.
Some of the new apps in the beta are NOT available via the Marketplace but can be installed via yum. Others are still in progress or not yet feature complete. You can find installation and app details further below.
The full changelog can be found here:
yum clean all yum --disablerepo=* --enablerepo=clearos,clearos-updates,clearos-centos upgrade yum clean all yum upgrade
Please post your feedback in the ClearOS 7.1 Release Candidate 1 Discussion Forum.
Virtual Machine and Cloud Images are not available for this beta.
There is no supported method yet from upgrading from ClearOS 6 to ClearOS 7. Additionally, the layout for Beta 3 is different due to the changes in the build system to Beta 2. Upgrades from Beta 2 require changes to the repo content and performance of a dist-upgrade. There may be support for migration of configuration backups.