From: mobinmob <mobinmob@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: limine-4.20230208.0
Date: Thu, 09 Feb 2023 21:13:58 +0100 [thread overview]
Message-ID: <20230209201358.qbv4sPne_sW6c_Vv3BE4jvp9ImJY-fmevmpbzK3MC2E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41420@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
New comment by mobinmob on void-packages repository
https://github.com/void-linux/void-packages/pull/41420#issuecomment-1424752209
Comment:
> I wouldn't go as far as to chainload another bootloader for ZFS... that isn't really the point of Limine, but if you wanna use it in that fashion that's okay.
>
> I would suggest reading the newly added `PHILOSOPHY.md` file in the root of the Limine repo for an idea behind the design and usage philosophy of the bootloader.
Ι will use limine to load the zfsbootmenu efi executable. That enables me to have boot environments (with native encryption optionally ). I will also use limine to load other kernels from the ESP.
I am currently using refind but I find limine configuration more straightforward.
It **fantastic** on a livecd - single configuration for uefi and bios and easy installation.
next prev parent reply other threads:[~2023-02-09 20:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 5:08 [PR PATCH] New package: limine-4.20221230.0 mintsuki
2023-01-03 9:17 ` [PR PATCH] [Updated] " mintsuki
2023-01-03 11:12 ` mintsuki
2023-01-03 13:00 ` mintsuki
2023-01-03 17:02 ` mobinmob
2023-01-15 4:58 ` [PR PATCH] [Updated] " mintsuki
2023-01-16 16:53 ` mintsuki
2023-01-22 9:53 ` [PR PATCH] [Updated] New package: limine-4.20230114.0 mintsuki
2023-02-04 13:39 ` New package: limine-4.20230120.0 mobinmob
2023-02-05 6:23 ` Vaelatern
2023-02-05 6:53 ` mobinmob
2023-02-05 6:54 ` mobinmob
2023-02-09 19:47 ` mintsuki
2023-02-09 19:55 ` [PR PATCH] [Updated] " mintsuki
2023-02-09 20:04 ` New package: limine-4.20230208.0 mintsuki
2023-02-09 20:13 ` mobinmob [this message]
2023-02-09 20:18 ` mobinmob
2023-02-09 20:20 ` mobinmob
2023-02-12 9:40 ` [PR PATCH] [Updated] " mintsuki
2023-02-13 15:37 ` [PR PATCH] [Updated] New package: limine-4.20230212.0 mintsuki
2023-02-13 15:49 ` New package: limine-4.20230212.1 mintsuki
2023-02-15 12:14 ` [PR PATCH] [Updated] New package: limine-4.20230215.0 mintsuki
2023-02-15 19:23 ` [PR PATCH] [Merged]: " Vaelatern
2023-04-01 17:39 ` fungilife
2023-04-01 17:42 ` classabbyamp
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=20230209201358.qbv4sPne_sW6c_Vv3BE4jvp9ImJY-fmevmpbzK3MC2E@z \
--to=mobinmob@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).