Category: DragonFly

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

DragonFlyBSD.org status page


Antonio Huete set up a DragonFly status page on status.io.

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/pkgbox64.dragonflybsd.org.  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

Minor upgrade step with dports


If you’re upgrading dports (and you probably are if you are going from DragonFly 3.4 to 3.6), there’s a minor issue in dports, inherited from FreeBSD ports: you need to manually remove perl before upgrading.  It’s all of one command, so it’s not a huge burden.  Joris Giovanngeli spotted it first.

Posted by     Categories: DPorts, DragonFly     0 Comments

Newest DragonFly committer: Eitan Adler


Eitan Adler is the newest DragonFly committer; you may recognize his name from some previous commits added by others, where he synced up various work between the BSDs.

Posted by     Categories: DragonFly, Goings-on     0 Comments

DragonFly 3.6 released


The 3.6 release of DragonFly is available now.  I just put up those images last night, so if your favorite mirror doesn’t have it, give it a few hours.

For those updating from 3.4 to 3.6: there’s an ABI change, so you will have to upgrade all your packages.  If you’re using pkgsrc and ready to switch to dports, now’s the time.  If you already switched to dports on your 3.4 system, binary packages for 3.6 have already been built and you can use pkg to upgrade.

Also for upgrades from 3.4: You can pull the 3.6 source normally:

cd /usr/src
git fetch origin
git branch DragonFly_RELEASE_3_6 origin/DragonFly_RELEASE_3_6
git checkout DragonFly_RELEASE_3_6

But there’s a slight change needed for the 3.4 to 3.6 transition: an extra reboot in the build process:

# make buildworld && make buildkernel && make installkernel && make installworld && reboot

# make upgrade

This is all noted in /usr/src/UPDATING and in the release notes, but I’m taking no chances.

Posted by     Categories: DragonFly, Goings-on     0 Comments

DragonFly 3.6.0 release very soon


As noted on the kernel@ list, it’s tagged but not yet in image form.

Posted by     Categories: DragonFly, Goings-on     1 Comment

Building lots of storage


Predrag Punosevac asked for good fileserver examples.  Several people answered, including me – the best answer is from Francois Tigeot, but there’s discussion of IPMI support in the thread.

Related: I wonder if the Backblaze Storage Pod would work for DragonFly?

Posted by     Categories: Device support, DragonFly     0 Comments

i386 dports maintainer wanted


John Marino isn’t interested in supporting the i386 architeecture for DragonFly and dports, so he’s not going to actively work on it.  (Packages for DragonFly 3.6 are already built, so that’s not a problem for release.)  If you feel like taking on a significant but interesting workload, check his message about the work involved.

Posted by     Categories: DPorts, DragonFly     0 Comments

BSDNow 11: The Gateway Drug


BSDNow episode 11 is up, with conversations about OpenSSH, FUSE, building an OpenBSD router, etc… and a whole hour of me talking about the upcoming DragonFly 3.6 release and this very Digest, too!

Posted by     Categories: BSD, DragonFly, Periodicals     0 Comments

BSDNow: a livestream that’s already completed


I just finished a whole hour of gabbing on about DragonFly and BSD work in general for BSDNow.  Because I am a ninny, I didn’t post something here earlier today so that people would know to watch the livestream.  Sorry!  However, it should be showing up in the next day or so on the BSDNow site.  When it does, I’ll link it.

Posted by     Categories: BSD, DragonFly     0 Comments

In Other BSDs for 2013/11/09


Not sure why, but there wasn’t a lot of things this week to pick out.

 

Posted by     Categories: BSD, DragonFly, FreeBSD, NetBSD, OpenBSD, PC-BSD, pkgsrc     2 Comments

Performance tuning


Matthew Dillon did some more performance tuning for DragonFly.  I’ll just pull a paragraph from the commit message, since that will have more impact than anything I say:

Improves fork/exec concurrency on monster of static binaries from 14200/sec to 55000/sec+. For dynamic binaries improve from around 2500/sec to 9000/sec or so (48 cores fork/exec’ing different dynamic binaries). For the same dynamic binary it’s more around 5000/sec or so.

