On May 29, Lucas Le Dore wrote:
> The problem on 2) is that udevd keeps /run directory busy (managing
Good catch. The problem actually is that udevd should not be running
anymore at that point, I need to understand better why it is not being
killed.
--
ciao,
Marco
signature.asc
Description: D
I've had the same issue!
Hope that the following info will help.
The installation failed:
Setting up udev (170-1) ...
mv: cannot move `/dev/.udev/' to `/run/udev/': No such file or directory
dpkg: error processing udev (--configure):
subprocess installed post-installation script returned error e
On Fri, May 27, 2011 at 5:07 PM, Marco d'Itri wrote:
>> Curious thing is that even if the directory does not exist,
>> /proc/mounts displays it as mounted...
> I would say "impossibile", even.
Is it ?
However, it's the state after bootup with udev-168.2 and
initscripts-2.88dsf-13.2, if the /run
On May 27, Lucas Le Doré wrote:
> Curious thing is that even if the directory does not exist,
> /proc/mounts displays it as mounted...
I would say "impossibile", even.
--
ciao,
Marco
signature.asc
Description: Digital signature
Sorry for the delay.
I don't know on which stage the /run directory should have been
created, but I had to do it myself to make things work.
Curious thing is that even if the directory does not exist,
/proc/mounts displays it as mounted...
Thanks,
Lucas
--
To UNSUBSCRIBE, email to debian-bug
severity 627500 normal
tag 627500 unreproducible moreinfo
thanks
I am unable to reproduce this bug and the submitter did not provide any
useful information, so I am demoting it.
--
ciao,
Marco
signature.asc
Description: Digital signature
On Sat, May 21, 2011 at 05:00:00PM +0200, Marco d'Itri wrote:
> > mv: cannot move `/dev/.udev/' to `/run/udev/': No such file or directory
> I do not understand how this could happen since postinst checks that
> /run is mounted. How is your system different?
>
I don't know, nothing special here.
> mv: cannot move `/dev/.udev/' to `/run/udev/': No such file or directory
I do not understand how this could happen since postinst checks that
/run is mounted. How is your system different?
if ! chrooted && [ -d /dev/.udev/ -a ! -d /run/udev/ ] \
&& grep -E -q "^[^[:space:]]+ /run tmpfs "
Package: udev
Version: 169-1
Severity: grave
aptitude upgrade fail on udev 169-1 configuration:
Setting up udev (169-1) ...
mv: cannot move `/dev/.udev/' to `/run/udev/': No such file or directory
dpkg: error processing udev (--configure):
subprocess installed post-installation script returned e
9 matches
Mail list logo
