MidnightBSD Developer Journal

As promised, we are posting more about MirPorts on MidnightBSD.

First, there is some information on how install MirPorts here, http://www.mirbsd.org/ports.htm

I'd like to thank the developers at MirBSD / MirOS for porting to MidnightBSD. 

We still consider mports as our primary ports system but we felt it was necessary to give our users more options.

Laffer1 wants more time for coding so I (Raven) will be handling some of the MidnightBSD blog updates from now on.

We were not accepted into the Google SoC program.  It's a bummer but let's move beyond that.  It looks like FreeBSD, NetBSD and DragonFly BSD were accepted (interesting no OpenBSD).

The ideas page will remain up.  http://www.midnightbsd.org/soc/

If you're a student  (or just a regular old developer) and would like to join the project, go to the developers page, http://www.midnightbsd.org/developer/index.html. 

The build cluster is back up at EMU.  We've moved the status site to http://www.midnightbsd.org/magus/

As the database schema has changed, the site is still undergoing work.  ctriv@ has done an excellent job with the new version.

We're now able to run multiple architectures and OS versions at the same time. 

MirPorts is now working on MidnightBSD. This now gives users a choice between two ports systems. I'll post more on this when I get time. MirPorts also run on MirBSD and Mac OS X.

mports:

Anyone using Dovecot should update to the new version in ports. There was a recent security issue.
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1218

We're still upgrading gnome ports for the 2.20 release. After that, we'll probably update KDE to 3.5.9 and then look at 2.22 gnome.

Chris and I did an interview regarding mports late last year. it's now on the NetBSD website.

http://www.netbsd.org/gallery/pkgsrc-interviews.html#mports

There are many interesting interviews about various ports systems in the BSDs on that site. Check it out.

We're working on a new MidnightBSD wiki. It will contain some documentation, todo lists, and other elements that developers and users want to collaborate on.

http://www.midnightbsd.org/wiki/FrontPage

The FSF has a nice list of supported wireless chipsets on Linux systems.  I have not yet reviewed the list to confirm that all of them are supported in MidnightBSD, but if not it might be a good area investigate.

http://www.fsf.org/resources/hw/net/wireless/cards.html

A third party is selling MidnightBSD 0.1 CDs.

http://www.linuxcd.org/view_distro.php?id_distro=394&PHPSESSID=8bb30f794a15cc2f17704dd93982b3cf

We do not get any economic gain from the sale of these CDs, but it might be an option for those on low speed connections.

First, a security update was applied to CURRENT for users who turn on the random IP id feature. It is off by default. This feature has a flaw in the random id generation.

See http://www.securityfocus.com/bid/27647/info

Second, we've updated a large number of ports in the last few days. The astro, archivers, accessibility, and net (except samba3) ports have been updated with the latest versions where possible. I'm currently working on the audio category.

Progress on Gnome 2.20 is still going strong as well. ctriv had a bit of a hardware snafu which has slowed the deployment of the new cluster software. I'm hoping to have many new port updates ready when it's back online.

Magus has been down since december for a rewrite. I've discussed this previously. The build master was brought down for a faculty member to take the video card in the last week. It had been up 113 days which is a record for any machines I'm running. The website has not been restored as of yet, but the system was upgraded to 1GB of RAM.

ctriv hopes to complete the software soon.

I've modified the analog port to report several additional BSDs including MidnightBSD, MirBSD and Dragonfly.

CURRENT now has a patch to correct a potential security issue with sendfile. Files were not checked prior to serving which would allow a file that was write only to be served. While this scenario is rare, we decided to fix it anyway.

sendfile is used by many daemons including Apache httpd.

Analysed requests from Fri-14-Sep-2007 11:13 to Fri-15-Feb-2008 10:04 (153.95 days).

Successful requests: 311,495 (10,072)
Average successful requests per day: 2,023 (1,438)
Successful requests for pages: 118,349 (4,210)
Average successful requests for pages per day: 768 (601)
Failed requests: 54,531 (1,623)
Redirected requests: 52,518 (1,814)
Distinct files requested: 41,433 (4,365)
Distinct hosts served: 19,626 (1,680)
Corrupt logfile lines: 15
Data transferred: 1.03 terabytes (21.44 gigabytes)
Average data transferred per day: 6.88 gigabytes (3.06 gigabytes)

I've updated several of the browser ports to correct security issues.

Firefox & linux-firefox
linux-flock
linux-seamonkey
Opera & linux-opera

I'm happy to announce the release of MidnightBSD for amd64 systems. (and Intel equivalents) This release does not include packages for KDE and several other programs like the i386 release, but you can build them with mports. XORG, Samba, WindowMaker, and several other ports are on the isos though.

The packages are also up on the FTP server along with the ISOs.

ftp.midnightbsd.org now uses round robin to speed up downloading packages with pkg_add -r, etc.

If you need to get to our main site, use ftp1.midnightbsd.org

ftp2 and ftp3 are aliases for our mirrors.

There was a minor build problem with sendmail in current. It has been fixed as of a few hours ago. Current has built successfully on an i386 box.

