YAFFS

YAFFS is, and will remain, a free-software project. That's why it is licensed under the GPL, to ensure it remains free. However, we also want to make YAFFS available to as many people as possible, and some people who wanted to use it found that they couldn't if it was GPLed. Consideration of the best way to take YAFFS forward has resulted in a dual-licensing scheme, similar to that used by MySQL AB and others. Here we explain how the various components are licensed and our reasoning for doing it this way.

Some of the obvious questions about the circumstances in which you do and do not need a Licence for YAFFS

While the YAFFS code is available free of charge under GPL, that entails the obligation to disclose Source Code for your application using YAFFS. An Aleph One Licence does not impose that obligation and so is attractive for proprietary projects.

We operate a cvs server for our active projects. Here we give details of the setup:-

The server is cvs.aleph1.co.uk. If you just want to browse or download code then it's easiest to access the repository over the web. This is also the best option if you are behind a firewall that does not allow direct CVS access (which is quite common).

If you want to use cvs directly then public read-only access is available, using the pserver mechanism. Execute the following (bash) commands to set environment variables, (or their equivalent for other shells):

export CVSROOT=:pserver:anonymous@cvs.aleph1.co.uk:/home/aleph1/cvs cvs logon