From: Sid Boyce <sboyce@blueyonder.co.uk>
To: unlisted-recipients:; (no To-header on input)
Cc: piotr@hosowicz.com, LKML Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: General questiin about SYSFS
Date: Mon, 17 May 2010 08:41:40 +0100 [thread overview]
Message-ID: <4BF0F334.8090108@blueyonder.co.uk> (raw)
In-Reply-To: <4BF0AA6C.1050102@example.com>
On 17/05/10 03:31, Piotr Hosowicz wrote:
> On 16.05.2010 23:08, Sid Boyce wrote:
>> As the message says, you have to change all instances of SSYSFS to ATTR
>> in the rules files in /etc/udev/rules.d to stop those messages
>> appearing on boot up.
>
> Ok, forget my next question - I risked breaking things and made a plain
> search and replace, reboot, things seem to work, no errors. I also had
> to change BUS to SUBSYSTEM.
>
> Regards,
>
> Piotr Hosowicz
>
I forgot to mention the BUS to SUBSYSTEM change, but it was obvious
when looking at the messages. One other I've seen (on openSUSE 11.3),
/etc/modprobe.conf deprecated, so I've moved it out of /etc and also
changed files in /etc/modprobe.d from xxxxxxx to xxxxxxx.conf. It all
helps keep the noise down.
No problems, I have been running with the modified files for some months.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
next prev parent reply other threads:[~2010-05-17 7:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 21:08 General questiin about SYSFS Sid Boyce
2010-05-17 1:45 ` Piotr Hosowicz
2010-05-17 2:31 ` Piotr Hosowicz
2010-05-17 7:41 ` Sid Boyce [this message]
2010-05-17 7:50 ` Piotr Hosowicz
-- strict thread matches above, loose matches on Subject: below --
2010-05-13 18:55 Piotr Hosowicz
2010-05-13 19:02 ` Piotr Hosowicz
2010-05-13 19:28 ` Randy Dunlap
2010-05-14 1:52 ` Piotr Hosowicz
2010-05-14 3:03 ` Greg KH
2010-05-14 7:19 ` Américo Wang
2010-05-13 20:07 ` Greg KH
2010-05-14 2:12 ` Piotr Hosowicz
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=4BF0F334.8090108@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=piotr@hosowicz.com \
/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