I don't want to say who is right or wrong and what anyone should do with their time since I've realy just started using Endian but I will say this.
1) The endian team has made it pretty clear that the only updates that will come to the community [i.e. non-paying users] will be via the ISO release [and tarball source and rpm packages. This is their choice and I can see where it saves them a fair amount of headaches. 2) For everyone's sake I hope they are making money. It is hard enough to start a opensource company these days so I hope they are able to stay in business. 3) I'm pretty happy with what I've seen so far, I deployed an endian firewall for a Water Department in Southern California with about 200 users. So far [day 8] there have been no major issues other then some kernel tuning I did and the RAID1 set up. There are some features and updates I'd like to see but I'm willing to do this myself. Here is how I'm handling packages and testing. First I installed Endian on a spare machine [a poor little AMD K6-2+ 550mhz with 384MB of memory]. Then I downloaded the source and rpm tarballs listed here http://www.endian.it/en/community/download/updates/ Once you have these you can put them on a webserver if you have one or put them directly on the endian build box. I have webserver so I stuck them both there. Then you need to install gcc and rpm-build and all their dependencies. Start with gcc and just rpm -Uvh gcc-3.4.5-2.endian6.i386.rpm and keep adding the packages to the coammand it calls for until it installs. [I think it was at least 6 packages]. Do the same thing with rpm-build [rpm-build-4.4.1-21.endian5.i386.rpm ]. Once you have these installed you can work directly on the source packages and rebuild, repackage then, and push them out to any endian2 firewall since you have the same base system. I did ClamAV by simply installing the source package from the source tarball clamav-0.88.3-0.endian5.src.rpm. Downloading the newest clamav from clamav.net and putting it in the /usr/src/endian/sources directory remving the old one updating /usr/src/endian/specs file then doing a rpmbuild -ba clamav.spec and it builds a new package and source for you. Not all of them are so easy and you might need to edit the spec file a fair amount but using this system you should be able to stay pretty current with your endian as long as you are willing to put in some time learning about how RPM works. Having said all that I'm willing to post any package I make and hope that it helps out other users. My next spare cycles will be spent finish one more update to the logwatch package so that it outputs html directly rather then the funny way the endian install handles it now [text output which is carved up by a cgi script and posted with pre tags. Looks great until you get a long line, then the tables blowout on the left.] After that I'll probably update p3scan just for kicks, I'm hoping that they bring out IMAP support soon.... And then I need to figure out how to get the content filter from squid to report an IP address instead of "unknown". ;) Well this is getting long so I hope that helps anyone who feels frustrated by the lack of contact by endian developers. Remember the true beauty of open source is that you have the power to make you own changes. Yes it takes time and knowledge but you can do it. -Mike ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Efw-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/efw-user
