From: George Fouse <gfouse@quantumtek.net>
To: Metrix <metrix007@yahoo.com>
Cc: SELinux@tycho.nsa.gov
Subject: Re: 2.2 kernel series
Date: Tue, 19 Feb 2002 21:18:55 -0500 [thread overview]
Message-ID: <3C73078F.A962A59A@quantumtek.net> (raw)
In-Reply-To: 20020220005027.31760.qmail@web20602.mail.yahoo.com
I'm afraid that I would have to completely disagree with the stated
premise
"most people are sticking with 2.2 in a production enviroment".
While there are (more accurately, have been) some issues with the 2.4
series, the obvious advantages predominate.
Given that premise, though, I understand his questions.
'Nough said.
Metrix wrote:
>
> why develop 2.4, 2.5 even? 2.4 has had quite a lot of
> problems, most people are sticking with 2.2 in a
> production enviroment, it would seem that the 2.2
> selinux patches are not being updated, which is a
> shame. also, does selinux audit there code ala openbsd?
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Sports - Coverage of the 2002 Olympic Games
> http://sports.yahoo.com
>
--
------------------------------
George Fouse,
President
Quantum Technology Associates
System and Network Services
------------------------------
--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2002-02-20 2:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 0:50 2.2 kernel series Metrix
2002-02-20 2:15 ` Dale Amon
2002-02-20 12:35 ` Russell Coker
2002-02-20 14:04 ` Stephen Smalley
2002-02-20 2:18 ` George Fouse [this message]
2002-02-20 13:55 ` Stephen Smalley
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=3C73078F.A962A59A@quantumtek.net \
--to=gfouse@quantumtek.net \
--cc=SELinux@tycho.nsa.gov \
--cc=metrix007@yahoo.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.