On Mon, 12 Sep 2011, Bob Proulx wrote:
Date: Mon, 12 Sep 2011 21:56:22 -0600
From: Bob Proulx
To: debian-user@lists.debian.org
Subject: Re: udev warning [partially SOLVED]
it...@nospammail.net wrote:
Now I have to resolve the same warnings coming from file
/etc/udev/rules.d
it...@nospammail.net wrote:
> Now I have to resolve the same warnings coming from file
> /etc/udev/rules.d/025_logitechmouse.rules
> This is a symlink to
> /etc/udev/logitechmouse.rules
> According to 'dpkg -S' the symlink is unknown.
> The target, though, is owned by package kcontrol.
On Sun, 11 Sep 2011, Bob Proulx wrote:
it...@nospammail.net wrote:
I noticed during boot a series of warnings coming from udevd.
...
udevd[451]: SYSFS{}= will be removed in a future udev version, \
please use ATTR{}= to match the event device, or ATTRS{}= to \
match a parent device, in \
/etc/
it...@nospammail.net wrote:
> I noticed during boot a series of warnings coming from udevd.
> ...
> udevd[451]: SYSFS{}= will be removed in a future udev version, \
> please use ATTR{}= to match the event device, or ATTRS{}= to \
> match a parent device, in \
> /etc/udev/rules.d/z60_xserver-xorg-i
On Sat, 10 Sep 2011, Sven Hoexter wrote:
On Sat, Sep 10, 2011 at 11:17:51PM +0300, it...@nospammail.net wrote:
Hi,
udevd[451]: SYSFS{}= will be removed in a future udev version, \
please use ATTR{}= to match the event device, or ATTRS{}= to \
match a parent device, in \
/etc/udev/rules.d/z6
On Sat, Sep 10, 2011 at 11:17:51PM +0300, it...@nospammail.net wrote:
Hi,
> udevd[451]: SYSFS{}= will be removed in a future udev version, \
> please use ATTR{}= to match the event device, or ATTRS{}= to \
> match a parent device, in \
> /etc/udev/rules.d/z60_xserver-xorg-input-wacom.rules:59
>
Hi,
I noticed during boot a series of warnings coming from udevd.
The following is an example warnings. The difference between the
warnings is the mentioned file, and the number after the colon (line
numbers?). The '\' is a line-continuation which I added.
udevd[451]: SYSFS{}= will be remo
On Fri, Jul 31, 2009 at 11:27:19AM -0700, Kushal Koolwal wrote:
>
> >Either use a Live CD or add init=/bin/bash to the kernel commandline
> > to make it accessible.
>
> Doing
>
> init=/bin/bash
> mount -o rw,remount /
> rm -rf /dev/.udev/
>
> worked fine!
mount -o remount,ro /
exec /sbin/init
>Either use a Live CD or add init=/bin/bash to the kernel commandline
> to make it accessible.
Doing
init=/bin/bash
mount -o rw,remount /
rm -rf /dev/.udev/
worked fine!
Thank you very much guys. You rock.
Kushal Koolwal
I do blog at http://blogs.koolwal.net/
__
On 2009-07-30 21:49 +0200, Kushal Koolwal wrote:
>>You should rm -rf /dev/.udev/, but it is better to leave the rest of
>>/dev alone.Sven, I did rm -rf /dev/.udev/ and when I restarted my system I
>>again
> got the warning message and /dev/.udev was created again automatically.
You will need to
>You should rm -rf /dev/.udev/, but it is better to leave the rest of
>/dev alone.Sven, I did rm -rf /dev/.udev/ and when I restarted my system I
>again
got the warning message and /dev/.udev was created again automatically.
Also I checked on another system which does not give this message and
On 2009-07-30 18:53 +0200, Kushal Koolwal wrote:
>>Assuming Kushal uses an initramfs, without it the boot process will
>> halt rather early if the kernel cannot find /dev/console.
> Actually I am not using initramfs. Would leaving /dev/console and deleting
> everything under /dev/.udev/ work?
Yo
>Assuming Kushal uses an initramfs, without it the boot process will
> halt rather early if the kernel cannot find /dev/console.
Actually I am not using initramfs. Would leaving /dev/console and deleting
everything under /dev/.udev/ work?
Kushal Koolwal
I do blog at http://blogs.koolwal.net/
On 2009-07-30 12:21 +0200, Γιώργος Πάλλας wrote:
> Kushal Koolwal wrote:
>> Recently I was having some trouble with my udev, so I purged udev, rebooted
>> system and re-install udev again. After that most of the udev startup error
>> went away but now I get the following warning message during s
Kushal Koolwal wrote:
> Recently I was having some trouble with my udev, so I purged udev, rebooted
> system and re-install udev again. After that most of the udev startup error
> went away but now I get the following warning message during system boot:
>
> .udev/ already exists on the static /de
Recently I was having some trouble with my udev, so I purged udev, rebooted
system and re-install udev again. After that most of the udev startup error
went away but now I get the following warning message during system boot:
.udev/ already exists on the static /dev!
Any ideas?
Please copy me
16 matches
Mail list logo
