From: Brian Jackson <brian@mdrx.com>
To: Adam Scislowicz <adams@fourelle.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 (ramdisk device naming at boot time(/dev/ramdisk/<n>) vs. after devfs is mounted(/dev/rd/<n>))
Date: Wed, 15 Jan 2003 12:29:16 -0600 [thread overview]
Message-ID: <200301151229.16547.brian@mdrx.com> (raw)
In-Reply-To: <3E25A0D1.1020004@fourelle.com>
devfsd.conf has some stuff in it about making symlinks. Maybe this would work
for you. It is worth a look.
--Brian Jackson
On Wednesday 15 January 2003 11:56 am, Adam Scislowicz wrote:
> In the 2.4.20 kernel, when using DEVFS the ramdisk naming is
> inconsistent. /dev/ramdisk/0 works for the kernel parameter initrd=
> while /dev/rd/0 works in fstab.
> For clarity: before DEVFS loads it must be referenced as /dev/ramdisk/0,
> yet DEVFS registers /dev/rd/<n>
>
> /)dam.. . . D o n ' t S t o p
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2003-01-15 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 17:56 2.4.20 (ramdisk device naming at boot time(/dev/ramdisk/<n>) vs. after devfs is mounted(/dev/rd/<n>)) Adam Scislowicz
2003-01-15 18:29 ` Brian Jackson [this message]
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=200301151229.16547.brian@mdrx.com \
--to=brian@mdrx.com \
--cc=adams@fourelle.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 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.