From: Greg KH <greg@kroah.com>
To: Burton Windle <bwindle@fint.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Please use the 'usbfs' filetype instead
Date: Fri, 20 Dec 2002 11:33:54 -0800 [thread overview]
Message-ID: <20021220193354.GE12128@kroah.com> (raw)
In-Reply-To: <20021220193050.GD12128@kroah.com> <Pine.LNX.4.43.0212201417500.2382-100000@morpheus> <20021220190538.GC12128@kroah.com> <Pine.LNX.4.43.0212201327410.2382-100000@morpheus>
Copied to lkml for others to refer to once 2.5.53 comes out...
On Fri, Dec 20, 2002 at 01:29:41PM -0500, Burton Windle wrote:
> Hello. I'm getting this message once per bootup, but I can't figure out
> why.
>
> uhci-hcd 00:07.2: Intel Corp. 82371AB/EB/MB PIIX4
> uhci-hcd 00:07.2: irq 11, io base 0000cce0
> Please use the 'usbfs' filetype instead, the 'usbdevfs' name is depreciated.
> drivers/usb/core/hcd.c: new USB bus registered, assigned bus number 1
> hub 1-0:0: USB hub found
> hub 1-0:0: 2 ports detected
>
> I see this change just started in 2.5.52-bk4. My /etc/fstab doesn't have
> usbdevfs, it has usbfs.
>
> I've grepped my entire /etc, and don't find any references to 'usbdevfs'.
> Is this a warning about the kernel using it, or user-space using that
> name? Can you offer a clue where I might find this, and correct it?
Is this a Red Hat machine?
If so, look in /etc/rc.sysinit. That's where Red Hat mounts usbdevfs.
For a Debian box, it's done in /etc/hotplug/usb.rc. I don't know where
the other distros do this, but it's probably one of the above two
places.
Don't worry, the usbdevfs name will stick around and work through 2.6,
I'm just trying to warn people that it will go away in 2.7.
Also, more recent 2.4 kernels support the usbfs name, if you want to
change the rc.sysinit file and not worry about it anymore.
Hope this helps,
greg k-h
parent reply other threads:[~2002-12-20 19:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.43.0212201327410.2382-100000@morpheus>]
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=20021220193354.GE12128@kroah.com \
--to=greg@kroah.com \
--cc=bwindle@fint.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.