search for: adoc

hi there say that i have this table >x<-table(adoc, oarb) >x oarb 0 1 adoc ab 1 0 am 5 1 ba 14 1 cc 271 3 ch 87 2 dz 362 6 fl 7 0 fs 84 2 is there...

...revisions (notably about documentation and statuses for ECO and similar modes), but some more get shelved as potential risk to be merged after a release. So as you might get a few free days for tinkering - please take a look at building and running the current git master branch builds. The NEWS.adoc and UPGRADING.adoc should do a good job about highlighting the changes that have landed. If I were to name one subject of interest, I'd say CPS HID that got revised broken USB report descriptor fix-up code, so hopefully fixes some problems with voltage reporting and does not regress where it...

...revisions (notably about documentation and statuses for ECO and similar modes), but some more get shelved as potential risk to be merged after a release. So as you might get a few free days for tinkering - please take a look at building and running the current git master branch builds. The NEWS.adoc and UPGRADING.adoc should do a good job about highlighting the changes that have landed. If I were to name one subject of interest, I'd say CPS HID that got revised broken USB report descriptor fix-up code, so hopefully fixes some problems with voltage reporting and does not regress where it...

...fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle also FTY and fightwarn branches 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn branches 504706d45 Makefile.am: nut-scanner does directly depend on clients after all 051b49d9f Revert "Revert "NEWS.adoc, UPGRADING.adoc, docs/docinfo.xml.in: finalize text before NUT v2.8.3 release"" 70faea2af Revert "tools/gitlog2version.sh: bump NUT_VERSION_DEFAULT=2.8.3.1 for next development cycle" e1d399b5e include/Makefile.am: nut_version.h: propagate failure (if there ever is one) writ...

...fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle also FTY and fightwarn branches 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn branches 504706d45 Makefile.am: nut-scanner does directly depend on clients after all 051b49d9f Revert "Revert "NEWS.adoc, UPGRADING.adoc, docs/docinfo.xml.in: finalize text before NUT v2.8.3 release"" 70faea2af Revert "tools/gitlog2version.sh: bump NUT_VERSION_DEFAULT=2.8.3.1 for next development cycle" e1d399b5e include/Makefile.am: nut_version.h: propagate failure (if there ever is one) writ...

Hi there, We're currently having problems mounting share from a windows server 2003 machine. The thing that I find surprising is about smbclient : in fact, I'm allowed to browse the share with the command smbclient : # smbclient //adoc/pastel -U mathus%9g8e Domain=[MIPIH] OS=[Windows Server 2003 3790] Server=[Windows Server 2003 5.2] smb: \> And when I try to mount this share with smbmount, here's what I get : p-emapb:/# smbmount //adoc/pastel /adoc/ -o username=mathus,password=9g8e81ae cli_negprot: SMB signing is mandat...

...it's updated: checking out ddl's master should suffice. > I would like to merge the ddl-hll branch back into master (and add DDL to the main "networkupstools" project), if it's ready. Is there anything else needed? I vaguely recall I wanted to move (in nut-ddl-raw/README.adoc) the detailed descriptions of 'special' comments and RW vars/instant commands declaration from the 'nds' section to the 'dev/seq' one and then comment out the 'nds' section till we're ready with the supporting software. Well, as I was there.. just did it. Sorry...

...nder Mandriva I can kiss Windows goodbye. Yeah. The application is called MB Navigator. It is a stand alone stock trading application linking me to my brokers servers. The application installed great. Upon executing the program is starts up just fine then I get this error: Can't create object:ADOC command I can't produce a log.txt file because the program actually executes and the log.txt file cannot capture the error. I hope someone can help because I am going to have a celebration if I can finally dump windows.

