From: "Alan Miles" <alanmiles@hfx.eastlink.ca>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Patrick J. Volkerding" <volkerdi@slackware.com>,
<Riley@Williams.Name>, <linux-kernel@vger.kernel.org>
Subject: RE: Problem with 2.4.19/2.4.20-pre7 multiple root floppy disks-2.4.18 works.
Date: Sat, 14 Sep 2002 18:51:51 -0300 [thread overview]
Message-ID: <JLEBIHHBMBHBAFPAJLEFCECLDAAA.alanmiles@hfx.eastlink.ca> (raw)
In-Reply-To: <1032035275.13636.15.camel@irongate.swansea.linux.org.uk>
Alan,
Thanks for your reply - I appreciate all the hard work you guys are doing.
My experience to-date with the kernel is to compile it - not to try and fix
something. However, I could try and fix it,
although I feel it would be better for the kernel maintainers to fix it, as
I am inexperienced with Linux kernel level
programming; I come from an application programming arena.
Pat, I am cc'ing you on this so you know what is going on - this is the
root-disk problem that I emailed you about.
Alan
-----Original Message-----
From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
Sent: September 14, 2002 17:28
To: Alan Miles
Cc: linux-kernel@vger.kernel.org; Riley@Williams.Name
Subject: Re: Problem with 2.4.19/2.4.20-pre7 multiple root floppy
disks-2.4.18 works.
On Fri, 2002-09-13 at 21:08, Alan Miles wrote:
> I reported this problem with 2.4.19 and have just tested the 2.4.20-pre7
> kernel. The same problem exists there.
> I must re-iterate that 2.4.18 works fine with all of my 7 uncompressed
> 1.44MB floppy disks, and the 2.4.18 system boots up fine.
Yes its in my bug list. Its up to someone it matters to to provide
patches. It could be a ramdisk change. it could well come from the
initrd loading cleanup/root ramfs stuff.
prev parent reply other threads:[~2002-09-14 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 20:08 Problem with 2.4.19/2.4.20-pre7 multiple root floppy disks- 2.4.18 works Alan Miles
2002-09-14 20:27 ` Alan Cox
2002-09-14 21:51 ` Alan Miles [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=JLEBIHHBMBHBAFPAJLEFCECLDAAA.alanmiles@hfx.eastlink.ca \
--to=alanmiles@hfx.eastlink.ca \
--cc=Riley@Williams.Name \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=volkerdi@slackware.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;
as well as URLs for NNTP newsgroup(s).