Re: Idea: Rename package `udev` to `systemd-udev`, plus new `udev` metapackage, to "preserve freedom of choice of init systems".

On 02/11/14 01:37, Martinx - ジェームズ wrote: Thoughts?! As I understand it, eudev is intended to provide all of udev's externally-visible functionality in an interface-compatible way, so it seems to me that whoever packages eudev should *probably* be able to declare it to be an adequate replace

Re: Idea: Rename package `udev` to `systemd-udev`, plus new `udev` metapackage, to "preserve freedom of choice of init systems".

On Sb, 01 nov 14, 23:37:32, Martinx - ジェームズ wrote: > > I'm thinking here about the future of `udev` and alt-init systems > (systemd-sysv | sysvinit-core | upstart)... > > Apparently, `udev` will stop working without systemd = PID1 (am I > right?), [citation needed] Kind regards, Andrei -- htt

Idea: Rename package `udev` to `systemd-udev`, plus new `udev` metapackage, to "preserve freedom of choice of init systems".

Guys, I'm thinking here about the future of `udev` and alt-init systems (systemd-sysv | sysvinit-core | upstart)... Apparently, `udev` will stop working without systemd = PID1 (am I right?), so, to keep Debian working with `sysvinit-core` and others (probably, I think), we'll need a

Re: Re (2): new udev

On 12/16/2009 2:52 PM, Tom H wrote: And yet the udev maintainer's response to the 'CONFIG_SYSFS_DEPRECATED" syslog message is "So do it." http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560821 I assume that if you are using "testing", you have to be prepared for problems and to make system chan

Re: Re (2): new udev

>> Some of the .rules files on your system are using >> a deprecated syntax, ... > The message in syslog has a rather obscure way of > putting that. Can't a syslog message be as direct > as Brian has stated it? >> ... and also your kernel isn't configured to udev's liking. > Non-obvious details,

Re: Re (2): new udev

hey are -- so why should I be expected to modify them? Maybe these rules will be updated automatically when I next reboot -- hence my question. /etc/udev/rules.d/z60_libchipcard-tools.rules is presumably created by the libchipcard-tools package, so I'd expect updates to that package to

Re: Re (2): new udev

d to modify them? Maybe these rules will be updated automatically when I next reboot -- hence my question. If the new udev package requires a particular version of the kernel then *that* should be pointed out. At minimum there should be something in apt-listmessages. -- "I'm so optim

Re (2): new udev

Folk, Observations from bystander. Date: Tue, 15 Dec 2009 16:21:28 -0500 Brian Nelson wrote, > Some of the .rules files on your system are using > a deprecated syntax, ... The message in syslog has a rather obscure way of putting that. Can't a syslog message be as direct as Brian has sta

Re: new udev

On 12/14/2009 10:16 AM, Rick Pasotto wrote: The udev module in testing got updated this morning. As a result I got these lines in my syslog: Dec 14 09:51:02 niof udevd[15399]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the eventdevice, or ATTRS{}= to match a

new udev

The udev module in testing got updated this morning. As a result I got these lines in my syslog: Dec 14 09:51:02 niof udevd[15399]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the eventdevice, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/z60_libch

"Issue(s?) with the new udev

Yesterday I upgraded to the latest udev (udev_0.100-1_i386.deb), and found at least one problem: tpb (ThinkPad buttons) would not run because of /dev/nvram not being reachable. I downgraded to udev_0.098-2_i386.deb, and the problem went away. I confess, configuring udev still occasionally mystefie

RESOLVED: Re: New UDEV breaks my rules

Mathias Brodala wrote: Hi Andrew. At some point I upgraded UDEV, and the following rule broke: BUS="usb", SYSFS{product}="Griffin PowerMate", NAME="powermate", SYMLINK="input/powermate", GROUP="audio", MODE="0660" […] What am I doing wrong? For the lazy, here is my new, "fixed

Re: New UDEV breaks my rules

Hi Andrew. >>> At some point I upgraded UDEV, and the following rule broke: >>> >>> BUS="usb", SYSFS{product}="Griffin PowerMate", NAME="powermate", >>> SYMLINK="input/powermate", GROUP="audio", MODE="0660" >>> >>> […] >>> >>> What am I doing wrong? >> You should correct the syntax corresponding

Re: New UDEV breaks my rules

> Hi Jason. > > > At some point I upgraded UDEV, and the following rule broke: > > > > BUS="usb", SYSFS{product}="Griffin PowerMate", NAME="powermate", > > SYMLINK="input/powermate", GROUP="audio", MODE="0660" > > > > It gives this error message: Jul 21 11:26:37 localhost udevd[8581]: > > add_t

Re: New UDEV breaks my rules

Hi Jason. > At some point I upgraded UDEV, and the following rule broke: > > BUS="usb", SYSFS{product}="Griffin PowerMate", NAME="powermate", > SYMLINK="input/powermate", GROUP="audio", MODE="0660" > > It gives this error message: Jul 21 11:26:37 localhost udevd[8581]: > add_to_rules: invalid B

New UDEV breaks my rules

At some point I upgraded UDEV, and the following rule broke: BUS="usb", SYSFS{product}="Griffin PowerMate", NAME="powermate", SYMLINK="input/powermate", GROUP="audio", MODE="0660" It gives this error message: Jul 21 11:26:37 localhost udevd[8581]: add_to_rules: invalid BUS operation Jul 21 11:

New udev breaks hotplug ?

in/hotplug by typing: cat /proc/sys/kernel/hotplug -> /sbin/udevsend So I set manually the /sbin/hotplug to be the hotplug handler and things work again as before. -- So, what is wrong? Is it a bug in the new udev package?