From owner-freebsd-current@FreeBSD.ORG  Wed Nov 20 12:20:42 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 827153C7
 for <current@freebsd.org>; Wed, 20 Nov 2013 12:20:42 +0000 (UTC)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com
 [IPv6:2607:f8b0:4003:c01::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 505F42615
 for <current@freebsd.org>; Wed, 20 Nov 2013 12:20:42 +0000 (UTC)
Received: by mail-ob0-f173.google.com with SMTP id gq1so5015602obb.4
 for <current@freebsd.org>; Wed, 20 Nov 2013 04:20:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=wxc6Q8NtFaaMyRYIdstaTqnc9HbnJNZXqOsW54WZh4Y=;
 b=TtXLhSY74Co+Bt7+JBvRdWayRDRETF0JzBO0dsjAHaJth5taS0VMrmoGl/R78EfNNb
 m92Fg4CTMDmDivHAQRVkLw/rPp9c7IdrTO/VJP3/IhNowY7gBmS1YXFRyY02z89eRxx3
 bRO/f9QXeH2yElZrUFFEGRKayDnKyyAiLNOJ9zBZWYj42AkXfMJyM+GOxF3VpaA7aLSY
 x0KWSB56ForHzL9CelrvNh01JJliQ3rAZgbWTObf5XPqrMbbLHnzkSr+dRv7hXG5mhMi
 mDg2ccX4QSTzqZjCtbcVVexVHug69Mzafag7q1YW7wTL+GMGga68sbIImtngq9dKCVpO
 pZPw==
MIME-Version: 1.0
X-Received: by 10.60.145.241 with SMTP id sx17mr246768oeb.57.1384950041583;
 Wed, 20 Nov 2013 04:20:41 -0800 (PST)
Received: by 10.76.177.234 with HTTP; Wed, 20 Nov 2013 04:20:41 -0800 (PST)
In-Reply-To: <528C95D4.4090806@freebsdonline.com>
References: <4041856.BpQXZdSKfK@aurora>
 <C33F6708-0FA5-4AC3-90BD-807B27FE264C@FreeBSD.org>
 <1995425.XJjfe8p5PP@aurora> <528C95D4.4090806@freebsdonline.com>
Date: Wed, 20 Nov 2013 13:20:41 +0100
Message-ID: <CAPS9+SuFCr-FEya9XB7XZN96ZgoBpG0O+x_GryV4hJAPd=XeDw@mail.gmail.com>
Subject: Re: random_harvestq eats much on geode-lx alix2c3
From: Andreas Nilsson <andrnils@gmail.com>
To: freebsdonline <lists2@freebsdonline.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.16
Cc: current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2013 12:20:42 -0000

> I did not deployed yet 10.x (I'm waiting for nanobsd.sh to correct
> problems with pkgng) for now I am running it on VirtualBox, but I hope it
> will also run well on Alix hardware. Your problems were on 10.x or 11.x?
>
> I just wanted to chip in concerning nanobsd: the whole point with it is
that it is easy to overide methods you don't like. Without to much patching
I have nanobsd working on zfs with pkgng.

If you use the official pkgng repo it is almost trivial:

define cust_pkg() in your config file, something like

cust_pkg() {
    pkg -c ${NANO_WORLDDIR} install $packages
    pkg -c ${NANO_WORLDDIR} clean
}

You might also have to temporarily place a working resolv.conf in
${NANO_WORLDDIR}/etc

If you have your own repo just add
export PACKAGESITE="proto://path/to/repo"
to the config file as well.

Given that thats all it takes, why wait for an "official" fix?

Best regards
Andreas