From: "Mohammad A. Haque" <mhaque@haque.net>
To: Jim Murray <jjm@jjm.com>
Cc: jeff@CYTE.COM, linux-kernel@vger.kernel.org
Subject: Re: 2.4.2 seems to break loopback and/or mount
Date: Thu, 22 Feb 2001 22:51:31 -0500 [thread overview]
Message-ID: <3A95DE43.54863C4E@haque.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0102222215190.8939-100000@light.jjm.com>
This is not the real problem. Loopback is just broken.
Jim Murray wrote:
>
> On Thu, 22 Feb 2001 jeff@CYTE.COM wrote:
>
> Compiling with kgcc compiler from RedHat 7.0 breaks loopback in the
> way you describe on 2.4.2-prex kernels and I suspect also in the real 2.4.2.
>
> Jim
>
--
=====================================================================
Mohammad A. Haque http://www.haque.net/
mhaque@haque.net
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
batmanppc@themes.org
=====================================================================
prev parent reply other threads:[~2001-02-23 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 1:22 2.4.2 seems to break loopback and/or mount jeff
2001-02-23 3:04 ` Mohammad A. Haque
2001-02-23 3:19 ` Jim Murray
2001-02-23 3:47 ` J Sloan
2001-02-23 3:51 ` Mohammad A. Haque [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=3A95DE43.54863C4E@haque.net \
--to=mhaque@haque.net \
--cc=jeff@CYTE.COM \
--cc=jjm@jjm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.