From: Felix Lechner via <help-guix@gnu.org>
To: gfp <gfp@posteo.at>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: question about proprietory packages
Date: Wed, 08 Jan 2025 09:51:31 -0800 [thread overview]
Message-ID: <8734htfb30.fsf@lease-up.com> (raw)
In-Reply-To: <c8b09e90-a713-48de-a542-0e400a7693d9@posteo.at> (gfp@posteo.at's message of "Wed, 8 Jan 2025 17:16:32 +0000")
Hi Gottfried,
On Wed, Jan 08 2025, gfp wrote:
> I want to know briefly (for security reasons) what proprietary
> packages/programmes are on my laptop installed or run.
I am not sure there is a single way. I wouldn't install them in the
beginning.
> I unset IME (Intel Management Engine)
I would disable IME completely. The options are very tricky. I believe
the standard settings enable remote re-activation after it was turned
off.
> What is the difference of Grub, EFI, Shepherd, gnu-boot?
EFI is proprietary (but grubx64.efi is not). Everything else is free
software.
> In the manual I read Guix starts immediately with Linux libre kernel.
That's after the boot process. EFI and Grub come first.
> Could somebody briefly describe where are proprietary packages hidden
> in those running/initialising services?
Booring often requires proprietary firmware blobs. They are usually
stored in ROM chips on your equipment.
Microcode updates are also proprietary.
Good luck!
Kind regards
Felix
next prev parent reply other threads:[~2025-01-08 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 17:16 question about proprietory packages gfp
2025-01-08 17:51 ` Felix Lechner via [this message]
2025-01-08 20:50 ` gfp
2025-01-08 20:59 ` Ekaitz Zarraga
2025-01-08 22:26 ` gfp
2025-01-08 22:47 ` Ekaitz Zarraga
2025-01-09 3:25 ` Ian Eure
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8734htfb30.fsf@lease-up.com \
--to=help-guix@gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=gfp@posteo.at \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).