On Sun, Jan 08, 2006 at 07:21:35PM +0100, Marco d'Itri wrote:
> Any comments?
> Subject: Bug#346543: udev netlink problems with kernel 2.6.15 on alpha
> To: [EMAIL PROTECTED]
> From: Uwe Schindler <[EMAIL PROTECTED]>
>
> I installed linux-image-2.6.15-1 (2.6.15-2) from Norbert on my alpha
> mach
On Mon, Jan 09, 2006 at 09:02:22AM +0100, Uwe Schindler wrote:
> At 02:00 09.01.2006, Kay Sievers wrote:
> >On Sun, Jan 08, 2006 at 07:21:35PM +0100, Marco d'Itri wrote:
> >> Any comments?
> >
> >> Subject: Bug#346543: udev netlink problems with kernel 2.6
On Thu, Aug 25, 2005 at 07:47:56PM +0200, Marco d'Itri wrote:
> An interesting comment.
> Subject: Bug#317333: acknowledged by developer (Bug#317333: fixed in udev
> 0.063-1)
> From: Mourad De Clerck <[EMAIL PROTECTED]>
> To: Marco d'Itri <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> On Thu, 200
On Wed, Sep 21, 2005 at 03:38:06AM +0100, Scott James Remnant wrote:
> Background: in the upcoming Ubuntu 5.10 we've been having some problems
> with /dev/input/mice not being created on startup despite the "mousedev"
> module being hard-loaded early in the boot sequence.
> (http://bugzilla.ubuntu.
On Tue, Sep 20, 2005 at 11:28:17PM +0200, Marco d'Itri wrote:
> FYI. It's unreproducible even by the submitter.
That's one of the problems with a synchronous udevstart. It should go
away for a lot of other reasons too and I refused all the "coldplug"
patches for udevstart for that reason.
I expect
On Sat, Sep 24, 2005 at 01:29:34AM +0200, Marco d'Itri wrote:
> On Sep 18, Kay Sievers <[EMAIL PROTECTED]> wrote:
>
> > The kernel event buffer is smaller than the udevsend buffer. I expect
> > udevsend is not called from the kernel. What's in /proc/sys/kernel/
Applied to the upstream udev tree.
Thanks,
Kay
On Wed, 2006-12-06 at 16:17 +0900, Kazuhiro Inaoka wrote:
> Please apply a patch to fix inotify syscalls on M32R.
> --- udev-0.103/udev_sysdeps.h.org 2006-12-06 05:29:31.503967152 +
> +++ udev-0.103/udev_sysdeps.h 2006-12-06 05:30:02.50213984
On 11/25/06, Frans Pop <[EMAIL PROTECTED]> wrote:
In Debian we are currently seeing some problems with drivers that are
repeatedly loaded unsuccessfully:
kernel: Intel ISA PCIC probe: not found.
FATAL: Error inserting i82365: no such device
kernel: Intel ISA PCIC probe: not found.
[...]
Accordin
On Tue, 2006-11-28 at 08:12 +0100, Bastian Blank wrote:
> On Mon, Nov 27, 2006 at 03:45:36PM +0100, Kay Sievers wrote:
> >For now you can just
> > blacklist all platform events like Marco already suggested.
>
> Nope. modprobe don
On Sun, 2006-10-29 at 00:10 +0200, Brice Goglin wrote:
> Kay Sievers wrote:
> > This is just for testing, if that works, we may need to fix the
> > kernel to create the bus-device driver link at the proper time
> > to be catched by DRIVERS==.
>
> Just wondering whether
On Sun, 2006-10-29 at 23:28 +0100, Brice Goglin wrote:
> reassign 389250 linux-2.6
> thanks
> Kay Sievers wrote:
> > On Sun, 2006-10-29 at 00:10 +0200, Brice Goglin wrote:
> >
> >> Kay Sievers wrote:
> >>
> >>> This is just for testing,
On Thu, 2006-11-16 at 12:33 +0100, Torsten Crass wrote:
> > It's probably you, since DVB devices work fine for me and apparently
> > everybody else.
>
> perhaps you and everybody else is accessing DVB devices via loadable
> modules, while I'm using a rather monolithic kernel with the drivers
> c
On Tue, 2005-02-08 at 21:53 -0800, Greg KH wrote:
>On Wed, Feb 09, 2005 at 03:24:31AM +0100, Kay Sievers wrote:
>> Can't you match against some interface attributes in sysfs, which are
>> telling you which one is the first interface of this device?
>>
>> You m
On Mon, 2005-02-14 at 09:30 -0800, Greg KH wrote:
>On Sun, Feb 13, 2005 at 04:14:41AM +0100, Kay Sievers wrote:
>> On Tue, 2005-02-08 at 21:53 -0800, Greg KH wrote:
>> >On Wed, Feb 09, 2005 at 03:24:31AM +0100, Kay Sievers wrote:
>> >> Can't you match against
.4.5.tar.gz
> >
> > Changes from 0.4.4:
> >
> > - Fix bug with vfat label reading (Kay Sievers, Fredrik Nilsson, Joeny)
>
> This seems to have fixed some filesystems and broken others. I got the
> following from a debian user:
>
> I just upgraded hal (from 0.4.4-
On Sun, 2005-01-16 at 18:36 +0100, David Eriksson wrote:
> On Sun, 2005-01-16 at 18:17 +0100, Kay Sievers wrote:
> > On Sun, 2005-01-16 at 18:08 +0100, Sjoerd Simons wrote:
> > >
> > > Both mlabel and udev_volume_id show the correct label ("ICYBOX"), but
&
On Tue, 2005-03-08 at 00:03 +0100, Marco d'Itri wrote:
> This rule causes udevstart 054 to segfault:
>
> BUS="pci", SUBSYSTEM="net", DRIVER="ipw2100", NAME="wlan"
>
> - Forwarded message from Thomas Breitner <[EMAIL PROTECTED]> -
>
> Subject: Bug#298192: udev: segfault with new rule on s
On Tue, 2005-03-01 at 21:26 +0100, Marco d'Itri wrote:
>reassign 297481 kernel-image-2.6.8-i386
>thanks
>
>On Mar 01, Kay Sievers <[EMAIL PROTECTED]> wrote:
>
>> This kernel will not work correctly with managed events. It has holes in
>> the sequence numbers.
> The problem lies within /dev/disk/by-id. Even though the card reader
> has four slots, it only has one serial number, so only one link is
> created in /dev/disk/by-id. It's called
> usb-Generic_STORAGE_DEVICE_05170 and it points to one of
> /dev/sd[abcd], not always the same one. I suppose
On Sat, 2007-03-03 at 17:59 +0100, Kay Sievers wrote:
> > The problem lies within /dev/disk/by-id. Even though the card reader
> > has four slots, it only has one serial number, so only one link is
> > created in /dev/disk/by-id. It's called
> > usb-Generic_STORAGE_D
On Wed, 2007-03-21 at 18:43 +0200, Guillem Jover wrote:
> The current .pc file has a wrong libdir (/lib), it should be /usr/lib
> as there is where the .so file is located. This makes pkg-config to
> not trim the -L argument which is problematic at least on sbox.
What do you mean? The .so file is
> I was willing to use /dev/disk/by-path/ devices with an iSCSI setup when
> I figured out not all devices were available by path. I discovered that
> it was because my iSCSI target provided several LUNs, which are not
> reflected by path_id.
>
> The attached patch solves the problem by appending
On Thu, 2006-08-17 at 22:46 -0700, Andrew Pimlott wrote:
> I suspect I have a similar problem to the reporter of this bug. I have
> a swap partition that is set up as an encrypted dm device with a random
> key, using the cryptsetup package. cryptsetup now has a test that calls
> vol_id, which thi
On Fri, 2006-08-18 at 08:59 -0700, Andrew Pimlott wrote:
> On Fri, Aug 18, 2006 at 02:13:53PM +0200, Kay Sievers wrote:
> > It's almost impossible to make libvolume_id stricter, in most cases,
> > even the kernel mounts a mkswap formatted (and obviously corrupt) fat
> > v
On Thu, 2006-10-12 at 13:26 +0200, Jö Fahlke wrote:
> Package: udev
> Version: 0.100-2
> Severity: normal
> Tags: patch
>
> My Epson scanner is not assigned to group "scanner" when I switch it
> on and scan the SCSI bus. This is because it identifies itself as
> type 3 (processor) and vendor "EP
On Wed, 2006-09-27 at 12:45 +0200, Marco d'Itri wrote:
> On Sep 27, Brice Goglin <[EMAIL PROTECTED]> wrote:
>
> > >> # PCI device 0x8086:0x4220 (ipw2200)
> > >> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:12:f0:12:05:03",
> > >> NAME="wifi"
> > >>
> > > Try replacing DRIVERS== with
On Thu, 2006-09-28 at 16:40 +0800, Dan Jacobson wrote:
> X-debbugs-cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
> Package: udev
> Version: 0.100-1
> Severity: normal
> File: /usr/share/doc/udev/writing_udev_rules/index.html
>
> Regarding
>
> USB Card Reader
>
> These dev
On Mon, 2006-08-14 at 19:43 +0100, Tim Phipps wrote:
> Package: udev
> Version: 0.093-1
> Severity: normal
>
> Feel free to change this to minor or wishlist. I'd like vol_id to not
> change the case of FAT partitions labels. I don't believe this will affect
> many people since FAT partitions are u
On Tue, 2006-08-15 at 10:08 -0500, Matt Zagrabelny wrote:
> Package: udev
> Version: 0.093-1
> Severity: minor
>
>
> typo in /usr/share/man/man7/udev.7.gz
>
> 'Asign' should be 'Assign'
Fixed.
Thanks,
Kay
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troubl
On Fri, Dec 13, 2013 at 12:12 AM, Andreas Cadhalpun
wrote:
> On 12.12.2013 23:19, Kay Sievers wrote:
>> On Thu, Dec 12, 2013 at 10:58 PM, Michael Biebl
>> wrote:
>>> This was removed upstream [1] and is highly unlikely to be added back.
>>> Especially conside
On Fri, Dec 13, 2013 at 12:26 AM, Michael Biebl wrote:
> Am 13.12.2013 00:12, schrieb Andreas Cadhalpun:
>> The Debian installer needs a way to load the firmware during
>> installation, otherwise the netinst.iso is pretty useless for WLAN
>> devices with non-free firmware.
>> Since a majority of t
On Fri, Dec 13, 2013 at 12:34 AM, Michael Biebl wrote:
> Am 13.12.2013 00:26, schrieb Michael Biebl:
>> Am 13.12.2013 00:12, schrieb Andreas Cadhalpun:
>>> The Debian installer needs a way to load the firmware during
>>> installation, otherwise the netinst.iso is pretty useless for WLAN
>>> device
On Fri, Dec 13, 2013 at 12:42 AM, Michael Biebl wrote:
> Am 13.12.2013 00:34, schrieb Michael Biebl:
> See also
> http://lists.freedesktop.org/archives/systemd-devel/2013-November/014771.html
>
> But that thread just echoes what Kay already said, that user-space
> firmware loading is deprecated a
On Fri, Dec 13, 2013 at 4:29 AM, Ben Hutchings wrote:
> On Fri, 2013-12-13 at 00:28 +0100, Kay Sievers wrote:
> [...]
>> >> Such an explicit message would probably use printk_emit() and pass
>> >> structured data with the filename and the ides from the kernel to
&
On Sat, Dec 14, 2013 at 11:19 PM, Shawn Landden wrote:
> It would be nice if systemd could implement the service supervisor
> side of the service readiness protocol that upstart calls "expect
> stop":
>
> The service doesn't fork, and when considers itself ready it raises
> SIGSTOP. The supervis
On Fri, Apr 25, 2014 at 3:51 PM, Julian Andres Klode wrote:
> I received the following bug report in Debian about
> gummiboot.
>
> On Sun, Apr 20, 2014 at 10:04:23AM +0200, Philipp Kern wrote:
>> Package: gummiboot
>> Version: 44-1
>> Severity: important
>>
>> gummiboot fails to install if there i
On Fri, Apr 25, 2014 at 7:10 PM, Julian Andres Klode wrote:
> On Fri, Apr 25, 2014 at 06:43:07PM +0200, Kay Sievers wrote:
>> On Fri, Apr 25, 2014 at 3:51 PM, Julian Andres Klode wrote:
>> > I received the following bug report in Debian about
>> > gummiboot.
>>
On Fri, Apr 25, 2014 at 8:25 PM, Julian Andres Klode wrote:
> The Debian kernels are configured
> CONFIG_FAT_DEFAULT_IOCHARSET="utf8"
> which causes iocharset=utf8 to be the default here, rather than
> iocharset=ascii. I can now
> either work around that in the gummiboot package by one of
>
> (1
On Thu, Aug 14, 2014 at 9:01 PM, Kay Sievers wrote:
> On Thu, Aug 14, 2014 at 3:07 PM, Simon McVittie
> wrote:
>> I recently opened this Debian bug, for which I attach a
>> patch that seems to work. Bug report quoted in full below.
>>
>> I would appreciate udev ma
On Thu, Jul 10, 2014 at 10:55 PM, Michael Biebl wrote:
> Am 10.07.2014 22:02, schrieb Peter Poeschl:
>> Package: udev
>> Version: 204-14
>> Severity: important
>>
>> Dear Maintainer,
>>
>>* What led up to the situation?
>> udev upgrade from 204-8 to 204-14 removed the file /etc/udev/links.conf
On Fri, Jul 11, 2014 at 1:35 PM, Michael Biebl wrote:
> Am 11.07.2014 05:01, schrieb Kay Sievers:
>> The logic in util-linux, libmount, losetup, ... tries to access
>> /dev/loop-control which will block and trigger a kernel-side module
>> auto-load.
>>
>> All tha
On Tue, May 12, 2015 at 2:01 PM, Julian Andres Klode wrote:
> Control: forwarded -1 k...@vrfy.org
>
> (Adding Kay Sievers & Harald Hoyer from upstream)
>
> On Mon, Aug 25, 2014 at 09:10:48PM +0200, Michael Tautschnig wrote:
>> Package: gummiboot
>> Version: 45-2
&
On Thu, Aug 14, 2014 at 3:07 PM, Simon McVittie
wrote:
> I recently opened this Debian bug, for which I attach a
> patch that seems to work. Bug report quoted in full below.
>
> I would appreciate udev maintainers' opinions on whether this is
> likely to break non-USB devices, or whether there is
On Tue, 2006-07-04 at 19:35 +0200, Marco d'Itri wrote:
> On Jul 04, Andreas Beckmann <[EMAIL PROTECTED]> wrote:
>
> > # ignore interfaces without a driver link
> > DRIVER!="?*", GOTO="persistent_net_generator_end"
> >
> > If I comment out this line, z25_persistent-net.rules is generated on
> > bo
On Wed, 2006-07-05 at 14:51 +0200, Andreas Beckmann wrote:
> I switched testing to another machine that can be rebooted more easily.
> It has only one (onboard) network interface:
> # PCI device 10ec:8139 (8139too)
>
> Kay Sievers wrote:
> ...
> > Care to provide:
> &g
> I've found that the problem appears to be related to vol_id failing to
> find proper information for my root device, /dev/sda1. I've run the
> commands 'e2label', '/lib/udev/vol_id', 'mount' and 'fdisk' with the
> following results:
Never use any of the all broken mkfs* tools without writing ze
On Wed, Jul 19, 2006 at 12:16:54PM +0200, Marco d'Itri wrote:
> Is this correct?
>
> - Forwarded message from [EMAIL PROTECTED] -
>
> From: [EMAIL PROTECTED]
> To: Debian Bug Tracking System <[EMAIL PROTECTED]>
> Subject: bluez-pcmcia-support: udev support broken
>
> Package: bluez-pcmci
On Tue, 2006-07-25 at 12:52 +0200, Felix Homann wrote:
> On Tuesday 25 July 2006 11:12, Filippo Giunchedi wrote:
> > what about the change from DEVPATH to PHYSDEVPATH Felix proposed in
> > bluetooth.sh?
>
> Hi again,
>
> MANFID=`cat /sys/$PHYSDEVPATH/manf_id`","`cat /sys/$PHYSDEVPATH/card_id`
>
On Tue, 2006-07-25 at 15:43 +0200, Felix Homann wrote:
> On Tuesday 25 July 2006 13:18, Kay Sievers wrote:
> > PHYSDEVPATH and the 'device' link are both deprecated and will go away
> > some day in the future, you better pass the values you want to use in
> > your sc
On Mon, Apr 27, 2009 at 00:31, Phil Endecott
wrote:
> So protocol==0 is not specific to this unusual device; even a keyboard or
> mouse will have 0 for its non-boot interfaces. So the current logic will
> only create /dev/by-id|path nodes for boot interfaces. Is that intentional?
These links go
On Mon, Apr 27, 2009 at 01:47, Phil Endecott
wrote:
> Kay Sievers wrote:
>> These links got added to distinguish multiple keyboards on
>> mainframe-like servers, that's why the rules have been so strict so
>> far, and cover only "real" input devices. :)
On Mon, Apr 27, 2009 at 02:36, Kay Sievers wrote:
>> Bus 001 Device 009: ID 077d:0410 Griffin Technology PowerMate
>
> The device also does not tell us anything interesting.
>
> Does the input subsystem tell us anything specific we might want to
> use to classify the devic
On Sun, Apr 26, 2009 at 21:54, Marco d'Itri wrote:
> Is this reasonable?
> With udev 0.140 (or rather: sometime after 0.125) we've lost the
> persistent device symlink /dev/input/by-path/platform-gpio-keys-event-
> due to the following change in 60-persistent-input.rules which no longer
> allows
It's consistent in all udev programs. Only long-options are supported
today. The short options are for convenience, or for compatibility to
old releases only.
Thanks,
Kay
> Package: udev
> Version: 0.105-4
> Severity: minor
> File: /usr/bin/udevinfo
>
> udevinfo accepts some short options that a
On Tue, 2008-01-08 at 18:17 +, Neil Williams wrote:
> When cross building packages depending on libvolume-id, pkgconfig fails
> to parse the pc file generated by udev because the exec_prefix value is
> not defined:
>
> $ pkg-config /usr/arm-linux-gnu/lib/pkgconfig/libvolume_id.pc --libs
> libv
On Tue, Jan 17, 2006 at 09:42:57PM +0100, Marco d'Itri wrote:
> On Jan 17, Kay Sievers <[EMAIL PROTECTED]> wrote:
>
> > That driver seem to bypass the kernel driver core. If that's the case
> > the driver needs to be fixed as udevd depends on proper MAJOR/MINOR
On Tue, Jan 17, 2006 at 09:50:21PM +0100, Kay Sievers wrote:
> On Tue, Jan 17, 2006 at 09:42:57PM +0100, Marco d'Itri wrote:
> > On Jan 17, Kay Sievers <[EMAIL PROTECTED]> wrote:
> >
> > > That driver seem to bypass the kernel driver core. If that's the ca
On Thu, Jan 19, 2006 at 03:24:05PM +0100, Marco d'Itri wrote:
> The boot procedure stop after some times at parport without creating devices
> (eg ttyS0 and others).
> The udev 0.080-1 had same behaviour. Previous versions to 0.080 where
> working. On the console I see:
>
> udevd [811]: udev_don
On Mon, Jan 30, 2006 at 10:51:10PM +0100, Marco d'Itri wrote:
> small typo in the manpage:
>GOTO Jumps to the next LABEL with a matching gname
> should read
>GOTO Jumps to the next LABEL with a matching name
Fixed.
Thanks,
Kay
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
On Fri, Feb 03, 2006 at 12:32:40PM +0100, Marc Haber wrote:
> On Wed, Feb 01, 2006 at 10:52:25AM +0100, Marco d'Itri wrote:
> > On Feb 01, Marc Haber <[EMAIL PROTECTED]> wrote:
> > > On Wed, Feb 01, 2006 at 03:08:42AM +0100, Kay Sievers wrote:
> > >
On Thu, Feb 09, 2006 at 08:25:14PM +0100, Bastian Blank wrote:
> Hi folks
>
> I got the following bugreport against multipath-tools, which by default
> uses scsi_id to detect multiple paths.
>
> scsi_id on SATA devices (via libata) returns a string like:
> | 0ATA_ST3160827AS_Linux_ATA-SCSI_simula
On Sun, Jan 29, 2006 at 12:07:50PM +0100, Marco d'Itri wrote:
> On Jan 29, di dit <[EMAIL PROTECTED]> wrote:
>
> I can see why the rule does not work, at the removable==1 level we have
> BUS=="block" instead of the expected BUS=="ide", and DRIVER is only
> available at the upper level.
> Kay?
Cor
On Sun, Jan 29, 2006 at 12:07:50PM +0100, Marco d'Itri wrote:
> On Jan 29, di dit <[EMAIL PROTECTED]> wrote:
>
> I can see why the rule does not work, at the removable==1 level we have
> BUS=="block" instead of the expected BUS=="ide", and DRIVER is only
> available at the upper level.
> Kay?
>
>
On Wed, Feb 01, 2006 at 12:00:26AM +0100, Sjoerd Simons wrote:
> On Tue, Jan 31, 2006 at 10:54:08PM +0100, Marco d'Itri wrote:
> > On Jan 30, Michael Ott <[EMAIL PROTECTED]> wrote:
> >
> > > I believe that dbus or fam will mount my disk. But my mobile memory will
> > > mount with udev 0.082 and no
> From: Marc Haber <[EMAIL PROTECTED]>
> To: Marco d'Itri <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Cc: Marc Haber <[EMAIL PROTECTED]>
> Subject: Re: Re: Bug#350235: ide pcmcia problem
>
> found 350235 0.84-1
> thanks
>
> On Sat, Jan 28, 2006 at 01:51:39PM +0100, Marco d'Itri wrote:
> > Indeed...
> When booting with an audio CD in the drive, at the stage of udev
> populating /dev/ I see these errors on the screen and also in the
> dmesg output:
> .
> [ 11.216120] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [ 11.216127] sr 3:0:0:0: [sr0] Sense Key : Ille
Yeah, devtmpfs misses the magic '!' -> '/' support. I'll go and fix this.
If you don't want to change the device name, you can fill-in the name
in the miscdevice structure, like:
static struct miscdevice tun_miscdev = {
.minor = TUN_MINOR,
.name = "tun",
.nodename = "net/
I take that back, tested it, devtmpfs works fine with the '!' magic.
The driver core translates the stuff already.
Looks like a different issue then. If you kill udevd, unload the
module, delete the possible remaining node, then load the module
again, what has devtmpfs created?
--
To UNSUBSCRI
On Thu, Mar 18, 2010 at 17:48, Didier 'OdyX' Raboud wrote:
> Hi udev upstreams !
>
> (please keep me and the Debian bug CC'ed).
>
> I am the Debian maintainer for usb-modeswitch and I got a user reporting that
> his 3G dongle was not "switched" anymore [0]. After some investigation, I
> strongly s
On Sun, Apr 18, 2010 at 23:08, Marco d'Itri wrote:
>> On Apr 18, Mario 'BitKoenig' Holbe wrote:
>> > KERNEL=="audio", NAME="%k0", SYMLINK+="%k"
>> Nowadays this is considered bad, accordingly to the upstream maintainer
>> you should not change the kernel name of a devic
On Mon, Apr 19, 2010 at 11:46, Marco d'Itri wrote:
> On Apr 19, Kay Sievers wrote:
>
>> > /lib/udev/rules.d/55-dm.rules
>> Device-mapper is work-in-progress, and probably just uses NAME=""
>> which is ok.
> There is this rule, which is what the ori
On Mon, Apr 19, 2010 at 12:13, Bastian Blank wrote:
> On Mon, Apr 19, 2010 at 11:56:37AM +0200, Kay Sievers wrote:
>> This is not supported and must be fixed. Udev does not support
>> swapping primary device names around, and devtmpfs will always create
>> the device node
On Mon, Apr 19, 2010 at 13:28, Mario 'BitKoenig' Holbe
wrote:
> On Mon, Apr 19, 2010 at 11:39:28AM +0200, Kay Sievers wrote:
>> On Sun, Apr 18, 2010 at 23:08, Marco d'Itri wrote:
>> >> On Apr 18, Mario 'BitKoenig' Holbe wrote:
>
Udev should no longer delete the link it has created:
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=6252f9e732c827defdac38e2eccab0657492d9c9
Still, replacing the default kernel-named nodes with links with the
same name can result in unexpected behavior and is not supported. It
On Tue, 2009-03-03 at 17:57 +0100, Michael Prokop wrote:
> * martin f krafft [20090303 16:01]:
> > also sprach Marco d'Itri [2009.02.16.1622 +0100]:
> > > > udev used to create links like
> > > I remember seeing another bug about this (which should be open), but I
> > > am not inclined to add com
On Wed, Mar 18, 2009 at 10:48, Marco d'Itri wrote:
> From: Phil Endecott
> I have a Griffin Powermate, which is a USB "knob" that can be used as
> e.g. a volume control, for scrolling through video/audio, etc. No
> /dev/input/by-* links are created for it. This is because
> persistent-input.ru
On Mon, Aug 9, 2010 at 08:02, Stanislav Maslovski
wrote:
> On Tue, Aug 03, 2010 at 08:20:03AM +0200, Kay Sievers wrote:
> Thanks for your input. I did what you suggested; the log from runnig
> 'udevadm test /class/block/sr0' is attached to this e-mail. I see lots
> of th
> srv:~# udevadm info
> custom logging function 0x160e010 registered
> selinux=0
> calling: info
> Segmentation fault
This was likely caused by using a va_list twice. This is expected to fix it:
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=d5a01cb8b31bd0791d1617c56d4c669a02018
78 matches
Mail list logo
