Md> A future initscripts package will do it for you.
Well I hope soon, as I am now getting several error messages that fly
off the screen and are not captured in any log files because they are
too early in the boot process. Some were from usbmount.
--
To UNSUBSCRIBE, email to debian-bugs-dist-r
On Apr 25, jida...@jidanni.org wrote:
> Md> This is expected if you have no /run/udev.
> How do I get it back, the proper way, to avoid the lifetime of error messages?
A future initscripts package will do it for you.
--
ciao,
Marco
signature.asc
Description: Digital signature
Md> This is expected if you have no /run/udev.
How do I get it back, the proper way, to avoid the lifetime of error messages?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> "AM" == Andreas Mohr writes:
AM> mv /run /run.old_possibly_broken
AM> Otherwise you'd destroy a large amount of criminal evidence :)
Too late. However before I removed it I find -ls'ed it.
And saw some files from Apr 7, and some from very recently.
Also I tried for a little while rm -f /run;
notfound 622309 167-3
thanks
On Apr 25, jida...@jidanni.org wrote:
> Md> Try to rm -rf /run and reboot.
> OK, now my trackpoint and sound work, but I'll be seeing
So there is no bug, as expected and described in the precedent messages
of this bug.
> error: runtime directory '/run/udev' not wri
Md> Try to rm -rf /run and reboot.
OK, now my trackpoint and sound work, but I'll be seeing
error: runtime directory '/run/udev' not writable, for now falling back to
'/dev/.udev'
messages from now on.
Installed: 168-1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
wit
> Md> Try to rm -rf /run and reboot.
> OK, thanks! I will try it on Monday.
No you shouldn't. ;)
mv /run /run.old_possibly_broken
Otherwise you'd destroy a large amount of criminal evidence :)
(and then perhaps run a diff -urN on the two directories, or some
comparational debug invocation of rsy
Md> Try to rm -rf /run and reboot.
OK, thanks! I will try it on Monday.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Apr 22, jida...@jidanni.org wrote:
> In contrast to my Thinkpad, 167-3 works fine on my EEEPC.
Yes, because so far the problem only appears on your thinkpad.
Since you still have provided no useful information, I will try with my
glass ball: it says that you have a damaged /run directory.
Try t
In contrast to my Thinkpad, 167-3 works fine on my EEEPC.
The only difference in the reportbug template is
/etc/udev/udev.conf changed:
udev_log="err"
Which is now missing, despite it being in
/etc/udev/udev.conf.
I will be happy to send you the results of any test you want me to run.
--
To UNS
10 matches
Mail list logo
