I’ve switched the web site software – again. If you are having trouble with links from other sites or anything you had bookmarked, you’ll need to browse around and locate the content again. I’m going to have forums back online soon and will post some of the major developments that have been made in the release of the Coyote Linux v4.00 distribution. I have made very infrequent posts about its progress as it is steady, but very slow. I think users of previous releases will be very pleased with many of the changes and technology?áenhancements?áthis version will introduce.
I have largely caved to the previous requests to make Coyote a much more all-in-one distribution for those wanting to use the Linux system as a multi-function machine (in addition to just being a firewall). The use of Suse Studio as a base for development has allowed me to add many features (smtp gateway, basic web services, etc) as optional components of the core distribution. While I wouldn’t personally run a border firewall with such features enabled, many users have expressed an interest in the past to have their network edge device/router serve these functions. Such functions will all need to be manually enabled and managed outside of the core Coyote administration interface, but will be available for those wanting a more “complete” Linux distribution for use as their network firewall.
More info to follow shortly.
I recently made a switch from trying to use OpenEmbedded for the Coyote Linux base platform to openSUSE. Specifically, I am now using appliances built at: http://www.susestudio.com/ as my testing platform. My development system is running a full install of SUSE 11.2. I hadn’t really looked at SUSE much in the past – however I am very pleased with its installation, hardware support, desktop, and (IMO) the YaST2 system configuration application is FAR superior to the Red Hat based system management utilities.
Many of you are going to question some of the decisions made when I selected the tools, platforms, and techniques for the development of Coyote Linux 4. I am going to write up a post as a preemptive set of answers which I will refer to when the questions, comments, flames, etc start pouring in.
One of the biggest changes to this release of Coyote Linux is the use of C# as the primary development language used for most of the administration, configuration, and maintenance utilities. Previous implementations of Coyote Linux made heavy use of C, Pascal (namely Delphi), and Bash shell scripting for this purpose. The change is being made to C# after nearly 2 years of working with the language in a cross-platform setting which involved the use of both Red Hat Linux and Windows 2003/2008 servers. The ability to use a single development environment (in my case, Visual Studio 2008) and produce executables that will execute in unmodified form on both Linux and Windows has seriously put the “R” in RAD programming. I am still actively involved in projects that require the development of cross-platform utilities and am already paying for all of the necessary licenses to provide my company with a full array of software and hardware to develop applications that work in a mixed server OS environment.
I have spent a great deal of time testing C# applications under Linux using Mono as the executing environment. While this is not necessarily the best choice for small, embedded hardware (486 / ARM class processing power) it works very well for anything using i686 or better technology. Another wonderful advantage of using this technology is the ability to run the same set of executables on both 32 and 64 bit hardware without the need for compatibility libraries to be installed. The installation of Mono dictates the 32/64 bit execution environment, preventing the need to recompile the full Coyote Linux software package.
Coyote Linux 4.0 will target 2 installation platforms. The first release of the Coyote Linux security suite will be as an add-on to existing installations of Red Hat or CentOS 5. After the suite has stabilized as an addon for existing distributions, a new installation OS will be added to accommodate the install on bare metal hardware and as both a Xen and VMWare hypervised guest.
The web sites that make up the Coyote Linux and Vortech Consulting customer services, product distribution sites, and e-commerce transaction processing consist of a mix of both Linux and Windows 2008 servers. The design chosen allows me to make use of the last 2 years of my work developing e-commerce and software delivery systems.
If you have any further questions or comments, you are welcome to visit the forums or post a comment to this blog.
I have decided to discontinue official releases of the Coyote Linux Floppy Firewall. My decision to do so has been a long time coming and was a hard one to make. I simply do not have the time nor desire to continue development of a floppy based solution. In fact, I don’t even own a system that has a floppy drive.
I would like to thank all of you that have contributed to Coyote’s development over the years. It would not have been near the success that it is if I had not had help from the many individuals willing to contribute their time and talents to help develop one of the most complete and user-friendly mini-distributions of Linux.
Anyone wishing to continue working on Coyote is welcome to do so, but will need to change the name of their distribution. In addition, I must remind the community that the Windows Wizard is not (and never has been) covered under the GNU public license and may not be redistributed in any modified form.
Finally, please do not email me asking me to keep the project open. I have given this decision a lot of thought and it is final.