From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Dropping of selinux & the X subsystem
Date: Thu, 12 Oct 2017 12:31:47 +0200 [thread overview]
Message-ID: <1507804307.19550.3.camel@ipfire.org> (raw)
In-Reply-To: <1507715810.4045.52.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Hello Michael,
The remove of SELinux is done, still the feature is enabled in the
kernel config, which is tracked by bug #11379 and assigned to Arne.
As you pointed in one of your mails to this list, there are still some
packages which are depend on SElinux in our repositories.
For compatibility reasons, we should keep the selinux libraries for a
while in the stable repository unless the build service is up again and
all modified packages have been build, tested and moved to the stable
repository...
In the meantime, I will work on removing the audit subsystem from our
distribution and then go on to remove X11.
The reason, why I have prior the remove of X11 support from cairo and
python3 was, that now an IPFire 3 basesystem and also the build
environment does not longer require any of the X11 libraries, which
saves us some space on the system and images and fasten to setup
the build environment a bit.
Best regards,
-Stefan
> Hello Stefan,
>
> I just wanted to know what the status is on dropping SELinux from the
> distribution as well as X.
>
> I have seen that you started working on the latter, and I know that
> we are
> almost done with SELinux. But just asking to confirm.
>
> Best,
> -Michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-10-12 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 9:56 Michael Tremer
2017-10-12 10:31 ` Stefan Schantl [this message]
2017-10-16 19:33 ` Michael Tremer
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=1507804307.19550.3.camel@ipfire.org \
--to=stefan.schantl@ipfire.org \
--cc=development@lists.ipfire.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