Michael W. Lucas’s next topic in his Mastery series is ‘Sudo‘.
Everyone passed their Summer of Code midterms! Not that this was a surprise; all the students have been consistently working and overcoming problems, but a 100% pass rate makes me happy.
Here’s the status reports:
On August 10th, Michael W. Lucas will be giving a talk on DNSSEC to the Metro Detroit Linux Users Group, and it’ll be livestreamed for everyone to see. His talks are energetic and entertaining, and it’s worth making time to see.
Joris Giovannangeli, one of the Summer of Code students for DragonFly, posted his thoughts on credential descriptors – have a read. He is working on capsicum and DragonFly, so this is a natural thought process.
These have been very easy to create over the last few weeks; there’s been a torrent of reading. Can I say torrent without making it sound like this is all downloaded large files? The word is overloaded. Anyway:
- How emacs changed my life, from I think the creator of Ruby. (via)
- Autodesk uses Creative Commons right.
- British kids in the early 80′s, using computers. Might induce nostalgia for some.
- Forth – The Early Years. (via)
- The Collapse of the Animal Crossing Economy. I am entertained by the intersection of games and economics. (via)
- Tagsistant, a tag-based filesystem. Works via command line, which is unexpected. (via Tim Darby on users@)
- Git and GitHub Secrets. (via)
- IE vs. murder rate. Correlation, rather than causation, but still funny. (via)
- toybox, a BSD-licensed command line environment for Android. I mentally said “so what?” until I saw the “Why is Toybox?” presentation. It’s an excellent talk that makes a sequence of good points about many topics on licensing and utility, and I recommend making time for watching it. (first link via)
- The Confused Deputy, an explanation of capabilities. (via #dragonflybsd on EFNet)
Your unrelated link of the week: What goes on when you are not there!
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.
- BeagleBone systems are getting popular.
- Distributed chrooted pkgsrc bulk builds. Very necessary documentation.
- …And a script to do all the setup for those builds.
- The VBSDCon site has more details on the upcoming convention. (via)
- The cxgbe(4) device has hardware dedicated to sniffing packets?
- FreeBSD has switched to the BSD-licensed version of patch.
- FreeBSD has an updated ACPI implementation.
- FreeBSD is importing OpenBSD’s rsu(4) wireless Realtek driver. Needs firmware.
- What’s new in pkgsrc-2013Q2. With screenshots!
- NetBSD now supports 2 new Centrino Wireless-N devices.
- NetBSD now has BIND 9.9.3-p2
- PHP 5.5 has hit pkgsrc.
If you have a computer with one of the very-very-new Haswell processors from Intel, Matthew Dillon has made some changes that will interest you. They shave off (in the example given) about 20% of CPU power usage without much effect on performance.
killall -T will now kill all processes associated with the current tty, except parents of the killall process itself. It’s a shortcut to “kill all these runaway items I started by accident”.
Thanks to the effort of a number of people, DragonFly (-current) now supports KMS and accelerated video on Intel 915 chipsets. It’s 2D and x86_64 only for now, but it’s much, much better than just using the vesa driver.
Every year, people ask “Why can’t writing documentation be part of Summer of Code?” (Not necessarily for DragonFly, but in general) Google has a “Doc Camp”, where a whole lot of documentation gets produced in sprints, and anyone can participate – not just Summer of Code students.
If this sounds interesting to you, your application has to be in by August
7th 9th. (URL and date updated)
Please welcome our newest DragonFly committer: Johannes Hofmann. He earned this by coming up with a significant chunk of DragonFly’s upcoming KMS/915 support, and it’s now easier to just have him work directly than to be constantly committing for him.
It’s week 6, I think, and the midterms are coming up. Here’s the status reports:
Since there’s a newer set of dports binary packages uploaded, I thought I’d spend my weekend upgrading, to catch up.
And that was it. Well, not really. I had to dump and restore my Postgres databases, cause of the switch from 9.0 to 9.2 as default. I had to build php5 from source to get the Apache module. Those two things together took longer than the entire download and upgrade of the rest of my system – some ~200 packages?
Michael W. Lucas wrote a blog post about pkgng and Ansible on FreeBSD. Will it work on DragonFly? We already have pkgng on DragonFly in the form of dports, and Ansible… might work? Please, someone try.
So many links came up recently that I had already finished this week’s entry when last week’s Lazy Reading was posted.
- The FatMac cooler. Cooler as in place to keep drinks cool.
- I always like seeing what people use for home BSD hardware.
- Note the embroidered dragonflies.
- Early mobile and video phones. Decades early. Look at the slideshow.
- Looking for evil in your firewall logs.
- Best Open Source games. Dunno how many work on any BSD. (via)
- The 2-clause BSD license and the ISC license are considered functionally equivalent?
- The GREP test, an excellent standard for code. (via)
- What if your klacky keyboard is too klacky? (also via)
- Soldering is Easy, the comic book.
- People are really starting to pile on Microsoft. (I already started) Unix-like systems are resuming their dominance of the market. Maybe ubiquity is a better word?
Your unrelated link of the week: Release the Kraken!
In part of a long thread about dports packages on the users@ list, Matthew Dillon notes that a new set of packages for i386 and x86_64, for 3.4 and for “3.6″ (meaning bleeding-edge DragonFly, even though that’s numbered 3.5) is mostly uploaded. He also notes that a Haswell-processor-based blade server for DragonFly is in the works, so much of the dragonflybsd.org infrastructure is going to move from his house to a datacenter, with the benefits that provides. It’ll also help automate binary package building.
Sepherosa Ziehau added SO_REUSEPORT to DragonFly. I don’t know how the mechanism works, because he didn’t include a description, but he did include a explanation of just how much it reduces CPU usage during as-high-as-physically-possible network load. He even wrote tools to test it more heavily.
Here’s what jumped out at me from reading source change mailing lists:
- pkgsrc now has Ruby 2.0.
- NetBSD now has wpa_supplicant and hostapd, and dhcpcd 6.0.3.
- NetBSD supports Nanjing QinHeng Electronics devices via puc(4). No idea what that is.
- NetBSD also supports Intel 8 Series SMBus devices, which I mention just because finding the right drivers for SMBus devices always frustrated me on Windows.
- NetBSD’s hostname has some new options.
- FreeBSD supports Coleto Creek devices: SATA, SMBus, and Watchdog. Not sure if that’s a brand name or a special type of construction. Also, AR934x and the Qualcomm Atheros DB120 development board, and the Broadcom BCM5725 network controller.
- OpenBSD now has sshd supporting encrypted host keys. I can’t find an open mail archive with OpenBSD source-changes as an archived list, so I don’t seem to be able to link to it directly.
I’m going to have to set a specific day of the week aside for these.
The Observe, Hack, Make 2013 festival is coming up at the end of the month in the Netherlands. Unfortunately, it’s already sold out, but there’s going to be at least one DragonFly developer there. (credit to Matthias Schmidt for letting me know about the festival)
The July issue of BSD Magazine is out, and the listed theme is “Security and Cryptography”, but there’s plenty else.
I’m late for this, even though the students weren’t. Mea culpa! There’s been a lot of discussion on IRC, in EFNet #dragonflybsd, between the students and various DragonFly developers.
Last week was relatively light, but somehow this week I read a zillion interesting things. It’s been too dang hot to do much else, other than flop in a chair and point a fan at my head.
- Chopping up CSV files. Tabular format will never die, and for good reason.
- Reanimated: The story of Vampire: The Masquerade Bloodlines. I like this idea that someone can just keep working on a project long after the originating company disappeared, just to improve it for their own benefit – no mention of open source or even a plan for it. See also Oblivion Lost or Complete for some of my personal game fix/improvement modification favorites. (via)
- I don’t think this systemd/Debian news is accurate in its reasoning, and they don’t say what’s going to happen with non-Linux Debian. However, it’s still crappy, any way you slice it. (via)
- The paranoid #! Security Guide. Lots of details that won’t necessarily apply to your BSD system, but the descriptions of various attacks are neat. (via)
- Another reminder of how easy it is to deal with a lot of text data at a Unix-ish command line. (via)
- Those ssh password attempts are still going, and have been for a decade. (via)
- Don’t care about the story, but I like the dragonfly illustration.
- Linus Torvalds swears a lot. The problem is not ‘office politics’ as he sees it, but that if you swear all the time as the leader of a project, it becomes commonplace. Linus really has to really freak out for people to notice something new. There’s other issues, like how other people emulate the behavior, but I’m pointing out the ‘verbal base sweariness’ of a project affects the entire tone.
- Quine Relay, where programming languages write each other. The Ouroboros illustration is appropriate. (via many places)
- History of emacs and vi keys. I like how this shows that the command styles in both editors was shaped by the available hardware. (via)
- Fear and Loathing in Debian^H^H^H^H^H^H/Ubuntu (or: who needs /etc/motd). A wonderful rant about the creeping complication of operating systems. Let’s place bets on when people start complaining about Linux bloat. (via luxh on EFNet #dragonflybsd)
Your unrelated link of the week: Bones Don’t Lie. An anthropologist who blogs about various discoveries of human remains. I really enjoy blogs where someone is talking about a subject they care about – not to sell a product, not to be paid (directly), but just because they like the topic and they want to share it with others. Of course I would think that, wouldn’t I?
Thanks to the efforts of a large number of people, KMS support is showing up in DragonFly. This supports accelerated video on the new Intel graphics chipsets that seem to show up on many recent laptops.
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:
- (Parts of?) full-disk encryption support in NetBSD.
- esp (the SCSI board) support for NetBSD/acorn.
- SipHash support in FreeBSD
- SYN Cookie support in FreeBSD.
Busy, busy week.
- An in-depth programming language comparison. These can be fun for reinforcing your language choices, but also interesting just for the depth of comparison. Spoiler: Java can be crazy slow; Perl can be crazy fast. The page has lots of charts which always make me happy. The quotes at the end per-language are enjoyable. (via ferz on EFNet #dragonflybsd)
- PC-BSD is using a content delivery network for their image delivery – that’s a good idea. It’s very hard to get people to consistently use mirrors, even if they are consistent and local.
- A Statistical Analysis of Nerf Blasters and Darts. Nerf guns are fun, charts are great, so that whole article is the bestest. (I think via)
- 1,200 computer interfaces from the movies. See this link for the story, and this link for more details and some new interfaces to that huge quantity of visual information, about visual information.
- 80′s childhood. It’s linkbait, but I like the sort of burst of how personal electronics looked at that point in time.
Something new and odd: A port of the Hammer (1) filesystem into Go, for go-fuse. As the author has said, it’s more for the practice of learning Go and Hammer than for producing anything useful. Still, an interesting way to learn.
Encryption seems to be the accidental theme tonight. A question about Hammer 2 and encryption prompted this list of possible solutions from Matthew Dillon. Hammer 2 is still months out, so these features both require time and someone interesting in doing them – though they sound quite possible.
Still not sure if I should be writing Hammer or HAMMER.
If you were wanting to encrypt your /home directory, Pierre Abbat has written up the explicit steps he took to do that very thing.
Week 3 is underway, and the students are starting to get into the meat of their projects:
The pkgsrc-2013Q2 branch has been out for some days, but the official release announcement has now been published, with details on the number of ports. You should be able to pull it down from dragonflybsd.org via git, by the way.
A U.S. holiday and very warm weather has made this a less intense week. At least for links.
- Someone help. A problem I never anticipated. (via)
- Git Cheat Sheet. This one’s for printing. (via)
- Real Life Tron on an Apple ][gs. (via)
- Neocities, an excellent idea. Follow the suggested links. (via)
- Mandelbulber, a cross between Electric Sheep and Xaos. (via I forget)
- A drawing of the Internet (ARPANet) in 1977. The whole thing. (via)
- Bunnie Huang’s making an open laptop. Won’t be cheap or easy, but it’s still neat.
- Vim 7.4a hits beta.
Your unrelated link of the week: A new Cyriak-animated video, this time for the band Bloc Party.
The official announcement has gone out. You should be able to pull pkgsrc-2013Q2 via git from dragonflybsd.org within the next 24 hours.
While these aren’t his BSD books, Michael W. Lucas has an interesting post up about the sales on his two recent books, SSH Mastery and DNSSEC Mastery. I’m always interested in seeing how self-publishing models work, whether it’s software or books or music. He points out that the point of his DNSSEC book is to see if a very difficult subject can be covered in a book like that – which it is. There’s very few published books that go that in-depth.
(I’m hoping for a whole “Mastery” series covering topics other writers don’t, especially in a BSD-friendly way.)
All the Summer of Code students for DragonFly have posted their second week reports:
- Daniel Flores: HAMMER2 compression feature
- Larisa Grigore: System V IPC in userspace
- Pawel Dziepak: Make vkernels checkpointable
- Joris GIOVANNANGELI: Capsicum
- Mihai Carabas: hardware nested page table support for vkernels
There’s a lot of progress for the second week, which is wonderful!
Some of the links this week go pretty in-depth. Enjoy!
- This short story from 1954 might serve as a reason to avoid single system image computing… (via Sascha Wildner)
- Vim and Ctags tips and tricks. (via)
- Psygnosis game box designs. Nostalgia for some, neat art for anyone else. (via)
- 50 years of ASCII, and here’s the table it comes from. Some other neat links there, too. (via)
- Richard Feynman and The Connection Machine. If you like stories about Feynman, who was a very interesting person, you may want to read Feynman, the comic book. I met the writer, Jim Ottaviani, years ago, and he was very energetic about both science and comics. Look up his other work if that sounds interesting – which it should. Here’s a sample from the Feynman book. (via)
Back to the Future: Preserving the History of Video Games. This is right around the corner from me. The game museum is as neat as it sounds (yes, they have games out to play), but the article doesn’t mention that it’s attached to a fantastic and huge kid’s museum.
- Building a Cray at home. Similar to this previously-linked idea. (via)
Your unrelated link(s) of the week: Candy Box and A Dark Room. Both are text-only games, but they use HTML5 for animation. They start minimal, and build up – be patient; there’s a lot of gameplay in there. These minimal games fascinate me. It’s like reading a book, where it goes from just static text to an entire world being built. (somewhat via)
Your bonus unrelated comics link of the week: Jack Kirby double-page spreads. It’s not an exaggeration to say this artwork crackles. (via I forget)
Earlier this week, Daniel Flores posted the first-week report on his Google Summer of Code project, file compression in Hammer. He mentioned that the LZ4 algorithm he is using seems to have the best performance with repeating text data, as in logfiles. I asked for numbers, and he provided them. The important data in the results is the total compression column. It shows how many 64k blocks were able to be compressed, with that type of data.
It looks like OpenJDK7 works in pkgsrc for DragonFly, thanks to Ryo ONODERA, and I think it’s working in dports too.
Supposedly it’s FreeBSD 9.0 under the hood on the new Playstation 4 systems. What does this mean for FreeBSD, or driver support, or BSD in general, or what you can run on that hardware? Possibly nothing other than a vague sense of superiority.
All the Summer of Code students for DragonFly have posted their first week reports:
- Daniel Flores: HAMMER2 compression feature
- Larisa Grigore: System V IPC in userspace
- Pawel Dziepak: Make vkernels checkpointable
- Joris GIOVANNANGELI: Capsicum
- Mihai Carabas: hardware nested page table support for vkernels
If any of these projects are interesting to you, or if you have any tips for these students on work they are doing, please provide feedback.
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)
I was going to make excuses for a low link count because of being on the road this week – but somehow I managed to find a lot to read anyway. We all win!
- Dragonflies with brain-tracking backpacks. Not DragonFly-relevant except for the subject creature. (via)
- Speaking of the actual bug, my daughter caught a dragonfly for me. That moth, incidentally, wasn’t as dead as I thought it was…
- Roguelikes breakdown. It’s an overview of roguelike games, which may not contain any surprises for you… the screenshots of graphical versions are nice, however, and there’s a lot of links to roguelike games at the end. (via)
- “If those services don’t trust me enough to give me an RSS feed, why should I trust them with my data?” Talking about APIs and how you should not trust your data to companies that won’t let you access it the way you want. Also, that’s a great pull quote, which is why I’m the second one to use it. (via)
- Great Works in Programming Languages. This is a list of titles but not links to the actual documents, though some (all?) are freely available. At least a few of you reading this just said, “Hey, I know what I’m doing this afternoon!” (also via)
- Rewriting history. It’s about shell history, though unfortunately Bash-specific.
- Ultimate Tic-Tac-Toe. Playable online. (via multiple places)
- I enjoy old analog computer(ish) pictures, so here’s two.
- Here’s another: the first stored program computer was 65 years ago as of yesterday.
- PDP-11 systems, still in service. Doesn’t saw what they are running. (via)
- Fax machine evolution, an animated gif. (via)
- The Pet Shop Boys don’t like BSD. Yeah, it’s a typo, but a funny one.
- Here’s an NSA/PRISM joke; one of many.
Your unrelated link of the week: Who you gonna call? This kills me because there was some obvious prop work and setup just to create this 7 second joke.
There’s already been some previous conversation about how much longer to support the i386 platform for DragonFly. It looks like PC-BSD will be the first ‘flavor’ of BSD to make the jump. Support for PC-BSD on i386 will be dropped after release 9.2. That includes ‘TrueOS‘, the version of PC-BSD for servers, which I did not know about until just now.
Whoops, I missed this when it happened, but: the freeze for pkgsrc-2013Q2 has started. That new quarterly release is anticipated for the end of the month.
The June 2013 issue of BSD Magazine is out, and the focus is Ruby. The PDF is free if you tell them your email address.
It’s possible your Internet service provider uses a non-routeable IP range (like 10.*) and occasionally your border device picks that up via DHCP by accident instead of an Internet address. If that happens to you, and you’re using DragonFly as your border gateway, it’s possible to prevent it with
Switching terminals in X with ctrl-alt-Fx requires a not-on-by-default option. This could catch anyone used to the old behavior, so I might be doing you a favor by mentioning it.
This is a text-heavy weekend, given yesterday’s post. Enjoy!
- SELinux’s toxic mistake. If people aren’t using something you built because it frustrates those same people, it’s not their fault. (via)
- Contrary to popular belief, QWERTY was not designed to slow the typist down. (via)
- VMS will finally reach end of life in 2020. VMS was a contemporary operating system to UNIX, and started on nearly the same hardware. (the PDP-11) Aw, I feel bad. Not so bad that I’d actually use it again, but still: Aww. (via luxh on EFNet #dragonflybsd)
- “At the point all my hardware undeniably works on BSD, I will probably move there.” This article is in no way scientific, but it makes me a little happy. (via a Google search)
- The Deepest Uncertainty. A surprisingly enjoyable description of set theory and other math bits. (via)
- 8 months in Microsoft, I learned these. None of these are a surprise, really, but point 5, “not giving back to the public domain is the norm” is really sad. The example given isn’t even code – it’s just describing a solution on a web page, publicly. (via)
- Trillian is publishing the specs for their IMPP communication service. A quote from the announcement: “…our commitment to run a business whose primary focus is its communication products, not advertising”
Your unrelated link of the week: ScummVM in a browser. Comes with some LucasArts game demos, too. (via many places)
If you’ve been reading the Digest for a while, you’ve seen me talk about the value of hosting or running your own services. It’s not too much of a surprise in my case; if you are working on an open-source operating system, you want to run it. It’s good to get the experience, and you can run programs the way you want, instead of picking from whatever vendors happen to sell you.
The PRISM disclosure, which I am going to assume everyone is familiar with at this point, is another facet. Every time you use another company for your email, your entertainment, your software, and so on, their information on you can be accessed. This isn’t a problem that can be fixed by going from one webmail provider to another. You can shop around, but notice that the author in that link effectively throws his or her hands in the air and says, “there’s no way out” by the end of the article. This is because corporations work as collecting agents for the government, even if they don’t plan to do so.
That sounds drastic, but there’s legal frameworks in every country for governments to require companies to give up data on any person, on request. It happens. I’ve seen it myself; I worked for Time Warner for several years, tracking down cable modem user information and handing it over as compelled by law. I know the lawyers at TW Corporate didn’t like doing it, but they didn’t have a choice. (I have some horrifying stories about what people would do to themselves and each other.)
Companies are increasingly working to create services to sell, not products to buy. A service never stops being consumed, so it forms an ongoing revenue stream. I’m not saying this is bad; I firmly believe that a financial incentive to be paid improves services. However, as only a consumer, you can end up not owning what you use. Other people have pointed this out, and I don’t want to sound like a frothing crazy person… but it is relevant, though not necessarily as catastrophic as some people pronounce.
What I’m working towards here is a reminder that you should run your own software, and running it on DragonFly is the best way. (Or some other operating system, I guess. If you have to.) Instead of trying to figure out what the least-bad commercial option can be, run it yourself. Good for privacy, good for learning. I know that’s not an option for everyone; fighting with Sendmail (for instance) is not an activity that many people pick voluntarily. But, if you’ve been thinking of setting up a replacement for Google Reader, or hosting your own mail, or own blog, etc… there’s never a better time than now.
(Follow all those links for some good information; consider it an early Lazy Reading post)
Sepherosa Ziehau has added a sort of queuing to altq, where TCP ACKs get higher priority. You may have seen this in any number of pf configurations, where returning data is given its own queue to keep high-volume transfers from slowing themselves down because the acknowledgements can’t get back to the sender. His commit has statistics on the performance improvement. He also added a ‘netrate‘ tool for calculating results from using netperf.
If you’re using DragonFly 3.5, your next update should be a full buildworld. That’s because John Marino is adding the framework for symbol versioning. This means that individual library (.so) files will internally keep track of newer and older symbols. The current behavior is to name the files differently, which can cause problems if an expected, linked file is missing – even if the needed symbols are present. The basic framework is being added now, and will be turned on all at once, to minimize the number of times that full buildworld is needed.
The ‘amd64′ specific parts of kernel architecture have been removed, since x86_64 covers all that. As a side effect of other changes, John Marino warns that upgrading DragonFly from a version older than 3.4, to a version newer than 3.4, will require an intermediate step of going to 3.4 first. e.g. If your machine is a DragonFly 3.0 system, you will need to upgrade to 3.4 before moving to, say, 3.6 once it is out. This won’t matter for some months, since the next release is months off.
Larisa Grigore posted an introduction of her Summer of Code project: Userland System V IPC in userland, and Daniel Flores wrote out his initial ideas for Hammer compression. That’s the remaining two projects introduced. If any of these interest you or you want to make suggestions, respond on the lists. Work starts on the 17th.
FreeBSDNews.net has a nice summary up of video from all (?) the presentations at BSDCan 2013. Of particular interest to DragonFly users: a video about pkg, the tool used for package maintenance in dports. In this presentation, it’s talking about use on FreeBSD, but the future stuff applies to DragonFly too.
Not as wordy this week, but still wordy. And linky!
- Max Headroom and the Strange World of Pseudo-CGI. A discussion of how old fake CGI can look better than modern, real CGI. This is an opinion I’ve had for quite a while, and my children pretty much ignore it every time I bring it up. (via)
- The Colby Walkmac, which predates the Mac Luggable. Linked to because it includes good pictures of what the (external) hardware was like. I find all the old ports interesting, since it’s all USB and the occasional eSATA these days… not that I’m complaining! I’ve never had a good experience with a 9-pin serial port. (via)
- A brief education on escaping characters.
- I get worried when remotely rebooting a server in a different town or even state. In Praise of Celestial Mechanics covers much more stressful circumstances: interplanetary reboots. Does Voyager 1 or 2 have an ‘uptime’ function?
- The equivalent of what you are doing right now, 20 years ago. I personally never got to see this; my experience was MUDs. Speaking of which…
- The Birth of MMOs: World of Warcraft’s debt to MUD. MUD == MMO, Roguelike == Diablo/Torchlight, Doom == almost everything else. There’s a number of game archetypes that haven’t changed in some time. (via)
- Playing with powerlines. I used to work at a company that used these lines for data transfer. It was neat technology, but it sure wasn’t easy to set up. Imagine wiring a city but only being able to use Ethernet hubs. Not switches, hubs. That, combined with undersized ARP caches/MAC tables, made it really difficult.
- OpenVPN on FreeBSD, which will come in handy for at least several readers, I’m sure, as the directions should apply to any BSD.
- Is there anything DNS can’t be used for? Cause now it’s domain-based mail policy publishing. (via ferz on EFNet #dragonflybsd)
- “Have you tried DragonFly?” posts on various forums seem to pop up with some regularity.
- Uses of tmux, explained. A slide show talking about how tmux works. (via)
Unrelated link of the week: I’ve had several deadlines and a mail server with issues this week at work, so this is all I got.
Since dports uses FreeBSD ports as a base, adding something to FreeBSD ports means it will show in dports, too. However, it doesn’t have to go that way. It’s possible to have dports packages that exist only in dports. If you have changes to a port that make it compile on DragonFly, that can be added too. For all of that, go to the dports issues page on GitHub.
The next pkgsrc freeze is planned for June 17th, 9 days from now. So, get your changes in now, for 2013Q2…
Another DragonFly/Google Summer of Code project introduction is up: Mihai Carabas wrote out his project on developing hardware nested page table support for vkernels. If Mihai’s name seems familiar, it’s because he was in Summer of Code for DragonFly last year, with a successful project.
Johnathan Perkin has a nice tutorial up about creating pkgsrc packages. It’s done on SmartOS, but I imagine it’ll generally apply to anything pkgsrc supports.
Joris GIOVANNANGELI has posted a description of his Summer of Code project for DragonFly, implementing the Capsicum kernel APIs. I expect the other students will post summaries soon, too.
If you are running DragonFly 3.5, make sure you do a full buildworld depending on how recent your version is. Just a quickworld will cause problems. DragonFly 3.4.x users are unaffected.
I pointed out in my converting-to-dports post from yesterday that I had to download dports and build pkg by hand in order to install binary packages. This was because my DragonFly system was upgraded from 3.2 to 3.4 and therefore didn’t have pkg installed.
John Marino has added a ‘pkg-bootstrap’ option to /usr/Makefile, for fixing exactly that problem. It downloads a static version of pkg, which then lets you upgrade to the full pkg and install binaries as you’d expect.
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.
I changed shiningsilence.com over from pkgsrc to dports over the last 48 hours or so. Here’s how it went, in a series of bullet points:
- I had to download dports source and build the pkg tool by hand; since this system was upgraded from DragonFly 3.2 to DragonFly 3.4, pkg wasn’t automatically present as it would be for a new installation.
- I took the output of ‘pkg_info’ and culled it down to the applications I knew I used, and that formed my ‘to-install’ list for dports. That worked in a very straightforward way.
- It took so long mostly because of two things: I was also dealing with an email problem at my workplace, which usually took precedence. Also, I had several applications that I had previously installed by hand and needed to reconfigure to work as a dports item.
- Installing from binaries is really fast! Really, the dports part of this was possibly the most brief.
- The only thing I needed to compile from source was php, in order to get the Apache plugin. I’m sort of surprised the option isn’t on by default.
- Using ‘pkg search packagename’ is a good idea, because ‘pkg install’ can pick up multiple versions of a package. e.g. ‘pkg install mysql-server’ selects mysql-server51, mysql-server55, and mysql-server56. You probably don’t want to install all three. Or even one, depending on your opinions.
- Overall, it went more easily than I had expected, given it only had half of my attention.
I’m switching this server from pkgsrc to dports. No post while I fight with old, stale configs and etc.