If you liked KDE3, you may like Trinity. Matthias Drochner would like you to help get it in pkgsrc.
Matthew Dillon has a very detailed commit message with changes to make sure Hammer will run overnight cleanups in situations as low as 256M of RAM. I think you can find that much RAM in breakfast cereal boxes these days.
The answer is “not very”. As I wrote in a post to kernel@, DragonFly 3.0 will be tagged soon, and released when there’s pkgsrc-2011Q4 packages to go with it. Probably a week if everything goes to plan.
Chris Turner reports success building JDK 1.6 on DragonFly x86_64, though it requires a bit of fiddling. Building 1.7 on x86_64 is getting closer but not yet, as far as I can tell.
If you install CUPS, or know that you will never print using lpr(1), you can make sure thatyour DragonFly system never builds lpr again by putting NO_LPR=true in /etc/make.conf.
What if you have a DragonFly system that you want to use for an wireless access point? Andrey N. Oktyabrski did, and he helpfully listed his solution.
What happens when you break enough things in DragonFly that you become a source of test cases? As Antonio Huete Jimenez (AKA “tuxillo” on IRC) found out, you get a stress test named after you.
I need to catch up on some older stuff, so here is a longer list of recent updates: libarchive to 3.0.2, xz to 5.0.3, mfi(4) and mfiutil(8) (LSI MegaRAID driver) updated, ATI SB7x0/SB8x0/SB9x0 AHCI devices (on motherboards I assume) updated, and the PHY ID for the Atheros F1 added. Thanks to everyone who did the work! I bet I missed something.
John Marino has pointed out, with a number of examples, that gnat-aux is the best pkgsrc-based compiler for DragonFly right now, in terms of compatibility and support. It’s certainly good news if you are an Ada programmer. He lists some interesting numbers to demonstrate this superiority, though you can’t buildworld with it yet. (gcc 4.4, on DragonFly as part of the system, will do this normally.)
Matthew Dillon has the mailarchive working again. It pulled from the NNTP version of the DragonFly mailing lists, and when NNTP broke, so did the archive. NNTP isn’t working, but at least the mailing list archive is functional.
I’m hoping to try out Mailman (with NNTP) as a replacement soon…
There’s a Youtube video showing how to set up a virtual kernel on DragonFly. I don’t think I linked to this before. (via)
Nuno Antunes has committed a large quantity of work on updating netgraph to version 7. His goal is to be able to run mpd5, though it’s not there yet. If you want to look at it, go to the monthly page and look around the 10th; there’s too much to link to individually.
Peter Avalos has updated OpenSSL to 1.0.0f; this is to fix 6 security issues identified in the OpenSSL changelog.
I just mentioned DNSSEC in last week’s Lazy Reading, and here’s a “How to get DNSSEC with BIND 9.8.1 working” article from Michael Lucas. It’s pretty simple… Conveniently, BIND 9.8.1 is available in pkgsrc as net/bind98.
You may want to update for this – a lockup bug with the re(4) (RealTek 8xxx series) driver has been fixed.
dma, which originated on DragonFly, is now at version 0.7, and so is the version in DragonFly.
If you’re running DragonFly on a very low-end system, you may be wondering about memory requirements for Hammer. Hammer is much less RAM-hungry than ZFS, so it looks like you can get away with 128M, as long as you don’t mind the occasional error message. You can manually tweak settings for it if you like. 256M is plenty.
It still strikes me as odd to consider systems with less than 1G of RAM as “low-memory”. What rich times we live in!
John Marino updated libm, bringing a large quantity of functions. This may be a stopgap measure for now. As a positive side effect, buffer overflow attacks are a bit harder now.
Chris Turner got it working on i386, at least, and his post will help you do the same. I don’t know if these changes have made it through to pkgsrc or for x86_64 yet.
That’s Managed System Interrupts, for when your hardware is passing a lot of data and generating a lot of corresponding hardware interrupts. MSI is what deals with all that traffic. High-bandwidth (10G) network cards, for instance. Anyway, Sepherosa Ziehau’s made more commits than what I’m linking to here, for support with various devices.
There’s many other MSIs out there, oddly enough.