MidnightBSD Developer Journal

I just uploaded an AMD64 snap to the FTP server. It includes all the recent enhancements such as OpenSSH 4.6, new sound code, etc. It does not include binary packages. The mports collection included was taken during transition with xorg. It would be useful to update mports after installing this snap.

The sparc64 snap is not ready yet. There are still some problems with sparc compatibility.

bugreport.midnightbsd.org was fixed.  Apparently I can't type in URLs properly.  Users should now be able to login.  bugzilla stores the base url in the database and this was entered incorrectly. 

linux-firefox needs to be updated to 2.0.0.3 which I will hopefully get to tonight. 

sparc64 release building is broken.  It appears sunlabel is broken so if you upgrade from an older release keep an old copy of this lying around until its fixed.  I was going to add a bug for this when I noticed bugzilla :)

x11-tookits/vte was reported broken today.  I'll be looking at that soon.  The transition is continuing to keep ports out of /usr/X11R6. 

We've been asked about migrating/merging to another ports system which may or may not happen.  We're talking it over right now.  In the mean time, we are operating on the assumption we'll keep our own ports.  There are pros and cons to this approach such as not worrying about some of the ports issues.  We would still need to build guis, package management and other tools on that system and it may or may not hold us back with GNUstep related elements.  The last point is my largest concern at the moment. 

Something to think about is ipfw.  Apple's working on some new extensions to ipfw for 10.5 that might be interesting to do in mbsd (see below lol)  Dynamic rulesets that alter rules based on conditions so that say large storms of traffic to port 80 that are "unusual" would be blocked by 10.5 server, etc.  The concept isn't amazing but their implementation might be.

And now for some good news.  Allbsd.org will start mirroring our CVS and possibly our FTP server.  I'll post details on the midnightbsd website later.

Lastly, I guess the MirBSD project doesn't like us using mbsd as an abbreviation.  I was under the impression they were just using mir or else I wouldn't have gone there.  I suppose some people might be confused so I'd love suggestions on alternatives.  mibsd seems weak.  I guess we could just call it Midnight as DragonFly does with their stuff....  ideas welcome.