Low on the source links this week, but there’s plenty else.
Update: from talk@nycbug, George Rosamond gives a nice APU setup summary.
I went from 1 link to lots all in one night.
Another long list. These are making my Friday nights take some extra effort.
A relatively short week; I’m on the move today.
I was thinking this was going to be a short week, but nope.
Part of this was done while traveling, but still a decent week for links.
More than the usual source commit messages this week.
Finally, a much more eventful week. I already noted LibreSSL’s release.
I have a backlog from stuff I missed last week while traveling, so we all benefit!
Some meaty links this week.
A relatively calm week – probably because there were many people at BSDCan.
I’ve got “coverage” of most every BSD this week.
If you didn’t know what the Heartbleed bug is, here’s your explanation, plus details. (via). You should probably update your systems.
Another week with lots of links.
Links everywhere this week!
Another week where I barely need to look up source code commits.
Read the first item, if nothing else.
As you read this, I’m at NYCBSDCon – or at least should be.
- FOSDEM 2014 videos are up. The second item listed is about the new version of ports, which includes dports. (via)
- Crochet-FreeBSD, a system for building bootable FreeBSD images for a variety of platforms including x86, ARM, and VM. (via Markus Pfieffer on IRC, indirectly)
- Effective Spam and Malware Countermeasures. Seen previously at BSDCan. ‘Greytrapping’, mentioned in the article, is new to me.
- Email delivery headaches. Mailing many people is somehow almost always a low-level irritation.
- DiscoverBSD’s 2014/02/03 roundup.
- Another n2k14 hackathon report. DragonFly uses that DHCP client he’s talking about.
- PC-BSD on eWeek.
- bsd-cloudinit – FreeBSD on OpenStack. (via)
- OpenBSD gained some VAX hardware. The only VAX hardware I ever saw was 6 feet tall; I can’t imagine these are easy to ship.
- OpenBSD updated to ldns 1.6.17.
- Seen via a pkgsrc list: Berlios.de is closing down its hosting, so this may affect you if you usually grab your pkgsrc packages from there.
- The proper way to break the FreeBSD ABI.
- Robert Watson’s privilege ideas.
- How to switch between mfi(4) and mrsas(4) on FreeBSD. mrsas(4) sounds like MRSA to me, which is a bit more worrisome
- FreeBSD supports MegaRAID Fury cards.
- The plan for ATF removal in NetBSD.
- DragonFly takes the FreeBSD patch(1) updates, and that’s fine, because FreeBSD made those changes to an import of DragonFly’s patch(1). Hooray for cross-pollination!
For once, I got this mostly done before late Friday night!
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.
Again, quiet from the holiday break.
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
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.
A lighter week for commits probably because of the U.S. holiday, but still plenty of things to link.
BSDNow 12, which I haven’t had a chance to watch yet, has the normal roundup of events and an interview with Amitai Schlair of NetBSD. There’s also a tutorial about ssh and tmux.
Not sure why, but there wasn’t a lot of things this week to pick out.
There’s a surprisingly large list this week.
- FreeBSD has updated netmap.
- FreeBSD supports VT-d DMAR hardware. Not totally sure what that is.
- FreeBSD supports the RealTek RTL8168G, RTL8168GU, RTL8411B, and RTL8168EP.
- FreeBSD updated byacc to version 20130925.
- FreeBSD has binary packages again.
- Managed Services using FreeBSD at NYI, a whitepaper.
- NetBSD has imported OpenBSD’s support for ASIX AX88178a and AX88179 USB network interfaces, in the axen(4) driver.
- NetBSD supports the Broadcom BCM56340 iProc based switch.
- OpenBSD supports unattended installation. See Also on Undeadly.
- OpenBSD has softraid booting documentation. Someone will find this useful, I’m sure.
- OpenBSD 5.4 is released.
- Inspecting Packets with OpenBSD and pf, the presentation from vBSDCon.
- Lua in pkgsrc has been modified.
- Ocaml in pkgsrc has been updated to 4.0.1.
- The BSD Router Project has hit 1.5. (via)
- PC-BSD 10 alpha images are available for testing.
- PC-BSD is doing weekly updates, an idea I support, unsurprisingly.
- No BSD systems in Google Code-In this year, darnit.
Once again, doing this at the last minute:
I am doing this one at the last minute. I had all the articles noted, but normally I build this post over the course of the week.
I got some PC-BSD items this week, too.
The pkgsrc repository in git for DragonFly is currently frozen. This is because many people have switched over to dports, and also because it’s a lot of work to keep it functional. If you do want to pull newer pkgsrc material, use cvs and grab it from a NetBSD server.
As the message notes, don’t go switching to DragonFly-current right now, cause there’s a lot of new material in there and it may not be quite safe. (There’s an ABI change that will require all new builds of your ports, for instance.)
BSDTalk 232 is 15 minutes of conversation with Thomas Cort about “Minix, NetBSD, and Summer of Code”.
Franco Fichtner recently received commit rights for DragonFly. This is so he could import mdocml, a OpenBSD-originating replacement for groff and man page display. Mdocml has been mentioned before on the Digest, and there’s a downloadable book. (See the more-interesting-than-it-sounds History of UNIX Manpages there too, but I digress.)
One advantage of using mdocml, as I understand it, is that groff is no longer required to view man pages. The only thing left in DragonFly that required a C++ compiler was groff. So, rebuilding could be a bit faster, and a bit less complicated.
Here’s the part that makes me happy: Changes made in DragonFly promptly made it back into NetBSD’s mdocml. Other changes rolled from DragonFly back into OpenBSD, too, and mdocml is in FreeBSD 10, though I don’t have a src change to point at right now. It all circled back around to DragonFly, too. It’s really neat to have a BSD-grown cross-BSD product.
(Incidentally, if you have a Thinkpad and keyboard issues, Franco has a patch for you to try.)
Less straight source links this week.
Related to DragonFly: Patrick Welche updated glib2 in pkgsrc, and is interested in hearing how it works for DragonFly users. If you have pkgsrc on your system and it’s not a quarterly release, try building t.
This week was relatively quiet, but also had the most cross-BSD work I’ve seen in a while. Look at the links and you’ll see.
Here’s more on Unbound, since it seems to be a trend.
Barely getting this done in time for Saturday…
There’s been a lot of commit activity across the BSDs, but my list doesn’t seem to reflect that. A lot of incremental work, I suppose.
I need to update this post during the week as I see stuff, or else I spend an hour rushing to get it all together before Satuday. I need to start watching PC-BSD src changes, too.
I hope I’m catching the interesting stuff; I’m only reading the src changes.
Definitely Saturdays for this summary. In other BSDs this week:
How many tags can I fit on this post? I think I’ll aim for Saturday for these BSD catchup posts. In theory, I can prep this and the Sunday Lazy Reading posts ahead of time, since they tend to be all-week items, and have the whole weekend covered.
Here’s what jumped out at me from reading source change mailing lists:
I’m going to have to set a specific day of the week aside for these.
I made a hesitant attempt to keep an eye on other BSD source changes over the last week. I complain about needing coverage for the other BSDs, so I’ll see what I can do:
Julio Merino is not renewing his membership of the NetBSD board of directors; he wrote an extensive post as to why. I agree with some of the issues he raised; they are possible on any open source project. I don’t necessarily think the solutions he proposes are correct.
I am clearly biased on this, but I think NetBSD needs a ‘NetBSD Digest’, to talk about the changes being made and the work being done. I once asked someone experienced in dealing with volunteers how you motivate people without a paycheck, and he said “Celebrate their accomplishments”. All the BSDs could use that. (via EFNet #dragonflybsd)
NetBSD uses pkgsrc but ships a version of xorg with NetBSD. This is effectively producing the same code twice. There’s a long discussion on tech-pkg@ (first article linked; keep reading) about moving to the pkgsrc version of xorg for NetBSD, which seems like a good idea for focusing effort, as far as I can tell. The thread goes on quite a way.
DragonFly didn’t participate this year, but it’s worth looking at the winners of the Google Code-In work for 2012 – there’s two people that were working on NetBSD in there.
For once, I got to read the commit logs for other BSDs…
The OpenBSD ‘Papers’ page has some videos listed to match the OpenBSD-related presentations from EuroBSDCon 2012.
Not only does NetBSD support the BeagleBoard, but Michael Lorenz is committing from it.
FreeBSD has brought in a new version of bmake and jemalloc. I’ve seen a number of other commits recently attributed to ‘NetApp’, which is good to see. Also, preliminary USB support for boot loaders.
PC-BSD is looking to use pkgng, the same binary package manager used in John Marino’s DPorts. It’s proving quite popular.
I’m glad 3.2 is out the door. I think I spent more time on release notes and watching package builds than any other release.
Your unrelated link of the day: Sir, You Are Being Hunted. I link to the Kickstarter for this game for no other reason than I think it would be fun to play.
John Marino is working on a very good idea: bringing bmake into DragonFly as a replacement for the current ‘make’. bmake is going through more active development and apparently also in use/will be used? on FreeBSD, so syncing up with the same make flavor as FreeBSD and NetBSD will help everyone. It’ll also remove the problem where you ‘make’ everything in DragonFly, except pkgsrc packages which you ‘bmake’. It’s not changed over yet.
(What does OpenBSD use for make?)
I don’t, but I know there are people that do. That’s why I’m pointing out this discussion where it appears that TeXLive 2012 won’t support NetBSD, which may mean no DragonFly either. There’s the not-yet-packaged alternative kertex. TeXLive is in pkgsrc, so I don’t know if that means the package will be discontinued or just altered.
(Please correct me where I go wrong here; I’m not very familiar with this, but it sounds like a drastic enough change that it should be mentioned.)
Update: as several people pointed out, it’s just prebuilt binary versions that aren’t being provided upstream. The packages will all still be present in pkgsrc. So, no functional change for most everyone.
DragonFly has a page on updating pkgsrc, and so does NetBSD. I don’t think I linked to the latter before, but even if I didn’t, it’s still useful.
BSDTalk 215 is out, with several NetBSD folks being interviewed at BSDCan 2012 about NetBSD 6.
Have you ever tried to run a service and realized you forgot to make an entry in rc.conf to enable it? It’s mildly annoying. There’s now a “one’ keyword (via NetBSD) that lets you enable a service, once. It still apparently performs sanity checks, unlike the otherwise-similar ‘force’ keyword.
There’s a NetBSD Hackathon going on February 10th through 12th, mostly online. I mention this because it may have some effect on pkgsrc, used by both NetBSD and DragonFly. Hackathons for pkgsrc usually happen separately, but no harm in keeping an eye out for any positive benefits.
Here’s some recent x86_64 bulk builds: one on DragonFly 2.11, one on NetBSd 5.0.2, and one on Linux 18.104.22.168. Some data of note: DragonFly is within 8%-ish total packages built compared to NetBSD, which could be considered the baseline. Linux, the more common platform for most of the software built, is another step less. I don’t know if there’s any dramatic conclusion to get from this other than, “Hey, a lot of packages build on DragonFly!”
I build this up over the course of the week, so I’m never sure what to put here. Does it matter? The meat is the links.
Your totally off-topic link for the week: Fat Birds.
Anton Panev is working on a Google Summer of Code project for NetBSD, adding support in pkgsrc for RPM/Debian package formats. He posted a status report recently; will this come to DragonFly via pkgsrc? I don’t know!
I spied a bulk build of pkgsrc using clang. It’s interesting to see the results… It’s on NetBSD, but it should be possible to try the same thing with CCVER on DragonFly. Any takers?
The pcc compiler is nearing 1.0. (via) This is seen as a gcc alternative, and it’s present in NetBSD/OpenBSD. I recall it didn’t work for DragonFly because of a lack of TLS support… Might be different now, if anyone wants to try. (see prior mentions on the Digest)
Apparently the surplus money from the recent NYCBSDCon is going to each of the BSD projects. Great news! Now, what to do with it…
The BSD Show!, the show I didn’t know was there, already has more 20 minutes more of content; an interview with Adam Hamsik about NetBSD.
They’re looking for more guests, too…
The compiler pcc, while having both history and speed, doesn’t get the attention that clang/LLVM gets. There’s a NetBSD blog article about building NetBSD with pcc. (via) I recall it couldn’t be used for DragonFly because of TLS support; I don’t know if that’s still an issue. It’s been covered here before.
Paul Onyschuk went and created a very neat and very long Gource movie using one of the oldest codebases out there: NetBSD. It’s available on Vimeo. His original data is available if anyone wants to try something similar.
Gource is a tool for visualizations from version control history; the video page has some examples. (via) I’d love to see this run on DragonFly. I’m curious to see what would happen on a huge, old repo, like NetBSD. Please hlep me, intarwebs!
Seen via email and Hubert Feyrer’s blog: There’s a NetBSD hackathon planned for February 19th through the 22nd. The meetup is via IRC. Since it’s NetBSD, it’ll include pkgsrc, and if it includes pkgsrc, it affects DragonFly. If you’re interested, show up – even being there to report on packages that compile or don’t (on DragonFly) would help.
It’s been possible for some time to automatically check for vulnerabilities in installed pkgsrc packages. However, it requires some initial setup work. NetBSD now will check automatically if there’s any packages installed. The same feature could work in DragonFly – I have a post about that even links to the appropriate changes. Someone want to take this on?
Recently, Sascha Wildner committed a huge number of changes to the various games, bringing them in line with what’s on NetBSD and style(9). This was all put together by Ulrich Spoerlein.
I draw attention to this not because it changed anything with the games in a functional sense, but because it’s huge (450 files changed, 31450 insertions(+), 29998 deletions(-)) and because it came out of nowhere. It’s always nice to have new surprise contributions arrive.
It’s New Year’s Eve Eve, and so here are a bunch of links I’ve built up over the past few days.
Everything that _why the lucky stiff did. (via) _why is one of those things that only the Internet lets exist. And he used DragonFly!
Roguelike games, evaluated via the Berlin Interpretation, on @Play. Also, a dedicated Roguelike handheld?
Naoya Sugioka is working on bringing tmpfs to DragonFly – I am a big fan of that idea.
top now uses CTIME, not WCPU.
Where I get more linkbloggy than usual:
Johannes Hofmann has taken over estd, a “frequency scaling daemon for NetBSD and DragonFly”. The newest release brings multicore support on DragonFly.
Stathis Kamperis, as part of his Summer of Code work, ported NetBSD’s POSIX message queues to DragonFly. He has a writeup of all the details, and even has test cases! It should be showing up in 2.5 soon.
Hubert Feyrer, for his PhD, put together a Virtual Unix Lab – a whole lab of NetBSD systems for teaching System Administration. It’s a good strategy for an environment where some percentage of the systems will be irretrievably mangled. It’s available as a book.
NetBSD now has a Projects Blog and a Twitter account. I’m not taking credit for the idea, but I do note a definite similarity between that and the DragonFly Digest, to which I say: quick, someone do this for FreeBSD and/or OpenBSD! More attention to all the BSD work being done is positive.