similar to: 4.2 update removed my zaptel settings fromrules.d/50-udev.rules

I have a machine running 4.1 did hte update to 4.2 my zaptel settings (asterisk pbx) seemed to have gotten lost in the update. The file was /etc/udev/rules.d/50-udev.rules Jerry

Package: xen-utils-common Version: 4.0.0-1 Severity: normal A strange issue, when deploying Xen using Puppet, /etc/udev/rules.d/xend.rules and /etc/udev/rules.d/xen-backend.rules files are empty. Specifically, the symlinks point to ../xend.rules and ../xen-backend.rules respectively in /etc/udev, but neither of those files exist. Manually copying those files from another host that was not

Package: xen-utils-common Version: 3.0.3-0-1 Severity: serious Justification: makes package uninstallable Usertags: grid5000 Hi, During a piuparts run over all the packages in etch, I ran into a problem with your package: Setting up xen-utils-common (3.0.3-0-1) ... ln: creating symbolic link `/etc/udev/rules.d/z60_xen-backend.rules' to `../xen-backend.rules': No such file or directory

Hi, seems there is one missing change in /trunk/scripts/udev/nut-usbups.rules.in BUS -> SUBSYSTEMS previous change [1] missed this. Now, the latest udev started to complain: > ... udevd[31526]: BUS= will be removed in a future udev version ... 098 udev version (from 2006) is required for this [2], but this is the same version as required for previous SYSFS -> ATTR change. I've

Trying to setup asterisk and zaptel on a Fedora Core 3. Its all working after reading up on udev but I still get errors. [root@redhat ~]# ztcfg -vvvvv Zaptel Configuration ====================== Channel map: Channel 01: FXO Kewlstart (Default) (Slaves: 01) Channel 04: FXS Kewlstart (Default) (Slaves: 04) 2 channels configured. Notice: Configuration file is /etc/zaptel.conf line 4: Unable to

I'm trying to work out how to set up a custom udev rule to override permissions on serial ports (/dev/ttyS* and /dev/ttyUSB*) on CentOS 5.3 The default rule, in /etc/udev/rules.d/50-udev.rules has the line: KERNEL=="tty[A-Z]*", NAME="%k", GROUP="uucp", MODE="0660" and I would like the mode to be 0666 Various docs on web say that you

Hi, I would like to change permissions of /dev/sda* and /dev/hda* files to 0644. I added the following rules to 99-udev.rules files: KERNEL=="[hs]d*", OWNER="root" GROUP="disk", MODE="0644 After restarting udev by strat_udev, I checked that permissions were changed: [root at gini rules.d]# ll /dev/sda* brw-r--r-- 1 root disk 8, 0 Sep 2 2009 /dev/sda

Hi Pawel, 2011/7/26 Pawel Sikora <pluto at agmk.net> > On Tuesday 26 of July 2011 14:33:15 you wrote: > > Hi Pawel, > > > > 2011/7/26 Pawel Sikora <pluto at agmk.net> > > > > > Hi, > > > > > > i have an orvaldi ups > > > http://en.orvaldi.com/index.php/en/product_catalog/product_view/11/162 > > > and it works

Does anyone else have any thoughts on automatically installing the udev rules file to avoid all of the "can't find UPS" errors? If we make this a ./configure parameter, we can check for the existence of the udev binary, and allow customization of the rule file name (for adjusting the number prefix). I still think it can't hurt to expand the USB driver error messages a bit (if

Hi, Has anyone written a SPEC file for zaptel, with kernel 2.6 and udev support? I can find some spec files here and there, but from what I can see they're all kernel 2.4 / non udev... -- Andreas Sikkema bbned NV Van Vollenhovenstraat 3 3016 BE Rotterdam t: +31 (0)10 2245544 f: +31 (0)10 413 65 45

I am migrating from Fedora 8 to CentOS 5.2 I have usb dvd On F8 I have /etc/udev/rules/00-my-custom.rules BUS=="scsi", SYSFS{vendor}=="TSSTcorp", SYSFS{model}=="CDDVDW SH-S203N ",SYMLINK="dvd",OWNER="rray" When I plug in dvd I get $ ll /dev/scd1 lrwxrwxrwx 1 root root 3 Aug 25 08:17 /dev/scd1 -> sr1 ll /dev/sr1 brw-r----- 1 rray disk 11, 1

Hi, I tried the patch recently added to support 5G ups by APC. Connecting to the ups failed because of wrong permissions of the usb device node. I had to add the new usb id to the udev rules to make it work. I attached my patch to this mail. Please consider applying. Thanks. Kind regards, Gerd -- Address (better: trap) for people I really don't want to get mail from: jonas at

Il 07/08/2014 15:09, Amit Shah ha scritto: > +udevrules_DATA = 90-virtio-rng.rules If rng-tools is packaged with "make dist" you need this to be dist_udevrules_DATA = 90-virtio-rng.rules or alternatively EXTRA_DIST = 90-virtio-rng.rules udevrules_DATA = 90-virtio-rng.rules > +AC_ARG_WITH([udevrulesdir], > + AS_HELP_STRING([--with-udevrulesdir=DIR], [Directory for udev

Il 07/08/2014 15:09, Amit Shah ha scritto: > +udevrules_DATA = 90-virtio-rng.rules If rng-tools is packaged with "make dist" you need this to be dist_udevrules_DATA = 90-virtio-rng.rules or alternatively EXTRA_DIST = 90-virtio-rng.rules udevrules_DATA = 90-virtio-rng.rules > +AC_ARG_WITH([udevrulesdir], > + AS_HELP_STRING([--with-udevrulesdir=DIR], [Directory for udev

Hi, I am sorry if this message has been reposted, but for some reason I am having problems with posting it. I configured asterisk and zaptel modules with fedora2. I want to be able to load the zaptel wcfxo and wcfxs modules. For now I will use only the Wildcard TDM400P card. I am able to load the modules but I cant configure them using ztcfg or zttool because the tools are compiled to use the

I have a third party application that I want to run a CentOS4 box that is expecting to access the generic SCSI devices through /dev/sga, /dev/sgb, etc. However, the devices set up by udev are /dev/sg0, /dev/sg1 etc. Does anyone know what syntax I could use to create a udev rule that creates symlinks sga -> sg0 etc. for each sg[0-N] device? Thanks James Pearson

Hi, I have a UPS device that seems to work fine with the blazer_usb driver. (I have guessed the driver by googling up the "Product" usb string 010937). However, it does not appear in the supported list, and I had to manually add a udev rule for granting access to the 'nut' user. Would be nice if the info I provide below could be used to help the project/future users to

G'day, all! It's my second trouble with NUT. Latest nut-2.6.1.tar.gz installed from source on Xenserver 5.6 SP2, UPS is Powercom WOW--500U FW3.A4 (USB). Problem with setting permissions for udev (described in /etc/udev/rules.d/52-nut-usbups.rules file): ACTION!="add|change", GOTO="nut-usbups_rules_end" don't work for me. Only when I changed ACTION to:

Thought I would write some notes about how I got an APC BackUPS XS 1500 working with newhidups under Gentoo 2006.0. The specific issue here is the permissions on the device files used that libusb uses to access the USB hardware. I followed Peter Selinger's instructions at http://www.mscs.dal.ca/~selinger/ups/backups.html on getting newhidups going with an APC device. The sticking point for

Hi I have had a Centos 5 installed with asterisk and zaptel for a couple of weeks, I had to reboot eh machine today, and when it rebooted it got stuck at "Starting udev" if I remove thew tdm400 it boots OK, but no zaptel has anyone seen this , and can offer any advice? Thanks Robb