Hi NoisyCoil,
Hi David,
> Again, I'd encourage this work to *also* keep an eye to long-term
implementation
> on Raspberry Pis. Pis are widely available and inexpensive, so
supporting them
I agree fully. Apples M's have been an important step for arm
architectures to move away from iot and smartphones. But unlike Apples M
architecture, the RPi's must not be patched to boot a different os.
Boards like RPi5 (Rock's, Hardkernel's, Banana's) are cheaper then
Apples M's.
NoisyCoil asked
> I have one question for the Tails developers/infra maintainers.
> Is there any chance Tails could provide time-based and tagged
From my point of view - that's also one of the biggest issue towards an
RPi5 image.
The last weeks I worked to buld a Trixe ARM64 for RPi5 on a RPi5 based
on NoisyCoil's repo and branch wip/triie/raspi, see my fork
https://gitlab.tails.boum.org/N9iu7pk/rpi-5 from NoisyCoil, branch
wip/triie/raspi, commit
https://gitlab.tails.boum.org/N9iu7pk/rpi-5/-/commit/31275aaee7ef1af2677b10effa75cf89c9df5640
(not public, you must be logged in)
It's possible to build images for a RPi5 on a RPi5. The image boots
(efi) but currently fails to find the live partition (initram stage).
It is a very experimental build and should only be used for development
purposes:
- to get arm64/aarch64 packages NoisyCoil's patch/hack (nginx reverse
proxy) was used twice: On the buld "machine" (RPi5) as well as inside of
the building virtual machine.
- due to this "hack" apt_cache-ng can't be used, the rake build must be
started with export TAILS_BUILD_OPTIONS="noproxy"
- a newer version of NoisyCoils Tor browser was needed (as 14.5.7 wasn't
available any more)
- follow the changes in the commit ...
I'll provide soon short doc/info for #10972 and try to solve the boot
problem.
Regards N9iu7pk
PGP 7426 4598 B5AD 4D12 1699 C710 [ D602 E331 4D12 FFCB ]
https://keys.openpgp.org/search?q=D602E3314D12FFCB
On 1/14/26 22:22, David A. Wheeler via Tails-dev wrote:
>
>> On Jan 14, 2026, at 7:07 AM, intrigeri <intrigeri@???> wrote:
>>
>> Hi NoisyCoil,
>>
>> Sorry for the delay! As you'll see below, there was no quick and easy
>> answer to your questions.
>
> I'm delighted to see some efforts that might lead to Tails on Apple silicon.
>
> Again, I'd encourage this work to *also* keep an eye to long-term implementation
> on Raspberry Pis. Pis are widely available and inexpensive, so supporting them
> would make sense. Since they *also* use ARM chips, much of the same work would apply.
> Basically, as changes are made, try to support them as well where
> it's easy (and document where it isn't). I'm aware there are few longer-pole
> issues in progress for both Apple Silicon & Raspberry PIs.
> My hope is that as they get resolved, the rest will more easily slide into place.
> Also, taking steps for similar platforms may mean that if you get
> stuck on one, you can can still complete the other.
>
> I wish good luck to all involved.
>
> --- David A. Wheeler
> _______________________________________________
> Tails-dev mailing list
> Tails-dev@???
> https://www.autistici.org/mailman/listinfo/tails-dev
> To unsubscribe from this list, send an empty email to Tails-dev-unsubscribe@???.