“monster” is a 48-core machine used for testing.

Posted by     Categories: DragonFly, Goings-on     0 Comments

DragonFly 3.6 branched


Branched, not released.  The release should happen in two weeks.  One major bug has been squished, and remember the upgrade process from 3.4 to 3.6 is a little different from normal.

Posted by     Categories: DragonFly, Heads Up!     0 Comments

DragonFly developer interview


DragonFly developer Francois Tigeot  was interviewed on linuxfr.org.  As you can probably guess from the names, it’s a French site, but don’t let that stop you if you’re an Anglophone.

Posted by     Categories: DragonFly, Goings-on     2 Comments

lpr, still in use


The venerable (from 1979!) program, lpr, has been superseded by CUPS in many installations.  Francois Tigeot suggested removing it, but it’s still directly usable in specific situations and easier to just shift out of the way.  It’s staying, but it’s interesting to see how it still gets used.

Update: Predrag Punosevac has descriptions of the various tools involved.

Posted by     Categories: DragonFly, Goings-on     1 Comment

Multiple TX queue support for mxge(4)


Multiple transmission queues are possible for the mxge(4) driver; I’m mentioning it because Sepherosa Ziehau’s post about this describes the exact tunables to configure this.

Posted by     Categories: Device support, DragonFly     0 Comments

DragonFly 3.6 branching this weekend


I’m planning to branch DragonFly 3.6 this weekend.  The actual release will come 2 weeks later.  (Ignore what I wrote about a dports installer/image.)

Posted by     Categories: DragonFly, Goings-on     0 Comments

Discontented with contention? Be content.


Matthew Dillon wrote a roundup post summarizing all the changes he’s made to DragonFly to improve SMP performance in the last few weeks.  He’s removed almost all contention from DragonFly.  This means better performance, scaling upward depending on the number of processors.

‘monster’, the system that builds all 20,000 items in dports, can complete the run in 15 hours.  Compare this to the 2 weeks it used to take me to build the 12,000 packages in pkgsrc.  This is admittedly on different hardware and different packaging systems, but it gives a sense of the scale of the improvement.

 

Posted by     Categories: Committed Code, DPorts, DragonFly, pkgsrc     4 Comments

New ideas for Capsicum and DragonFly


Joris Giovannangeli, who worked on porting Capsicum to DragonFly for Summer of Code 2013, is continuing his work.  He’s posted a detailed note on how to do capability management in a new way, with it retaining compatibility with FreeBSD’s capsicum implementation.

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

Possible to poweroff


The ‘poweroff’ command, the equivalent of ‘halt -p’, has been added based on a suggestion from Robin Hahling.

Posted by     Categories: Committed Code, DragonFly     2 Comments

Speedups for SMP


Matthew Dillon has gone after reducing contention and improving SMP performance as vigorously as possible, using dports builds on a 48-processor machine as a test.   The machine’s building more than 1000 packages an hour, last I saw on IRC.

Posted by     Categories: DragonFly, Goings-on     2 Comments

ldns, drill updates


John Marino has updated ldns and drill to version 1.6.16.

Posted by     Categories: DragonFly, Goings-on     0 Comments

Clock explanations


Chris Turner was curious about clock skew when running under a VM, and Sepherosa Ziehau very kindly explained the different types of internal clock for DragonFly, and how to control them – a topic I’ve never understood deeply.

Posted by     Categories: Device support, DragonFly     0 Comments

SMP contention improvements


Matthew Dillon was using poudriere, the dports build tool, on a 48-core system.  Poudriere was building all 20,000+ dports, so the machine was quite busy.  He decided to get rid of as much contention as possible, and he’s listed all the ways DragonFly’s been streamlined by these efforts.  We need to revisit some of our previous benchmarks

Posted by     Categories: Committed Code, DragonFly     2 Comments

Searching DragonFly man pages with Mozilla


There is a search plugin for Mozilla that searches DragonFly man pages.  (Thanks Samuel Greear)

