From: "H. Peter Anvin" <hpa@zytor.com>
To: klibc list <klibc@zytor.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: klibc tree status
Date: Sun, 12 Feb 2006 20:54:11 -0800 [thread overview]
Message-ID: <43F010F3.5030305@zytor.com> (raw)
I have just pushed out a git tree which actually has the root-mounting
code removed from the kernel. Since there are any number of strange
boot configurations out there, I would really appreciate any help in
testing this stuff out.
I have *NOT* implemented support for the following, which I'm hoping has
fallen out of use by now:
-> Setting boot flags via rdev, as opposed to on the command
line
-> When loading the ramdisk from a block device, stop and
ask the user for a second disk. This one could probably
be implemented without too much trouble if people actually
care.
git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-klibc.git
-hpa
next reply other threads:[~2006-02-13 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 4:54 H. Peter Anvin [this message]
2006-02-13 11:43 ` [klibc] klibc tree status Martin Michlmayr
2006-02-13 15:57 ` H. Peter Anvin
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=43F010F3.5030305@zytor.com \
--to=hpa@zytor.com \
--cc=klibc@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