selinux-refpolicy.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dominick Grift <dominick.grift@defensec.nl>
To: Chris PeBenito <pebenito@ieee.org>
Cc: refpolicy <selinux-refpolicy@vger.kernel.org>
Subject: Re: [RFC] Purging dead modules
Date: Mon, 11 Jan 2021 16:23:47 +0100	[thread overview]
Message-ID: <ypjl35z7fqf0.fsf@defensec.nl> (raw)
In-Reply-To: <352607e8-2de0-fc71-8403-15942d65c837@ieee.org> (Chris PeBenito's message of "Mon, 11 Jan 2021 09:48:37 -0500")

Chris PeBenito <pebenito@ieee.org> writes:

> I'm looking to remove modules for dead programs, such as hal and
> consolekit. The question is how long to keep modules for dead
> programs?  I'm thinking something like 3-5 years.

Agree

some suggestions:

sectoolm, kdumpgui, kudzu, readahead, smoltclient, tmpreaper,
firewallgui, gift, podsleuth, ptchown, sambagui, yam, hotplug, pcmcia,
dnssectrigger, kerneloops, keyboardd, rhgb, roundup, speedtouch, w3c,
xprint

>
> Also, please propose other modules that you think should be dropped.

-- 
gpg --locate-keys dominick.grift@defensec.nl
Key fingerprint = FCD2 3660 5D6B 9D27 7FC6  E0FF DA7E 521F 10F6 4098
https://sks-keyservers.net/pks/lookup?op=get&search=0xDA7E521F10F64098
Dominick Grift

  reply	other threads:[~2021-01-11 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 14:48 [RFC] Purging dead modules Chris PeBenito
2021-01-11 15:23 ` Dominick Grift [this message]
2021-01-11 15:48   ` Russell Coker
2021-01-11 23:52     ` Topi Miettinen
2021-01-13 13:21       ` Chris PeBenito
2021-01-13 13:33         ` Dominick Grift
2021-01-19 15:11           ` Chris PeBenito

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=ypjl35z7fqf0.fsf@defensec.nl \
    --to=dominick.grift@defensec.nl \
    --cc=pebenito@ieee.org \
    --cc=selinux-refpolicy@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;
as well as URLs for NNTP newsgroup(s).