All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Dibowitz <phil@ipom.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and raw support
Date: Tue, 26 Apr 2005 06:14:36 +0000	[thread overview]
Message-ID: <426DDC4C.6050006@ipom.com> (raw)
In-Reply-To: <426CC269.5090400@ipom.com>

[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]

Greg KH wrote:
> I really don't know if they got that patch or not, sorry.

What version of util-linux has that patch, do you know?

Well http://www.kernel.org/pub/linux/utils/util-linux/ only goes up to
q, so I'm guess that's it. I'll file a bug report, thanks.

> 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.

Fair enough. Wouldn't it make sense to make a simple raw module that
simply was equivalent to opening the block device with O_DIRECT if for
no other reason than, erm, "backwards" compatiblity with other unices -
for ease of the writers of mplayer/xine/ogle/etc.?

> 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.

I would be interested to experiment, even though I'm sure you're
right... but I think I'm missing something... don't the major/minor
number need to be the same:

[phil@rider rc2.d]$ sudo mknod /dev/raw/raw1 c 22 0
[phil@rider rc2.d]$ sudo raw /dev/raw/raw1 /dev/hdc
Device '/dev/raw/raw1' is not a raw dev
[phil@rider rc2.d]$ ls -l /dev/raw/raw1 /dev/hdc
brw-rw----  1 root cdrom 22, 0 Apr 25 21:36 /dev/hdc
crw-r--r--  1 root root  22, 0 Apr 25 23:08 /dev/raw/raw1

--
Phil Dibowitz                             phil@ipom.com
Freeware and Technical Pages              Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
 - Benjamin Franklin, 1759


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  parent reply	other threads:[~2005-04-26  6:14 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
2005-04-26  6:14 ` Phil Dibowitz [this message]
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=426DDC4C.6050006@ipom.com \
    --to=phil@ipom.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 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.