similar to: Custom udev rules to override defaults?

Anyone have an idea as to how to automatically detect the USB number and create a sym link in the dosdevices directory. The problem is that I have several USB devices not used at the same time, and when the USB to serial adapter is connected, a /dev/ttyUSB? is assigned. To use this assignment under WINE, I need to automatically detect /dev/ttyUSB? and then create a sym link in

Hi All, I've written a custom udev rule to change the permissions of /dev/ttyS* but it doesn't seem to be working at boot up. If I run /sbin/udevcontrol reload_rules; udevtrigger The rules are parsed, applied and the permissions are then correct but why is it not doing so at boot? The file in questions I've called /etc/udev/rules.d/49-udev-override.rules and it contains

I have been struggling with setting up two serial ports on an HP/Compaq D512S (Intel P4) under CentOS-5. I am not at all sure why these things were not auto-configured when I initially installed the CentOS system from CDs but they were not. I have found various resources on the web and from them uncovered the setserial utility. What I need from somebody is guidance on how to use this utility to

> Hello Arnaud, Hi Alex, > First of all i want to thank you for such useful and convenient > system tool as NUT. I think it is one from most important tools > for server machines. And it make its work excellent. thanks > I use NUT on SuSE distro and adapted init-scripts from package for > this distro style. Send you them with hope that you find them useful > for

Hi, On a regular FC4 machine there are 76 device file for /dev/ttyS*. I tried running minicom on a Xen machine (domain 0) whose serial port is connected to a different machine (a machine with no VGA/Keyboard/Mouse). It gave the following error: minicom: WARNING: configuration file not found, using defaults Device /dev/ttyS1 access failed: No such file or directory. So I checked, and ls

On 7/5/23 03:17AM, Jim Klimov wrote: > Ah, I thought you missed in my earlier reply the part about a bug with debug printouts in 2.8.0 (fixed on master since), > did not comment on that when you replied with quoting... So, for now options are to bump debugging to 3+ or to build > your own in one of many ways possible :\ I think I'm not following you - with debug 3 -->> it

Hello! I got my hands on a CyberPower 1500AVRT, and i'm trying to get it connected to my Gentoo machine. I've followed all the basic guides on setting up NUT and UPS' but have had no luck. My current ups.conf is: [cyberpower-gentoo] driver = cyberpower port = /dev/ttyS0 desc = Workstation Upon running /etc/init.d/upsd start or upsdrv start I get: * Starting

I'm trying to Compile/Package and then (on a different box) Config/Run 2.8.1. Both boxes are Raspberry Pi 4b on Bullseye with a generic USB UPS. -- I'm trying to get nut running on my Raspberry (bullseye/11). (I'd also love to share a working 2.8.1 for Raspberry with the world, but...) I compiled the latest code from git: version 2.8.1-774-g963abbd87 I compiled it on one system

Greetings all; Back to a thread I started back in May of 2008 I think. I never did get this belkin and nut to talking, so I thought I'd make another run at it. Trying to run the driver as the user gene, I'm getting this: --------------------------- [root at coyote ups]# su gene -c "/sbin/belkin -D -a myups" Network UPS Tools - Belkin Smart protocol driver 0.21 (2.2.2) debug

A while back I got help in getting my Palm Pilot to connect to CentOS, and through the advice I got here I was able to successfully back up my files to the computer using the CentOS default Palm utility. However, I now want to use JPilot to sync and install files. But when I attempt to sync through JPilot, I get the following error: ******************************* Syncing on device /dev/pilot

I just installed CentOS 5.1 on a Dell Vostro 200 (Intel G33) which has a Sunix PCI-Express (x1) 8-port RS-232 card installed. For me it looks like only 4 ports are recognized, but I'm not sure if it's even working with those 4. >From 'dmesg' I see this: ... Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 19

Hi, I'm having trouble getting my Palm to sync with jpilot on my Centos system via USB. When I sync, I get this error in jpilot: pi_accept Illegal seek Exiting with status SYNC_ERROR_PI_ACCEPT Finished I have jpilot syncing fine with this Palm over the network, BTW. For USB, I set things up for udev as described on various websites. Here are the relevant ports & symlink (created

Ah, I thought you missed in my earlier reply the part about a bug with debug printouts in 2.8.0 (fixed on master since), did not comment on that when you replied with quoting... So, for now options are to bump debugging to 3+ or to build your own in one of many ways possible :\ On Wed, Jul 5, 2023, 06:23 Karl Schmidt <karl at lrak.net> wrote: > On 7/4/23 10:01PM, Jim Klimov wrote: >

I have a new APC Smart-UPS SUA2200RM2U. I've had no success with the manufacturer's PowerChute software and smart signaling, so I have decided to try NUT. The smartups driver can't make contact through the serial port. Since this is rack-mounted, it comes with a 940-1524 serial cable. As far as I can tell, this is supposed to work with smart signaling. Here's my ups.conf:

Hi All I am connecting a ups via a usb to serial converter. Works fine, however when the converter is unplugged and plugged back in, udev creates another device e.g instead of ttyUSB0 it creates ttyUSB1. Here is the udev rule that I added to the top of the 025_nut-usbups.rules file in order to create a static symlink should udev decide to create the device as either ttyUSB0 or ttyUSB1.

Arnaud et al, I have been meaning to collect some of the documentation updates for permission-related errors, and I was wondering if you would mind if we moved the scripts/udev/README and scripts/hotplug/README files out of scripts/ and into the docs/ directory (probably docs/permissions.txt). We could also cover the *BSD /dev/usb* permission issues there, as well. Any thoughts on this? -- -

Can someone please help me with writing a udev rule? I need /dev/ttyUSB0 to automatically have 777 rights when plugged in. I'd like it to only apply to that one specific device. I'm not sure where to start, what files to look at and also what to write to make it work. TIA Brad This e-mail transmission contains information that is confidential and may be privileged. It is intended only

I made the following devd script.. sh cd /tmp fetch mkdir /usr/local/etc/devd sed -Ene 's/SYSFS\{idVendor\}==\"(.*)\", SYSFS\{idProduct\}==\"(.*)\", MODE=.*/attach 100 {\ device-name "ugen[0-9]+";\ match "vendor" "0x\1";\ match "product" "0x\2";\ action "chown @RUN_AS_GROUP@

I hope this is not to far off topic. I have a Windows 2003 guest on a CentOS 5.5 KVM host. I need to use the serial port on the win2003 guest for the application it is serving. I have no idea what needs to be done but it looks like the linux host is trying to use the serial port as the priamary console but I don't really understand what that is or where it is configured. What I need is for

I am new to CentOS and have installed the dgap rpm for the mentioned 16 port board. I turned on in Services dgap. However, when I reboot the system the ttys disappear. Could it be that the udev rpm is not installed? When I run the mpi install and load program, everything works. But a reboot deletes it all! Help!