MidnightBSD Developer Journal

Smultron and i are working on migrating the website to the new design he has created.  Feel free to tell us about broken links, etc.  

Nightlily offered to help me with the german pages when she gets back from her trip to Mexico.   

mports are in the best condition in months.  Run 96 on magus had only 11 failures and very few untested ports.  Anyone holding off on updating mports, should consider grabbing a copy.

Please report any ports that are misbehaving as we want this to be very good for the release. 

When is 0.2 coming?  Very soon.  I'm doing one last magus run for testing.  Run 98 will be tagged upon completion pending any new issues.  That will conclude mports for this release.

Here is a list of remaining task prior to 0.2 release: 

• Placing run 98's binaries (magus) on the FTP server
• Changing the name of the release in the src code (0.2-RELEASE)
• Making last minute adjustments to src/release and sysinstall to handle the packages we generated.
• Fixing the csup/cvsup files and src/Makefile to point to the cvs branch
• Creating a test iso set on x86 to find any last minute problems.
• Tag the src tree
• Build the final isos 

I've reverted to libiconv 1.11.  Several key ports have been failing on magus that would hold up the release.  We can't wait for all these developers to fix their code, and patching would take too long in this case.

You'll most likely have to rebuild a good number of ports.  I suggest waiting until after the release. 

There is a yet unpatched security vulnerability in libxslt.   We'll update our port as soon as possible.

 Our objective has been to stabilize the ports tree for 0.2 release.  Two ports have been causing us headaches for way to long.  They appear to be working.  graphviz and gnuplot are fixed.

We've also updated doxygen which failed on magus.  Several other ports are still broken including GNUmail, Abiword, xemacs-packages, and finance/libofx. 

Regardless of our situation, I plan to tag the ports tree this week.  We need to get moving on 0.3.

Our mports are not updated for these yet. 

Several days ago, we had an issue on our main server, stargazer.  It was corrected, but mailman was not restarted completely.  That's been corrected and users should be receiving mailing lists postings.

We've had light activity so far this month.  Many developers are busy with summer vacations, moving, trips, etc.   

I've updated the rsync port to 3.0.3 and fixed the Firefox port  The linux-thunderbird port was updated for a security issue last night.  

We're still having some problems with graphviz building on some systems and magus.  It works on both of my local systems.  graphviz is a show stopper for the 0.2 release at this point.  We need that port to build on magus before I can do the release.  The point of this release is to get users a security fixed version with recent packages.  0.3 is a feature/technology release.

 I've setup an anonymous cvs mirror (pserver) for MidnightBSD.  This is rsync'd every two hours from stargazer.  It won't help with bandwidth as it's still on the same network, but the system is much faster (sata, pentium d 805, ...) 

For instance, to checkout mports:

cvs -d :pserver:anonymous@ds9.midnightbsd.org:/home/cvs co mports

Foxconn is delibertly forcing users to run windows on their motherboards. Avoid their motherboards.

http://www.pcworld.com/businesscenter/article/148854/attack_code_released_for_new_dns_attack.html 

 The security issue affecting some operating systems with X11 forwarding is not an issue on MidnightBSD.

http://www.openssh.com/txt/release-5.1

I began the day planning to create a snap in preperation for our new release.  I ended up modifying the script used to separate packages for release isos, and looking at what packages are missing that we might want to include.

One problem I had not anticipated was the position we're in selecting a default desktop environment.  I had been planning on using Etoile + GNUstep.  That may still come to pass, but Etoile is not ready for this release.  The next logical choice is Gnome.  It is not used extensively in the BSD community as PC-BSD and DesktopBSD both use KDE.  I'm indifferent as I alternate between KDE, Gnome and other environments on my systems periodically.  I like to try out new verisons, and I'm fond of applications from several environments.  I started this project hoping to offer something unqiue, and I want to suceed at that.  If we role with Gnome, it would be new in the BSD world, but nothing special among the countless Linux distros and Solaris.  Many people do love Ubuntu and that ships with Gnome.  Another problem with Gnome is that it depends on Firefox.  We can't ship a Firefox binary do to usage restrictions for new ports.  The webkit work with the project might save us on this issue down the road. 

Presuming a native Firefox or Seamonkey is built, it's possible to get a fully working Gnome environment on MidnightBSD.  KDE 3.5.8 is also working, but we don't have a QT4 port available to work on KDE 4.1.  As for GNUstep and Etoile, I think we need some people porting and upstreaming patches for those projects to proceed on those fronts.  I also have an interest in improving the underlying operating system.  I have a few radical ideas that I'd like time to explore.

MidnightBSD 0.2 will ship with KDE-lite or KDE3 ports as a necesity.  I also plan to include the GNUstep ports if they're working at the time of release.  Until the browser matter is settled, I can't do much with Gnome. 

I'd appreciate feedback via comments on this blog, email, mailing list communication or chat in iRC about the direction you think the project should go. 

Regardless of the choices, we need to accomplish the following tasks.

1. Finish the new installer and package tools

2. Select a desktop environment, port it completely without any "freebsd hacks" and upstream the patches. 

3. Work on integration of the environment with the OS, and usability.

Then there's the matter of making the kernel changes I'd like to see as well as bringing in new hardware support.

Recently, I added pcc to midnightbsd. While testing mksh, the maintainer noticed that some symbols were missing. Linking libgcc with pcc worked as did libpcc (Mirports version).

Any programs compiled with pcc should link libpcc with them.

Most DNS software packages have a common design problem, they don't use random source ports. There is a great deal of coverage on this issue at isc.org as well as a CVE, etc.

I've committed a patch to MidnightBSD CURRENT tonight. Until I test it seriously, I'm not going to put it on stable branches. I've also updates all three bind ports with the latest patch level.

These patches are known to slow down bind. I don't think most midnightbsd users run DNS servers, so it shouldn't be a big issue. Any ISP or larger DNS deployment should update their servers though.

My patch does not include all the documentation updates.

I saw this article linked on the FreeBSD website today. It might be helpful for beginner kernel hackers.

http://www.freesoftwaremagazine.com/articles/writing_a_kernel_module_for_freebsd

Tonight, I updated the chroot tarball used by 0.2 magus nodes. This will allow us to test and build ports with a very similar environment to a 0.2-RELEASE machine.

I'm hoping to get this release done by the middle of the month, but we'll have to see what happens with mports.

I updated some of the t-shirts on the MidnightBSD store with our newer logo. I also created two other shirts. "I Love BSD" and "Hello World" are geeky shirts without the MidnightBSD branding.

I have not purchased any of these shirts yet, so I don't know how well they come out. I used at least 900pt x 900pt size with each image.

http://www.cafepress.com/midnightbsd