search for: usbinfo

...nning of the subdirectory list? It seems that it is writing some *.in files during 'make dist', which should undergo variable substitution. (There will probably be other dependency issues to resolve, but that would be the first step.) On a related note, I would like to add some code to nut-usbinfo.pl to blacklist bogus vendor IDs (e.g. 0x0000, or the Lakeview Research VID) from the HAL files. I guess we can leave them in the udev/hotplug files, but eventually we will want to separate them out as well (as discussed previously) -- - Charles Lepple

On May 29, 2015, at 8:09 AM, Bastien Nocera <hadess at hadess.net> wrote: > It would also be useful to include a full URL to the NUT Perl script > (to a git repository perhaps), so people don't need to check out the > full repo to update it. I'm not sure how useful the nut-usbinfo.pl script will be without the NUT repository: it scans the NUT source files for certain macros containing USB VIDs and PIDs. The NUT URL listed in the file <https://github.com/networkupstools/nut/commits/master/scripts/upower/95-upower-hid.rules> refers to the history of a checked-in version...

...ower-hid.rules # # This file was automatically generated by NUT: # https://github.com/networkupstools/nut/ # # To keep up to date, monitor upstream NUT # https://github.com/networkupstools/nut/commits/master/scripts/upower/95-upower-hid.rules # or checkout the NUT repository and call 'tools/nut-usbinfo.pl' Or do you see any other better wording? thanks and cheers, Arno -- Eaton Data Center Automation - Opensource Leader NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr ---------...

...> New Revision: 1556 > > Log: > USB "improved maintenance" code. Refer to docs/new-drivers.txt for > more information... > > Added: > trunk/drivers/usb-common.c > trunk/drivers/usb-common.h > trunk/tools/ > trunk/tools/Makefile.am > trunk/tools/nut-usbinfo.pl (contents, props changed) > Modified: > trunk/ChangeLog > trunk/Makefile.am > trunk/configure.in > trunk/docs/new-drivers.txt > trunk/drivers/ (props changed) > trunk/drivers/Makefile.am [snip] I noticed in the Makefile.am you flagged this driver as broken. What...

...####################################################################### # Uninterruptible Power Supplies with USB HID interfaces # -# to keep up to date, monitor: http://svn.debian.org/wsvn/nut/trunk/scripts/upower/95-upower-hid.rules +# This file was automatically generated by NUT (nut/tools/nut-usbinfo.pl) +# to keep up to date, monitor upstream NUT https://github.com/networkupstools/nut/commits/master/scripts/upower/95-upower-hid.rules +# and upstream UPower http://cgit.freedesktop.org/upower/tree/rules/95-upower-hid.rules -# only support USB, else ignore +# newer hiddev are part of the usbmis...

...gt; > # https://github.com/networkupstools/nut/ > > # > > # To keep up to date, monitor upstream NUT > > # > https://github.com/networkupstools/nut/commits/master/scripts/upower/95- > > upower-hid.rules > > # or checkout the NUT repository and call 'tools/nut-usbinfo.pl' > > > > Or do you see any other better wording? > > The rest is fine. > ok, thanks. I'll just wait for your ack on the above UPower repos. point, to push the remaining commit. thx and cheers, Arno -- Eaton Data Center Automation - Opensource Leader NUT (Network...

