similar to: compiling nut-2.2.2 on Solaris

[Andrew: please subscribe to the nut-upsuser list: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser Also, please gzip any attached logs.] > Hello, > > I downloaded NUT ver 2.6.2 and tried it on my Linux development > board. when I configure and it notified me that "USB drivers > requested, but libusb not found." > Then I download libusb

Hello, I have been trying to get a TrippLite Internet Office 750 UPS to talk to my Linux PBX for a couple of evenings now and I'm getting nowhere... I tried searching the list archives before posting here (I'm sure I'm not the first one to try to get this going) but they seem to be offline... The UPS is unfortunately USB based but I thought I'd give it a try anyway. Here is

Hi Stephen, It's been a little busy at home, so I haven't had a chance to go over the pull request in depth, but I didn't want you to think it hadn't been considered. On Apr 19, 2014, at 1:23 AM, Stephen J. Butler wrote: > I've added a pull request with changes to drivers/libusb and drivers/usbhid-ups mainly. They are to resolve issues I encountered when setting up a

Sorry about the noise guys. Below a significantly improved patch. The main difference is that all calls to usb_get_string_.. have been wrapped in a new function nut_usb_get_string()  that is implemented in libusb.c This was necessary in order to make the bufflen_fix available in libusb.c where usb_get_string() is called in libusb_open() This wrapper function mops up and hides all the work

I was about to copy wmmintrin.h for the FreeBSD project, but I noticed that the file (clang/lib/Headers/wmmintrin.h) does not have a copyright statement in it, though it says: * The above copyright notice and this permission notice shall be included in * all copies or substantial portions of the Software. Also, the license is significantly different than what is contained in LICENSE.TXT, as the

I've added a pull request with changes to drivers/libusb and drivers/usbhid-ups mainly. They are to resolve issues I encountered when setting up a Tripp Lite SMART1500LCDT, but I think they're generally useful to the community. Here is the pull request comment I sent: https://github.com/networkupstools/nut/pull/122 Had trouble getting nut to work for my new Tripp Lite SMART1500LCDT. So

I recently put together a new machine w/ a SuperMicro H8SCM and an AMD Opteron 4228 HE... I've having an issue where the clock on the machine skips around... The wierd part is that it's very sudden when it happens... ntp sometimes brings it back, but it can't when the clock gets too far ahread (1000 seconds), ntp dies... In order to catch it happening, I ran a sleep 60 loop

Hello all, First off, thanks for all of your hard work on OpenSSH! I recently updated our SSH infrastructure from OpenSSH 3.8.1p1 to Cygwin 1.7 (which includes OpenSSH 5.4p1) and noticed that when running commands via ssh on my Windows machines I no longer have access to the full set of Windows environment variables. Digging through source, I see that this change was introduced in v4.0 (the

Is anyone here running a USB UPS on Solaris? I'm looking to upgrade my UPS (from a SmartUPS 620 with RS232 comms), and most of the modern UPSs use USB ... TX, Huge.

--- linux power <linuxpower2002@yahoo.no> skrev: > Dato: Sun, 29 Sep 2002 21:40:07 +0200 (CEST) > Fra: linux power <linuxpower2002@yahoo.no> > Tema: Fwd: SOLVED SOLVED:Connecting problem:Need > Help > Til: samba@lista.samba > > Yes it was the iptables firewall that was the > problem. > The port 137-139 were not opened as I thought they > were. I should

CentoOS 7 python-cryptography package is at version 0.8.2 It has a build-requires for python-cryptography-vectors of the same version (but different source tarball apparently) There is no python-cryptography-vectors in CentOS 7 base or updates. There is one in EPEL but it is version 0.8 -=- If you relax the BuildRequires to just require python-cryptography-vectors then the build fails

There were a few notes in this thread that may indicate open areas for development. I forward merely as FYI. http://www.metzdowd.com/pipermail/cryptography/2015-January/024231.html ---------- Forwarded message ---------- From: Peter Gutmann <pgut001 at cs.auckland.ac.nz> Date: Sun, Jan 4, 2015 at 9:29 PM Subject: Re: [Cryptography] Why aren?t we using SSH for everything? To: calestyo at

Hi all, while fiddling with VmWare View without being able to join windows7 client to samba4 domain, we stumbled on the following article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1028164 which says, should we run MS Windows 2008R2 AD, we should enable the "Allow cryptography algorithms compatible with Windows NT 4.0"

Le Friday, 31 March 2023, 17:47:14 EDT John-Mark Gurney a ?crit : > hvjunk wrote this message on Thu, Mar 30, 2023 at 23:12 +0200: > > I've been battling similar issues, and the only methods I've found (with sftp) was to use > > software like pureftd or crushftp (using crushftp lately as production) that does handle these > > issues "out of the box" > >

On Sep 15, 2015, at 9:31 PM, Charles Lepple <clepple at gmail.com> wrote: > >> Trying to track down the source of the problem, I checked Yast to make sure I had at least 0.1.8 version for libusb. I saw this (attached photo). Is it then actually using ?compat instead of the ?real? libusb? And is that a problem? > > You're right, both the -compat and real libusb

CentOS tracks RHEL and there is something I think probably can only be done in a point release but I believe should be done. Update to nss and curl. The problem - the version of curl that ships with CentOS does not support ECC cryptography. A newer version would, but requires manual specification of the ciphers if the TLS/SSL library used (NSS on RHEL/Fedora) does not have the ECC ciphers

I get the following error on r809 (but it looks like the code change happened here). Does HIDDevice_t need to be defined/changed in one of the headers? if gcc -DHAVE_CONFIG_H -I. -I../../drivers -I../include -I../../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DINET6 -O2 -D_REENTRANT -DNETSNMP_USE_INLINE -Wall -Dlinux -I.

Hello all, Here is build instructions for putting NUT on a Raspberry Pi. Charles - Feel free to put this on your docs list. # Do an rpi-update to prevent USB strangeness #some dependencies from repo sudo apt-get -y install m4 libtool libudev-dev automake #fixing autoconf for later sudo ln -s /usr/share/autoconf/Autom4te /usr/local/share/autoreconf/Autom4te sudo ln -s /usr/bin/autom4te

Hi Steve thanks for your answer. I follow your tutorial untill this instruction: wget "http://downloads.sourceforge.net/project/libusb/libusb-1.0/libusb- 1.0.18/libusb-1.0.18.tar.bz2? r=http%3A%2F%2Fwww.libusb.org%2F&ts=1404210716&use_mirror=softlayer-ams" -O libusb-1.0.18.tar.bz2 in my opiniono there are 2 " that are not needed and i when -O libusb- 1.0.18.tar.bz2 is not

Rob - Just stepping in from the sidelines . . . with a few tidbits. Nut uses pkgconfig to find and identify stuff as part of it's build . . . So, depending on where your libusb install went, if it wasn't in the default "PKG_CONFIG_PATH" setting, it won't be found. Much like other shell variables, you can adjust that setting to find anything you like . . . IE