search for: wsvn

....org/Documentation/UserManual/Features http://test.networkupstools.org/Documentation/UserManual/Compatibility/Stable I'm currently preparing the support of 4 Eaton network (SNMP) PDUs (the full Eaton range, from Aphel and Pulizzi) This is based upon the outlet collection: http://svn.debian.org/wsvn/nut/trunk/docs/new-names.txt?op=file&rev=0&sc=0 And will be as simple as creating a few .h files like that one: http://svn.debian.org/wsvn/nut/trunk/drivers/mgemib.h?op=file&rev=0&sc=0 See also http://svn.debian.org/wsvn/nut/trunk/docs/powersaving.txt?op=file&rev=0&sc=0 for...

...t the information tone that the number is not connected. I would like to try vzaphfc and I am looking for information on it. >From previous posts I found that the only place where the sources seem to be maintained and available is at the debian site which I found here : http://svn.debian.org/wsvn/pkg-voip/zaptel/trunk/vzaphfc/ But I couldn't find any place where I could download a tarball. Is vzaphfc an inplace replacement of the zaptel of bristuff? Or something separate? Thanks!!

...or executing command Could not communicate with the ups: Inappropriate ioctl for device THE UGLY: It is possible to create a deb with patched in support for the Powerware 5115A using the following steps: 1. sudo apt-get source nut 2. sudo apt-get build-dep nut 3. wget 'http://svn.debian.org/wsvn/nut/trunk/drivers/nut_usb.c?op=file&rev=1220&sc=1' -O nut_usb.c.new 4. wget 'http://boxster.ghz.cc/projects/nut/browser/trunk/scripts/udev/nut-usbups.rules.in?format=raw' -O nut-usbups.rules.in.new 5. wget 'http://svn.debian.org/wsvn/nut/trunk/drivers/nut_usb.h?op=file&r...

My UPS Powercom WOW-1000U does greatly work with NUT, but not auto-cofigurable... This UPS is not usb-hid ups, and works well with this settings in NUT: [powercom] desc = "powercom" driver = powercom port = "/dev/serial/by-id/usb-POWERCOM_CO.__LTD._USB_to_Serial-if00-port0" type = IMP lsusb -v fragment attached. Unlike other UPSes, gnome-power-manager does

..."tags" directory - with Subversion, tags can be deleted (to keep the tags directory organized and relevant), but if you go back in the repository timeline, you can still refer to the tags for diffs and such. The most up-to-date place to track revisions is here: http://svn.debian.org/wsvn/nut Personally, I think wsvn is not as transparent as Trac, so I will be synchronizing my local Trac setup from time to time: (yes, I will try and automate this at some point) http://boxster.ghz.cc/projects/nut If you are a developer, you can access the repository via: svn+ssh://svn.debia...

...nough or because I don't manage to capture it. > > I would have thought finding the place in the code where it is trying to > reset the UPS connection wouldn't be this hard. > this is not the problem. This code is in the smartmode() function of apcsmart.c: http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c we see the 5 attempts to go to smart mode ('Y' command), but my aim is to understand why it is failing, and how to cleanly solve this without impacting support for other units. Some more questions: - how are you handling the device's permissions? Refer to...

...nough or because I don't manage to capture it. > > I would have thought finding the place in the code where it is trying to > reset the UPS connection wouldn't be this hard. > this is not the problem. This code is in the smartmode() function of apcsmart.c: http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c we see the 5 attempts to go to smart mode ('Y' command), but my aim is to understand why it is failing, and how to cleanly solve this without impacting support for other units. Some more questions: - how are you handling the device's permissions? Refer to...

...forward it to him and invite him to contact me. I hope to have good feedback and reaction on it, though I'm currently (and at least until the end of march) not much available... Arnaud -- [1] http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-March/000776.html [2] http://svn.debian.org/wsvn/nut/trunk/data/driver.list?op=file&rev=0&sc=0 [3] http://svn.debian.org/wsvn/nut/trunk/docs/new-names.txt?op=file&rev=0&sc=0 [4] http://svn.debian.org/wsvn/nut/trunk/drivers/dstate.h?op=file&rev=0&sc=0 -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools...

On Mon, Mar 31, 2014 at 02:22:50PM +1030, Rusty Russell wrote: > > It's head of my virtio-next tree. Hey Rusty, While we have your attention --- what's your opinion about adding TRIM support to virtio-blk. I understand that you're starting an OASIS standardization process for virtio --- what does that mean vis-a-vis a patch to plumb discard support through virtio-blk?

On Mon, Mar 31, 2014 at 02:22:50PM +1030, Rusty Russell wrote: > > It's head of my virtio-next tree. Hey Rusty, While we have your attention --- what's your opinion about adding TRIM support to virtio-blk. I understand that you're starting an OASIS standardization process for virtio --- what does that mean vis-a-vis a patch to plumb discard support through virtio-blk?

