From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@suse.de>,
andrew@digital-domain.net
Subject: Re: [Bugme-new] [Bug 7065] New: Devices no longer automount
Date: Sat, 02 Sep 2006 02:48:20 -0700 [thread overview]
Message-ID: <44F95364.8020901@goop.org> (raw)
In-Reply-To: <20060902094239.GH26849@kroah.com>
Greg KH wrote:
> This was narrowed down to a broken userspace configuration by the
> freedesktop.org developers.
>
> Many thanks to them.
>
> So no kernel issue here.
>
Do you have a reference to what the fix is?
Thanks,
J
--
VGER BF report: H 0
next prev parent reply other threads:[~2006-09-02 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200608281700.k7SH0CYl013187@fire-2.osdl.org>
2006-08-28 19:10 ` [Bugme-new] [Bug 7065] New: Devices no longer automount Andrew Morton
2006-09-02 9:42 ` Greg KH
2006-09-02 9:48 ` Jeremy Fitzhardinge [this message]
2006-09-02 9:51 ` Greg KH
2006-09-02 9:55 ` Jeremy Fitzhardinge
2006-09-02 10:31 ` Andrew Clayton
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=44F95364.8020901@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=andrew@digital-domain.net \
--cc=greg@kroah.com \
--cc=kay.sievers@suse.de \
--cc=linux-kernel@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