From: Pete Zaitcev <zaitcev@metabyte.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: So, what about kwhich on RH6.2?
Date: Wed, 03 Jan 2001 23:07:52 -0800 [thread overview]
Message-ID: <3A542148.AAE1D8E9@metabyte.com> (raw)
In-Reply-To: <3A541361.65942CB3@metabyte.com> <200101040611.WAA01811@pizda.ninka.net>
> Date: Wed, 03 Jan 2001 22:08:33 -0800
> From: Pete Zaitcev <zaitcev@metabyte.com>
>
> Are we going to use Miquel's patch? I cannot build fresh 2.2.x on
> plain RH6.2 without it. The 2.2.19-pre6 comes out without it. Or
> is "install new bash" the official answer? Alan?
>
> I do not understand, I just got a working 2.2.19-pre6 build on one of
> my 6.2 Sparc64 systems, what kind of failure do you see?
Oops. I cannot reproduce it anymore. Since I am quite sure
in my recollection of this problem, I conclude that there
was a kernel (perhaps 2.2.19-pre3), that called kwhich with
several arguments. No problem now on the pre6.
-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-04 7:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 6:08 So, what about kwhich on RH6.2? Pete Zaitcev
2001-01-04 6:11 ` David S. Miller
2001-01-04 7:07 ` Pete Zaitcev [this message]
2001-01-04 8:13 ` Andrew Morton
2001-01-04 8:12 ` Andi Kleen
2001-01-04 8:24 ` Andrew Morton
2001-01-04 14:42 ` Alan Cox
2001-01-04 14:41 ` Alan Cox
2001-01-04 22:03 ` J . A . Magallon
2001-01-04 22:12 ` Albert D. Cahalan
2001-01-05 10:57 ` Mike A. Harris
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=3A542148.AAE1D8E9@metabyte.com \
--to=zaitcev@metabyte.com \
--cc=davem@redhat.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