From owner-freebsd-emulation Sun Oct 4 12:22:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14122 for freebsd-emulation-outgoing; Sun, 4 Oct 1998 12:22:21 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14101 for ; Sun, 4 Oct 1998 12:22:07 -0700 (PDT) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with SMTP id OAA01101; Sun, 4 Oct 1998 14:21:40 -0500 (EST) Date: Sun, 4 Oct 1998 14:21:39 -0500 (EST) From: John Fieber To: Joao Carlos Mendes Luis cc: emulation@FreeBSD.ORG Subject: Re: APC PowerChute under FreeBSD In-Reply-To: <199810041904.RAA10040@roma.coe.ufrj.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 4 Oct 1998, Joao Carlos Mendes Luis wrote: > I've seen it, but it appears to support only 220v models and > has a very poor documentation. What documentation? :) Actually, adding support for new models is pretty trivial. However, I'm not using it at all for the moment because it had some problems with FreeBSD 3.0-BETA that I haven't even begun to investigate. I'd actually like to find something else because on the surface the upsd config file looks relatively simple and flexible but in practice it is incomprehensible and I've failed to get it to do anything beyond the simplest of shutdown procedures. > I've also tried the Linux apcupsd (binary only), but it also seems > to have an ioctl emulation incompatibility. And I thought serial ports > were the most portable device between unixen, after /dev/null. :) Since I've just been working in the guts of the emulator to get Sybase running...what is the ioctl in question? -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message