From: "John O'Donnell" <johnod@voicefx.com>
To: kees <kees@schoen.nl>, linux-kernel@vger.kernel.org
Subject: Re: old binary works not with 2.2.18
Date: Mon, 18 Dec 2000 20:20:48 -0500 [thread overview]
Message-ID: <3A3EB7F0.3050905@voicefx.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0012182026170.8049-100000@schoen3.schoen.nl>
kees wrote:
> Hi,
>
> I have an old 4GL application (from SCO3.2v4) that is a neat database
> tool. Under 2.2.17 with iBCS this works well:
I am just curious. Did you re-compile the iBCS2 module after upgrading
to 2.2.18 to did you force the module to load up...
With Slackware and kernel upgrades this is a regular procedure with me
otherwise chaos ensues :-)
Johnny O
--
<SomeLamer> what's the difference between chattr and chmod?
<SomeGuru> SomeLamer: man chattr > 1; man chmod > 2; diff -u 1 2 | less
-- Seen on #linux on irc
=== Never ask a geek why, just nod your head and slowly back away.===
+==============================+====================================+
| John O'Donnell (Sr. Systems Engineer, Net Admin, Webmaster, etc.) |
| Voice FX Corporation (a subsidiary of Student Advantage) |
| One Plymouth Meeting | E-Mail: johnod@voicefx.com |
| Suite 610 | www.voicefx.com |
| Plymouth Meeting, PA 19462 | www.campusdirect.com |
+==============================+====================================+
-
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:[~2000-12-19 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-18 19:30 old binary works not with 2.2.18 kees
2000-12-19 1:20 ` John O'Donnell [this message]
2000-12-19 17:05 ` kees
2000-12-19 17:48 ` John O'Donnell
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=3A3EB7F0.3050905@voicefx.com \
--to=johnod@voicefx.com \
--cc=kees@schoen.nl \
--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