From: Bill Davidsen <davidsen@tmr.com>
To: John Richard Moser <nigelenki@comcast.net>,
Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: Re: noexec=on doesn't work
Date: Thu, 14 Dec 2006 16:22:58 -0500 [thread overview]
Message-ID: <4581C0B2.1010500@tmr.com> (raw)
In-Reply-To: <457B0FD7.2030804@comcast.net>
John Richard Moser wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I'm running on an Athlon 64 in 32-bit mode, running 32-bit Ubuntu with
> kernel 2.6.19 (Ubuntu version 2.6.19-7-generic for the curious;
> compiled for 586). Apparently, 'noexec=on' on the kernel command line
> does nothing; the NX bit seems to not work.
Straining my memories of i586, I don't think that it even COULD do
noexec... I don't have any here to try at the moment. In any case an
option which isn't known or isn't implemented should generate a warning.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2006-12-14 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 19:34 noexec=on doesn't work John Richard Moser
2006-12-09 20:03 ` Kyle McMartin
2006-12-09 20:10 ` John Richard Moser
2006-12-11 19:53 ` Eric Piel
2006-12-11 22:01 ` John Richard Moser
2006-12-14 21:22 ` Bill Davidsen [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=4581C0B2.1010500@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.net \
/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