...ov/pre-283-2) appveyor.yml: handle > also FTY and fightwarn branches > 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn > branches > 504706d45 Makefile.am: nut-scanner does directly depend on clients after > all > 051b49d9f Revert "Revert "NEWS.adoc, UPGRADING.adoc, docs/docinfo.xml.in: > finalize text before NUT v2.8.3 release"" > 70faea2af Revert "tools/gitlog2version.sh: bump > NUT_VERSION_DEFAULT=2.8.3.1 for next development cycle" > e1d399b5e include/Makefile.am: nut_version.h: propagate failure (if &gt...

...ov/pre-283-2) appveyor.yml: handle > also FTY and fightwarn branches > 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn > branches > 504706d45 Makefile.am: nut-scanner does directly depend on clients after > all > 051b49d9f Revert "Revert "NEWS.adoc, UPGRADING.adoc, docs/docinfo.xml.in: > finalize text before NUT v2.8.3 release"" > 70faea2af Revert "tools/gitlog2version.sh: bump > NUT_VERSION_DEFAULT=2.8.3.1 for next development cycle" > e1d399b5e include/Makefile.am: nut_version.h: propagate failure (if &gt...

Hi Daniele and Arnaud, While tracking down the Cyber Power voltage scaling issue, I found the DDL repository extremely helpful. Instead of searching across all of the old mailing list posts, I was able to run 'git grep' in the Cyber Power directory, and the consistency of the data made it an easy task. I had a motherboard failure on my main computer, and I was trying to recreate the

So, NUT v2.8.3-rc1 is out. I first thought it was the release, but some CI runs convinced me otherwise, so there would be a bit of back and forth on the master branch as some recipes get fixed. Apparently, some parallel runs stepped onto each other's toes sometimes, but coinciding the wrong way just once in a few hundred builds. Hopefully I found why and will re-publish in a few hours. Jim

So, NUT v2.8.3-rc1 is out. I first thought it was the release, but some CI runs convinced me otherwise, so there would be a bit of back and forth on the master branch as some recipes get fixed. Apparently, some parallel runs stepped onto each other's toes sometimes, but coinciding the wrong way just once in a few hundred builds. Hopefully I found why and will re-publish in a few hours. Jim

...plete, if they >> would do so soon, but it seems prudent to ask the greater NUT user and >> developer community to test custom builds of master branch with their >> devices and use-cases, to help ensure no new bugs get delivered this time ;) >> >> Take a look at NEWS.adoc for the whole feature change set since the >> previous release, and UPGRADING.adoc for highlights of the changes that are >> expected to impact existing deployments and/or packaging recipes. >> >> On my side, I still have plans for some documentation changes, >> incl...

...> wrote: >> >> That's MinutemAn and such a key word exists in usbhid-ups subdriver >> tripplite-hid :) >> >> >> Specifically, the "PRO RT 2U" series is among the few mentioned by name: >> ```` >> $ git grep -i minuteman >> NEWS.adoc: ? * add Delta Minuteman UPS VID/PID [PR #1230, issues #555 >> and #1227] >> drivers/tripplite-hid.c:/* Delta/Minuteman */ >> drivers/tripplite-hid.c: ? ? ? ?/* Delta/Minuteman Enterprise Plus >> E1500RM2U */ >> drivers/tripplite-hid.c: ? ? ? ?/* Delta/Minuteman PRO1...

I am wondering if there is a way to have Nut Server monitor a Minutemen UPS. https://minutemanups.com/uninterruptible-power-supply/pro-rt2u-line-interactive-uninterruptible-power-supply/ Thanks James -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20231213/254b1111/attachment.htm>

SlashDot had an article today on a Linux server malware attack, <http://it.slashdot.org/story/14/03/18/2218237/malware-attack-infected-25000-linuxunix-servers>. I wonder if there is a simple test to see if a CentOS machine has been infected in this way? The article mentions Yara and Snort rules to test for this, but I wonder if there is something simpler? Alternatively, are there Yara or

...to Stream and later switch the setup to be fully upstream-first. We also discussed a README file for the mirrored content - I created the initial version here for reviews and suggestions: https://gitlab.cee.redhat.com/red-hat-enterprise-linux-documentation/rhel-8-docs/-/blob/master/centos/README.adoc Hope that helps, Tomas -- Tom?? ?apek Senior Documentation Program Manager Customer Content Services irc: tcapek Too brief? Here's why: the email charter <https://medium.com/virtual-teams-for-systemic-change/the-email-charter-an-idea-worth-spreading-688b8940f892> -------------- nex...

...nder: MVL is used to say how many of the *SCALAR* register file get utilised to "make up" a vector). oh. ah. bruce (et al), isn't there an option in RVV to allow Vectors to sit on top of the *scalar* register file(s)? (Zfinx) https://github.com/riscv/riscv-v-spec/blob/master/v-spec.adoc#vector-registers > Or maybe we'll > be able to synthesize a predicate from an active vlen and pattern match? the purpose of having a dynamic VL, which comes originally from the Cray Supercomputer Vector Architecture, is to not have to use the kinds of instructions that perform bit-man...

On Tue, Oct 1, 2019 at 8:08 AM Robin Kruppe <robin.kruppe at gmail.com> wrote: > > Hello Jacob and Luke, > > First off, even if a dynamically changing vscale was truly necessary > for RVV or SV, this thread would be far too late to raise the question. > That vscale is constant -- that the number of elements in a scalable > vector does not change during program execution