From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and raw support
Date: Tue, 26 Apr 2005 05:54:27 +0000 [thread overview]
Message-ID: <20050426055426.GA5082@kroah.com> (raw)
In-Reply-To: <426CC269.5090400@ipom.com>
On Mon, Apr 25, 2005 at 10:39:43PM -0700, Phil Dibowitz wrote:
> Greg KH wrote:
> >
> > What distro are you using? In order to have udev and raw working
> > together, you need a new version of the raw userspace program (sorry,
> > forgot about this until right now.) I know SuSE ships it in their
> > distro, don't know about everyone else.
>
> Debian unstable.
>
> /sbin/raw seems to be part of util-linux which is at version 2.12p-4 in
> debian unstable - i.e. 2.12p with 4 local debian revisions which may or
> may not include code from later util-linux releases.
I really don't know if they got that patch or not, sorry.
> > Also, why use raw at all? It's depreciated, nasty code, which no one
> > likes at all, and has no real-world use. It is also going to be ripped
> > out of the kernel entirely one of these days. The only people who like
> > it are people who want to create useless benchmarks...
>
> I've never used it in linux, only in Solaris... but I'm told that it
> will provide better DVD Video read performance. Many of the DVD players
> out there provide support for raw devices, and in fact recommend using them.
For Linux? Just use O_DIRECT and it should work the same.
> Since even on my high-end system I don't get the DVD playback that I get
> on my living room DVD player, I decided to give it a shot.
My crappy, slow, no-memory, 2+ year old laptop gives great dvd playback,
perhaps you have some other issues with your system (sorry, I'm not
going to be able to help out here, as I don't know anything about video
playback other than it "works for me")
> Why is it depricated? What's wrong with using raw devices?
Because you should use O_DIRECT to access block devices directly, which
properly uses the kernel io subsystems. raw goes around all of that,
and thinks it is smarter than the kernel. In the end, it is wrong, and
can be slower.
Anyway, you can get around this by creating the device node by hand if
you really want. I suggest you file a debian bug to get them to fix the
raw program to work properly with udev.
Good luck,
greg k-h
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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
next prev parent reply other threads:[~2005-04-26 5:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 10:11 udev and raw support Phil Dibowitz
2005-04-25 20:14 ` Greg KH
2005-04-25 20:19 ` Phil Dibowitz
2005-04-25 20:38 ` Greg KH
2005-04-26 4:42 ` Phil Dibowitz
2005-04-26 5:26 ` Greg KH
2005-04-26 5:39 ` Phil Dibowitz
2005-04-26 5:54 ` Greg KH [this message]
2005-04-26 6:14 ` Phil Dibowitz
2005-04-26 6:34 ` Greg KH
2005-04-26 6:38 ` Phil Dibowitz
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=20050426055426.GA5082@kroah.com \
--to=greg@kroah.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).