The following release notes provide an overview of the ClearOS Enterprise 5.1 release. All users should read this document, but special attention should be made by users upgrading their systems to this release.
- Windows 7 Support with Samba 3.4.3
- Graphical console tool
- Improved usability in the web-based interface
- NTP server support
- Core system upgraded to CentOS 5.4
In addition, the following new ClearOS services are available:
- Antimalware Updates (Antivirus, Antiphishing, etc)
From time to time, Service Packs are released with all the latest updates and bug fixes included. If you have the original release or an older service pack installed, there is no need to re-install or upgrade! All you need to do is visit the Software Updates page in webconfig to install all the available updates.
- Released March 5, 2010 - Information on ClearOS Enterprise 5.1 Service Pack 1
ClearOS 5.x supports upgrades from ClarkConnect 4.x and later. Upgrades from earlier versions (or systems originally installed with an earlier version) are not supported. When you run the ClearOS installer, make sure you select the upgrade option. As with any upgrade, please backup any critical data.
In addition, users who have installed third party software packages or used the command-line to install software should also run the following commands:
For those of you upgrading from ClarkConnect 5.0, a live command line upgrade is available:
yum install app-upgradeto51 rpm -e --justdb --nodeps system-logos yum upgrade
You can download ClearOS Enterprise 5.1 from the downloads section of the web site.
- ClearOS Enterprise 5.1 First Release - MD5Sum: bbaff882fc04cdba58cc19772a2f0a45
- ClearOS Enterprise 5.1 Service Pack 1 - MD5Sum: 3b3358c754311a003d70df05d0198888
There are three ways to install or upgrade ClearOS:
- Bootable CD
- USB key (requires Internet access)
- PXE-enabled network card
The User Guide for more information on how to create your install media.
The following key packages are no longer included in this release:
- apt (replaced by yum)
- bpalogin (deprecated)
- dev (replaced by udev)
- dspam (deprecated)
- gallery (unsupported, but still available)
- pcmcia-cs (deprecated)
- squirrelmail (unsupported, but still available)
Apt has been replaced by yum.
The bandwidth management system is very different in ClarkConnect 4.x. Old bandwidth rules will need to be re-configured using the new Bandwidth. Port ranges are no longer supported.
Some options in the Flexshare system have been simplified. In ClarkConnect 4.2 and earlier, it was possible to configure different groups for a single Flexshare. This option is no longer available – a Flexshare can only be assigned to a single group.
Support for very old CPUs has been dropped (i586 / Pentium 2 or earlier).
The Bacula LAN Backup/Restore feature will be deprecated in a future release. You can still use this powerful backup tool in ClearOS, but we expect to replace it with a simpler backup tool. For those with fast networks, the Remote Server Backup solution is a good option.
The new Protocol Filter tool handles peer-to-peer blocking (among many other protocols). If you have enabled peer-to-peer blocking in ClarkConnect 4.x, you should review and reconfigure your peer-to-peer policy
The /dev/ system has been replaced by udev.
The web proxy software has been upgraded to 2.6.STABLE21. I mportant features (notably IP reporting for the content filter) are not yet available in Squid 3.0. For this reason, ClearOS will continue to use the same source code version used by Red Hat Enterprise Linux / CentOS.
The Windows/Samba software is now completely integrated into the ClearOS LDAP/directory system. If you have configured your 4.x system as a primary domain controller (PDC), you will need to rejoin every workstation to the 5.x system. This is an unfortunate but unavoidable requirement in the 4.x to 5.x upgrade.
Just to re-iterate the warning message above: if you have customized the Windows/Samba configuration outside of the webconfig, you will need to carefully review and possibly re-integrate those custom changes. If you enabled roaming profiles in ClarkConnect 4.x, then we're looking at you.
If you are upgrading from 4.0, 4.1 or 4.2, please review the ClarkConnect 5.0 release notes.