From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: gfp <gfp@posteo.at>, Felix Lechner <felix.lechner@lease-up.com>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: question about proprietory packages
Date: Wed, 8 Jan 2025 21:59:21 +0100 [thread overview]
Message-ID: <0b8d842d-746b-4980-a6aa-9f560ef6a964@elenq.tech> (raw)
In-Reply-To: <1b1e0a60-4ba2-42a9-bdc2-5912217f07f9@posteo.at>
Hi,
On 2025-01-08 9:50 PM, gfp wrote:
> Hi Felix,
>
> I bought a laptop of the company Tuxedo
> where I can disable IME.
Don't they disable that by default?
> The options were really tricky. Difficult.
Yes they are, but you can do it!
> I will check again, if they enabled it again. Hopefully not.
>
> I didn´t install any proprietary in the beginning.
> But I don´t know, and that´s why my question,
> if on my laptop is something installed beforehand.
> I don´t have enough knowledge about boot process etc.
>
> I assume Shepherd is the Guix init system like systemd in other linux
> distros. Is that right?
Yes.
> What is Grub? Is EFI a part of Grub?
Grub is a bootloader.
In a very simplified way, which I hope is right:
1. EFI runs Grub.
2. Grub chooses the kernel to run and runs it.
3. The kernel runs the init system, which prepares everything for you.
> I guess Guix community replaced "EFI" with "grubx64.efi"
> that´s why we can find this file in the boot/EFI folder.
No, Grub is an EFI application (some software that can be launched from
EFI). EFI is going to search in the /boot/efi folder for the
applications that it can run. That's why Grub has to be there.
> > Booring often requires proprietary firmware blobs
>
> What do you mean by "Booring" I don´t understand this word?
> Thanks
I think he means Booting, with T.
> Gottfried
>
Hope this helps,
Ekaitz
next prev parent reply other threads:[~2025-01-08 21:00 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
2025-01-08 20:50 ` gfp
2025-01-08 20:59 ` Ekaitz Zarraga [this message]
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=0b8d842d-746b-4980-a6aa-9f560ef6a964@elenq.tech \
--to=ekaitz@elenq.tech \
--cc=felix.lechner@lease-up.com \
--cc=gfp@posteo.at \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).