linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott James Remnant <scott@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev/ubuntu problem solved
Date: Thu, 12 Jul 2007 08:52:15 +0000	[thread overview]
Message-ID: <1184230335.10350.11.camel@wing-commander> (raw)
In-Reply-To: <200707101653.31621.aj@dungeon.inka.de>


[-- Attachment #1.1: Type: text/plain, Size: 1568 bytes --]

On Wed, 2007-07-11 at 17:35 -0700, Greg KH wrote:

> On Wed, Jul 11, 2007 at 09:34:31AM +0100, Scott James Remnant wrote:
> > On Tue, 2007-07-10 at 17:39 +0200, Kay Sievers wrote:
> > 
> > > On 7/10/07, Andreas Jellinghaus <aj@dungeon.inka.de> wrote:
> > > > I finally figured out what is wrong with udev on ubuntu.
> > > >
> > > > ubuntu mounts usbfs as /proc/bus/usb/.usbfs
> > > > and has udev create /dev/bus/usb and bind-mounts that as /proc/bus/usb.
> > > 
> > > What are theses guys smoking? That's so sick to bind-mount
> > > /dev-directories to /proc! I wouldn't support such a system at all. It
> > > is totally broken.
> > > 
> > It works <g>
> > 
> > What we do is mount the usbfs filesystem on /dev/bus/usb/.usbfs, and
> > symlink the devices file from that into the parent directory (so
> > that /dev/bus/usb/devices exists).
> > 
> > The whole lot is then bind-mounted to /proc/bus/usb; so an application
> > using /proc/bus/usb sees the same tree as a fixed one.
> > 
> > We would fix the apps, but unfortunately we don't have the source to
> > VMware!
> 
> vmware originally said they would fix their program up to handle this
> properly.  Unfortunatly, they seem to have forgotten this and do not
> seem to be willing to do this, especially when distros do looney things
> like this to apease them :)
> 
VMware appears to work on my laptop here, which is running the
development version of Ubuntu (which lacks the /proc/bus/usb hack).

Scott
-- 
Scott James Remnant
Ubuntu Development Manager
scott@ubuntu.com

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 286 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

[-- Attachment #3: Type: text/plain, Size: 226 bytes --]

_______________________________________________
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

  parent reply	other threads:[~2007-07-12  8:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 14:53 udev/ubuntu problem solved Andreas Jellinghaus
2007-07-10 15:39 ` Kay Sievers
2007-07-10 15:46 ` Andreas Jellinghaus
2007-07-10 16:19 ` Kay Sievers
2007-07-11  7:32 ` Andreas Jellinghaus
2007-07-11  8:34 ` Scott James Remnant
2007-07-11 10:09 ` Kay Sievers
2007-07-12  0:35 ` Greg KH
2007-07-12  8:52 ` Scott James Remnant [this message]
2007-07-12 16:09 ` Greg KH
2007-07-12 16:58 ` Scott James Remnant
2007-07-12 18:37 ` Greg KH
2007-07-13  8:44 ` Scott James Remnant

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=1184230335.10350.11.camel@wing-commander \
    --to=scott@ubuntu.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).