Category: DragonFly

NSS/LDAP and DragonFly

One of the requirements to get NSS/LDAP working on (most) any unixlike system is to have dynamic binaries; meaning they are dependent on various libraries to run.  Since you’re talking about programs for login when you’re talking about NSS/LDAP, that means if the libraries aren’t available, you can’t log in.  DragonFly has static binaries just to avoid that problem.

Francois Tigeot proposed switching to dynamic binaries and building a /rescue directory with static backups, as is the case with I think FreeBSD and NetBSD.  If you follow the thread, it looks like the best path is to use initrd instead.  Initrd stands for INITial Ram Disk, and is the first volume the computer sets up to boot from BIOS.  Since initrd gives the computer enough space to load all the needed modules (like Hammer2…), it works without making the computer dependent on various libraries or having a bloated /rescue directory.

(Someone correct me if I have the details wrong.)  As long as we’re talking about things that would help DragonFly in a larger environment, can someone work on a VM balloon memory driver, too?

Posted by     Categories: DragonFly, Goings-on     1 Comment

GUI images for DragonFly 3.6 sort of

If you noticed the lack of a GUI DVD image for the 3.6 release of DragonFly, I posted a followup note on the users@ list that talks about the steps to get X installed.  It’s not much work, with pkg set up.

IPv6 test patch

Sepherosa Ziehau has an IPv6 patch for you to try.  What’s it do?  I think it improves performance under multiple streams of traffic, but that’s from looking at the code and totally guessing.

Posted by     Categories: DragonFly, Please test     0 Comments

Hammer 2 work and notes

Matthew Dillon committed the start of a Hammer 2 cluster API. I noticed, while looking at the commit, that there’s a design document, a freemap design document, a changes list, and – most important for anyone interested – a TODO list.

Posted by     Categories: DragonFly, Hammer     2 Comments

tcplay updated to 2.0

Alex Hornung has updated tcplay in DragonFly to 2.0, and cryptdisks is updated to match.  If you have a short memory, tcplay(8) is the tool on DragonFly to manage TrueCrypt volumes.  Is DragonFly the only BSD to have this?  I think so, based on very few seconds of googling.

Posted by     Categories: Committed Code, DragonFly     1 Comment

Some 10G results on DragonFly

In part because I asked him, Sepherosa Ziehau benchmarked 10G ix(4) with 2 ports on DragonFly.  The results?  Good, both for bandwidth and for CPU usage.

Posted by     Categories: Device support, DragonFly     0 Comments

Connection speedup for x86_64

A recent commit from Sepherosa Ziehau has a 5% improvement in the number of network connections per second a x86_64 machine can accept.  He’s also reducing the number of IPIs during network activity.  If this seems somewhat esoteric, it’s because network speeds are getting so fast that the benefits come from reducing the accompanying CPU load.

Posted by     Categories: Committed Code, DragonFly     0 Comments

tzdata2014a and an odd thing

Sascha Wildner updated the time zone database on DragonFly to tzdata2014a.  The odd thing isn’t that update – Sascha updates like clockwork, haha! – but the release notes.  Apparently Even Microsoft is starting to support time zone names, sorta, finally.

Posted by     Categories: Committed Code, DragonFly     0 Comments

Building world for 3.7 users

If you’re on DragonFly 3.7, you will need to build world before building the kernel again if you are updating to some point in the last 24 hours.  Sascha Wildner points out the related commit.

Posted by     Categories: Committed Code, DragonFly, Heads Up!     0 Comments

Setting up Poudriere

Poudriere is the tool for building all of ports/dports, and Michael W. Lucas has written up his experience using it to build a custom ports set.  He’s doing on FreeBSD, but if you ignore the geom-specific parts, it should generally apply to DragonFly.

Posted by     Categories: DPorts, DragonFly, FreeBSD     0 Comments

New USB on by default

DragonFly has moved from the old USB stack to USB4BSD by default.  That means:

  • If you are already using USB4BSD, you will want to remove WANT_USB4BSD from your kernel config.
  • If you have trouble, switch back to the old USB.
  • There’s some drivers that are not yet converted; help with them would be appreciated.  
  • A full kernel/world build and ‘make upgrade’ will be needed in either case.

