search for: loulou

Displaying 4 results from an estimated 4 matches for "loulou".

2008 Aug 07
1
package.skeleton does invalide regular name, bis... (PR#12020)
...le that are not in the current directories. If we give a single file to code_file (like code_file=3D"riri/fifi.R"), it does not reconize fifi.R as a regular name and change it to riri/zfifi.R If we give several file to code_file (like code_file=3Dc("riri/titi.R","riri/loulou.R")), it does not reconize titi.R as a regular name, change it to toto/ztiti.R and we get an error on riri/loulou.R Christophe --- 8< --------------------- > package.skeleton(name=3D"miniKml",code_files=3Dc("miniKml/R/global.R","mi= niKml/R/global2.R"),f...
2023 Sep 23
1
Nut-upsdev Digest, Vol 206, Issue 5
...rmissions) ?? 0.016575??? [D2] libusb1: No appropriate HID device found ?? 0.016605??? libusb1: Could not open any HID devices: insufficient permissions on everything ?? 0.016626??? No matching HID UPS found ?? 0.016658??? [D5] send_to_all: SETINFO driver.state "cleanup.exit" root at LOULOU:/tmp/nut# ./drivers/huawei-ups2000 -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... Network UPS Tools - NUT Huawei UPS2000 (1kVA-3kVA) RS-232 Modbus driver 0.05 (2.8.0-2557-g81fca30b2) Warning: This is an experimental driver. Some features may not function correc...
2023 Sep 23
1
Nut-upsdev Digest, Vol 206, Issue 5
...75 [D2] libusb1: No appropriate HID device found > 0.016605 libusb1: Could not open any HID devices: insufficient > permissions on everything > 0.016626 No matching HID UPS found > 0.016658 [D5] send_to_all: SETINFO driver.state "cleanup.exit" > root at LOULOU:/tmp/nut# ./drivers/huawei-ups2000 -DDDDDD -d1 -s test -x > port=auto -x vendorid=... -x productid=... -x subdriver=... > Network UPS Tools - NUT Huawei UPS2000 (1kVA-3kVA) RS-232 Modbus driver > 0.05 (2.8.0-2557-g81fca30b2) > Warning: This is an experimental driver. > Some features...
2023 Sep 19
1
Nut-upsdev Digest, Vol 206, Issue 5
Well, now that the `subdriver` option got added to `usbhid-ups` too, you can at least try that (by building again the current master). See command-line help for the subdrivers it would currently recognize, and copy e.g. the first word as the matching option, e.g.: ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... and try to lockpick your