docs
zfsbootmenu
docs | zfsbootmenu | |
---|---|---|
236 | 161 | |
1,714 | 779 | |
0.0% | 4.4% | |
0.0 | 9.2 | |
about 2 years ago | 9 days ago | |
Shell | ||
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docs
-
A Brief History of the U.S. Trying to Add Backdoors into Encrypted Data
marcan of the Asahi Linux project got into a discussion on reddit about this, and says that when it comes to hardware, you just can’t know.
> I can't prove the absence of a silicon backdoor on any machine, but I can say that given everything we know about AS systems (and we know quite a bit), there is no known place a significant backdoor could hide that could completely compromise my system. And there are several such places on pretty much every x86 system
(Long) thread starts here, show hidden comments for the full discussion https://old.reddit.com/r/AsahiLinux/comments/13voeey/what_is...
I highly recommend reading this if you’re interested https://github.com/AsahiLinux/docs/wiki/Introduction-to-Appl...
-
The Register looks at the first release of Fedora Asahi Remix
Depends on the box. In general if there is a hardwired HDMI port it works, if it's an alt mode it doesn't yet. The feature pages give detail by hardware, heres a direct link to the M2 page https://github.com/AsahiLinux/docs/wiki/M2-Series-Feature-Su...
-
Fedora Asahi Remix
https://github.com/AsahiLinux/docs/wiki/M1-Series-Feature-Su...
According to this page it should work on M1 MBP, but there is also a note about a specific patch released next week.
-
Sonoma updates bricking MBPs
I'm just refuting that OP's dot update problem on Sonoma was caused by the refresh rate bug. In all likelihood OP doesn't have a weird Sonoma/Ventura dual boot situation going on (or Ashai Linux for that matter, who wrote a great article about this). In all my testing (and with a large enterprise sample size) we had zero reports of the refresh bug impacting an Apple Silicon Mac running just Sonoma itself.
- Speaker Support in Asahi Linux
-
Tuxedo Pulse Gen 3
> They don't support variations of software at all. They support the hardware. [...] Asahi does not need to support applications at all.
From their FAQ page[1]:
> We will eventually release a remix of Arch Linux ARM, packaged for installation by end-users, as a distribution of the same name. The majority of the work resides in hardware support, drivers, and tools, and it will be upstreamed to the relevant projects. The distribution will be a convenient package for easy installation by end-users and give them access to bleeding-edge versions of the software we develop.
As distro maintainers, it is their job to make sure the applications they package work on the hardware they support. This includes submitting patches upstream when that is not the case, as application maintainers likely wouldn't want to support such a niche environment directly. So, yes, they rely on volunteers to fix issues, but they will likely have to support many applications themselves.
There is still a lot of broken software, as this list[2] is surely not exhaustive.
> Same deal for any other hardware manufacturer. [...] Really not much different to other hardware manufacturers since Linux started.
No, it's very different. First of all, the amount of Linux hackers who volunteered to reverse engineer the wide variety of hardware was orders of magnitude larger than the Asahi team. Even if they limit the amount of devices they support, modern computers are far more complex than in the early days of Linux. Regardless of how talented the Asahi team is, maintaining all the hardware of a modern computer is a sisyphean task for a project run by volunteers.
Secondly, hardware manufacturers could see the benefit of getting their hardware to run in Linux, and many eventually took over support from volunteers. Apple has shown no interest in doing so, and has historically been hostile to open source.
> Asahi devs have made it clear that Apple has chosen to avoid blocking installation of other operating systems.
The fact they allow installation of other operating systems today, doesn't mean that this decision couldn't change in the future. Services are a large part of their business, and allowing a group of hackers to use their hardware without being part of their software ecosystem may seem like a non-issue today, but if this group grows larger assuming projects like Asahi are successful, this might become a considerable loss of income which wouldn't be in their best interest.
> Apple has no issue with it.
Can you point me to an official ackgnowledgment of Asahi Linux by Apple? Or any indication that leaving this door open was a sign of good will, instead of a lack of interest in closing it? What makes you think they wouldn't eventually lock down Macbooks in the same way they do iPhones and iPads?
> ARM is a stable well supported platform for Linux
It's really not. A lot of software works, but when it doesn't, the user is SOL. As you can see on their Broken Software page[2], the major issue is precisely with AArch64 support. This should improve eventually, and Asahi is certainly a torchbearer in this scenario, but today it's yet another hurdle of using Apple hardware.
[1]: https://asahilinux.org/about/#is-this-a-linux-distribution
[2]: https://github.com/AsahiLinux/docs/wiki/Broken-Software
- Asahi Linux Team Uncovers macOS Refresh Rate Bugs: Sonoma Boot Failures
-
Update on the Sonoma bug situation
More information about the macOS Sonoma ProMotion bug here.
-
PSA: Don't upgrade to Ventura 13.6+ or Sonoma 14.0+ on Apple Silicon with custom display settings
Here’s the actual issue for anyone that cares, fully documented : https://github.com/AsahiLinux/docs/wiki/macOS-Sonoma-Boot-Failures
zfsbootmenu
-
Bash Debugging
We use a couple nice home-grown functions in ZFSBootMenu to help debug things. We have a zdebug logging function that's peppered liberally throughout the code base - https://github.com/zbm-dev/zfsbootmenu/blob/master/zfsbootme...
Hitting ctrl-t on our main menu will, when booting with debug logging enabled, show a screen like this: https://imgur.com/Ge75zkP
We also have a flamegraph profiling mechanism that can be enabled with https://github.com/zbm-dev/zfsbootmenu/blob/master/zfsbootme... . That will dump data to a serial port, which when re-assembled, can be used to produce a graph like https://raw.githubusercontent.com/zbm-dev/zfsbootmenu/master...
Bash is suprisingly flexible.
-
Pure Bash Bible
A lot of what's in the Pure Bash Bible is horrifically slow. Many of those things are substantially faster, even when paying the cost of starting a new process, when you use an external and commonly available tool. I wrote a bash performance profiler that outputs data in a format that flamegraph.pl recognizes - it really helped identify where we could improve the performance of ZFSBootMenu.
https://github.com/zbm-dev/zfsbootmenu/releases/tag/v1.12.0
Don't fall in the trap of thinking things have to be written entirely in bash; it's okay to use other tools to help fill in the gaps.
-
Some preinstalled options/defaults suggestion
If instead of "opensuse" you're asking for bootloader as grub can't boot from zfs, then, like i metnioned, i don't use grub2, i uninstalled it, instead i'm using https://github.com/zbm-dev/zfsbootmenu
-
ZFSBootMenu how to increase font resolution?
I thought the following was supposed to fix this issue: https://github.com/zbm-dev/zfsbootmenu/commit/84da18e64ebcc0c483e7b2c7d3972f7d91784e63
-
How do I configure the refind.conf and refind_linux.conf (and or config.yaml (for ZFSBootMenu)) files properly when installing Arch Linux with ZFS Native Encryption?
All release assets, including EFI executables and kernel/initramfs pairs, are signed with signify, which provides a simple method for verifying that the contents of the file are as this project intended. Once you've installed signify (that's left as an exercise, although Void Linux provides the signify package for this purpose), just download the desired assets from the ZFSBootMenu release page, download the file sha256.sig alongside it, and run:
-
How to keep Ubuntu from creating a dozen /var subdirectories?
I think the consensus is that you probably shouldn't be installing a ZFS on root using the native installer anymore. They aren't really maintaining the packages that make that work. Instead the suggestion is to go the zfsbootmenu route of installing.
-
Cloned my root dataset and now it won't boot because NTP daemon can't reach time servers
Glad to hear that everything is working for you! I've opened a PR that adds a warning about this condition - it should likely make it into 2.2.0.
-
Ubuntu 23.04 Desktop's New Installer Set To Ship Without OpenZFS Install Support
You can install following instructions at https://openzfs.github.io/openzfs-docs/Getting%20Started/Debian/Debian%20Bullseye%20Root%20on%20ZFS.html which I've automated with https://github.com/HankB/Linux_ZFS_Root/tree/master/Debian. For scripting, you should also look at https://github.com/zbm-dev/zfsbootmenu. I'd probably go that way if I were starting from scratch.
-
Void Linux and root-on-ZFS question
ZBM provides an amazingly useful script in it's wiki here. This runs when a new kernel is updated by xbps and it snapshots your system before the kernel is installed. This creates a boot environment, and via the magic of ZFS boot environments, allows you to rollback any kernel update to a known, working configuration.
-
When root on ZFS breaks on Arch Linux
* https://docs.oracle.com/cd/E86824_01/html/E54764/beadm-1m.ht...
> A ZFS boot environment is a bootable clone of the datasets needed to boot the operating system. Creating a BE before performing an upgrade provides a low-cost safeguard: if there is a problem with the update, the system can be rebooted back to the point in time before the upgrade.
* https://klarasystems.com/articles/managing-boot-environments...
Or perhaps:
> In essence, ZFSBootMenu is a small, self-contained Linux system that knows how to find other Linux kernels and initramfs images within ZFS filesystems. When a suitable kernel and initramfs are identified (either through an automatic process or direct user selection), ZFSBootMenu launches that kernel using the kexec command.
* https://github.com/zbm-dev/zfsbootmenu
What are some alternatives?
idevicerestore - Restore/upgrade firmware of iOS devices
root-on-zfs-systemdboot - Dual-boot Root-on-ZFS config for Debian w/ systemd-boot
tinygrad - You like pytorch? You like micrograd? You love tinygrad! ❤️ [Moved to: https://github.com/tinygrad/tinygrad]
archiso-zfs - Easily load ZFS kernel module on any Archiso.
FEX - A fast usermode x86 and x86-64 emulator for Arm64 Linux
ramroot - Load root file system to ram during boot.
asahi-installer - Asahi Linux installer
dracut - dracut the event driven initramfs infrastructure
AsahiLinux
zectl - ZFS Boot Environment manager for Linux
nixos-apple-silicon - Resources to install NixOS bare metal on Apple Silicon Macs
nonguix