Sascha Wildner’s announcement email has all the gory details, including the kernel config changes to move back to the old USB setup.  This is of course in master; 3.6 users are unaffected.

Posted by     Categories: Device support, DragonFly, Please test     0 Comments

Backing up Hammer to non-Hammer volumes

Hammer’s ability to stream to remote disks is great, but what if you have storage that uses some other file system?  Antonio Huete Jimenez put together a shell script that will dump out the contents of a Hammer PFS, for upload to whatever.  Read the README for the details.

Note for docbook and upgrading

If you are upgrading packages on your DragonFly 3.6 system, and you have docbook installed, there’s an extra step needed because of the moving around of several docbook packages.  If you don’t have docbook installed – nothing to see here.

Posted by     Categories: DPorts, DragonFly     0 Comments

Summer of Code 2014 followup

I followed up with Google on why DragonFly isn’t in Summer of Code this year.  It is exactly as I suspected: they want to get new organizations in.  DragonFly’s been doing it for 6 years, so they are picking new orgs over returning ones.  This is apparently the same reason NetBSD isn’t in this year, either.

(Honestly, I can use the break.)

Posted by     Categories: DragonFly, Google Summer of Code     3 Comments

arcmsr(4) update

Sascha Wildner has updated arcmsr(4), which brings in support for the Areca ARC1214, ARC1224, ARC1264, ARC1284, and ARC1883 models, from FreeBSD.  Please test if you have the appropriate hardware.

Posted by     Categories: Device support, DragonFly     0 Comments

Bugs site now supports OpenID, the bug reporting site for DragonFly, uses Redmine.  It’s been updated and now can take OpenID for your login.

Posted by     Categories: DragonFly, Goings-on     0 Comments

coretemp available on DragonFly by default

Coretemp is now in the default kernel configs for DragonFly, so you can use coretemp to see your Intel CPU temperature.

Posted by     Categories: Device support, DragonFly     0 Comments

For Intel graphics users who can’t find a monitor

If you’re using the i915 driver for xorg, and xorg dies with a “No monitor specified for screen” error, there’s a config change to fix that, or you can just update.

Posted by     Categories: Device support, DPorts, DragonFly     0 Comments

In Other BSDs for 2014/03/01

Another week where I barely need to look up source code commits.

Posted by     Categories: Conventions, DragonFly, FreeBSD, NetBSD, OpenBSD, PC-BSD     1 Comment

pfi and authorized_keys support

pfi, the automated installer that nobody knows about, now supports installing an authorized_keys file as part of an install.  Credit goes to Alex Hornung for adding the functionality.

ACPICA 20140214 brought in

Sascha Wildner brought in ACPICA 20140214, and his commit message has a list of the updates.

Posted by     Categories: Committed Code, DragonFly     3 Comments

Spreading DMA

The DragonFly Mail Agent is being suggested as a possible sendmail replacement for FreeBSD.

Posted by     Categories: BSD, DragonFly, FreeBSD     1 Comment

DragonFly 3.6.1 released

I’ve tagged version 3.6.1 of DragonFly, and built ISO/img files of it.  They should be available by now on mirrors if you need them, or you can just upgrade as normal.   See the linked tag commit message for what’s changed.

Posted by     Categories: DragonFly, Goings-on     0 Comments

Do you have ACPI _PMM?

Grep /var/run/dmesg.boot for PMM, and if it turns up, Sepherosa Ziehau has a patch he’d like you to try.

Posted by     Categories: DragonFly, Please test     0 Comments

Clockmod replaces p4tcc

See the announcement, and the commit.  I’m not totally sure what this affects.

Posted by     Categories: Committed Code, DragonFly     0 Comments

i915 users: lose your monitor?

If you have i915 chipset-based video on DragonFly, and you get a “Output xxx has no Monitor section” complaint in your xorg logs, look at this fix using xrandr.

Posted by     Categories: Device support, DragonFly     0 Comments

Two AMD changes

