From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Mylex DAC vs RAM disk in 2.4.2 devfs
Date: 17 Apr 2001 09:23:45 -0700 [thread overview]
Message-ID: <9bhqmh$50d$1@cesium.transmeta.com> (raw)
In-Reply-To: <01041713220107.28478@lyta> <20010417140859.E4385@kallisto.sind-doof.de>
Followup to: <20010417140859.E4385@kallisto.sind-doof.de>
By author: Andreas Ferber <aferber@techfak.uni-bielefeld.de>
In newsgroup: linux.dev.kernel
>
> Hi,
>
> On Tue, Apr 17, 2001 at 01:22:01PM +0200, Russell Coker wrote:
>
> > 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).
>
> What about simply "ramdisk"? ;-)
>
The standard name is /dev/ramX. If you want it directorized I suggest
/dev/ram/X.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-04-17 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 11:22 Mylex DAC vs RAM disk in 2.4.2 devfs Russell Coker
2001-04-17 12:08 ` Andreas Ferber
2001-04-17 16:23 ` H. Peter Anvin [this message]
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='9bhqmh$50d$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox