On Mon, 26 Jul 2010, Martin Pitt wrote:
> so we can just copy the script and replace "configure" with "remove". Do
> you want to prepare an SRU/debdiff yourself, or want me to do it?
I haven't done one in a while, but I can take a crack at it.
Scott
--
[MASTER] package policykit-1 0.96-1 faile
Scott Talbert [2010-07-19 4:00 -]:
> UDEV [1277516625.070541] remove /devices/virtual/bdi/0:21 (bdi)
Hm, I'm not sure about this. I don't see anything in udev or udisks
which would issue events on bdi devices, and usually they originate
from the kernel. Does this also appear in udevadm mon
> I tried that on lucid (install devicekit-disks, devkit-disks --dump,
> purge, and trigger), and /proc and /sys are still fine. How exactly did
> you reproduce this? On karmic, before the upgrade? Any other steps than
> I did?
On Karmic I did:
dpkg -r devicekit-disks --ignore-depends=devicekit-di
On Mon, 28 Jun 2010, Martin Pitt wrote:
>> You're right - it was technically still mounted (per 'mount') but
> /proc was empty. Ie, 'ls -l /proc' returns an empty directory.
>
> That sounds seriously wrong. What is the exact output of "mount" and
> "cat /proc/mounts" when this happens?
The output
On Sat, 26 Jun 2010, Martin Pitt wrote:
> seems that wasn't a scenario where the udevadm trigger would cause /proc
> to be unmounted -- in your "mount output after trigger", /proc is still
> mounted.
You're right - it was technically still mounted (per 'mount') but /proc
was empty. Ie, 'ls -l /