Here’s two recent changes in DragonFly that may interest you if you have an AMD processor: Compute Units are now supported, thanks to Mihai Carabas, and Imre Vadasz ported over km(4), for temperature monitoring on 14h and 15h CPUs.  I’m still not totally clear on what Compute Units are.

Posted by     Categories: Device support, DragonFly     2 Comments

DragonFly 3.6.1 soon

As I mentioned on kernel@, I’m going to roll a point release of DragonFly soon.  Push in your changes if you want to get them in!

Posted by     Categories: DragonFly, Goings-on     0 Comments

3.8 release goals

Antonio Huete put together a list of goals for the next release on the DragonFly bugtracker.  Some of them are pretty ambitious, some of them are relatively easy, but they are all very useful.

Posted by     Categories: DragonFly, Goings-on     3 Comments

Go maintainer for DragonFly needed

We’ve got Go builders running for DragonFly, but nobody actively maintaining Go itself on DragonFly.  The dports version builds, but there’s a Go release coming up and having native support would be much better than relying on chance FreeBSD build compatibility.

The current error as I type this is a TLS problem that sounds like a simple fix, if only I knew where it was.

Posted by     Categories: DPorts, DragonFly     0 Comments

For Summer of Code: >63 CPUs

Here’s a potential DragonFly and Summer of Code project: adding support for more than 63 cores to DragonFly.  Matthew Dillon has already outlined how.

ACPICA-20140114 added

There seems to be a lot of ACPI-related updates lately: Sascha Wildner has updated ACPICA in DragonFly to what I think is the very latest version.  See his commit for the differences.

There really is a daemon in there

John Marino updated daemon(8) on DragonFly.  For some reason, I didn’t know it was a standalone program.  I knew about the idea of daemons as helpers based inside the computer, which is why so many server programs end with a ‘d’ – sshd, ftpd, and so on.  Inexplicably, I never actually saw the program itself.

Posted by     Categories: Committed Code, DragonFly     1 Comment

In Other BSDs for 2014/02/08

As you read this, I’m at NYCBSDCon – or at least should be.

Posted by     Categories: BSD, DragonFly, FreeBSD, NetBSD, OpenBSD, pkgsrc     0 Comments

C-state sysctl followup

Probably because of the C-state changes, Sepherosa Ziehau wants people to use a new set of sysctls instead of the hw.cpu_mwait* ones – at least on x86_64.  This won’t affect you if you aren’t already familiar with them, probably.

Posted by     Categories: DragonFly, Goings-on     0 Comments

New C-state possibilities

It’s now possible to reach deeper power-saving C-states  with DragonFly, thanks to work from Sepherosa Ziehau.  It’s possible to have it auto-adjusted by setting two sysctls.

Posted by     Categories: Device support, DragonFly     0 Comments

Summer of Code application in

I put in the application for Google Summer of Code 2014, for DragonFly.  Will we get in for a 7th year?  I hope so!

(I still want more mentors; contact me if you’re interested.)

Posted by     Categories: DragonFly, Google Summer of Code     0 Comments

DragonFly and Google Summer of Code 2014

I already asked this question on kernel@, but I’ll repeat it here.  Who is interested in mentoring for DragonFly, for Google Summer of Code 2014?  The org application period is starting today, and it would be neat to do this for a seventh year in a row.

Posted by     Categories: DragonFly, Google Summer of Code     1 Comment

Better ACPI C-State support

If you have an Intel-based system, and are running DragonFly master, there’s new c-states (power-saving modes) for you to try.  Sepherosa Ziehau posted a note about testing and feedback.

Posted by     Categories: Device support, DragonFly, Please test     0 Comments

Did I mention new USB?

There’s been periodic commits updating the USB4BSD support in DragonFly; I haven’t been linking to them because they are generally incremental. However, it’s good to (re?)mention just how you can build DragonFly with that new USB support.

Intel video users, please note

xf86-video-intel-2.21.15 should now work on your DragonFly system.  I don’t see it in dports, yet, though.

Posted by     Categories: Device support, DragonFly     2 Comments

Time zone changes

