Markus Pfieffer has committed Larisa Grigore’s Google Summer of Code work, “SysV IPC in userspace”. It’s been a bit since the event finished, but it’s in DragonFly now.
Matthew Dillon acquired one of the Acer c720 Chromebooks recently. There were changes needed for the boot process, for the keyboard, an update from FreeBSD for the ath(4) wireless (g), smbus, and trackpad… but it works now, and he detailed exactly how to get it running, and even upgrade the drive.
‘M M’ had trouble with his “Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC” on DragonFly some time ago. He was able to get it working, and he documented the somewhat convoluted procedure here.
If you want to track the bleeding edge of DragonFly, which is currently version 3.7, I happened to describe it in a reply to Filippo Moretti, on users@. Long-time users will know this/do this already, but it’s worth repeating just because new users may not realize how easy it is.
Things are picking up again after the break.
- Faces of FreeBSD: Isabell Long. Note that she came in via Google Code-In. That’s the value of those programs.
- OpenBSD: Randomness, sooner.
- OpenBSD’s change to PIE for i386 means special upgrade procedures – if you’re on i386. Also, here’s PIE. atexit(3) changes also changes the upgrade method this one time for… all platforms? I’m not sure.
- The DiscoverBSD roundup for 12/31/2013.
- The FreeBSD Test Suite. It’s similar to what NetBSD has, but see the source link for comments on what’s different. DragonFly has a test setup too, though I’ve never tried it – is there one for OpenBSD?
- Pkgsrc-2013Q4 is branched.
- FreeBSD has improved NFS performance.
- NetBSD has updated libpcap, tcpdump, wpa, bind, and dhcpcd.
- OpenBSD has updated xterm, glproto, and some other xenocara parts.
The ixgbe(4) driver, for a number of Intel 10Gb network cards, has been updated by Sepherosa Ziehau to version 2.5.15. Note that this changes the interface name to ‘ix’ by default. This driver is actually written by Intel.
Franco Fitchner has updated mdocml in DragonFly to 1.12.3. The changelog is right on the front page of the vendor site.
Update: Undeadly has a nice summary of the changes.
A reminder based on a question from Pierre Abbat: John Marino isn’t working on 32-bit packages for dports; there’s a volunteer who will, but until the volunteer is ready, 3.7 users will want to build from source.
Here’s how my upgrade from DragonFly 3.4 to 3.6 for this server went.
The system install went normally. I rebooted before performing ‘make upgrade’, as noted in UPGRADING and elsewhere.
I already have dports installed, so a binary upgrade should be possible. I had heard of people with older version of pkg, having trouble getting it to notice upgrades. I rebuilt pkg, and ran ‘pkg upgrade’. A number of the updates coredumped. Here’s one example:
[156/160] Upgrading gtk2 from 2.24.19 to 2.24.19_2...Segmentation fault (core dumped)
After the upgrade, I had two problems: PHP wasn’t working for the website, and some programs would segfault.
The random segfault was fixable by forcing a binary upgrade of all packages. Since there were some programs on the system that were still new enough that the version number was the same as on the remote repository, pkg didn’t upgrade them. Those packages were linked against old versions of system libraries that predated the locale changes in DragonFly 3.6, so they’d crash. Forcing the update for all packages fixed the issue.
The other problem, PHP on the web server, is not new to me. The binary package for PHP does not include the module for Apache. The solution is to build from source with that option selected. I understand that pkg is destined to support (some?) port options in the future. There’s also an immediate workaround for locking it.
However, the port would not build because of a security issue. The binary package installed without any warning. This, I am told, will change to pkg giving you the option to install if you are aware of the security problem, and whether it really affects you. (which is just what I want, yay!)
Anyway, other than the system changes biting me because I didn’t realize some packages weren’t updated, it went very quickly. That is the reason for binary updates through pkg, or at least a major one.
If you have a DragonFly 3.4 system that has already been switched over to dports, and you upgrade it to DragonFly 3.6, you might see an odd problem. Rebuild pkg, and it will work.
I’ve only seen a few reports, so I don’t know if this is even likely to happen to most upgraders.
ISA device support is really gone. Well, except for keyboard and some spots where it can’t be be removed. I don’t think I’ve even seen an ISA card in some years…
John Marino has moved DragonFly from binutils 2.22 to 2.24. I think this may require a full buildworld when upgrading… not sure. Anyway, binutils has a changelog if you are curious.
I had a sometimes-great, sometimes-difficult trip to New York City over the past few days, and while I was there, I met the ball of energy that is George Rosamond of NYCBUG (which is having a huge party right now.) He and I talked for a bit about various aspects of the BSD ecosystem, and one thing he noted was that people aren’t generally aware of all the licenses in use for the different software packages on the system, or even the individual licenses in the system files.
There is an ACCEPTABLE_LICENSES setting in pkgsrc, where software licensed under terms not in that list won’t install. That’s useful, but frustrating, because it keeps people from getting what they asked for – a software install. Something that would be useful – and it could be cross-BSD very easily – would be a license audit summary.
There’s meta-data on every package in FreeBSD’s ports and DragonFly’s dports and pkgsrc and OpenBSD’s port system. Why not say ‘pkg licenses’ in the same way you can say ‘pkg info’, and get a summary of the licenses you have installed in the system? (or pkg_licenses, etc. You get the idea) This wouldn’t prevent people from installing software, but it would give a very quick view of what you were using.
> pkg licenses
Software package License
---------------- -------
foo-2.2.26 Apache license
bar-7.999999 Donateware
baz_ware-20131209 MIT
quux-silly-6.5 BSD
It could be extended to the base system, but I’d like to see this in all the packaging systems as a common idea, in the same way that ‘info’ in a packaging command always shows what’s installed.
If you have a Hammer volume that is offline, meaning that you don’t have the pseudo-file-systems null-mounted anywhere, it won’t get cleaned up in overnight processing. You just have to manually specify it.
If you have a bge(4) network card and it’s giving you problems every time you configure it, there’s a fix on the way.
Rett Kent has volunteered for maintaining i386 support under dports. Good luck! 3rd-party software management is difficult.
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.
Remember the ‘mini roadmap’, mentioned last week yesterday? John Marino put together a Google Docs spreadsheet to track the task status; several items are already cleared off. Take a look and tackle a task.