From: Dale Amon <amon@vnl.com>
To: Erich Schubert <erich@debian.org>
Cc: Luke Kenneth Casson Leighton <lkcl@lkcl.net>, SELinux@tycho.nsa.gov
Subject: Re: Debian SELinux backports project
Date: Thu, 17 Nov 2005 18:18:04 +0000 [thread overview]
Message-ID: <20051117181803.GD2431@vnl.com> (raw)
In-Reply-To: <1132237644.16126.11.camel@wintermute.xmldesign.de>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
On Thu, Nov 17, 2005 at 03:27:24PM +0100, Erich Schubert wrote:
> Hi Luke,
> I'll not support older kernels. I'll recommend to either build your own
> kernel, or get the linux-image 2.6.14+ from unstable.
> Fortunately, the linux kernel doesn't depend on much userspace programs.
> Obviously, the kernel cannot depend on a library, which is very
> nice. ;-)
> But the debian "vanilla" kernels do depend on a tool to generate
> appropriate init ramdisks, so I'll probably include an unmodified
> "backport" of yaird or one of the other initrd tool, once I've decided
> which I prefer. Yaird worked okay on a test machine of mine, but not on
> a second one, unfortunately; but I don't know why yet... Looked like
> some module was missing for mounting the root which is on software raid;
> the "old" kernel had these drivers built in, making it of course harder
> for yaird to detect the appropriate modules...
I've spent loads of time on the Debian battle myself ;-)
One of the issues with the kernel is that last time I
looked, even the kernel source packages in etch were
rather oldish. I'm not against doing my own from scratch
from kernel.org, but for operational systems it is better
to depend on official debian kernel sources if at all
possible.
I expect I will come back to the selinux debian problem
within the next couple weeks as it is on my whiteboard
as something I would like to use in development project
I'm currently working on.
FWIW, count me in.
--
------------------------------------------------------
Artemis Systems Development
Dale Amon amon@islandone.org +44-7802-188325
International linux systems consultancy
Hardware & software system design, security
and networking, systems programming and Admin
"Have Laptop, Will Travel"
------------------------------------------------------
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-17 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 13:05 Debian SELinux backports project Erich Schubert
2005-11-17 14:11 ` Luke Kenneth Casson Leighton
2005-11-17 14:27 ` Erich Schubert
2005-11-17 18:18 ` Dale Amon [this message]
2005-11-18 2:46 ` 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=20051117181803.GD2431@vnl.com \
--to=amon@vnl.com \
--cc=SELinux@tycho.nsa.gov \
--cc=erich@debian.org \
--cc=lkcl@lkcl.net \
/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.