Recent updates to tzcode apparently fixed a long-standing time zone bug in DragonFly.  POSIX says the America/New_York timezone is picked as default if nothing else has been selected.  That didn’t happen in DragonFly – until recently.  If your timezone seemed to suddenly jump to U.S. Eastern time, that’s because you never picked before.

ACPI update

There’s a new ACPI version in DragonFly, and Sascha Wildner wants you to update your BIOS, just to be sure.

Posted by     Categories: Device support, DragonFly     0 Comments status page

Antonio Huete set up a DragonFly status page on

Posted by     Categories: DragonFly, Goings-on     0 Comments

Go testing for DragonFly

Brad Fitzpatrick showed up on the users@ list and mentioned that for DragonFly to be supported in Go, it needed to show up in the Go Dashboard with building reports.  I now have the Go builder running on pkgbox32/  Check the builder page to see status.

Note: Installing the port of Go from Dports works just fine; this is the mechanism for testing Go on a per-commit basis for the people who work on Go – so a ‘fail’ notice on the builder page doesn’t necessarily mean anything, unless you are developing Go itself.  This may already be clear to you.

Posted by     Categories: DPorts, DragonFly     2 Comments

DragonFly has ASLR

Address Space Layout Randomization, since 2010.  Carsten Mattner asked, and Alex Hornung answered.  (Set the sysctl vm.randomize_mmap to 1 to enable it.)

Posted by     Categories: DragonFly, Goings-on     2 Comments

The cheapest possible DragonFly

With everyone buying tablets lately, the low end of computers is getting pretty low-cost indeed.  Creating single-purpose computers is possible, and I was thinking of doing that to create a Go-testing system.  (Though probably not necessary for me.)  It got me to thinking, though…

How low-cost a system could run DragonFly?  The master-slave and low system requirements of Hammer lead to some interesting possibilities.  There’s no Arduino equivalent for DragonFly because there’s no DragonFly on ARM, despite all my wishing.  DragonFly has been run on Soekris systems before, and might work on a PCEngines ALIX board.  Ebay, my basement, or Craigslist are options too, but not as fun.  Who has suggestions?

Posted by     Categories: Device support, DragonFly     6 Comments

ACPICA update for testing

If you want to test out the latest (20131218) update to ACPICA, Sepherosa Ziehau’s got a patch for you.  This will be good for anyone who wants to use less electricity.  (updated to reflect this doesn’t enable deeper C-states as I thought it did.)

Posted by     Categories: DragonFly, Goings-on, Please test     0 Comments

ACPI updates and power states

ACPI has been updated in DragonFly by Sepherosa Ziehau, to potentially support the very low-power sleep states available with Haswell CPUs.

Note: Sepherosa clarified that the lower power states are not available – yet.

Posted by     Categories: Device support, DragonFly     0 Comments

32-bit DragonFly 3.7 and dports

There are no binary packages built for dports, on DragonFly 3.7, for 32-bit machines, at this time.  Pierre Abbat found this out.  You can build from source, of course, or just use 3.6 packages.  Don’t forget -DBATCH to avoid getting asked for build options when building from source.

Testing USB4BSD

Markus Pfeiffer has added more of his work on USB4BSD to DragonFly, and a reminder: if you want to try it out, there’s just a few options to set.

Posted by     Categories: Device support, DragonFly     0 Comments

Trackpad support summary

I didn’t post this before, and should have: Matthew Dillon posted a summary of all the trackpad improvements he added, and how to make use of the various features.

Other network improvements

Sepherosa Ziehau is continually trying to squeeze more network performance into DragonFly.  I’m not always so good at pointing it out, but here’s several commits from him that improve performance on several chipsets.

Posted by     Categories: Committed Code, DragonFly     0 Comments

Hal, dbus, and VMWare tip. Also pkg locking

Warren Postma found that hal and dbus caused a crash in VMWare for DragonFly.  The answer is to use moused, not dbus.

Also, if you want to keep a custom or just older package from dports on your system, as karu.pruun did, ‘pkg lock’ is the answer.

cyapa mousepad support grows

Matthew Dillon is continuing his work on chromebook hardware, and he’s been playing with the multi-touch touchpad.  There’s a number of new features based on position and the number of fingers used.

