public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Udev error and how to fix it.
Date: Tue, 16 Mar 2010 04:30:19 -0500	[thread overview]
Message-ID: <4B9F4FAB.2000601@gmail.com> (raw)
In-Reply-To: <20100316092534.06a901a0@digimed.co.uk>

Neil Bothwick wrote:
> On Tue, 16 Mar 2010 04:15:15 -0500, Dale wrote:
>
>    
>> Mar 16 01:55:54 smoker udevd[1275]: 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 /lib/udev/rules.d/70-nut-usbups.rules:42
>>
>> There are more but they are all pretty close to this.  I googled and
>> searched the forums and the best fix seemed to be to delete the files
>> in /etc/udev/, re-emerge udev andthen reboot.  So I did that.  I still
>> get the same error message tho.
>>      
> Of course you did, udev is complaining about rules in /lib/udev/rules.d.
> You have three choices
>
> 1) Ignore the messages, they are only deprecation warnings.
> 2) Fix the rules file(s) but they will be overwritten the next time you
>     update that package.
> 3) Bug the devs to fix it.
>
> The only time to really worry is if you get these messages from your own
> rules files, then 1 is not an option while 2 and 3 become the same.
>
>    

OK.  So for once it is not me that messed up something.  :-D  I can live 
with that.

Now to go beat up Seamonkey a little bit.

Dale

:-)  :-)



  reply	other threads:[~2010-03-16  9:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16  8:42 [gentoo-user] Udev error and how to fix it Dale
2010-03-16  9:00 ` Dirk Uys
2010-03-16  9:15   ` Dale
2010-03-16  9:25     ` Neil Bothwick
2010-03-16  9:30       ` Dale [this message]
2010-03-16  9:48         ` Neil Bothwick
2010-03-16  9:59           ` Dale
2010-03-17 12:48             ` Iain Buchanan
2010-03-17 14:06               ` Dale
2010-03-16 17:39     ` James Ausmus
2010-03-16 19:29       ` Dale
2010-03-16  9:02 ` Neil Bothwick
2010-03-16  9:18   ` Dale
2010-03-16 10:13     ` Philip Webb
2010-03-16 10:31       ` Dale
2010-03-16 12:44       ` Neil Bothwick
2010-03-16 15:37         ` Zeerak Mustafa Waseem
2010-03-16 17:19           ` Willie Wong
2010-03-16 17:33             ` Zeerak Mustafa Waseem
2010-03-16 18:13               ` Dale
2010-03-16 18:38               ` Neil Bothwick
2010-03-16 19:25                 ` Dale
2010-03-16 19:58                   ` Neil Bothwick
2010-03-16 20:15                     ` Dale
2010-03-16 21:28                       ` Neil Bothwick
2010-03-16 21:42                         ` Dale
2010-03-16 19:39                 ` Alan McKinnon
2010-03-17  1:17               ` Peter Humphrey
2010-03-17  7:56                 ` Zeerak Mustafa Waseem
2010-03-17 12:58                   ` Iain Buchanan
2010-03-17 13:05                     ` Zeerak Mustafa Waseem
2010-03-17 14:25                       ` Willie Wong
2010-03-18  0:29                         ` Iain Buchanan
2010-03-18  1:57                           ` [gentoo-user] " walt
2010-03-18  9:52                             ` Willie Wong
2010-03-18 16:58                             ` Frank Steinmetzger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B9F4FAB.2000601@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox