Lazy Reading for 2013/01/20

Ok, now posting this on the correct day…

Your unrelated comic link of the week: The Game, by Boulet.  Goes with some of the links.

A favor with xorgs and DPorts

If you have a DragonFly 3.3 system with DPorts, can you install xorg, then ssh -Y from another machine to there, and see if you can remotely run an X program like xterm with local display?  I’ve done this twice on two different machines with DPorts and it won’t work.  xorg won’t write the security info to ~/.Xauthority, with ssh or xhost or whatever.   It’s driving me crazy.

(Yeah, slow news day.)

Lazy Reading for 2013/01/13

It’s a very short week this week.  I was on the road for work, so I didn’t see anywhere as much of the Internet as I may have liked.  Count my dports writeup yesterday as part of this and it averages out to a good amount of reading.

  • Favorite Linux Commands.  Not all of them are Linux/bash specific.  (via)
  • Advanced Vim Registers.  Or buffers, or clipboards, if you want to get messy with terms.  (via)
  • “I hate BSD so much!”, he yelled at his spittle-flecked monitor.
  • TOME, a roguelike.  Read through the comments for discussion of many other roguelike games.

Your unrelated link of the week: New Tokyo Ondo.  via Jesse Moynihan, whose Forming comic on that site is an epic read.  Epic, as in it’s actually telling a NSFW world creation story.

An early DPorts education

John Marino’s DPorts project, mentioned here briefly before, is interesting.  I had two separate people ask me how it works, so a better explanation is in order.  I’ve tried it out on a test machine over the past few weeks.

Background:

Dports is an effort to use FreeBSD’s ports system as a base for DragonFly, and the pkg tool as a way to manage binary packages built from DPorts.  This is complicated, so I’ll explain each part in order.

  • FreeBSD ports are a FreeBSD-specific collection of software installation files that automate building 3rd-party software on FreeBSD.  You’ve probably already heard of them.  (Note there’s no mention of DragonFly.)
  • DPorts is a collection of files that map to existing FreeBSD ports, and contain any changes necessary to make that port also build on DragonFly.  Many of those programs build without changes on DragonFly.  DPorts builds from source.
  • pkg is used for package management, and is usable on FreeBSD and on DragonFly.  The binary packages produced from building with DPorts can be installed from remote locations and managed separately using pkg, so that software upgrades and installation can be performed with binaries only.  (It’s much faster that way.)

Every port seen in DPorts is known to build on DragonFly.  John Marino adds a port only after it builds successfully, using poudriere as a bulk software tool.   Ports are only updated to a newer version when that newer version builds, too, so once something arrives in DPorts, it should never break from being updated at some point in the future.

Installing:

To use DPorts, you need two things:

  1. DragonFly 3.3 or later, though 3.3 is the most recent right now.
  2. You need to rename /usr/pkg so that your existing pkgsrc binary programs don’t get accidentally used while working with DPorts, causing confusion.  If anything goes wrong with DPorts when you are installing it and you want to go back, remove all the DPorts packages and rename /usr/pkg back to normal.

(Don’t confuse pkg, the management tool, with /usr/pkg, the normal installation directory for pkgsrc. ) For the installation of the base port files:

cd /usr
make dports-create-shallow

If you’ve already renamed your /usr/pkg directory, git won’t be in your path any more.  You can instead download a tarball and unpack it, which also happens to be possible automatically via that same Makefile.

cd /usr
make dports-download

Downloading via git is fastest, so if you do need to use the tarball via make dports-download, build devel/git, delete /usr/dports, and then pull it again with make dports-create-shallow.  This all comes from John Marino’s Github site for DPorts.

Managing DPorts

DPorts doesn’t use pkg_info, pkg_add, and the other tools traditionally seen on DragonFly for pkgsrc.  Instead, package management is done with pkg.   Use pkg info, pkg install, pkg remove, and pkg update to list, install, delete, and upgrade various packages on your system.  Packages built from source or downloaded as prebuilt binaries are managed the same way, using these tools.

See some of the other writing about pkg for FreeBSD for details on how it works.

Since DPorts doesn’t update a package until it gets a successful build, and installations are of successfully built binary packages, upgrades with prebuilt packages should always succeed.  Since they’re binary, they should be fast.  There’s a lot of ‘shoulds’  in this sentence, but these are reasonable suppositions.

What about pkgsrc?

Pkgsrc and DPorts shouldn’t be used at the same time, since one system’s packages may be at different versions but still get picked up during building for the other system.  That’s about it for restrictions.

I intend to try building an experimental release of DragonFly with DPorts, to see if all the right packages can be added, but no guarantees.  DPorts is brand new and does not yet have a repository for downloading packages, so the normal caveats apply; don’t install it on a mission-critical machine, and be ready to deal with any surprises from using it if you do try it out.

What packages are available?

Browsing the Github repo will show you all listed packages.  More complex packages like xorg, openjdk7, and libreoffice install, as does xfce.  Parts of KDE 3 and KDE 4 are in there.  (I haven’t tried either.)  I’m not sure about Gnome, but I don’t think anyone ever is.  There’s no vim, but there is emacs.

That’s just what I see at this exact minute.  It changes daily as more packages are built.  Changes from DragonFly builds are sometimes relevant to the original FreeBSD port, so there’s benefits for everyone here.

What next?

Try it now if it has all the packages you need, or wait for a binary repository to be created to speed things up.  Remember, this is a new project, so a willingness to deal with problems and contribute to fixes is necessary.

More on the Himeno Phoronix benchmark, and memory allocation

If you recall, Phoronix recently ran a bunch of benchmarks on DragonFly.  One spot that didn’t look good was the “Himeno Poisson Pressure Solver”.  I’m no closer to knowing what capability it actually tests other than itself, but Alex Hornung, Matt Dillon, and Venkatesh Srinivas figured out that cache coloring was the missing ingredient.  DragonFly now scores the same as Linux.

Tangentially related, this cache coloring is happening in nmalloc, which is now used on 64-bit DragonFly systems.  The previous one, dmalloc, had problems in long-running programs.

Lazy Reading for 2013/01/06

I’m going for the terse list of links.  It’s sort of Neukirchen-ish.

Your unrelated link(s) of the week: Some very good tutorial videos.  Don’t worry, it’s just electrostatic dischargewire safetyfun with capacitors, and how to make a Windows shortcut (via/via)

DPorts and what it’s about

John Marino has been working for some time on a project he calls, ‘DPorts’.  You may have noticed his recent commits for it.  He wrote up a summary on users@ to explain what he’s doing.  It’s translating FreeBSD ports to DragonFly in a way that appears to be (relatively) low-maintenance.   It only works on DragonFly 3.3 and up and you can’t use it at the same time as pkgsrc.

Most interesting to me, it gets rid of the quarterly release chase that happens with pkgsrc releases.  Since it’s primarily a binary install system, packages are only upgraded when the results are known to work.