From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: Adrian Bunk <bunk@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>,
Roman Zippel <zippel@linux-m68k.org>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Early userspace, Linux development (Re: perhaps init/ should update the reference to "change floppy")
Date: Sun, 9 Sep 2007 11:59:00 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0709091157540.15624@localhost.localdomain> (raw)
In-Reply-To: <E1IUBUG-0003nA-W2@flower>
On Sun, 9 Sep 2007, Oleg Verych wrote:
> * Sat, 8 Sep 2007 08:08:06 -0400 (EDT)
> []
> > from init/do_mounts_rd.c:
> >
> > ...
> []
> > if (rd_prompt)
> > change_floppy("root floppy disk to be loaded into RAM disk");
> > create_dev("/dev/root", ROOT_DEV);
> > create_dev("/dev/ram", MKDEV(RAMDISK_MAJOR, n));
> > return rd_load_image("/dev/root");
> > }
> > ...
> >
> > but isn't it a bit archaic to suggest that an explicit ramdisk will
> > be found only on a floppy? can't one be provided on a CD or DVD?
> > just suggesting that the terminology could probably be updated.
>
> All this is userspace code, ugly, unmaintained and all that kind of
> things.
>
> == Kernel panics without userspace, do you need such kernel? ==
um ... all i asked was whether that code should be updated to reflect
more than just floppies. i didn't foresee the can of worms here.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
prev parent reply other threads:[~2007-09-09 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0709080802430.8930@localhost.localdomain>
2007-09-09 1:21 ` Oleg Verych
2007-09-09 15:59 ` Robert P. J. Day [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=Pine.LNX.4.64.0709091157540.15624@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®