plainly said if you unforked pfSense and M0n0wall you would essentially not have alot of what both offer because then they would not be reaching such diverse goals, both projects are good, and have solidbasis to exists, its like saying unfork BSD... theres a purpose for them to exists, and other ides will grow from these projects im sure, even a NAS system has grown from m0n0wall. If you dont like what they are doing create your own, or add to whats missing for what you need, hence the reason i track both projects and have a customized build.
On Sun, 2005-11-27 at 16:42 -0500, Chris Buechler wrote: > Colin Smith wrote: > > >Also, it is my understanding that Scott and Chris originally forked because > >of Manuel's (obvious) resistance to taking his project in an entirely new > >direction. Few if any bridges were burned. It most certainly was not an 'ego > >thing'. > > > > > > > > I won't bother responding to most of this, but I will say this much. > Someone emailed Manuel (m0n0wall founder and primary developer) and me > (primary m0n0wall list poster and doc writer, as well as co-founder of > this project) suggesting we merge the projects and not split efforts. > Manuel replied before I got a chance to, and he's on the same page as > us. Paraphrasing what Manuel said, the goals of the project are > significantly different enough that it makes sense to keep them > separate. m0n0wall's focus on embedded platforms leaves it with a file > system that isn't suitable for a packaging system, and while it might > change slightly for version 1.3, it will still not be suitable for most > packages because it will never be a "normal" file system. > > Manuel is a stickler for doing things the *right* way, which is what has > made m0n0wall a killer project. But that's also left a lot of users out > in the cold, without the ability to do things they want or need to do. > Manuel's stance is these things don't belong on a firewall (whatever > they might be). And I agree. Things like ntop, various network > management tools, and all kinds of similar things, don't belong on a > firewall in an ideal network environment. But, when you look at a > network that only has maybe 3-5 machines, or maybe even up to 10-20, > segregating these services leaves you in a situation where you have more > servers and administrative machines than end user machines (or at least > an unacceptably expensive ratio). It's better to have these things on > the firewall than to not have them at all, when you have no other > feasible options (for non-technical reasons, usually cost). > > In short, Manuel agrees with what we're doing, we obviously agree with > what we're doing, and there's absolutely no animosity between the > projects, so there really isn't any room for argument. > >
