'william opensource4you' posted a summary of the steps he took for setting up a DragonFly system with XFCE4, using dports. It's pretty straightforward, and thanks to dport's binary nature, should be exactly reproducible.
John Marino brought up a point every operating system project will have to think about: when does support for i386 (i.e. 32-bit x86 processors) stop? Follow the thread for details. There's no final answer, yet.
As posted in my email to users@: Version 3.4 of DragonFly is officially out. The release ISO/IMG files are all available at the usual mirrors: http://www.dragonflybsd.org/mirrors/ The release notes have details on all the changes: http://www.dragonflybsd.org/release34/ If you are planning to try the new dports system for installing third-party software, check the DPorts Howto page: http://www.dragonflybsd.org/docs/howtos/HowToDPorts/ If you have an installed DragonFly 3.2 system and you are looking to upgrade, these (not directly tested) steps should work, as root:
cd /usr/src git fetch origin git branch DragonFly_RELEASE_3_4 origin/DragonFly_RELEASE_3_4 git checkout DragonFly_RELEASE_3_4... And then go through the normal buildworld/buildkernel process found in /usr/src/UPDATING. If you are running a generic kernel, that can be as simple as
make buildworld && make buildkernel && make installkernel && make installworld && make upgrade(and then reboot) If you encounter problems, please report them at bugs.dragonflybsd.org. I get better at testing for each release, but I also get better at discovering new problems just after release.
These are getting denser and denser with links, in part because I'm looking harder and in part because Hacker News is becoming a better and better source of links; there seems to be a new go-to site for tech links every 8-12 months. Slashdot, then Digg, then Reddit, then Hacker News...
- Intel has published a HTML5 development environment. I don't even know if it would work on DragonFly or even any BSD, but I feel efforts to make tools that are actually, genuinely, crossplatform should be looked at. Defensive platform-specific content seems to still be a thing.
- The Eternal Mainframe. The argument is a little wild-eyed, but the underlying thesis: "Cloud == Mainframe" is valid. (via)
- A Primer on IPv4, IPv6, and Transition. I signed up for an IPv6 tunnel recently, but I'm not directing traffic over it. I should be. (via)
- How to make Your Open Source Project Really Awesome. The title is linkbaity, but the steps listed are correct. You will look at the "If you want to completely screw your users..." notes and nod to yourself, recognizing something that bit you. (via)
- There's still Apple ][ software being sold. I vaguely feel like I bought from there before... (via)
- Everything's being put into a git repo these days. (via) Wait, spoke too soon. (thanks, 'bla' in comments)
- Scaling Pinterest. I like seeing what technology is used as a site transitions from "oh yeah, running on leftover hardware in my basement" to "we need to hire yet another person to keep this all running". (via)
Are you using hotplugd? If you are, this post from 'william opensource4you' about a small patch he made may be useful to you.
John Marino has committed updates for libmpfr, diff utils, grep, and libexpat/libbsdxml. Libmpfr, the one item that I suspect doesn't spring instantly to mind, is a library for floating-point computation.
As I described in a post to the kernel@ mailing list, the DragonFly 3.4 images are getting uploaded for mirroring and downloaded for testing. Assuming no surprises happen, we will be able to release very soon.
For those of us still on IPv4 networks, the BSD-specific OpenGrok site bxr.su should now be available in general, not just on IPv6.
The April 2013 issue of BSD Magazine is all about FreeNAS. I mean, every article is FreeNAS related. If you're curious about the product, this is the place to start. (The magazine is also now available in ePub format in addition to PDF.) Does FreeNAS count as another BSD flavor, rather than an appliance? I'm not sure.
Now's the time to put in your application for Summer of Code projects, if you're a student. The application period runs until May 3rd. There's already been some proposals on the mailing lists; now they can be put in officially. I'll point out the last link is from a returning GSoC student, and has a lot of detail; use that as an example if you're thinking about your own application.
I think spring has arrived; everything's turning green, and a young man's thoughts turn to computer hardware upgrades. Time to move to 64-bit! Anyway, lots of links this week. These are getting more and more content-filled over time, but I don't think anyone minds...
- For the Bitcoin enthusasts: '...when my wife refuses to bring him cake on our sofa, he calls it a “denial-of-service attack”' (via)
- Make It So, coverage of computer interfaces from movies. I always thought that was what Enlightenment was trying to achieve: the Interface From The Future. (via several places)
- Same computer interface topic, but from anime movies. It would be nice if this became something people actively worked on, instead of Bitcoin selling and Facebook monetizing. (via)
- Flat icons/monochromatic icons seem to be another microtrend. This is probably because few people do small dimensional icons well. My favorite was always the BeOS set.
- On benchmarks. It says what you should already know, but I like the Phoronix/MD5 benchmarking joke. (via EFNet #dragonflybsd)
- This article titled "The Meme Hustler" draws a finer line than I've seen before between "open source" and "free software". The author, Evgeny Morozov, seems to also have a hate-on for Tim O'Reilly. See some reviews of a recent Morozov book for a counterpoint, of sorts.
- Spacewar championship, 1972, in Rolling Stone. Exactly two years before I was born! At this point, finding things older than me makes me a bit happy. There's a picture of a Dynabook in there, photographed by Annie Liebowitz. It's entertaining to read this 40-year-old story and see how well it predicts the future. I'm also sort of amazed it exists, in Rolling Stone. More Spacewar links here.
- Meet the Web's Operating System: HTTP. "Because HTTP is ultimately the one social contract on the web that, amidst a million other debates over standards, rules, policies, and behavior, we have collectively agreed to trust." (via)
- Ancient computers in use today. I've linked to a story about that IBM 402 before, but the following pages about VAX and Apple ][e systems are new. Well, new to read, certainly not new hardware. (via)
- Yahoo Chat! A Eulogy. The spray of forbidden words is an entertaining acknowledgement message. (via)
- The $12 Gongkai Phone. Bunnie Huang breakdowns are always fun, and he's describing a strange sort of open source that isn't through license. (via)
- The FreeBSD Foundation is looking to hit a million dollars donated this year, which seems quite possible given last year's performance. Donate if you can; their activities help the whole BSD community.
- A Complete History of Breakout. It's not actually complete, but that's OK. It includes Steve Jobs being a jerk and Steve Wozniak being very clever, which is their traditional roles. (via)
- Ack 2.0 is out. It's a very useful utility; I'd like to see more standalone utilities created this way.
- Space Claw, Flickr via BBS. You'll need telnet. (via)
If you administer one of the DragonFly mirrors, there's a new /dports directory that can be mirrored. See that second link for details.
Ivan Uemlianin expressed a desire to read about the boot process, and how BSD works in general. I made a short list of suggestions.
Peter N. M. Hansteen has a long writeup about using and creating ports on OpenBSD, which is apparently a reprint of an article he wrote for BSD Magazine back in 2008. I don't remember if I read it, so it's new to me, in any case. Port and package creation across the BSDs is juuuust close enough that reading about one version will leave you with a good guess about the others.
BSDCan 2013, which is happening in a few weeks, is going to have a "Documentation Lounge", which is essentially a docs sprint, but with a much more relaxed-sounding name. Anyway, it's a good thing to contribute to.
John Marino published a 'cheatsheet' (also, typo fix)for DragonFly 3.5 users who want to try dports, using DragonFly 3.4 packages.
John Marino has a concise explanation of why dports mostly uses gcc 4.4 still to compile, even if you're building DragonFly itself with the default 4.7. It's a reason to not use NO_GCC44 - yet.
Eric Radman sent along a plug for a utility he is working on called entr(1). The desciption is "Run arbitrary commands when files change." The site for it has several nifty examples - run make when *.c files change, or convert Markdown files to HTML as soon as they are modified. The really nice thing about it is that it's perfectly BSD-friendly, and uses kqueue, but will also work on Linux. This beats the "This runs on the one flavor of Linux I use, in one particular shell!" approach I've seen from some other developers. See the reddit discussion of it for comparisons to inotify.
No, it's not in pkgsrc/ports yet.
Update: And thanks to Thomas Klausner, it's in pkgsrc as sysutils/entr, and in ports as sysutils/entr thanks to Eitan Adler. You have no reason not to try it now.