From: LA Walsh <law@sgi.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: user limits for 'security'?
Date: Mon, 25 Jun 2001 12:42:51 -0700 [thread overview]
Message-ID: <3B37943B.AC711DB0@sgi.com> (raw)
In-Reply-To: <3B379058.FF66AF14@sgi.com>
I suppose another question related to the first, is 'limit' checking
part of the 'standard linux security' that embedded Linux users might
find to be a waste of precious code-space?
-l
--
The above thoughts and | I know I don't know the opinions
writings are my own. | of every part of my company. :-)
L A Walsh, law at sgi.com | Sr Eng, Trust Technology
01-650-933-5338 | Core Linux, SGI
prev parent reply other threads:[~2001-06-25 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 19:26 LA Walsh
2001-06-25 19:42 ` LA Walsh [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=3B37943B.AC711DB0@sgi.com \
--to=law@sgi.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
all inboxes | Powered by JetHome®