...rocedure I used to compile is also the same as Denis suggested, but I made some changes on my own in the "build NUT" step since I added the "nutdrv_atcl_usb.c" source file from the last version of NUT, not present in the latest Windows build. Those are: - Patched file "nut-usbinfo.pl" as otherwise it will abort the make process with an error. In the section "process the driver name" with the following code (same as latest NUT linux version): elsif ($nameFile eq "nutdrv_atcl_usb.c") { $driver="nutdrv_atcl_usb"; - Patched the "make...

...automatically generated by NUT: > # https://github.com/networkupstools/nut/ > # > # To keep up to date, monitor upstream NUT > # https://github.com/networkupstools/nut/commits/master/scripts/upower/95- > upower-hid.rules > # or checkout the NUT repository and call 'tools/nut-usbinfo.pl' > > Or do you see any other better wording? The rest is fine. Cheers

..., it's the right time to send it. @Greg: here is the list of postponed patch, with rationales. If you feel some of this should not wait for 2.8.0, tell me back. postponed - 8-10 (pyperl / snmp...) => need tree / deps handling revamp + [PATCH] "oops, forgot that I changed where nut-usbinfo.pl is to be run from!" - 11 => need advanced sysOID matching (is_subtree may not be enough, a linked list of sysOID may be needed... need more investigation) - 12 => not needed (static are refreshed and settable!). Need confirmation from Greg. - 19 => status "DYING" needs di...

...b.com/networkupstools/nut/ >> > # >> > # To keep up to date, monitor upstream NUT >> > # >> https://github.com/networkupstools/nut/commits/master/scripts/upower/95- >> > upower-hid.rules >> > # or checkout the NUT repository and call 'tools/nut-usbinfo.pl' >> > >> > Or do you see any other better wording? >> >> The rest is fine. >> > > ok, thanks. > > I'll just wait for your ack on the above UPower repos. point, to push the > remaining commit. > here is the patch, before I completly f...

On Mon, 22 Jul, at 12:07:34PM, Matt Fleming wrote: > On Thu, 18 Jul, at 01:22:04PM, Adrian Irimia wrote: > > Hi, > > ? > > ? I have a bootable usb with syslinux 5.10 on wich the following?code is working ok. > > ??? LABEL - > > ?? MENU LABEL GRUB LEGACY > > ?? MENU INDENT 1 > > ???? COM32 chain.c32 > > ???? APPEND boot fs

...the 2nd error message). >? > Thanks for the report, I can reproduce this bug. I'll take a look. Adrian, could you try 6.02-pre9? -- Matt Fleming, Intel Open Source Technology Center -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: USBInfo.Txt URL: <http://www.zytor.com/pipermail/syslinux/attachments/20130722/8043f3f4/attachment.ksh>

I've grabbed a snapshot of NUT from just a couple days ago. Glad to see APC's new 5G UPSes added to the list (though you probably want to add it to the UDEV 52-nut-usbups.rules file as well...). My issues with new APC Smart-UPS units (SMT1000) : Powering-down the unit, whether with upsdrvctl or upscmd will not obey the specified delay in offdelay, or ups.delay.shutdown. Instead, a

...b ports, compare the results against the data and then > write/install a rule that will allow upsdrvctl to start gid 'nut'. Theoretically, that is the sort of information that we are already gathering from the NUT drivers: https://github.com/networkupstools/nut/blob/master/tools/nut-usbinfo.pl That script generates (among other things) the scripts/udev/nut-usbups.rules.in file, which gets its @RUN_AS_GROUP@ token replaced by the group name at configure time. On the Debian 7 (wheezy) box where I just verified that udev works, it is installed to /lib/udev/rules.d/52-nut-usbups.rules T...

UPDATE: I managed to build the windows port using a guide a user posted a while ago. I?ve also corrected a couple of variables like the SleepEx() function instead of the sleep() used in Linux. I?ve successfully compiled the EXE for nutdrv_atcl_usb but when I execute it via upsdrvctl it gives the following output: C:\MinGW\msys\1.0\home\Administrator\nut-2.6.5-7\drivers>nutdrv_atcl_usb

Hi Arnaud, hi developers, attach there is the patch for riello drivers. Can you tell me if there is other to change in order to accomplish your rules and if the steps I have followed to create the patch are all rights? Cheers, Elio Parisi. Elio Parisi Centro Ricerche RPS SpA Viale Europa, 7 37045 Legnago VR Tel. +39 0442 635811 Fax. +39 0442 635934 Skype Id: - Voip: E-mail: E.Parisi

2015-05-29 14:09 GMT+02:00 Bastien Nocera <hadess at hadess.net>: > On Fri, 2015-05-29 at 13:59 +0200, Arnaud Quette wrote: > > Hi Richard and the list, > > > > you'll find attached a patch for 95-upower-hid.rules, which adds: > > - the "usbmisc" filtering, as added in your repo, > > - more comments, including one that points at your UPower

Here are a series of my recent changes to NUT. The first few in the set are primarily little fixes and improvements. In among those are a few for .gitignore files which of course you can ignore for SVN, and there's one for a commit to a generated file which of course should not be tracked in any VCS. Then there are a couple or three to do with generating the header files used by

On 12/14/2013 09:04 PM, Charles Lepple wrote: >> Is there someway nut can be modified to probe the 0664 permission usb >> devices >>> and then connect as root before dropping permissions back to the "nut" >>> gid? > Given that the udev method should still work (and seems to, for handcrafted > udev rules files), I would like to run that to ground first.