I never thought much of the site either or that Yes Linux would last as long as it has but it's been around for a few years now and since you already seemed to have lived the entrepreneur's dream lets not go and step on or make fun of someone elses dream.
Plus according to the Yes Linux forums they've moved away from the SME base they started with. I think the greencomputer.com started out using e-smith/SME as it's base also but has probably moved away but I'm not sure on that.
I've copied the below from Yes Linux forum
YES Server -> YES 1 is derived from SME Server, but YES Linux -> YES 2 is a complete rewrite of the product. As is stands now we don't have any such migration tool from SME Server to YES Linux. We hope to have atleast a HOWTO that describes such a process. We are working with Elitelan
http://elitelan.com to develop such a document. If you are interested in participating or even developing an automation tool please feel free and we will help you in the process.
Here are some of the major changes from YES 1 -> YES 2:
- system now based on java
- new dynamically configurable java initial boot process
- configuration system now uses ant (used by internal application or commandline)
- configuration files don't get overriden so any custom changes are permenant
- changed database servers from mysql -> postgres
- changed email servers from qmail -> postfix
- changed webmail from imp -> squirrelmail
- changed imap server to courier-imap (we still use Maildir mail storage format so existing mail is portable)
- upgraded to apache 2 and all yes specific configurations use modular fragments not one monolithic file
- only one system account will be <administrator> created during introduction. all other accounts are virtual accounts
- all virtual accounts are stored in postgres vs native (allowing for single signon - SSO)
- administration application will be able to integrate any language so third party developer are free from writting perl wrappers
- backup system uses mondo rescue ->
http://www.microwerks.net/~hugo/ - YES Linux system updates can now be executed autonomously and users can build custom repositories with which the update process will use for synchronization.
- pluggable authentication and synchronization method for system updates
- filesystem is journaled using ext3 and has a logical volume manager (lvm)
- removed of samba (webdav is the preferred method)
- removed template based system
- removed perl configuration system
- removed the requirement that only our administration application can be used. now any such tool can be used such as webmin