lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 25 May 2012 21:31:42 +0800
From:	Jeff Chua <jeff.chua.linux@...il.com>
To:	Kay Sievers <kay@...y.org>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Alan Stern <stern@...land.harvard.edu>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] USB: remove CONFIG_USB_DEVICEFS

On Fri, May 25, 2012 at 5:01 PM, Kay Sievers <kay@...y.org> wrote:
> On Fri, May 25, 2012 at 9:16 AM, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
>> On Fri, May 25, 2012 at 03:06:33PM +0800, Jeff Chua wrote:
>
>>> >> VMware USB Arbitration Service Version 8.4.19
>>> >> USB: Unable to open "/proc/bus/usb/devices" (No such file or directory).
>
> I think vmware tries to open the usual /dev/bus/usb/ nodes directly
> after it has tried the deprecated /proc nodes.
>
> Udev would create the /dev/bus/ nodes.
>
> Or the kernel would create them itself if:
>  CONFIG_DEVTMPFS=y
>  CONFIG_DEVTMPFS_MOUNT=y
> is used.
>
>> Use /dev/usb/ device nodes instead.  If you have a distro that has static
>> device nodes, just add them to the package that has those nodes, and you
>> should be fine.  That will bring you into the mid 2000's as far as
>> device nodes go, I'm amazed that this hasn't been noticed before now.
>
> Many distros have disabled the USB_DEVICEFS option and there are
> usually no reports about problems any more.
>
> But I guess the number of systems that want to run USB devices, and
> pass them along to virtualization, but have an unmanaged static /dev
> are close to one user these days. :)

Yep, it's just me (the one), I guess. Configured kernel as suggested,
and it's all working now.

Sorry, as for the distro, it's just bare minimum...but works wonderfully well.

Thanks again for all your help!

Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