From: John Richard Moser <nigelenki@comcast.net>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: post 2.6.7 BK change breaks Java?
Date: Tue, 06 Jul 2004 13:49:33 -0400 [thread overview]
Message-ID: <40EAE62D.8090800@comcast.net> (raw)
In-Reply-To: <20040706161451.GA26925@merlin.emma.line.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Matthias Andree wrote:
| On Tue, 06 Jul 2004, John Richard Moser wrote:
|
| I've been pointed to the NX feature off-list and investigated, my CPU
| (AMD Athlon XP 2500+ Model 10 "Barton") doesn't support the noexec flag,
Your CPU doesn't need to support an NX flag. See
http://en.wikipedia.net/wiki/PaX for two ways to mimic the same
functionality. I'm not sure if any noexec patches other than PaX can do
this though; the thing IS about 3 years old.
Anyway, it was just a longshot. I've got nothing else to offer on the
subject of java dying because of in-kernel issues.
| and dmesg does not contain any output that MX was enabled, and the Java
| "Killed" problem persists when the kernel is booted with noexec=off.
|
| It must have entered the tree between v2.6.7 and revision 1.1757 in
| Linus' tree.
|
| BTW, how do I tell BitKeeper "pull up to revision..."? bk pull and bk
| undo -aREV is a way, but it's wasteful.
|
Dunno.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA6uYrhDd4aOud5P8RAsDwAKCANubhFZRy8cMywXF+/VFzX+sNNgCfY5l9
0u+mKXtBIimd4xQSEVIplJE=
=RXue
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-07-06 17:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 23:11 post 2.6.7 BK change breaks Java? Matthias Andree
2004-07-06 15:55 ` John Richard Moser
2004-07-06 16:14 ` Matthias Andree
2004-07-06 17:49 ` John Richard Moser [this message]
2004-07-06 22:45 ` Andy Isaacson
2004-07-09 13:51 ` Jesper Juhl
2004-07-09 14:54 ` Con Kolivas
2004-07-09 16:37 ` José de Paula
2004-07-09 17:55 ` Jesper Juhl
2004-07-10 11:41 ` Go Taniguchi
2004-07-11 15:16 ` Jesper Juhl
2004-07-11 15:19 ` Con Kolivas
2004-07-11 15:35 ` Jesper Juhl
2004-07-11 15:35 ` Grzegorz Kulewski
2004-07-11 15:38 ` Jesper Juhl
2004-07-12 0:56 ` Jesper Juhl
2004-07-12 3:20 ` Brian Gerst
2004-07-12 3:57 ` Brian Gerst
2004-07-12 11:01 ` Jesper Juhl
2004-07-12 12:38 ` Brian Gerst
2004-07-12 14:05 ` Matthias Andree
2004-07-12 15:59 ` Linus Torvalds
2004-07-12 21:50 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2004-07-06 18:38 Ray Lee
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=40EAE62D.8090800@comcast.net \
--to=nigelenki@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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