...MU. At least x86's implementation of the DMA ops for devices that aren't behind an IOMMU should be very fast. Are there any other weird cases for which this might be a problem? > > Please also update the virtio specification: > https://tools.oasis-open.org/version-control/browse/wsvn/virtio/ > I'm not sure it will need an update. Perhaps a note in the PCI section indicating that, if the host expects the guest to program an IOMMU, then it should use the appropriate platform-specific mechanism to expose that IOMMU. --Andy

...MU. At least x86's implementation of the DMA ops for devices that aren't behind an IOMMU should be very fast. Are there any other weird cases for which this might be a problem? > > Please also update the virtio specification: > https://tools.oasis-open.org/version-control/browse/wsvn/virtio/ > I'm not sure it will need an update. Perhaps a note in the PCI section indicating that, if the host expects the guest to program an IOMMU, then it should use the appropriate platform-specific mechanism to expose that IOMMU. --Andy

...ices that aren't >> behind an IOMMU should be very fast. >> >> Are there any other weird cases for which this might be a problem? >> >> > >> > Please also update the virtio specification: >> > https://tools.oasis-open.org/version-control/browse/wsvn/virtio/ >> > >> >> I'm not sure it will need an update. Perhaps a note in the PCI >> section indicating that, if the host expects the guest to program an >> IOMMU, then it should use the appropriate platform-specific mechanism >> to expose that IOMMU. &gt...

...ices that aren't >> behind an IOMMU should be very fast. >> >> Are there any other weird cases for which this might be a problem? >> >> > >> > Please also update the virtio specification: >> > https://tools.oasis-open.org/version-control/browse/wsvn/virtio/ >> > >> >> I'm not sure it will need an update. Perhaps a note in the PCI >> section indicating that, if the host expects the guest to program an >> IOMMU, then it should use the appropriate platform-specific mechanism >> to expose that IOMMU. &gt...

I have an FC5 system with a powerware 5110 usb ups. The system seems to find the UPS ------------------------------ [root@b1 src]# lsusb Bus 004 Device 001: ID 0000:0000 Bus 003 Device 002: ID 0592:0002 Powerware Corp. Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 ------------------------------- [root@b1

...d in our brand new automake system. The compilation is currently broken (@Peter: I've not yet succeeded in giving the good CFLAGS for libdummy-hal... If you have an idea), so avoid using --with-hal for the moment. Some details about this are given in the docs/nut-hal.txt: http://svn.debian.org/wsvn/nut/trunk/docs/nut-hal.txt?op=file&rev=0&sc=0 * I would like to thanks the NUT Development Team, and especially Peter Selinger, Charles Lepple, Carlos Rodrigues and Arjen de Korte for their dedication and support to the project. And as always, a big thank to MGE which gives me time to wor...

...d in our brand new automake system. The compilation is currently broken (@Peter: I've not yet succeeded in giving the good CFLAGS for libdummy-hal... If you have an idea), so avoid using --with-hal for the moment. Some details about this are given in the docs/nut-hal.txt: http://svn.debian.org/wsvn/nut/trunk/docs/nut-hal.txt?op=file&rev=0&sc=0 * I would like to thanks the NUT Development Team, and especially Peter Selinger, Charles Lepple, Carlos Rodrigues and Arjen de Korte for their dedication and support to the project. And as always, a big thank to MGE which gives me time to wor...

...> + if (query.flags[FL_LOAD_OFF] == '1') { > + status_set("SHUTDOWN"); > + } Please check the megatec version in the development trunk*. This section has changed and I guess it works similarly to what you wanted here. * http://svn.debian.org/wsvn/nut/trunk/drivers/megatec.c?op=file&rev=0&sc=0 -- Carlos Rodrigues

...of useless status commands, > unsupported by my ups, but these seem more than enough for a start. > well, I personally won't make the driver (no hardware and no time). but we can help you in doing one, and it's not that hard. have a look at the following docs: http://svn.debian.org/wsvn/nut/trunk/docs/new-drivers.txt?op=file&rev=0&sc=0 http://svn.debian.org/wsvn/nut/trunk/drivers/skel.c?op=file&rev=0&sc=0 creating a new serial driver is not really hard, really! I've seen in the header that you based your work on this: http://www.csc.liv.ac.uk/~greg/projects/li...

In honor of RailsConf, I''m releasing an authorization plugin with 3 test apps that show you how to use the system. A reasonably lengthy description can be found here: http://www.writertopia.com/developers/authorization I will also be talking about the plugin''s architecture in my RailsConf talk on Saturday. Some features: - Nice English-like way of expressing permissions through