From: Tom Rymes <tom@rymes.net>
To: development@lists.ipfire.org
Subject: Re: Can/should we prospectively drop various kernel capabilities related to firmware access?
Date: Sun, 05 Jun 2022 21:52:45 -0400 [thread overview]
Message-ID: <1AE71C68-8777-4AE1-AC6F-8F8F2784B7E3@rymes.net> (raw)
In-Reply-To: <bfa5c6de-ffce-ce66-d252-f10a2c3ac743@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
> On Jun 5, 2022, at 11:58 AM, Peter Müller <peter.mueller(a)ipfire.org> wrote:
[snip]
> Following this principle, I would like to see things such as the multimedia
> stack we currently support in IPFire 2.x go in IPFire 3.x.
[snip]
Peter,
This should be an interesting discussion, but first I want to confirm that I am reading the above sentence correctly. Specifically, “go in” could be interpreted two different ways:
1.) be added to
2.) be removed from
I assume it’s the latter, based on the context, but I figured it was worth asking just to be certain.
As for your main question, I understand the impulse for users to want to have a single machine to host files, serve as a firewall, be a hypervisor, and so on, but I tend to agree with your assessment that the firewall should be as dedicated a machine as possible.
As for the firmware issue, is it not possible to boot from another medium to accomplish this goal?
Tom
prev parent reply other threads:[~2022-06-06 1:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 15:58 Peter Müller
2022-06-06 1:52 ` Tom Rymes [this message]
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=1AE71C68-8777-4AE1-AC6F-8F8F2784B7E3@rymes.net \
--to=tom@rymes.net \
--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