Posted by     Categories: Device support, DragonFly     0 Comments

Netmap on the way

Franco Fitchner is bringing in netmap to DragonFly.  I don’t think it’s complete yet.

Posted by     Categories: Committed Code, DragonFly     0 Comments

GSoC: SysV IPC code added in

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.

DragonFly on a Chromebook c720

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.


Posted by     Categories: Device support, DragonFly, Goings-on     3 Comments

RTL8191SE support

‘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.

Tracking the bleeding edge of DragonFly

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.

Posted by     Categories: DragonFly, Someday you will need this     0 Comments

In Other BSDs for 2014/01/04

Things are picking up again after the break.

Posted by     Categories: BSD, DragonFly, FreeBSD, NetBSD, OpenBSD     0 Comments

ixgbe(4) updated

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.

Posted by     Categories: Device support, DragonFly     0 Comments

mdocml updated to 1.12.3

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.

Posted by     Categories: Committed Code, DragonFly     0 Comments

A reminder about 32-bit dports

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.

Posted by     Categories: DPorts, DragonFly     0 Comments

My DragonFly 3.6 upgrade adventure

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.

Go APE for bge and bnx

The bnx(4) and bge(4) network drivers now have APE support, thanks to Sepherosa Ziehau.  What’s that mean?  Other than an opportunity for punning jokes, I don’t know.

Posted by     Categories: Device support, DragonFly, FreeBSD     2 Comments

A pkg fix for 3.4 upgraders

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 support is really gone

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…

Posted by     Categories: Device support, DragonFly     1 Comment

Binutils update to 2.24

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.

Posted by     Categories: DragonFly, Goings-on     0 Comments

A BSD plan: license summaries

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.

Posted by     Categories: BSD, DPorts, DragonFly, FreeBSD, NetBSD, OpenBSD, pkgsrc     4 Comments

Remember: manually clean up offline Hammer volumes

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.

A bge(4) fix for some hardware

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.

Posted by     Categories: Device support, DragonFly     0 Comments

Someone for i386 and dports work

Rett Kent has volunteered for maintaining i386 support under dports.  Good luck!  3rd-party software management is difficult.

Posted by     Categories: DPorts, DragonFly     0 Comments

Minimal installation notes

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.

New pkg 1.2 on the way

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.

Posted by     Categories: DPorts, DragonFly, Goings-on, Heads Up!     0 Comments

Mini roadmap checklist

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.

Posted by     Categories: DragonFly, Goings-on, I like alliteration     0 Comments

DragonFly roadmap, post 3.6

John Marino posted a possible ‘roadmap’ for DragonFly, now that we’re past the 3.6 release.  The thread went on for some ways as it was discussed, including my crazy ideas.  Notably, several suggested items have already been tackled – an iwn(4) upgrade has already happened, and an update to bmake, based on John’s vendor branch update instructions.

Posted by     Categories: DragonFly, Goings-on     2 Comments

Hammer2 status

This is a little old, but Matthew Dillon noted the status of his Hammer2 work a little while ago.  Some highlights: he’s intending Hammer2 to be usable on a single host by the time of the next DragonFly release (summer 2014), the Summer of Code project for compression has already been integrated, and he listed different parts of the work that may be interesting for anyone wanting to chip in.

Slightly related: Matt posted some Hammer2 comments on the DragonFly 3.6 release story on Slashdot that may be interesting.  Don’t bother reading the other comments; they’ll make your eyeballs bleed.

Posted by     Categories: DragonFly, Goings-on, Hammer     0 Comments

DragonFly in KVM

If you’re planning to run DragonFly in KVM, remember this post from Matthew Dillon, giving the settings he uses.  This will save you a bit of time.

Good news for iwn(4) users

If you have a recent laptop with an iwn(4) wireless chipset, Matthew Dillon’s recent work getting an updated version of the driver together will probably help you.  It was done specifically to support a Intel Centrino Wireless-N 2230, but many more should also now work.

Posted by     Categories: Device support, DragonFly, FreeBSD     0 Comments