From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: RFC: move kernels out of /boot
Date: Thu, 18 Jan 2024 16:27:37 +0100 [thread overview]
Message-ID: <20240118152737.B183521298@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48024@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
New comment by Jipok on void-packages repository
https://github.com/void-linux/void-packages/issues/48024#issuecomment-1898669655
Comment:
I'm glad that at least someone is thinking about solving an important problem(https://github.com/void-linux/void-packages/issues/46006). But getting UKI involved annoying me. Are the goals of this decision even that useful to people? It seemed to me that it was created only to oppress people and the benefits offered are so minimalistic that the quote “Those who are ready to exchange freedom for security are worthy of neither freedom nor security” comes to mind.
UKI gives "Providing a fully verified boot process", that is, bad corporations can prohibit the user from changing the kernel (and, accordingly, the system) as is the case now on Android. And other delights in the form of the inability to boot if you live in the “wrong” country. And also contributes to the implementation of DRM. And vendorlock. LinuxD damn.
next prev parent reply other threads:[~2024-01-18 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 22:46 [ISSUE] " Duncaen
2024-01-02 11:22 ` dkwo
2024-01-09 16:10 ` mbsmith
2024-01-09 16:12 ` classabbyamp
2024-01-09 16:13 ` classabbyamp
2024-01-09 16:13 ` classabbyamp
2024-01-09 16:27 ` mbsmith
2024-01-18 15:13 ` Jipok
2024-01-18 15:27 ` Johnnynator [this message]
2024-02-12 14:44 ` CtrlC-Root
2024-05-13 1:47 ` github-actions
2024-05-13 1:48 ` CtrlC-Root
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=20240118152737.B183521298@inbox.vuxu.org \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).