Date: Wed, 20 Nov 2013 13:20:41 +0100 From: Andreas Nilsson <andrnils@gmail.com> To: freebsdonline <lists2@freebsdonline.com> Cc: current@freebsd.org Subject: Re: random_harvestq eats much on geode-lx alix2c3 Message-ID: <CAPS9%2BSuFCr-FEya9XB7XZN96ZgoBpG0O%2Bx_GryV4hJAPd=XeDw@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPS9%2BSuFCr-FEya9XB7XZN96ZgoBpG0O%2Bx_GryV4hJAPd=XeDw>