-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rasberry PI (RPI) support #114
Comments
Oh nice, sounds great and I'd definitely welcome to support that. :) |
Using qemu-debootstrap and skipping the installation of grub are the most important parts to build the image for the rpi. At least in this case a raw arm64 (and likely also other architectures) image can be build. The fsck step was not required. But I guess it can be put in again. |
JFTR, vmdb2 was orphaned "recently": https://tracker.debian.org/news/1004074/accepted-vmdb2-0132-2-source-all-into-unstable/ Is there any news from your side regarding buster support, @adrelanos + @Algernon-01? |
I don't know much about it. vmdb2 seems back to life? trixie has a newer version of vmdb2. Potentially useful packages:
It might be possible to extract the required packages, build commands from here somewhere:
Needless to say that his is non-trivial. This is the most comprehensive overview of different boot methods that I have found so far: |
It's possible.
@Algernon-01 managed to implement it in @Whonix which is using grml-debootstrap. (https://github.com/Whonix/Whonix/pull/419)
In essence if I did not overlook something - deduction from theory (code reading):
export DEBOOTSTRAP='qemu-debootstrap'
export FSCK='no'
(?) (Maybe @Algernon-01 can explain?)Would be cool if grml-debootstrap supported RPI out of the box.
The text was updated successfully, but these errors were encountered: