As the title says, if you install MySQL from pkgsrc-current, you’ll now get version 5.5.
Michael W. Lucas is looking for someone to improve the Extended DNSSEC Validator. Specifically, add BSD support. It’s an idea worth supporting, because the standard it works with makes self-signed certificated perfectly feasible.
If you want to take advantage of the binary packages of DPorts, and have a x86_64 system with a recent DragonFly 3.3 on it: Francois Tigeot has you covered. There’s no i386 packages yet, which are the ones I could use right now, darnit.
If you want to try DPorts, see my earlier article.
The new vm.read_shortcut option has been turned on by default by Matthew Dillon, which should lead to some performance improvements. That improvement has been measured for tmpfs, at least. There’s also some buffer cache improvments that help on x86_64 systems, too.
Update: As Venkatesh Srinivas pointed out, tmpfs also no longer uses the mplock, so it’ll take better advantage of multiple processors.
Thanks to Antonio Huete Jimenez, it’s now possible to set the MAC address for each interface and specify the disk serial number in the command line for a vkernel.
The fine folks at the New York City BSD User Group have created a mailing list specifically for using The Onion Router on BSD. Please join if you are interested in TOR, and especially if you are using something other than FreeBSD, since that’s the only ‘supported’ BSD TOR runs on right now.
There’s two changes in pkgsrc recently that might affect you: graphics/png was updated, so many dependent packages will require recompilation. Also, editors/emacs was moved to a general package instead of being specifically named by version, so now you can install ’emacs’ instead of ’emacs24′ or whichever version.
I have a pf question for anyone who is interested. I have this setup in my /etc/pf.conf, to prioritize my VoIP link. (this system also does NAT.)
extif="em0" intif="nfe0" ipphone = "192.168.0.101"
altq on $extif cbq bandwidth 768Kb queue { std, voip }
queue voip bandwidth 168Kb priority 7 cbq(borrow)
queue std bandwidth 600Kb priority 1 cbq(default)
nat on $extif from $intif:network to any -> ($extif)
pass in quick on $intif proto udp from $ipphone to any tag VOIP_OUT keep state
pass in on $intif from $intif:network to any keep state
pass out on $intif from any to $intif:network keep state
pass out on $extif tagged VOIP_OUT keep state queue(voip)
pass out on $extif inet proto tcp all modulate state flags S/SA queue(std)
pass out on $extif inet proto { udp, icmp, gre } all keep state
When I run this, ‘pfctl -s queue’ shows most of the data getting run through the ‘voip’ queue. I unplug the ATA, I still see the number of packets going up. It seems packets are getting tagged that shouldn’t be, but I’m not sure why. Anyone else have a similar – but working – setup?
Update: it was the underscore character in the tag. Everything matched it, it seems. Removing that made it work as expected.
If you’re near Germany, or like IPv6, the Schlund Technologies mirror for DragonFly is for you – it supports HTTP, FTP, and rsync.
The machines at dragonflybsd.org are now on a different part of the Internet, so if you were having problems connecting over the past few days, it should be better now. Matthew Dillon wrote up details of what he changed and why he changed it, including a note about future blade server plans.
Matthew Dillon is moving dragonflybsd.org’s network link to a new VPN today. (It may have already happened; I only just read the email.) This may help the people that have reported their network path to dragonflybsd.org seems to die somewhere in the Cogent network…
Or is it ‘statii’? English is wonderfully inconsistent. Anyway, Michael W. Lucas has posted an update on his two upcoming publications: the second edition of Absolute OpenBSD and DNSSEC Mastery. Both are in progress, and you can download the ‘pre-release’ version of DNSSEC Mastery now.
It was planned some time ago, but versions of Samba older than 3.5 are now out of pkgsrc, and version 3.5 will hopefully be replaced by 4.0 soon. Ruby 3.0 and 3.1 will also be going soon.
Hubert Feyrer wrote a review of Ansible 0.9, a management tool for multiple systems, similar to Puppet or maybe Chef. Just after doing that, Ansible 1.0 came out, with support for pkgsrc via pkgin-installed packages. This is the first solution (that I know of) that supports pkgsrc package management for multiple systems.
Markus Pfeiffer reports success using Xen HVM to run DragonFly, which may be useful for any of you Xen users. He reports not being able to use more than 2 virtual CPUs, though Scott Tincman reports successfully using 4 (with qemu), so your mileage may vary.
Updated: noting qemu usage as Markus pointed out in comments.
If you’ve been feeling the need for reading about filesystems, Daniel Phillips has posted more notes about his Tux3 filesystem design, which can be contrasted with HAMMER. (thanks, Venkatesh Srinivas)
I meant to post this a while ago; it’s a few days old but still useful. John Marino gave some stats on DPorts progress, plus he and Francois Tigeot also had some tips on xorg setup. The successful build count is higher by now, and I think KDE3 is done, though I haven’t tried it.
If you have a BSD Certification, and it’s nearing the end of its 5-year term, the BSD Certification Group has published the guidelines for re-certification. Has it really been 5 years since the first certifications happened? Geez.
I found this off of the NYCBUG mailing list, so hat tip to them.
It’s a very short week this week. I was on the road for work, so I didn’t see anywhere as much of the Internet as I may have liked. Count my dports writeup yesterday as part of this and it averages out to a good amount of reading.
- Favorite Linux Commands. Not all of them are Linux/bash specific. (via)
- Advanced Vim Registers. Or buffers, or clipboards, if you want to get messy with terms. (via)
- “I hate BSD so much!”, he yelled at his spittle-flecked monitor.
- TOME, a roguelike. Read through the comments for discussion of many other roguelike games.
Your unrelated link of the week: New Tokyo Ondo. via Jesse Moynihan, whose Forming comic on that site is an epic read. Epic, as in it’s actually telling a NSFW world creation story.
John Marino’s DPorts project, mentioned here briefly before, is interesting. I had two separate people ask me how it works, so a better explanation is in order. I’ve tried it out on a test machine over the past few weeks.
Background:
Dports is an effort to use FreeBSD’s ports system as a base for DragonFly, and the pkg tool as a way to manage binary packages built from DPorts. This is complicated, so I’ll explain each part in order.
- FreeBSD ports are a FreeBSD-specific collection of software installation files that automate building 3rd-party software on FreeBSD. You’ve probably already heard of them. (Note there’s no mention of DragonFly.)
- DPorts is a collection of files that map to existing FreeBSD ports, and contain any changes necessary to make that port also build on DragonFly. Many of those programs build without changes on DragonFly. DPorts builds from source.
- pkg is used for package management, and is usable on FreeBSD and on DragonFly. The binary packages produced from building with DPorts can be installed from remote locations and managed separately using pkg, so that software upgrades and installation can be performed with binaries only. (It’s much faster that way.)
Every port seen in DPorts is known to build on DragonFly. John Marino adds a port only after it builds successfully, using poudriere as a bulk software tool. Ports are only updated to a newer version when that newer version builds, too, so once something arrives in DPorts, it should never break from being updated at some point in the future.
Installing:
To use DPorts, you need two things:
- DragonFly 3.3 or later, though 3.3 is the most recent right now.
- You need to rename /usr/pkg so that your existing pkgsrc binary programs don’t get accidentally used while working with DPorts, causing confusion. If anything goes wrong with DPorts when you are installing it and you want to go back, remove all the DPorts packages and rename /usr/pkg back to normal.
(Don’t confuse pkg, the management tool, with /usr/pkg, the normal installation directory for pkgsrc. ) For the installation of the base port files:
cd /usr make dports-create-shallow
If you’ve already renamed your /usr/pkg directory, git won’t be in your path any more. You can instead download a tarball and unpack it, which also happens to be possible automatically via that same Makefile.
cd /usr make dports-download
Downloading via git is fastest, so if you do need to use the tarball via make dports-download, build devel/git, delete /usr/dports, and then pull it again with make dports-create-shallow. This all comes from John Marino’s Github site for DPorts.
Managing DPorts
DPorts doesn’t use pkg_info, pkg_add, and the other tools traditionally seen on DragonFly for pkgsrc. Instead, package management is done with pkg. Use pkg info, pkg install, pkg remove, and pkg update to list, install, delete, and upgrade various packages on your system. Packages built from source or downloaded as prebuilt binaries are managed the same way, using these tools.
See some of the other writing about pkg for FreeBSD for details on how it works.
Since DPorts doesn’t update a package until it gets a successful build, and installations are of successfully built binary packages, upgrades with prebuilt packages should always succeed. Since they’re binary, they should be fast. There’s a lot of ‘shoulds’ in this sentence, but these are reasonable suppositions.
What about pkgsrc?
Pkgsrc and DPorts shouldn’t be used at the same time, since one system’s packages may be at different versions but still get picked up during building for the other system. That’s about it for restrictions.
I intend to try building an experimental release of DragonFly with DPorts, to see if all the right packages can be added, but no guarantees. DPorts is brand new and does not yet have a repository for downloading packages, so the normal caveats apply; don’t install it on a mission-critical machine, and be ready to deal with any surprises from using it if you do try it out.
What packages are available?
Browsing the Github repo will show you all listed packages. More complex packages like xorg, openjdk7, and libreoffice install, as does xfce. Parts of KDE 3 and KDE 4 are in there. (I haven’t tried either.) I’m not sure about Gnome, but I don’t think anyone ever is. There’s no vim, but there is emacs.
That’s just what I see at this exact minute. It changes daily as more packages are built. Changes from DragonFly builds are sometimes relevant to the original FreeBSD port, so there’s benefits for everyone here.
What next?
Try it now if it has all the packages you need, or wait for a binary repository to be created to speed things up. Remember, this is a new project, so a willingness to deal with problems and contribute to fixes is necessary.