From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Some sysfs attrs have vanished!
Date: Sat, 21 Jul 2007 01:08:20 +0000 [thread overview]
Message-ID: <20070721010820.GA9987@kroah.com> (raw)
In-Reply-To: <20070715205343.GA18557@DervishD>
On Sun, Jul 15, 2007 at 10:53:43PM +0200, DervishD wrote:
> Hi all :)
>
> I don't know if I screwed anything while compiling my 2.6.20.14
> kernel, and I'm not sure how much time has this been happening because I
> removed one of the units and so I removed some bits from my rules file,
> so please tell me if I'm doing wrong anything obvious.
>
> Well, here is the story: I have two DVD recorders, and until I
> removed one of them (long story) I had my udev.rules configured to
> assign names to them based on $ATTRS{model}. And it worked, I swear. One
> of them reports something like "HL-DT-ST" and the other said
> "DUW1616/ARR", or something very similar.
>
> Today I've put again the second recorder and I did run "udevinfo" to
> get the model strings (I didn't remember them exactly) and to my
> surprise, there's no ATTRS{model}!
I would ask on the dvb mailing list, perhaps the driver code changed
somehow to not export this attribute anymore?
thanks,
greg k-h
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2007-07-21 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 20:53 Some sysfs attrs have vanished! DervishD
2007-07-21 1:08 ` Greg KH [this message]
2007-07-23 6:42 ` DervishD
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=20070721010820.GA9987@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).