A fellow whom I’ve only seen named as Bill is working on what he calls ipfw2, though technically what’s already in DragonFly is ipfw2, since it’s the second version of ipfw. Either way, he has a project page up describing what he’s done so far, and what he plans.
If you look at your local DragonFly mirror, you’ll see ISO and IMG versions of DragonFly 4.0.0RC3. Please run, break, and report.
(Check the iso-images directory.)
The release candidate for DragonFly 4.0 came out last week, and normally the release would happen after a week. There’s still a few people reporting an odd freeze, so until we can find a cause, we’ll continue to wait.
Your local mirror should have a copy of the release candidate for DragonFly 4.0.0 by now. Please try it out and report problems. Note that this is a x86_64 only version; there’s no i386 version though you may be able to manually build on i386.
It’s been possible to install and run clang on DragonFly for a long time, of course, and at least build world with it. However, John Marino is putting in significant work to make clang one of the system compilers, replacing the older gcc44 that’s in DragonFly now. (The newer gcc47 stays.) This won’t be part of the next release, but it should be available soon after.
There’s been so much work in DragonFly recently that makes a desktop easier (i915 support, dports, and so on), that I decided to resurrect an older Dell machine and use it as my desktop.
The Dell that I’m using is a leftover from someone else’s workplace; it’s 7 years old, and has “only” 4G of RAM and a Core 2 DuoE6600 CPU in it. It works, however.
Setting up DragonFly and installing xorg and so on is pretty straightforward. Using dports makes it crazy quick to add all the packages. I went for XFCE4 because I could. Starting X gave me some trouble at first; the default config couldn’t find the mouse and would eventually crash.
Running ‘X -configure’ created a xorg.conf file I could edit, and these lines in /etc/rc.conf gave me a working mouse:
moused_enable="YES" moused_type="auto" moused_port="/dev/ums0"
The crashing problem with my radeon-driven video card was fixed by turning off the acceleration – uncommenting this line in xorg.conf did it:
Video performance isn’t as nice as I would like it with acceleration, but this is an older machine anyway.
I couldn’t get sound working. Francois Tigeot has a branch of DragonFly that contains newer sound drivers brought over from FreeBSD, here:
git://leaf.dragonflybsd.org/~ftigeot/dragonfly.git (pcm_2014_september branch.)
It doesn’t support device cloning, so I can run Youtube videos and XMMS, but not audio from both at the same time. (for instance; not that you’d want to do this other than by accident)
I installed x11/webfonts, and web pages look a bit better after changing my default font preferences.
And… that’s about it. It’s a working desktop. Digging up a half-height video card that has working acceleration is a next step, but I can’t imagine that’ll be expensive. I wish I had done this a long time ago.
I’m doing this little extra feature because I ran into several news items over the past week or so that made me say “what the hell?” out loud to my monitor.
Fedora To Get a New Partition Manager. All? Almost all? Linux distributions use gparted, which is open source and can be updated. Why not add to that? Also, it’s yet another preannouncement about how this new replacement tool will work – it’s not functional yet.
Text streams should be the fallback interface in Unix. Every 2 or 3 years someone gets this idea in some form – somehow it doesn’t overcome 40+ years of text usage.
Revisiting How We Put Together Linux Systems. Nobody can find fault with ideas like easier package management and signing. (Though maybe having the same upgrade mechanism for base + 3rd party software isn’t a good idea) However. this answer, coming from part of the group behind systemd, ties all software installation into having a btrfs volume – even requiring a virtual btrfs volume if there isn’t one installed. Incompatible software versions are dealt with by turning /usr into a sort of container. That kills any sort of need to interoperate with other software. And of course it assumes there is no Unix but Linux. (via)
Grump grump grump.
If you are on DragonFly, using pf, using altq, and using fairq to control usage, there’s a latency bug that Matthew Dillon recently fixed. He’s posted an announcement and committed fixes to master and 3.8, so it’s only an upgrade away.
You should perform a full world and kernel install if on master.
Several people (including me) have been getting bit by a problem: when performing an installworld with a changed kernel, the vn kernel module is loaded, but it was built by the previous kernel and may cause problems when it doesn’t match up.
To fix that, vn is now built in, instead of being a separate module. The rescue initrd (which is what is being mounted when it has this problem) is now installed via a ‘make rescue‘ command that can wait until a successful installworld and reboot.
If you are tracking DragonFly master, your next kernel build should be full, not quick.
The portable (meaning ready to be brought into other operating systems) version of LibreSSL is out.
If you’re looking to use LDAP on DragonFly, follow this thread (read the first, keep going) as people talk about implementing it, what they installed, etc. I haven’t tried it myself, yet.
Another ‘quiet’ week – lots of commit activity in the other BSDs, but not a lot to point at directly.
- PostgreSQL/FreeBSD performance and scalability on a 40-core machine. (PDF link, via) There’s comparison to DragonFly’s results, mentioned here before. DragonFly’s solution of shared page tables is dismissed because it would require work to do, though I think that’s a symptom of FreeBSD’s more complex locking model rather than complexity of what’s in DragonFly.
- pkgsrc-2014Q2 is out.
- Here’s some notes on the systemd compatibility GSoC/OpenBSD project.
- The FreeBSD ixgbe(4) driver understands RSS, and so does igb(4).
- FreeBSD GENERIC kernels can now use vt(4), the replacements for syscons.
- FreeBSD images can now boot UEFI.
- FreeBSD 9/10 users using the WITH_NEW_XORG option have a temporary binary ports repository to use, to handle the change in the drivers.
I have a backlog from stuff I missed last week while traveling, so we all benefit!
- PC-BSD 10.0.2-RC2 is out.
- PC-BSD will be at SouthEast LinuxFest.
- Here’s the roadmap for Lumina, PC-BSD’s new desktop environment.
- DiscoverBSD’s summary for 2014/06/16.
- FreeNAS vs. NAS4Free. Didn’t need to be 8 pages. (via)
- Peter’s pf tutorial is very popular.
- The freeze for pkgsrc-2014Q2 has started. (I’m a bit late on this one.)
- pkgsrc has a new Pkgsrc Management Committee.
- This thread, “Best pdf viewer in pkgsrc?” may be useful even if you aren’t on pkgsrc.
- NetBSD gained vmx(4) from OpenBSD.
- NetBSD now has pigz 2.3.1, which apparently stands for ‘parallel gzip‘.
- Here’s one OpenBSD/GSoC project status update; I haven’t seen others.
- Another OpenBSD desktop project started.
- BoringSSL. (via) Already, benefits.
- Ways to test pf.
- FreeBSD/gnats has gone away, and none too soon.
- Again, I love to see cross-pollination.
- The July and August NYCBUG meetings: timekeeping and OpenBSD ports. Here’s some notes on what to expect for the August meeting.
I tagged DragonFly 3.6.3, at Sascha Wildner’s suggestion. Why do that when there’s a 3.8.1 out? This way there’s a version of 3.6 that has all the fixes included, including the recent OpenSSL updates. This ‘final versioning’ should probably be done for every release. I’ll work on final images.
The 3.8.1 tag was planned for tonight; I’m waiting to find out if there needs to be a new set of binary ports for 3.8.1 before I tag.
I tagged DragonFly 3.8.1; you can see a list of the changes in the tag message. New images are built. If you are already running 3.8.0, a normal
make src-update and rebuild will get you everything.
Matthew Dillon posted a note about the next point release of DragonFly, coming within a few days. Chunks of it like the recent OpenSSL and Sendmail fixes are already on the 3.8 branch.
I assume I’ll be the one rolling it, and I plan to put together a 3.6.3 tag too, just so there’s a final version of 3.6 that has all changes rolled up.
Sascha Wildner has removed some drivers in the x86_64 config. This will only really affect you if you use a custom kernel and still have entries for those drivers in the config file.
If you are saying “Hey, what about LibreSSL? And do I write it LibReSSL?”, it’s not set up as a portable release yet. Also, I don’t know the correct capitalization, either. There is some debate about the lack of notification from OpenSSL to LibreSSL, though other vendors were notified days before.
BSDNow 040 has an interview with Karl Lehenbauer at FlightAware, a tutorial on OpenBSD’s packaging system, and more from BSDCan 2014.
Binary dports packages for 3.8 have been built; they are available for download. (link goes to release versions of the packages. Future updates will be in ../LATEST)
For upgrades from 3.6: You can pull the 3.8 source normally with git:
git fetch origin
git branch DragonFly_RELEASE_3_8 origin/DragonFly_RELEASE_3_8
git checkout DragonFly_RELEASE_3_8
Assuming you are using an unmodified kernel, here’s the steps I usually do for an upgrade:
# make buildworld && make buildkernel && make installkernel && make installworld && make upgrade
After upgrading from 3.6, pkg (as designed) will download the appropriate 3.8 packages with
Thanks to John Marino and people I don’t know the name of in the gcc project, DragonFly is now part of the gcc test suite.
“What about clang?” you say? We’re not picky; DragonFly works with either.
The slides from Francois Tigeot’s talk about benchmarking DragonFly with PostgreSQL are now online – link is to a PDF.
Imre Vadasz is our newest DragonFly committer. Welcome, Imre!
I’ve seen Atlassian Confluence, a Java-based wiki program, in a few places. Atlassian apparently offers their software at a discount (free?) to qualified open source projects. I set up Confluence 5.4 on DragonFly as a test run, and it generally worked. That’s great! I tried to set up version 5.5, and it will not start.
May 08, 2014 7:24:41 PM org.apache.catalina.core.ContainerBase startInternal SEVERE: A child container failed during start java.util.concurrent.ExecutionException: java.lang.InternalError: platform not recognized at java.util.concurrent.FutureTask.report(FutureTask.java:122)
This is annoying. DragonFly (or any BSD) is not supported by Atlassian for Confluence, so it’s not a surprise… but I was so close! Their product has a very nice interface and I was planning to replace Mediawiki at my workplace with it, for some internal documentation. This FreeBSD bug report is the closest fix I can find, but it’s old enough it shouldn’t matter now.
NYCBUG has a presentation from John Baldwin, happening on the 7th (tomorrow!), all about Bhyve, the BSD hypervisor.
The reaction I have heard a number of times from new DragonFly users: hey, this runs really fast, even when I try to load it down!
The pkg tool, used in DragonFly (and FreeBSD) for ports, is at version 1.2. Version 1.3 will apparently be able to solve the problem where one port is ended and replaced with another. This is a problem that’s been around forever, and I don’t just mean with pkg. I don’t know how soon 1.3 will be out, or what version FreeBSD is at.
Just so nobody’s surprised: DragonFly process IDs now go an order of magnitude higher.
All the dragonflybsd.org sites (www, bugs, gitweb, lists, leaf) should be available via https now, thanks to a wildcard certificate from InterNetX. Also, all the machines have an up-to-date version (1.0.1g) of OpenSSL installed to prevent the Heartbleed issue.
I wrote up some thoughts for the next release of DragonFly. There’s some project work in there for anyone interested. The next release should be near the end of May.
One of the requirements to get NSS/LDAP working on (most) any unixlike system is to have dynamic binaries; meaning they are dependent on various libraries to run. Since you’re talking about programs for login when you’re talking about NSS/LDAP, that means if the libraries aren’t available, you can’t log in. DragonFly has static binaries just to avoid that problem.
Francois Tigeot proposed switching to dynamic binaries and building a /rescue directory with static backups, as is the case with I think FreeBSD and NetBSD. If you follow the thread, it looks like the best path is to use initrd instead. Initrd stands for INITial Ram Disk, and is the first volume the computer sets up to boot from BIOS. Since initrd gives the computer enough space to load all the needed modules (like Hammer2…), it works without making the computer dependent on various libraries or having a bloated /rescue directory.
(Someone correct me if I have the details wrong.) As long as we’re talking about things that would help DragonFly in a larger environment, can someone work on a VM balloon memory driver, too?
If you noticed the lack of a GUI DVD image for the 3.6 release of DragonFly, I posted a followup note on the users@ list that talks about the steps to get X installed. It’s not much work, with pkg set up.
Normally I’d save this for Lazy Reading, but I’m indirectly involved: the Rochester Institute of Technology now has a minor in Open Source and Free Culture. Here’s the press release. I taught one of the precursor classes, Humanitarian Free/Open Source Development (essentially open source development methods) last spring. Steve Jacobs was my advisor years ago and Remy Decausemaker was my (best) student from the HFOSS class. In any case, the courses are definitely worth it. (via)
I’ve tagged version 3.6.1 of DragonFly, and built ISO/img files of it. They should be available by now on mirrors if you need them, or you can just upgrade as normal. See the linked tag commit message for what’s changed.
As I mentioned on kernel@, I’m going to roll a point release of DragonFly soon. Push in your changes if you want to get them in!
Antonio Huete put together a list of goals for the next release on the DragonFly bugtracker. Some of them are pretty ambitious, some of them are relatively easy, but they are all very useful.
Probably because of the C-state changes, Sepherosa Ziehau wants people to use a new set of sysctls instead of the hw.cpu_mwait* ones – at least on x86_64. This won’t affect you if you aren’t already familiar with them, probably.
Recent updates to tzcode apparently fixed a long-standing time zone bug in DragonFly. POSIX says the America/New_York timezone is picked as default if nothing else has been selected. That didn’t happen in DragonFly – until recently. If your timezone seemed to suddenly jump to U.S. Eastern time, that’s because you never picked before.
If you want to test out the latest (20131218) update to ACPICA, Sepherosa Ziehau’s got a patch for you.
This will be good for anyone who wants to use less electricity. (updated to reflect this doesn’t enable deeper C-states as I thought it did.)
This post from Konrad Neuwirth asking how to do a minimal installation of DragonFly led to this list of all the ‘knobs’ you can set to make your installation smaller, from John Marino. (And your buildworld faster, if that’s appealing to you.) I also pointed at rconfig and PFI, which are criminally underdocumented.
pkg 1.2 is coming out. This brings a number of new features, but as John Marino posted, you may want to delete your old pkg.conf to keep the new version from complaining about an old config file. This upgrade is a step on the way to signed packages, which is a Good Idea.
John Marino posted a possible ‘roadmap’ for DragonFly, now that we’re past the 3.6 release. The thread went on for some ways as it was discussed, including my crazy ideas. Notably, several suggested items have already been tackled – an iwn(4) upgrade has already happened, and an update to bmake, based on John’s vendor branch update instructions.
This is a little old, but Matthew Dillon noted the status of his Hammer2 work a little while ago. Some highlights: he’s intending Hammer2 to be usable on a single host by the time of the next DragonFly release (summer 2014), the Summer of Code project for compression has already been integrated, and he listed different parts of the work that may be interesting for anyone wanting to chip in.
Slightly related: Matt posted some Hammer2 comments on the DragonFly 3.6 release story on Slashdot that may be interesting. Don’t bother reading the other comments; they’ll make your eyeballs bleed.
Eitan Adler is the newest DragonFly committer; you may recognize his name from some previous commits added by others, where he synced up various work between the BSDs.
For those updating from 3.4 to 3.6: there’s an ABI change, so you will have to upgrade all your packages. If you’re using pkgsrc and ready to switch to dports, now’s the time. If you already switched to dports on your 3.4 system, binary packages for 3.6 have already been built and you can use pkg to upgrade.
Also for upgrades from 3.4: You can pull the 3.6 source normally:
git fetch origin
git branch DragonFly_RELEASE_3_6 origin/DragonFly_RELEASE_3_6
git checkout DragonFly_RELEASE_3_6
But there’s a slight change needed for the 3.4 to 3.6 transition: an extra reboot in the build process:
# make buildworld && make buildkernel && make installkernel && make installworld && reboot
# make upgrade
This is all noted in /usr/src/UPDATING and in the release notes, but I’m taking no chances.
As noted on the kernel@ list, it’s tagged but not yet in image form.
Matthew Dillon did some more performance tuning for DragonFly. I’ll just pull a paragraph from the commit message, since that will have more impact than anything I say:
Improves fork/exec concurrency on monster of static binaries from 14200/sec to 55000/sec+. For dynamic binaries improve from around 2500/sec to 9000/sec or so (48 cores fork/exec’ing different dynamic binaries). For the same dynamic binary it’s more around 5000/sec or so.
“monster” is a 48-core machine used for testing.
The venerable (from 1979!) program, lpr, has been superseded by CUPS in many installations. Francois Tigeot suggested removing it, but it’s still directly usable in specific situations and easier to just shift out of the way. It’s staying, but it’s interesting to see how it still gets used.
Update: Predrag Punosevac has descriptions of the various tools involved.