Hi Stuart,
On 07/10/2016 19:54, Stuart Henderson wrote:
> It doesn't build, it requires 64-bit atomic operations and the usual way
> to request these on those i386 CPUs which support it (-march=i686) didn't
> work when I tried it.
I have successfully built seamonkey on FreeBSD and on Gentoo Linu
On 10/31/16 11:48 AM, Jeff Ross wrote:
On 10/31/16 7:54 AM, Jan Stary wrote:
On Oct 30 11:28:55, jr...@openvistas.net wrote:
Hi all,
I'm moving to a new server hosted at m5 and I'm ready to pull the
trigger on
making the switch.
In the past doing this sort of move I've run into dns update
del
Marko Cupać writes:
> Hi,
Hi,
> On my 6.0 -stable box, installed freshly from 6.0 release, I see this
> line in my master.passwd:
>
> proxy:*:71:71:Old proxy daemon (remove in 6.0):/nonexistent:/sbin/nologin
>
> Is it safe te remove it, as comment suggests?
AFAIK it was only used by ftp-proxy
On Sun, Oct 30, 2016 at 12:36:12PM +0100, Jasper Siepkes wrote:
> Hi all,
>
> I've got a question about how OpenBSD deals with routes and interfaces
> that are considerd 'down'. I've noticed that when an interface in
> OpenBSD is down the route to that interface will remain in the routing
> table
Hi,
On my 6.0 -stable box, installed freshly from 6.0 release, I see this
line in my master.passwd:
proxy:*:71:71:Old proxy daemon (remove in 6.0):/nonexistent:/sbin/nologin
Is it safe te remove it, as comment suggests?
--
Before enlightenment - chop wood, draw water.
After enlightenment - chop
Bitcoin of Romanian still saves OpenBSD?
On 10/31/16 7:54 AM, Jan Stary wrote:
On Oct 30 11:28:55, jr...@openvistas.net wrote:
Hi all,
I'm moving to a new server hosted at m5 and I'm ready to pull the trigger on
making the switch.
In the past doing this sort of move I've run into dns update delays--even
with the ttl on my dns set to
On 10/31/16 12:10 AM, Philipp Buehler wrote:
Am 30.10.2016 18:28 schrieb Jeff Ross:
It seems like I should be able to use pf to redirect all inbound
traffic except ssh to the new server. I tried redirecting web traffic
as a test with the following rule in pf.conf:
#pass all non-ssl web traffic
On Mon, Oct 31, 2016 at 11:09:09AM +0100, Stefan Sperling wrote:
> On Mon, Oct 31, 2016 at 05:56:12PM +0800, johnw wrote:
> > Hi, I know my cpu (Intel E8400) support vt-x/vt-d, but when I run vmd,
> >
> > vmd: /dev/vmm: Operation not supported by device
>
> > Is this cpu support to run vmd?
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, Oct 31, 2016 at 08:57:40AM -0500, Vijay Sankar wrote:
> With the vob format, I have not had any problems with subtitles or audio
> streams. It is important for me to use OpenBSD especially since I believe it
> will be around much longer than
Thanks very much. Yes, I am using mp3,flac so that there are two versions.
With the vob format, I have not had any problems with subtitles or audio
streams. It is important for me to use OpenBSD especially since I believe it
will be around much longer than other operating systems. So I have not tr
On Oct 30 11:28:55, jr...@openvistas.net wrote:
> Hi all,
>
> I'm moving to a new server hosted at m5 and I'm ready to pull the trigger on
> making the switch.
>
> In the past doing this sort of move I've run into dns update delays--even
> with the ttl on my dns set to 300, there is a lot of e-ma
On 10/29/16 22:00, Stuart Henderson wrote:
>
> No, you won't able able to. I don't think this card is supported at all
> (and those 3ware cards which are supported, don't support management on
> OpenBSD).
>
Since 3ware was bought by LSI, and LSI was bought by Avago I wonder
if the newer Avago RA
On 2016-10-29, Walter Alejandro Iglesias wrote:
> Does acme-client take in care /etc/acme-client.conf in any way?
Not yet.
On 10/31/2016 06:09 PM, Stefan Sperling wrote:
> It seems the current implementation only supports a CPU if dmesg displays
> "VMX/EPT", not just "VMX" (the vmmopen() function only succeeds if EPT
> support is present).
>
> As for if or when this will change, I cannot say.
>
> Keep in mind that we'r
On Mon, Oct 31, 2016 at 05:56:12PM +0800, johnw wrote:
> Hi, I know my cpu (Intel E8400) support vt-x/vt-d, but when I run vmd,
>
> vmd: /dev/vmm: Operation not supported by device
> Is this cpu support to run vmd?
> vmm0 at mainbus0: VMX
It seems the current implementation only supports a CPU
Hi, I know my cpu (Intel E8400) support vt-x/vt-d, but when I run vmd,
vmd: /dev/vmm: Operation not supported by device
What is this mean?
I did run kvm/qemu/linux on this machine before, and just checked my
bios setting,
the "Intel® Virtualization Technology" is enabled.
Is this cpu support t
> Gesendet: Sonntag, 30. Oktober 2016 um 16:21 Uhr
> Von: "Simon Ruderich"
> An: "Vijay Sankar"
> Cc: misc
> Betreff: Re: Ripping CDs and DVDs
>
> On Sat, Oct 22, 2016 at 05:44:59PM -0500, Vijay Sankar wrote:
> > Hi,
> >
> > In preparation for my retirement in 2050, I am setting up a media serve
On 10/25/2016 04:47 PM, Stephen Bertoni wrote:
Have you tried this instead?
root@...[~]config -e -o /bsd.new /bsd
OpenBSD 5.9-stable (GENERIC) #0: Thu May 7 23:16:45 CEST 2015
root@...***.org:/usr/src/sys/arch/i386/compile/GENERIC
Enter 'help' for information
ukc> disable upd
19 matches
Mail list logo
