public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: linux-kernel@vger.kernel.org
Cc: rgooch@atnf.csiro.au
Subject: Mylex DAC vs RAM disk in 2.4.2 devfs
Date: Tue, 17 Apr 2001 13:22:01 +0200	[thread overview]
Message-ID: <01041713220107.28478@lyta> (raw)

I have just upgraded a machine with a Mylex DAC hardware RAID controller to 
kernel 2.4.2 with devfs.

It seems that /dev/rd is used by both the RAM disk in the kernel and the 
Mylex controller!

This is wrong of course, there are two problems, one is the situation of what 
happens if you need both Mylex RAID and a RAM disk.  The other is the problem 
that Mylex devices get treated as ram disks by devfsd which cause an upgrade 
to break (the compatibility sym-links are not created correctly).
I believe that the RAM disk should be changed as /dev/rd has been used by 
Mylex controllers for a long time.  I am willing to submit patches to the 
kernel and to devfsd if this suggestion is accepted and someone can suggest a 
good directory name for ram-disks (I don't want to have the same problem 
again).

-- 
http://www.coker.com.au/bonnie++/     Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/       Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/     My home page

             reply	other threads:[~2001-04-17 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 11:22 Russell Coker [this message]
2001-04-17 12:08 ` Mylex DAC vs RAM disk in 2.4.2 devfs Andreas Ferber
2001-04-17 16:23   ` H. Peter Anvin
2001-04-18  7:17 ` Richard Gooch

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=01041713220107.28478@lyta \
    --to=russell@coker.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@atnf.csiro.au \
    /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