The pkgsrc-2013Q2 branch has been out for some days, but the official release announcement has now been published, with details on the number of ports. You should be able to pull it down from dragonflybsd.org via git, by the way.
The official announcement has gone out. You should be able to pull pkgsrc-2013Q2 via git from dragonflybsd.org within the next 24 hours.
All the Summer of Code students for DragonFly have posted their second week reports:
- Daniel Flores: HAMMER2 compression feature
- Larisa Grigore: System V IPC in userspace
- Pawel Dziepak: Make vkernels checkpointable
- Joris GIOVANNANGELI: Capsicum
- Mihai Carabas: hardware nested page table support for vkernels
There’s a lot of progress for the second week, which is wonderful!
If you have an Emulex BladeEngine 2 or 3, or an Emulex Lancer, it should work in DragonFly, thanks to Sascha Wildner’s recent commit. Emulex has 10Gb network cards, in case you were like me and not familiar with the name.
(You thought I was going to type “Sepherosa Ziehau”, didn’t you?)
FreeBSD ports, and therefore Dragonfly dports, will drop KDE 3.5 items sometime very soon. It’s possible to continue to build them in dports, but it’s extra work. If you need them, volunteer, because otherwise they will be dropped. (An idea I fully support.)
Earlier this week, Daniel Flores posted the first-week report on his Google Summer of Code project, file compression in Hammer. He mentioned that the LZ4 algorithm he is using seems to have the best performance with repeating text data, as in logfiles. I asked for numbers, and he provided them. The important data in the results is the total compression column. It shows how many 64k blocks were able to be compressed, with that type of data.
If you have a mps(4) device (LSI Fusion-MPT 2 SAS disk controller), you may be interested in Matthew Dillon’s large commit of bugfixes from FreeBSD. Specifically, he notes that the drive gets ‘overtagged’, and performance can be greatly improved by reducing the number of tags used.
Thanks to Sepherosa Ziehau, Netperf will now calculate Jain’s fairness index. That is a formula that is both interesting and unfamiliar to me. Not that I understand it, of course – it’s just because it has a neat name.
It looks like OpenJDK7 works in pkgsrc for DragonFly, thanks to Ryo ONODERA, and I think it’s working in dports too.
Because Sepherosa Ziehau changed mbstat, anyone on bleeding-edge DragonFly will need to rebuild world, or else netstat will become confused.
All the Summer of Code students for DragonFly have posted their first week reports:
- Daniel Flores: HAMMER2 compression feature
- Larisa Grigore: System V IPC in userspace
- Pawel Dziepak: Make vkernels checkpointable
- Joris GIOVANNANGELI: Capsicum
- Mihai Carabas: hardware nested page table support for vkernels
If any of these projects are interesting to you, or if you have any tips for these students on work they are doing, please provide feedback.
There’s already been some previous conversation about how much longer to support the i386 platform for DragonFly. It looks like PC-BSD will be the first ‘flavor’ of BSD to make the jump. Support for PC-BSD on i386 will be dropped after release 9.2. That includes ‘TrueOS‘, the version of PC-BSD for servers, which I did not know about until just now.
There’s support for a new timer mechanism in DragonFly 3.5, for x86_64 users: TSC. Sepherosa Ziehau added support and has described how to disable it – it’s on by default. It speeds up some very basic (and frequently used) system calls.
It’s possible your Internet service provider uses a non-routeable IP range (like 10.*) and occasionally your border device picks that up via DHCP by accident instead of an Internet address. If that happens to you, and you’re using DragonFly as your border gateway, it’s possible to prevent it with PF dhclient.
If you get your Hammer drive really full, a normal cleanup won’t make enough space. When that happen, use ‘hammer reblock’ in increasing increments. That works because it does cleanup in much smaller steps.
If you’ve been reading the Digest for a while, you’ve seen me talk about the value of hosting or running your own services. It’s not too much of a surprise in my case; if you are working on an open-source operating system, you want to run it. It’s good to get the experience, and you can run programs the way you want, instead of picking from whatever vendors happen to sell you.
The PRISM disclosure, which I am going to assume everyone is familiar with at this point, is another facet. Every time you use another company for your email, your entertainment, your software, and so on, their information on you can be accessed. This isn’t a problem that can be fixed by going from one webmail provider to another. You can shop around, but notice that the author in that link effectively throws his or her hands in the air and says, “there’s no way out” by the end of the article. This is because corporations work as collecting agents for the government, even if they don’t plan to do so.
That sounds drastic, but there’s legal frameworks in every country for governments to require companies to give up data on any person, on request. It happens. I’ve seen it myself; I worked for Time Warner for several years, tracking down cable modem user information and handing it over as compelled by law. I know the lawyers at TW Corporate didn’t like doing it, but they didn’t have a choice. (I have some horrifying stories about what people would do to themselves and each other.)
Companies are increasingly working to create services to sell, not products to buy. A service never stops being consumed, so it forms an ongoing revenue stream. I’m not saying this is bad; I firmly believe that a financial incentive to be paid improves services. However, as only a consumer, you can end up not owning what you use. Other people have pointed this out, and I don’t want to sound like a frothing crazy person… but it is relevant, though not necessarily as catastrophic as some people pronounce.
What I’m working towards here is a reminder that you should run your own software, and running it on DragonFly is the best way. (Or some other operating system, I guess. If you have to.) Instead of trying to figure out what the least-bad commercial option can be, run it yourself. Good for privacy, good for learning. I know that’s not an option for everyone; fighting with Sendmail (for instance) is not an activity that many people pick voluntarily. But, if you’ve been thinking of setting up a replacement for Google Reader, or hosting your own mail, or own blog, etc… there’s never a better time than now.
(Follow all those links for some good information; consider it an early Lazy Reading post)
Sepherosa Ziehau has added a sort of queuing to altq, where TCP ACKs get higher priority. You may have seen this in any number of pf configurations, where returning data is given its own queue to keep high-volume transfers from slowing themselves down because the acknowledgements can’t get back to the sender. His commit has statistics on the performance improvement. He also added a ‘netrate‘ tool for calculating results from using netperf.
If you’re using DragonFly 3.5, your next update should be a full buildworld. That’s because John Marino is adding the framework for symbol versioning. This means that individual library (.so) files will internally keep track of newer and older symbols. The current behavior is to name the files differently, which can cause problems if an expected, linked file is missing – even if the needed symbols are present. The basic framework is being added now, and will be turned on all at once, to minimize the number of times that full buildworld is needed.
The ‘amd64’ specific parts of kernel architecture have been removed, since x86_64 covers all that. As a side effect of other changes, John Marino warns that upgrading DragonFly from a version older than 3.4, to a version newer than 3.4, will require an intermediate step of going to 3.4 first. e.g. If your machine is a DragonFly 3.0 system, you will need to upgrade to 3.4 before moving to, say, 3.6 once it is out. This won’t matter for some months, since the next release is months off.
Larisa Grigore posted an introduction of her Summer of Code project: Userland System V IPC in userland, and Daniel Flores wrote out his initial ideas for Hammer compression. That’s the remaining two projects introduced. If any of these interest you or you want to make suggestions, respond on the lists. Work starts on the 17th.