Re: apc ups daemon

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanasis wrote: Is there a port of the apcupsd or any other daemon for ups on openbsd? nut works well. Takes a bit of reading, if you're coming from apcupsd, but it's very flexible. - -- David Talkington dt...@drizzle.com - -- PGP key:

Re: Building OpenBSD

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric Furman wrote: If you like troubleshooting then OpenBSD is going to be no fun for you. OpenBSD Just Works You'll also find that your best friend is 'man' instead of 'google'. That's an adjustment that takes time for Linux refugees ... ;-)

Gigabyte GA-G31M-ES2L boot failure

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is FYI in case it interests anyone. I've given up on this board and will be exhanging it. Boots and runs: 4.4-i386 Fails to boot: 4.4-amd64, 4.5-i386, 4.5-amd64. The amd64 disks will get to fdc0... and then hang indefinitely. 4.5-i386

Re: sendmail vs. other MTAs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Henning Brauer wrote: the wrong design that sendmail abondoned long ago. ... unlike sendmail's preprocessed configuration file, to which it clings tenaciously. Seriously, having to chase down a source file to make configuration changes is not

Re: build fails on 4.5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ted Unangst wrote: On Mon, Apr 27, 2009 at 1:54 PM, Maurice Janssen maur...@z74.net wrote: === libexec/ld.so /bin/sh: cd: /usr/src/libexec/ld.so - No such file or directory *** Error code 1 The mirror is broken because rsync, in its infinite

Re: where to order now ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Liam J. Foy wrote: Yes, we are pleased to be a new reseller based in the UK (we serve Europe too of course! - the 'we' bit is a close friend who is involved in distribution in the UK (which is what we're also setting up)). We are not associated

Re: European orders

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 bofh wrote: In your case, I believe the best option is to download and donate. The only problem is that most people forget part 2 - donate. May I suggest a compromise? It sounds like many cannot afford the CDs and shipping, and most who spend

Re: European orders

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Theo de Raadt wrote: Donations and sales do not mix. Businesses cannot do that. It is either a sale, or it is a gift. Please don't confuse the two. Depends on your status. The type of transaction I described is common among nonprofits in the

Re: openbsd in virtualization

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stuart Henderson asked: how does one increase efficiency and reduce IT costs by making things more complicated? And Marc Balmer adds: And, quite obviously, reduce stability and after all security. Apologies if this is wandering too far off

Re: openbsd in virtualization

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Donahue wrote: I run OpenBSD under VMware Server and ESXi. (Both are free) It is fairly stable and the performance isn't bad. I would recommend you use the Other Linux (64-bit) profile so you can get access to the e1000 virtual NIC. In an

Re: openbsd in virtualization

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Donahue wrote: I don't have the VM image around any more, but I don't remember any unexpected performance problems. The VM was acting as a firewall/DHCP server ... The problem was disk i/o, so you might not perceive the issue on a firewall.

4.4 on ESXi 3.5 (was: vic(4) on amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Archambault wrote: I'm fairly confident that using anything other than the default e1000 network device with 64-bit guests is discouraged by VMWare. It would appear that you're correct. Though the documentation does not make that clear, I

vic(4) on amd64

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Salutations -- I see that the vic(4) driver is still not in amd64/conf/GENERIC. Has anyone any recent experience with this driver+platform, or know whether its absence reflects a known problem or just lack of testing? For the record, it works

resolved: xenocara: build problem: Package xdmcp was not found...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 dt...@drizzle.com wrote: This occurs when building xenocara after updating /usr/src, /usr/ports, /usr/xenocara to -stable from cvs and successfully building kernel and src: -

xenocara: build problem: Package xdmcp was not found...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Salutations -- This occurs when building xenocara after updating /usr/src, /usr/ports, /usr/xenocara to -stable from cvs and successfully building kernel and src: -

ports-security

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Salutations -- The archive of ports-security shows the last post to be from January 2006. What is the appropriate channel through which to receive security notices regarding ports and packages? Cheers -d David Talkington dt...@drizzle.com -