From: Nico Schottelius <nico-kernel@schottelius.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: bastian@schottelius.org
Subject: [2.6.0] ramdisk rd.o problems with devfs
Date: Tue, 2 Sep 2003 13:18:46 +0200 [thread overview]
Message-ID: <20030902111846.GA9257@schottelius.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
Hello!
When using modprobe rd I got no new devices under /dev.
Shouldn't be /dev/ram/X created?
Are there any known bugs in 2.6.0 ramdisk, which makes it
impossible to boot from initrd?
Are there changes to the 2.4 initrd?
Sincerly,
Nico
--
quote: there are two time a day you should do nothing: before 12 and after 12
(Nico Schottelius after writin' a very senseless email)
cmd: echo God bless America | sed 's/.*\(A.*\)$/Why \1?/'
pgp: new id: 0x8D0E27A4 | ftp.schottelius.org/pub/familiy/nico/pgp-key.new
url: http://nerd-hosting.net - domains for nerds (from a nerd)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-09-02 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 11:18 Nico Schottelius [this message]
2003-09-04 23:36 ` [2.6.0] ramdisk rd.o problems with devfs Dave Olien
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=20030902111846.GA9257@schottelius.org \
--to=nico-kernel@schottelius.org \
--cc=bastian@schottelius.org \
--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