From: "H. Peter Anvin" <hpa@zytor.com>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: klibc list <klibc@zytor.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [klibc] klibc tree status
Date: Mon, 13 Feb 2006 07:57:31 -0800 [thread overview]
Message-ID: <43F0AC6B.3010005@zytor.com> (raw)
In-Reply-To: <20060213114340.GC32626@deprecation.cyrius.com>
Martin Michlmayr wrote:
> * H. Peter Anvin <hpa@zytor.com> [2006-02-12 20:54]:
>
>>I have *NOT* implemented support for the following, which I'm hoping
>>has fallen out of use by now:
>>
>> -> When loading the ramdisk from a block device, stop and
>> ask the user for a second disk.
>
>
> This is most certainly still being used, e.g. in Debian to allow
> starting the installer from floppy disks.
Are you splitting the ramdisk between multiple floppies, or do you have
kernel + ramdisk floppies?
-hpa
next prev parent reply other threads:[~2006-02-13 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 4:54 klibc tree status H. Peter Anvin
2006-02-13 11:43 ` [klibc] " Martin Michlmayr
2006-02-13 15:57 ` H. Peter Anvin [this message]
2006-02-13 17:47 ` H. Peter Anvin
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=43F0AC6B.3010005@zytor.com \
--to=hpa@zytor.com \
--cc=klibc@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tbm@cyrius.com \
/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