OpenBSD Journal

ekkoBSD?

Contributed by jose on from the another-s/OpenBSD/MyBSD/g-project? dept.

ak writes: "This has just appeared on freshmeat. There's not much to website, and most of the links a broken. It does say it's a fork of OpenBSD 3.3-CURRENT.

http://ebsd.sunsite.dk/ http://freshmeat.net/releases/125141/ "

Some people I know had a look around at this. Without starting a flame war, it looks like it has a few glitches due to the state of the build they pulled. Additionally, they are on the same track as MicroBSD was, and have mixed ekkBSD and OpenBSD references throughout. You may want to steer clear of this project until it proves itself to be legitimate. Some organized project to try and do different things with OpenBSD, such as applying new ACL patches and the like, sounds useful, but only if it's also got the same quality control that OpenBSD does.

(Comments are closed)


Comments
  1. By Darren () darren@dazdaz.NOSPAMM.org on mailto:darren@dazdaz.NOSPAMM.org


    So basically ...

    Differences Between OpenBSD and ekkoBSD:
    ---------------------------------------------
    "This OS is intended to be a platform to build secure single servers and workstations, with more user-friendly tools to help speed up installation and administration. The intent is not to allow "the un-read masses" to build these systems, but to allow the people who take the time to use ekkoBSD an easier time doing it. It is also our intention to keep politics to a minimum in the development of ekkoBSD.
    "

    Sounds like a plan, but rolling these back into OpenBSD would make life easier and is probably a better strategy long term.

    Comments
    1. By Anonymous Coward () on

      Sounds like a plan, but rolling these back into OpenBSD would make life easier and is probably a better strategy long term.

      Not all changes would be accepted by Theo, such as MAC and port ACL's (if that's what ekko is working on). But you're right for patches that are inline with Theo's goals.

      Is a whole new OS necessary? Perhaps they're planning on Major changes, but if they are also so lean on developers, wouldn't add-on patches be easier, a la Stephanie? This would also cure the need/desire to patch every single file to include "copyright ekkobsd" as not all files need to be changed.

      Comments
      1. By zil0g () on

        ever heard of "Linux"? this is "how it's done".

        thank you, and good night.

        Comments
        1. By Anonymous Coward () on

          how what is done?

  2. By Anonymous Coward () on

    the word "waste" comes to mind.

  3. By Anonymous Coward () on

    one wonders whether this is the reincarnation of MicroBSD.. ; )

  4. By djm () on

    Why bother releasing OpenBSD as a whole new OS when all you want are a couple of patches relative to the canonical distribution? Why not just maintain a set of coherent patches? By choosing this route, the ekkoBSD developers make additional work for themselves and are always going to be behind OpenBSD for fixes.

    I sincerely doubt whether they will be able to attract the combined capability of the OpenBSD team, so their OS is likely to be OpenBSD+patches for the forseeable future. In this case, why not just call it OpenBSD+patches and not pass off other people's work as your own?

    I'll also note that, unlike other OpenBSD+patches projects, ekkoBSD doesn't direct people back to the OpenBSD poster and CD shop.

  5. By Rick Collette () on http://ebsd.sunsite.dk

    I e-mailed this to Jose, he said I should post this to the site.

    One thing that was brought to my attention, that was purely an accident, was the S&R inside the INSTALL.TXT which refers to "OpenBSD 1.0".

    I'd also like to point out: This is not meant to be OpenBSD+patches. It is a complete fork.

    ------------------
    Hmm.. looks like I got a little more attention than I intended. So I'll go ahead and shoot this "why I did it" bit + explain some of the concerns.

    1) I'm not a crew of people. I'm one guy. So, yes - ekko will follow Open in technology as far as being up to date.

    2) Is this MicroBSD? No. We're not even geographically close: Outback Dingo is in Florida. I live in California. We also don't share the same ideas and goals (100%).

    3) Why don't I point back to the posters and shirts and stuff? I just don't want to go anywhere NEAR this one. Open was forked from Net, I've forked ekko from Open. I'm also not a big fan of providing funding to someone who bashes my country.

    4) About the copyrights: I have only added (note: ADDED, not searched and replaced) my copyright to things I actually made changes to. I have left the OpenBSD copyright info intact, because that's what the BSD license says I have to do, and the Open team did, after all, perform substantial code changes to most of the Net OS.

    5) Why another OS? Why not OpenBSD+patches? No more than the project leader of Open wants people confused with Net, I don't want people confused with Open. I don't want people to report *my* coding problems, bugs, etc to the Open team when it's not their problem.

    6) The biggest gripe from people this far seems to be the typical "eh, it's just open with some changes.. big deal." Yep. That's right. No argument here. Everyone needs a hobby, this is mine.

    Comments
    1. By Joel Rees () joel~at~alpsgiken^gr=jp on mailto:joel~at~alpsgiken^gr=jp

      Well, Rick, I'd suggest you make this list the start of your FAQ.

      But you might also want to put a URL in #3, so I can get an idea of what it is you call US-bashing.

    2. By Anonymous Coward () on

      you say:
      "I'd also like to point out: This is not meant to be OpenBSD+patches. It is a complete fork."

      then you say:
      ""eh, it's just open with some changes.. big deal."" Yep. That's right. No argument here."

      so, which one is it? a fork, or "OpenBSD+patches"?

      "Open was forked from Net, I've forked ekko from Open. I'm also not a big fan of providing funding to someone who bashes my country."

      you state you forked, and you follow by saying you do not support those who bash your country. so? do explain.

      "I don't want people to report *my* coding problems, bugs, etc to the Open team when it's not their problem."

      a whole lot of blah-blah that does not prove how this has happend or will happen.

      somehow, you plan on removing every instance of the name "OpenBSD" from your fork so your users do not get confused? good luck. that should take a few years without breaking the law.

      I can not reason *why* a fork is needed. making a few changes and additions does not warrant a fork.

      I can see a project where its sole purpose is to add fucntionality the core OpenBSD group will not allow. that is worth doing after your patches are rejected, not until then.

      Comments
      1. By tedu () on

        orig quote: "I don't want people to report *my* coding problems, bugs, etc to the Open team when it's not their problem."

        you: "a whole lot of blah-blah that does not prove how this has happend or will happen."

        me: you missed the point. everytime somebody releases a patch (ipf, stephanie, ...) people show up on misc@ saying it doesn't work. he's trying to be helpful by differentiating products. i don't know how he can prove to your satisfaction that people won't show up on misc@, but at least he can try.

        with patches, people ask "why doesn't openbsd work with this patch?" if it's not a patch, but a renamed project, i think it drives home the point. people will realize "why doesn't ekkobsd work?" is not an appropriate question for misc@.

        he's not trolling the mailing list, and to my knowledge, wasn't responsible for the deadly post. so who cares?
        whether you find it useful or not, let him have his fun.

    3. By click46 () click46@genmay.net on mailto:click46@genmay.net

      sounds like your sole motivation is politics. I dont like Theo bashing the US as much as the next guy, but politics and code don't mix well at all.

      good luck.

      Comments
      1. By alias_51 () on

        "sounds like your sole motivation is politics. I dont like Theo bashing the US as much as the next guy, but politics and code don't mix well at all."

        That could be exactly the point, starting ekkoBSD means not dealing with OpenBSD politics, kind of like starting OpenBSD meant not dealing with NetBSD politics. I think most people have a much easier time dealing with their own opinions and politics.

        And that wasn't only reason on the list

      2. By RC () on

        > I dont like Theo bashing the US as much as the next guy

        I'm an American, and frankly, I agree with Theo for the most part.

    4. By Rick Collette () on http://ebsd.sunsite.dk

      I am really happy that this has sparked such interest...

      #6: A fork IS a change from something original. 5 and 6 are pretty much the same.

      What I'm saying is what I mean. Don't try to read too much into it, I'm not that deep and philosophical.

      This is going to happen. I'm not asking for approval. If it lasts 3 months, then I had fun. If it lasts 3 years, I had even more fun. If you want to help me out, I'll take the help.

      If this does cover everything, I apologize. Please don't take my not answering any more questions as me being rude, I'm just really busy right now and probably will not be able to respond to things as quickly.. as I said before: this is my hobby. I'm going to enjoy it.

      Comments
      1. By tony () tony@libpcap.net on http://libpcap.net

        This is quite a project... how do you plan on syncing all the changes that are added into OpenBSD? Will you blindly commit, or will you go over every line to make sure it's something you want in the first place?

        What about other things that have been showing up on the misc@ lately? Perhaps this is a good opportunity to use qmail or postfix instead of sendmail, and some other DNS than bind? What are your thoughts on replacing other programs for other ones (to make it more ekko than open).

        Good luck with your endeavors.

    5. By Anonymous Coward () on

      "I'm also not a big fan of providing funding to someone who bashes my country"

      Give me break .... A piece of advice: never leave the USA because *everybody* has a problem or two with some your government's policies and actions.
      A seeming inability of too many American citizens to think independantly of Whitehouse statements and Fox-news reports is bound to make people question the sophistication of the 'average' American -- they seem to be overly naive for citizens of a country that is suppose to have a public education system.

      Theo as I recall questioned the motives of your government over it's war in Iraq (as did many of your own citizens). You have to admit (if the fanatical patriotism in the air hasn't completely destroyed your brain) time hasn't exactly lent much support your current governments claims that were suppose to 'justify' an invasion. It pretty much looks like they invaded primarily to get control the oil reserves from here....

      In any case ... none of it should have anything to do with funding operating systems.

      Comments
      1. By Anonymous Coward () on

        "A seeming inability of too many American citizens to think independantly of Whitehouse statements and Fox-news reports is bound to make people question the sophistication of the 'average' American" Too many? Could it that"too many" Americans ARE thinking independently and that their philosophy just happens to coincide with that of the current White House and Fox News? Fox ratings are high because people tune in to what they want to see and hear. By the way, this thread began because somebody decided to think independently and started ekkoBSD.

        "they seem to be overly naive for citizens of a country that is suppose to have a public education system." The correct usage would be "supposed".

        "It pretty much looks like they invaded primarily to get control the oil reserves from here.... "
        There's nothing to say to someone predisposed to hate us. In the end, it's binary. You're for us or against us.

        Comments
        1. By Anonymous Coward () on

          "Could it that too many Americans ARE thinking independently and that their philosophy just happens to coincide with that of the current White House and Fox News?"

          No, not likely. To be thinking independently and agree, they would have to at least be made aware of all the facts of a given matter. Taking the issue of Iraq again, it is clean the American people were not given correct information by their government. Thus support given to the government by anyone who believed it was given under false pretenses. Whether the administration lied, or was just wrong -- time will tell, but the statements of at least one outgoing intelligence official tends to favour 'lied'.

          The correct usage would be "supposed".

          Yes it is -- and trying to discredit a person rather than counter their arguements is called 'poisoning the well'. A well known means of fallacious arguement, and the obvious reason you pointed out a mistake in spelling/grammer. Touche.

          There are a host of reasons (some rational, most not) that so many people 'hate Americans'. However, making a critical observation of a government when there is a clear reason to suspect their motives (and the failure of a large number of people to question them) hardly constitutes an irrational predisposition to hate an entire diverse group of people.

          The "you're for us or against us" thing is just idiocy. You've definately listened to one to many Presidential speeches.

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]