From: James de Lurker <jtl2nospamMUNGIEjump@hotmail.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Need testers for Modules policicy on RHEL4
Date: Thu, 30 Mar 2006 07:18:48 +0100 [thread overview]
Message-ID: <442B7848.8060406@hotmail.com> (raw)
In-Reply-To: <442B182D.9060104@redhat.com>
Daniel J Walsh wrote:
> I have back ported the entire selinux tool chain to RHEL4. I have also
> attempted to create a modular policy to match RHEL4 policy as closely as
> possible.
> These packages are out on
> ftp://people.redhat.com/dwalsh/SELinux/RHEL4_MODULAR
No offence Dan, but I happen to be one of those marginalised "enthusiasts"
that cannot afford the costs of personally supporting RHEL. Nor would I if
it were offered Free and Gratis.
Standard Contract rates apply if RH wish to benefit from any more effort
expended by me for RH commercial distros.
I became inactive on the project after spending months building RH9 test
setups only to see it switch to FC. That was to support the early rpm
packaging.
I'll likely become an active and thorough tester again on a community basis
when the selinux project decides to base its work on a genuine community
based Linux distro that would also be treated seriously in the enterprise
by commercial entities. With FC the poor relation.
I already find it distasteful that Redhat are effectively gaining
commercial advantage from a project support by a US government body.
The separation of FC and RHEL is mere sophistry IMHO.
In the UK one of our defense organisations was effectively forced to hand
over work on hardening a commercial OS because EU competition rules
forbade subsidy of commercial projects from government / taxpayer funds.
Sorry if this is OT for a tech developers list, but it is important.
Novell are struggling as competitors to RedHat to gain certifications for
enterprise level products, and I dont see the US Govt offering them the
equivalent assistance for community based projects.
--
-- James
>From and Reply To are INVALID.
All public postings use munged headers[1]- To contact me off list:
1) Remove "M U N G I E j u m p" ONLY: leave that "nospam" in there!
2) change "hotmail" 2 "myrealbox" after the @
--
This message was distributed to subscribers of the selinux mailing 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:[~2006-03-30 6:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 23:28 Need testers for Modules policicy on RHEL4 Daniel J Walsh
2006-03-29 23:44 ` Stephen J. Smoogen
2006-03-30 20:00 ` Daniel J Walsh
2006-03-30 20:59 ` Christopher J. PeBenito
2006-03-30 6:18 ` James de Lurker [this message]
2006-03-30 13:20 ` Stephen Smalley
2006-03-31 18:28 ` James de Lurker
2006-04-03 4:55 ` End User Mailing List / Group Randal T. Rioux
2006-04-03 12:32 ` Erich Schubert
2006-04-03 13:52 ` Stephen Smalley
2006-04-05 3:42 ` End User Mailing List / Group / Policy Made Easy Randal T. Rioux
2006-04-05 11:57 ` Erich Schubert
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=442B7848.8060406@hotmail.com \
--to=jtl2nospammungiejump@hotmail.com \
--cc=dwalsh@redhat.com \
--cc=see.the.sig.2.reply.by.email.offlist@hotmail.com \
--cc=selinux@tycho.nsa.gov \
/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.