We're also testing a new threading fix for libpthread in relation to fork() calls.

During December, we had to shutdown the build cluster for the holidays. In the mean time, many new computers were purchased and shuffled around at EMU. Systems were moved and disconnected. Today, I've restored access to 3 cluster nodes. Each node currently has 0.1.1 (snap) on it which was basically 0.1.1 release. I'm upgrading the nodes to 0.2. These nodes are labeled build1, build2 and build3. We also have a 0.1.1 node and the build master working.

At the same time, Chris has been working on rewriting parts of our cluster software to work better with multiple architectures as well as support multiple releases concurrently. When the cluster is back online, we'll have 9-10 nodes running on p4 chips with either 0.1.1 release or 0.2 current. The cluster build time will be slower, but we can test both branches. A full build took less than a day with all the nodes. Usually it was done in 10 hours. Based on the increase in ports and less nodes, I suspect it will take a day or so to do a run.

In addition to this work, I'm also planning on setting up two machines to do amd64 builds, and one or two machines for sparc64. Chris already had a sparc on current for this purpose.

The Eastern Michigan University computer science department has been quite generous giving us access to so many machines.

I've been quite lazy about maintaining this developer blog. I'd like to catch people up on happenings in the project.

First, smultron has been working on a new website design for us. It includes a new logo design similar to the logo we're using on the blog and cia.vc. MidnightBSD was named after my cat and this new logo includes a cat as well as the obvious other usage of Midnight. I'm very impressed with his progress on the site. It will be published when it's complete. Originally, we had hoped to publish a new site with the 0.1.1 Release, but well things happen. The new design improves navigation quite a bit.

Chris (ctriv@) is working on libmport. This is the library that will be used with the command line and GUI replacements for pkg_add and friends. He has made great progress with most of the new code in his local subversion repository. He's promised a checkin of that code soon. raven@ has been looking at the libmport code in preperations for the new GUI tools to manage ports. I believe she is planning on using GNUstep. Chris will write the mport command line tool.

I've been working on several things. The build cluster found many ports that are broken and we've been trying to get many ports current or at least patched for critical security holes. KDE was updated over the weekend to 3.5.8. We're behind on many other ports including php, seamonkey (well this one isn't really done anyway), gnome related ports, etc. I committed an update for php5 today, but many of the "extras" are not updated yet. With the build cluster down, I can't test many ports at the moment. Please submit bug reports or email us if you find bad ports. (math/R is known to be broken as well as devel/ncurses)

The build cluster has not been run since mid December. We had to shut it down for the holidays at EMU and ctriv@ has been working on a new version of the software to allow us to test multiple OS versions and architectures. However, his work was stalled on that so that he could finish up libmport during the holidays. I suspect we'll have the build cluster hardware setup by next week and some of the machines upgraded to CURRENT. Our new plan is to run 5 machines on CURRENT and 5 on 0.1.1 for i386. We also want to test CURRENT on amd64 and sparc64. ctriv has a sparc machine for that and I'm hoping to get my netra working as well.

I have been working on the Live CD and installer as well. I'll post an update on that next week.

archite created a wifi network script that looks interesting. He's posted it for the OpenBSD community on undeadly as well. He's also been doing some scripting for things on stargazer.

We did an interview for the NetBSD pkgsrc 10 years celebration, however it hasn't been posted yet. It was a fun interview.

I've been upgrading our server "stargazer" which hosts the website, cvs and other services for MidnightBSD. I recently purchased two seagate drives for a RAID 1 on /home where I store the CVS repository and other files. The motherboard has an onboard intel raid controller (ATA).

That process was fairly painless.

The other issue is the failing video card. The fan on the current card is wobbling and occasionally stopping which has caused problems. I'm not in a position to run headless with the system, so I purchased a new evga nvidia 6100 LE AGP fanless video card from NewEgg. However, the package was stolen at my front door (or never delivered). After spending half my morning on the phone with Fedex and contacting NewEgg, I have a replacement coming in 5-7 days. Both companies have provided courteous customer service, but I'm left wondering what happened to my video card. Was it stolen on my doorstep? Did a driver forget it on the truck? Including shipping, the card was only $43 dollars. I guess at this rate, I could have gone to a local store and bought a card. Of course, then it wouldn't be fanless.

I'm left with a whining video card for another week. In case anyone is curious about the server specs, I'll list them now.

Dell Precision 650 Workstation
Dual Xeon 2.0Ghz
1.5GB PC2700 ECC RAM
1 Seagate 80GB IDE disk (2MB cache 7200RPM) (primary boot disk)
2 Seagate 160GB IDE 8MB Cache 7200RPM
1 IDE CD burner
integrated intel gigabit nic
ATI AIW 9600 XT (soon to be replaced?)
integrated LSI scsi controller (used to have a backup volume (72GB) until the raid...)

Originally, the system was my desktop which explains the ATI AIW card. I used to dual boot BSD and Windows XP on the system. I'm in the process of setting up a backup "server" for data which should be live in the next week. I'm waiting for a new heatsync/fan for the CPU.

The CVS repository is backed up weekly to a system offsite.