Fresh meat...hehe

leeach · 03-13-2004, 01:02 PM

http://www.ekkobsd.org

ekkoBSD as a core OS offers security, stability, and flexibility to your infrastructure. As a default installation, ekkoBSD gives you an E-Mail server, Web Server, ssh, and several other services that would normally need to be added and secured.

Platforms:

ia32(x86)
sparc64
sparc32

Stack · 03-13-2004, 04:38 PM

Quote:

License

Copyright (c) 2003 The ekkoBSD Project
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

I dont think they can legally call the above a *BSD since it is not being released under the BSDL... Anyways looks like you should stay away and at the same time prevent fragmentation...

leeach · 03-13-2004, 05:40 PM

Quote:

Originally posted by Stack
I dont think they can legally call the above a *BSD since it is not being released under the BSDL... Anyways looks like you should stay away and at the same time prevent fragmentation...

http://www.ekkobsd.org/faq/
FAQs
Q: Why did you fork? Why not just join another BSD project and make that project stronger?

A: We honestly made an attempt to do just that, but our ideas were not well received. Instead of giving up, we decided to take advice that has been given many times before: "If you don't like it, you're free to create your own system." This doesn't mean we're turning our backs on the BSD community, or even that we won't be able to make the other BSD projects stronger. We hope that other projects will adopt changes we make, as we plan to adopt changes from them as well. Collaboration is a very important part of developement, and we think that all of the BSD projects should be able to benefit from each other.

Q: That logo looks alot (EXACLY) like Marshall Kirk McKusicks Beastie! Did you get permission?

A: We appreciate your concern. Yes we did.

chort · 03-13-2004, 08:40 PM

Hmmm, it seems very similar to OpenBSD, I wonder if it's a fork?

One has to question why this is really necessary. I don't think FreeBSD or OpenBSD really lacking in the areas they describe. It seems the main focus is to be "user friendly" with a GUI installer, etc... I found the FreeBSD installer to be friendly enough, and you can't beat the OpenBSD installer for simplicity. If it's just a pretty installer front-end, why not just provide a "Live CD" ISO like Knoppix has done with Debian?

One of the big problems with Linux IMHO is that it has made fragmentation trendy. There are hundreds of Linux "distros" and it seems that any half-way amature can start their own distro. On the one hand, it doesn't really tend to dilute the development talent pool because the fork starters are generally much less talented (with the exceptions of OpenBSD from NetBSD and IPCop from Smoothwall), but on the other hand it's a really disservice to users and the community at large to muddy the waters and cause confusion when what is really needed is more standardization (to have any chance of replacing Windows this decade).

Oh well, best of luck to them I guess.

leeach · 03-14-2004, 12:18 AM

Quote:

On the one hand, it doesn't really tend to dilute the development talent pool because the fork starters are generally much less talented

While generally true, I can't be mad at them for basically being forced into doing their own thing.

Stack · 03-14-2004, 01:57 AM

Quote:

Originally posted by leeach
While generally true, I can't be mad at them for basically being forced into doing their own thing.

Can we be mad at them for calling it a BSD when they most likely are not allowed to? As far a i know you have to release the code under the BSDL to be able to use the trademarked "BSD" in the release name...

leeach · 03-14-2004, 09:27 AM

Quote:

Can we be mad at them for calling it a BSD when they most likely are not allowed to?

Let's not go making assumptions here. I hate assumptions...