From: Greg KH <greg@kroah.com>
To: Andi Kleen <ak@suse.de>, Kay Sievers <kay.sievers@vrfy.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.18-rc1
Date: Sun, 9 Jul 2006 16:36:01 -0700 [thread overview]
Message-ID: <20060709233601.GA4646@kroah.com> (raw)
In-Reply-To: <200607100117.30052.ak@suse.de>
On Mon, Jul 10, 2006 at 01:17:30AM +0200, Andi Kleen wrote:
> On Saturday 08 July 2006 18:02, Greg KH wrote:
> > On Sat, Jul 08, 2006 at 04:44:08PM +0200, Andi Kleen wrote:
> > > Greg KH <greg@kroah.com> writes:
> > > >
> > > > Perhaps, that is odd. The scanner should default to the logged in user,
> > > > right? Please file a bug at bugzilla.novell.com and the SuSE people can
> > > > work on it there.
> > >
> > > I have a similar problem with my printer. But /dev/usblp0,
> > > /dev/usb/lp0 don't even appear, no matter what the permissions are.
> >
> > What version of udev are you using? It works fine for me here with a
> > USB printer (that's what I tested the changes with.)
>
> udev-068git20050831-9 (from SUSE 10.0 I think)
That's the issue, look in Documentation/Changes for the proper version
of udev for the past few kernel versions to handle this kind of issue
(again, it was a stupid libsysfs problem, which caused us to finally
drop that piece of crud from udev...) This has been documented as such
since last October, see commit ad7e14a55ed7648d02a4df8e460e291d80a18c98.
It was necessary to do this for the input drivers to get them to all
work properly, please see the old archives for details as to the
necessity of it.
Also, that change caused the creation of Documentation/ABI/ which
describes the rules that programs that look at sysfs class stuff, must
be able to handle a symlink there.
That older version of udev in 10.0 can't handle the symlink, but I think
that Kay had a version somewhere that was patched to handle it. I'd
just recommend upgrading to 10.1 :)
thanks,
greg k-h
next prev parent reply other threads:[~2006-07-09 23:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 4:26 Linux v2.6.18-rc1 Linus Torvalds
2006-07-06 9:44 ` Matt Keenan
2006-07-06 12:49 ` Jonathan Corbet
2006-07-06 16:22 ` Linus Torvalds
2006-07-06 12:34 ` Alistair John Strachan
2006-07-07 0:11 ` Andrew Morton
2006-07-06 12:44 ` Nigel Cunningham
2006-07-06 19:44 ` David R
2006-07-06 22:17 ` Greg KH
2006-07-07 21:11 ` David R
2006-07-08 8:14 ` Borislav Petkov
2006-07-08 14:19 ` Kay Sievers
2006-07-08 14:44 ` Andi Kleen
2006-07-08 14:44 ` Andi Kleen
2006-07-08 16:02 ` Greg KH
2006-07-09 23:17 ` Andi Kleen
2006-07-09 23:36 ` Greg KH [this message]
2006-07-07 1:05 ` Hervé Fache
2006-07-07 15:41 ` Steve Fox
2006-07-09 10:34 ` Benjamin Herrenschmidt
2006-07-10 13:21 ` Will Schmidt
2006-07-10 14:40 ` Alan Cox
2006-07-10 21:17 ` Benjamin Herrenschmidt
2006-07-11 17:00 ` Steve Fox
2006-07-10 21:16 ` Benjamin Herrenschmidt
2006-07-10 16:38 ` Steve Fox
2006-07-10 18:30 ` Steve Fox
2006-07-07 17:52 ` lost cpufreq (Re: Linux v2.6.18-rc1) Tomasz Torcz
2006-07-07 19:07 ` Dave Jones
2006-07-07 20:27 ` Tomasz Torcz
2006-07-07 20:35 ` Dave Jones
2006-07-10 10:03 ` Takashi Iwai
2006-07-08 14:09 ` [patchset 0/3 -2.6.18-rc1] pc8736x_gpio: fix re-modprobe errors Jim Cromie
2006-07-08 14:16 ` [patchset 1/3 -2.6.18-rc1] pc8736x_gpio: fix re-modprobe errors - define and use constants Jim Cromie
2006-07-08 14:29 ` [patchset 2/3 -2.6.18-rc1] pc8736x_gpio: fix re-modprobe errors - undo region reservation Jim Cromie
2006-07-08 14:34 ` [patchset 3/3 -2.6.18-rc1] pc8736x_gpio: fix re-modprobe errors - fix/finish cdev-init Jim Cromie
-- strict thread matches above, loose matches on Subject: below --
2006-07-06 19:25 Linux v2.6.18-rc1 Moore, Robert
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=20060709233601.GA4646@kroah.com \
--to=greg@kroah.com \
--cc=ak@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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