Posted by     Categories: DragonFly, Goings-on     1 Comment

Multiple queues support for GigE


I stole Sepherosa Ziehau’s email subject for the title of this post, because that’s exactly what has happened.  Gigabit networking cards under DragonFly will perform very well under extreme load – all of them.

Posted by     Categories: Device support, DragonFly     0 Comments

Getting pkgsrc


As a followup to news that the git feed of pkgsrc through dragonflybsd.org is not being updated, Max Herrgard wrote out how to fetch pkgsrc via CVS, or tarball, or another git feed.  CVS is still the ‘official’ way.

Posted by     Categories: DPorts, DragonFly, pkgsrc     0 Comments

Flush and sync changes ongoing


Matthew Dillon’s been working to make huge parallel software builds (i.e. dports) go a bit faster, so watch out.  This only affects you if you are running DragonFly 3.5, of course.

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

DragonFly pkgsrc repo is frozen


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

Posted by     Categories: DragonFly, Goings-on, NetBSD, pkgsrc     1 Comment

Continuous dmesg


If you’re watching for a certain event, dmesg(8) on DragonFly now has a -f flag that will display new output as it’s logged, sort of like ‘tail -f’.

Posted by     Categories: Committed Code, DragonFly     0 Comments

Radeon KMS driver added


The Radeon KMS driver from FreeBSD has been imported to DragonFly by Francois Tigeot.  It still has problems with ttm, but don’t let that stop you from taking advantage of it.

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

Memory statistics changes


While looking for a different bug, Matthew Dillon made some changes in the way memory usage is totaled in DragonFly.  You’ll see this most when using ‘systat -vm 1′ or ‘vmstat’, probably.

Posted by     Categories: Committed Code, DragonFly     0 Comments

Google Code-In 2013 and Summer of Code 2014 announced


Google has a post up about the 10th anniversary of Summer of Code, with next year’s version of the event getting some changes – an increase in the students allocated and in the student stipend, and more events.  I’m planning to apply for DragonFly, for 2014.

Google is also doing the Code-In, for 13 to 17-year-old students, again.  DragonFly participated in the first year (the only BSD to do so), but sat out last year.  I’m not currently anticipating DragonFly being involved for 2013, cause of reasons.  (It’s a lot of work!)

gdb, kgdb updated


John Marino has accomplished the major task of updating gdb/kgdb, to version 7.6.1 for DragonFly.

Posted by     Categories: Committed Code, DragonFly     0 Comments

Here, there, everywhere for mdocml


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

 

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

Even more Summer of Code


I had this to post, and managed to miss it: Daniel Flores, whose Summer of Code project was Hammer compression, posted a final report.

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

A little more Summer of Code


I know I said Summer of Code was complete for DragonFly, but Larisa Grigore published some rough benchmarks of her “SysV IPC in userland” work, plus a followup.

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

Why dports?


DragonFly has generally shifted over to dports for 3rd-party software management, away from pkgsrc.  Because of that, I haven’t been building binary packages of the quarterly pkgsrc releases.  Pierre Abbat asked why on users@, and here’s my explanation of the change.

Posted by     Categories: DPorts, DragonFly, pkgsrc     1 Comment

Huge locale changes; full buildworld needed


John Marino has put in a large patch to DragonFly 3.5, updating all sorts of language-related items.  As he warns, you will need a full buildworld/buildkernel in a specific order to update.  On the plus side, you can now probably use your native language for nvi and for git.

Posted by     Categories: Committed Code, DragonFly, Heads Up!     1 Comment

Hammer2 boot support


If you want to boot from a Hammer 2 /boot volume, you now can.  Hammer 1 never worked well as /boot, though it was technically possible.  Hammer 2 will be just fine.

Note that you can’t turn on recently-added disk compression since the bootloader doesn’t understand it, and Hammer 2 is not ready for anything but being worked on.  Don’t try it unless you’re ready to be submitting code changes to fix Hammer2.

Posted by     Categories: DragonFly, Hammer     0 Comments