Physics, coding and black metal.

Vyssiikkaa, koodausta ja bläck metallia.

Apparently also politics when it doesn’t devolve into screaming into aether.

  • 0 Posts
  • 7 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle



  • I am placing careful (nevermind that, this seems very nice) interest in this.

    Few questions (since I’m on mobile, and it’ll take me a while to get back to my computer to find out for myself):

    • How does managing sieve work with this?
    • Does it play along with rspamd?
    • Is it tested on x64_64 only?
    • Does it support PGP, can email be encrypted-at-rest using this?
    • Is there a way to run this behind a reverse proxy that handles the certificates? I’m not too keen on dealing with two separate sets of those in separate places.
    • Does this require LDAP?

    If missing, are those on roadmap?



  • I’d recommend going with the vanilla Raspberry Pi OS then. Sure, it’s not as lightweight as one would usually hope from a SBC OS, and it has the usual problems that apt has, but it general, it works. It has the firmware stuff ready, so no hassle with that. It has device trees set up in a generally-usable way from the get go, etc.

    I didn’t go that route myself and spent couple of days trying to get hardware acceleration to work where I wanted with the VideoCore chip, after which I gave up. VideoCore just isn’t that well supported by the general software stacks, but this was a year or so ago, so it might’ve improved.

    Also note that this is all RPi4 specific. Older RPis work quite well.


  • RPi uses a lot of software hacks to get its low-cost hardware running. It is certainly doable on other distros, but using anything but the official ones on RPi is asking for trouble, and you better know how to deal with device trees, etc.

    If you want SBC that is more standard-compliant and has better mainline driver support you should look at e.g. Pine64’s SBCs, such as RockPro64.