From: Douglas Gilbert <dougg@torque.net>
To: linux-kernel@vger.kernel.org,
Meino Christian Cramer <mccramer@s.netic.de>
Subject: Re: 2.4.0: Raw devices ?
Date: Sat, 13 Jan 2001 13:33:48 -0500 [thread overview]
Message-ID: <3A609F8C.DD30BBCF@torque.net> (raw)
Meino Cramer wrote:
> short question: How cabn I activate/where can I find the raw devices
> often described as /dev/raw[12]* in/with kernel linux-2.4.0.
There doesn't seem to be any config option for raw
devices in lk 2.4.0 , they are just there. However
the raw (8) utility expects them in a different place
from where Documentation/devices.txt currently says
they are. You may have to set up these char devices:
$ ls -l /dev/rawctl
crw-r--r-- 1 root root 162, 0 Jan 13 05:12 /dev/rawctl
$ ls -l /dev/raw/*
crw-r--r-- 1 root root 162, 1 Jan 13 05:12 /dev/raw/raw1
crw-r--r-- 1 root root 162, 2 Jan 13 05:12 /dev/raw/raw2
crw-r--r-- 1 root root 162, 3 Jan 13 05:12 /dev/raw/raw3
crw-r--r-- 1 root root 162, 4 Jan 13 05:12 /dev/raw/raw4
etc.
Recent versions of dd meet the alignment requirements
of raw devices as does lmdd (from the lmbench package).
I have done some timings of disk to disk copies using
raw devices compared to other devices. See:
http://www.torque.net/sg/fst_copy.html
> And where can I find the "raw" utility...
In both RH 6.2 and 7.0 the raw (8) utility is in the
util-linux package (RH have applied a "raw" patch for
those two lk 2.2 versions). Read man (8) raw to find
out how to bind a raw device to an existing block device.
Example:
$ raw /dev/raw/raw1 /dev/sda3
Doug Gilbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-13 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 18:33 Douglas Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-13 5:15 2.4.0: Raw devices ? Meino Christian Cramer
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=3A609F8C.DD30BBCF@torque.net \
--to=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mccramer@s.netic.de \
/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.