similar to: squeeze, Xen and udev

Hi. I'm using nut with debian squeeze. When the computer boots and nut is loaded, I get the following messages: "Starting the hotplug events dispatcher: udevdudevd [451]: BUS= will be removed in a future udev version. please use SUBSYSTEM= to match the event device. or SUBSYSTEMS= to match a parent device. in /lib/udev/rules.d/52-nut-usb.rules:6 . Synthesizing the initial hotplug

I have a Centos 5 machine which I've just compiled the 3.10.4 kernel on (remembering to set CONFIG_SYSFS_DEPRECATED) because I needed new rtlwifi drivers for my rtl8192cu device. So far, so good. It seems to work. Except /proc/bus/usb doesn't exist anymore. USB_DEVICEFS has been removed. An older kernel (3.2.9) says Usbfs entries are files and not character devices; usbfs

Package: udev Severity: important X-Debbugs-CC: pkg-xen-devel@lists.alioth.debian.org Hello! When installing the udev package in a Xen domU, ``strange'' things happen. The following is a bit of guesswork, some hard facts are probably missing, but I hope that the udev and / or Xen maintainers can make some sense out of it. I'm for now happy with having a usable Xen server again...

Hello list. My server: Gentoo 2.6.21-xen dom0 xen-tools 3.2.1 lvm 2.02.28-r2 udev-115-r1 Symptoms: normally I run 4 domUs. About once a week I have a need to restart a domU. Sometimes it works just fine, but other times it does not and I''ll get a message back saying "Error: Device 0 (vif) could not be connected. Hotplug scripts not working". The domU config file has not

Hi, I got a centos guest started on fc6 finally by creating the mkinitrd by hand. But the thing is centos seem to hang after the services are started properly and just before the login prompt. I also notice that ''udev'' is failing at the beginning, which could be why mingetty hangs. I am guessing that udev is the service that creates the necessary ttys. So is there something I

I am running a Debian Squeeze Xen 4.0.1 Hypervisor and 2.6.32-5-xen-amd64 dom0. My xen-tools.conf: lvm = vg00 size = 100Gb # Disk image size. memory = 2048Mb # Memory size swap = 2G # Swap size # noswap = 1 # Don''t use swap at all for the new system. fs = ext4 # use the EXT3 filesystem for the disk image. dist = `xt-guess-suite-and-mirror --suite` # Default

Hello, Not sure this is the right place to ask Xen user-questions. I am running Lenny and try to upgrade a domU to Squeeze. After the installation of a new xen-kernel in the domU and upgrading udev I did a reboot but then the kernel does not find the root anymore, and it's dropping me to a shell. When I look into /dev/ I don't see any disks or partions. Is here somebody who can help me

After a reboot, I can't reproduce the problem anymore which is quite frustating. 2011/6/14 Tzafrir Cohen <tzafrir.cohen at xorcom.com> > On Tue, Jun 14, 2011 at 03:44:32PM +0200, Olivier wrote: > > Hi, > > > > I'm using a two-years old installation script for the first time on a > > Squeeze (linux 2.6.32) platform. > > For an unknown reason (might

Hello, The current dependancy on hotplug|udev (>= 0.59) seems bad. As far as I remember, last week, when I tried to install Ralph packages, I got an error from hotplug/udev and I had to use udev from backports.org Anyone know which version of udev/hotplug we will have to depends on ? Maybe we could simply rely on a recent udev dependancy, because afaik udev now provides hotplug. -- Julien

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

In case people here don't follow the udev mailing list, udev seems to be quasi-dropping klibc support. Well, see the forwarded message below. As I don't agree with the "omg udev is complex! use glibc!" rationale, I want klibc and udev to remain working with each other.... Assuming some minor breakage in the near future, is klibc open to accepting patches for "basic C

> Added: > trunk/scripts/hotplug/Makefile.am > trunk/scripts/udev/Makefile.am > Modified: > trunk/ChangeLog > trunk/Makefile.am > trunk/configure.in > trunk/docs/configure.txt > trunk/scripts/Makefile.am > trunk/scripts/hotplug/ (props changed) > trunk/scripts/udev/ (props changed) > trunk/scripts/udev/README > Log: > -

I've been testing * on FC3. I have everything compiled and installed. However, when I do 'modprobe wcfxo' (I have an X100P clone), I get the following in /var/log/messages: Nov 24 10:23:40 jfd wait_for_sysfs[3366]: either wait_for_sysfs (udev 039) needs an update to handle the device '/class/zaptel/zaptimer' properly (no device symlink) or the sysfs-support of your

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 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

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

Hi all I recently setup a CentOS 5.2 server, running XEN (using HyperVM), and then moved the hard drive from my test box to my Intel server.The problem I now have, is that it doesn't bootup properly. Shortly after I see the udev service started, the machine reboots. This keeps on going the whole time. I have managed to kill udev on start-up (with CTRL + C), and then it boots up. So, do I

salut Jean-Luc, 2005/10/9, Jean-Luc Coulon (f5ibh) <jean-luc.coulon@wanadoo.fr>: > > Package: nut-usb > Version: 2.0.2-1 > Severity: normal > > Hi, > > The latest version of udev: 0.070-3 conficts with hotplug. > This means that while the new udev includes the hotplug functionalities, > the rules in /etc/hotplug/usb/libhidups and /etc/hotplug/usb/libhid.usermap

Hi all, Here's a brief history of my adventure: I purchased a CyberPower 685 AVR and decided to connect it through USB to my Gentoo linux machine running kernel 2.6.22. While the device was detected properly and added to /dev, it was added with the wrong permissions (gid was set to 'usb' instead of 'nut', as it was expected to be according to the rules under

Hi all, CentOS 5.2, not yet updated to 5.3. Based on the alert on udev, I attempted to update udev and libvolume packages with the following result. A check of what's currently on the system reveals udev-095-14.19.el5 which I believe to be the affected version. Is it just that it hasn't rolled out to all the mirrors yet? Thanks in advance, -Ray [root at wh01]# yum clean all