Re: Kubuntu's udev broken with 2.6.18-rc2-mm1

From: Laurent Riffard
Date: Mon Jul 31 2006 - 04:08:06 EST

Le 31.07.2006 05:37, Greg KH a écrit :
> On Sun, Jul 30, 2006 at 10:27:06PM -0400, Andrew James Wade wrote:
>> On Sunday 30 July 2006 20:03, Greg KH wrote:
>>> Something's really broken with that version of udev then, because the
>>> 094 version I have running here works just fine with these symlinks.
>> Maybe, but some really odd things were happening in /sys with the
>> patch. I could still follow the bogus symlinks. More than that
>> /sys/class/mem/mem$ cd ../../class
>> and
>> /sys/class/mem/mem$ cd ../..
>> _both_ ended up with a $PWD of /sys/class.
> Ick, ok, the problem is that my "virtual device" patch isn't in my
> "public" patch set that Andrew pulls from. It will fix this issue up.
> I'll work on cleaning it up to be used by everyone tomorrow and move it
> to the tree that Andrew pulls from. Then the next -mm release should
> have this issue fixed.
> If you want to verify this, please apply the patch at:
> and let me know if it solves your issue (note that the reference
> counting is not completly correct in that patch, that's why I haven't
> unleashed it on -mm yet.)

device-virtual.patch won't apply on top of 2.6.18-rc2-mm1:

linux-2.6-mm$ head -4 Makefile

linux-2.6-mm$ quilt pop -a
Aucun patch retiré

linux-2.6-mm$ quilt push
Application de patches/device-virtual.patch
patching file drivers/base/Makefile
patching file drivers/base/base.h
Hunk #1 succeeded at 44 (offset 1 line).
patching file drivers/base/core.c
Hunk #1 succeeded at 434 (offset 60 lines).
Hunk #2 FAILED at 486.
Hunk #3 succeeded at 615 (offset 61 lines).
1 out of 3 hunks FAILED -- rejects in file drivers/base/core.c
patching file drivers/base/virtual.c
patching file include/linux/device.h
Hunk #1 succeeded at 356 (offset 5 lines).
Le patch patches/device-virtual.patch ne s'applique pas proprement
(forcez l'application avec -f)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at