On 03/06/12 01:28, Edward M. wrote:
On 03/05/2012 10:25 PM, v...@ukr.net wrote:
What's the mistake and how can I fix it?
try adding it to:
/usr/pkg/etc/mk.conf
Indeed - you probably also want to choose the more specific
PKG_OPTIONS.bind98 version as the 'default options' setting
On Mon, 05 Mar 2012 23:28:59 -0800
Edward M. martinezedward...@gmail.com wrote:
try adding it to:
/usr/pkg/etc/mk.conf
Thanks! It helped!
Now I can see that the same configuration file is mentioned on the
HowToPkgsrc page. But maybe it is worth fixing this page:
On Mon, Mar 5, 2012 at 11:26 PM, Pierre Abbat p...@phma.optus.nu wrote:
I'm profiling a program so that I can optimize it and hopefully get it to run
in real time. Here's
the profile of the program running under Linux:
Flat profile:
Each sample counts as 0.01 seconds.
% cumulative
Good day.
Today I tried to update 2.10 to 3.0 on my VPS. 3.0 do not boot. Have
anybody tested dfly on kvm? Is it possible to update, or I must use 2.10
there?
On 3/6/2012 17:35, Andrey N. Oktyabrski wrote:
Good day.
Today I tried to update 2.10 to 3.0 on my VPS. 3.0 do not boot. Have
anybody tested dfly on kvm? Is it possible to update, or I must use 2.10
there?
DFly 3.0.1 (i386) wouldn't boot on virtualbox until VT-x extensions were
enabled
2012/3/6 Andrey N. Oktyabrski a...@bestmx.ru:
Good day.
Today I tried to update 2.10 to 3.0 on my VPS. 3.0 do not boot. Have anybody
tested dfly on kvm? Is it possible to update, or I must use 2.10 there?
Hi,
We have some known issues with 3.0 in recent versions of kvm and qemu.
They are
On 06.03.12 20:55, John Marino wrote:
Today I tried to update 2.10 to 3.0 on my VPS. 3.0 do not boot. Have
anybody tested dfly on kvm? Is it possible to update, or I must use 2.10
there?
DFly 3.0.1 (i386) wouldn't boot on virtualbox until VT-x extensions were
enabled (APIC-caused panic). You
On 03/06/12 05:24, v...@ukr.net wrote:
On Mon, 05 Mar 2012 23:28:59 -0800
But maybe it is worth fixing this page:
http://www.dragonflybsd.org/docs/newhandbook/pkgsrc/#index7h3
as well, because that was the place where I learned about the
'/etc/mk.conf/ file?
Fixed - thanks for the
