home.social

#rauc — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rauc, aggregated by home.social.

  1. Brand in Stuttgart-Bad Cannstatt: Feuer bricht in Hochhaus aus – zwölf Menschen verletzt

    Die Feuerwehr rettete zwei Bewohner über eine Drehleiter. Foto: Blaulichtzentrale.de / Alexander Hald In der Nacht zum Mittwoch bricht…
    #Stuttgart #Deutschland #Deutsch #DE #Schlagzeilen #Headlines #Nachrichten #News #Europe #Europa #EU #Baden-Württemberg #Brand #evakuiert #Feuer #Feuerwehr #Germany #hoch #PolizeiberichtStuttgart #Rauc #Stuttgart-BadCannstatt
    europesays.com/de/199288/

  2. #news ⚡ Grüne wollen auch in Deutschland Rauchverbot an öffentlichen Orten: Das angekündigte Rauchverbot an öffentlichen Orten in Frankreich sollte nach dem Willen der Grünen auch in Deutschland gelten.Der gesu... hubu.de/?p=280565 | #deutschland #gruene #orten #rauc

  3. #news ⚡ Grüne wollen auch in Deutschland Rauchverbot an öffentlichen Orten: Das angekündigte Rauchverbot an öffentlichen Orten in Frankreich sollte nach dem Willen der Grünen auch in Deutschland gelten.Der gesu... hubu.de/?p=280565 | #deutschland #gruene #orten #rauc

  4. #news ⚡ Grüne wollen auch in Deutschland Rauchverbot an öffentlichen Orten: Das angekündigte Rauchverbot an öffentlichen Orten in Frankreich sollte nach dem Willen der Grünen auch in Deutschland gelten.Der gesu... hubu.de/?p=280565 | #deutschland #gruene #orten #rauc

  5. 📣 RAUC & labgrid community meetup at 2024 in Nürnberg.

    📅 Date: Wednesday, April 10th
    🕒 Time: 14:30 - 15:30
    📍 Location: Cafe in Hall 4, located at 4-640a

    Join us for a casual gathering to talk about these open-source projects. It's a good opportunity to meet fellow developers and users in the & communities, exchange ideas, and discuss future directions.

    No need to RSVP—just come by if you're interested. See you at !

    @labgrid @rauc

  6. 📣 RAUC & labgrid community meetup at #embeddedworld 2024 in Nürnberg.

    📅 Date: Wednesday, April 10th
    🕒 Time: 14:30 - 15:30
    📍 Location: Cafe in Hall 4, located at 4-640a

    Join us for a casual gathering to talk about these open-source projects. It's a good opportunity to meet fellow developers and users in the #labgrid & #RAUC communities, exchange ideas, and discuss future directions.

    No need to RSVP—just come by if you're interested. See you at #ew24!

    @labgrid @rauc

  7. 📣 RAUC & labgrid community meetup at #embeddedworld 2024 in Nürnberg.

    📅 Date: Wednesday, April 10th
    🕒 Time: 14:30 - 15:30
    📍 Location: Cafe in Hall 4, located at 4-640a

    Join us for a casual gathering to talk about these open-source projects. It's a good opportunity to meet fellow developers and users in the #labgrid & #RAUC communities, exchange ideas, and discuss future directions.

    No need to RSVP—just come by if you're interested. See you at #ew24!

    @labgrid @rauc

  8. 📣 RAUC & labgrid community meetup at #embeddedworld 2024 in Nürnberg.

    📅 Date: Wednesday, April 10th
    🕒 Time: 14:30 - 15:30
    📍 Location: Cafe in Hall 4, located at 4-640a

    Join us for a casual gathering to talk about these open-source projects. It's a good opportunity to meet fellow developers and users in the #labgrid & #RAUC communities, exchange ideas, and discuss future directions.

    No need to RSVP—just come by if you're interested. See you at #ew24!

    @labgrid @rauc

  9. 📣 RAUC & labgrid community meetup at #embeddedworld 2024 in Nürnberg.

    📅 Date: Wednesday, April 10th
    🕒 Time: 14:30 - 15:30
    📍 Location: Cafe in Hall 4, located at 4-640a

    Join us for a casual gathering to talk about these open-source projects. It's a good opportunity to meet fellow developers and users in the #labgrid & #RAUC communities, exchange ideas, and discuss future directions.

    No need to RSVP—just come by if you're interested. See you at #ew24!

    @labgrid @rauc

  10. I just released version 0.2.0 of #caterpillar, my little application, wrapping around #rauc for system updates on e.g. embedded platforms using attached media.

    The application now exposes its own #dbus interface, which can be used for interactive workflows. The non-interactive use-case on first start is still the default (but can be turned off).

    The documentation has been extended as well, to describe these new features.

    crates.io/crates/caterpillar

    #rustlang #linux #update

  11. I just released version 0.2.0 of #caterpillar, my little application, wrapping around #rauc for system updates on e.g. embedded platforms using attached media.

    The application now exposes its own #dbus interface, which can be used for interactive workflows. The non-interactive use-case on first start is still the default (but can be turned off).

    The documentation has been extended as well, to describe these new features.

    crates.io/crates/caterpillar

    #rustlang #linux #update

  12. I just released version 0.2.0 of #caterpillar, my little application, wrapping around #rauc for system updates on e.g. embedded platforms using attached media.

    The application now exposes its own #dbus interface, which can be used for interactive workflows. The non-interactive use-case on first start is still the default (but can be turned off).

    The documentation has been extended as well, to describe these new features.

    crates.io/crates/caterpillar

    #rustlang #linux #update

  13. I just released version 0.2.0 of #caterpillar, my little application, wrapping around #rauc for system updates on e.g. embedded platforms using attached media.

    The application now exposes its own #dbus interface, which can be used for interactive workflows. The non-interactive use-case on first start is still the default (but can be turned off).

    The documentation has been extended as well, to describe these new features.

    crates.io/crates/caterpillar

    #rustlang #linux #update

  14. I just released version 0.2.0 of #caterpillar, my little application, wrapping around #rauc for system updates on e.g. embedded platforms using attached media.

    The application now exposes its own #dbus interface, which can be used for interactive workflows. The non-interactive use-case on first start is still the default (but can be turned off).

    The documentation has been extended as well, to describe these new features.

    crates.io/crates/caterpillar

    #rustlang #linux #update

  15. I created a tool for automatically discovering and installing #RAUC update bundles from attached block devices: crates.io/crates/caterpillar

    I just released 0.1.0 as a first version with a very small set of features, but I'm really glad it is finally out there!

    Big thanks go out to #nonlinearlabs for being so patient with this project and funding the work!
    If you're into #synthesizer hardware you should check them out:
    nonlinear-labs.de/

    #rustlang #embedded #linux #boot #update #udisks2 #dbus

  16. I created a tool for automatically discovering and installing #RAUC update bundles from attached block devices: crates.io/crates/caterpillar

    I just released 0.1.0 as a first version with a very small set of features, but I'm really glad it is finally out there!

    Big thanks go out to #nonlinearlabs for being so patient with this project and funding the work!
    If you're into #synthesizer hardware you should check them out:
    nonlinear-labs.de/

    #rustlang #embedded #linux #boot #update #udisks2 #dbus

  17. I created a tool for automatically discovering and installing #RAUC update bundles from attached block devices: crates.io/crates/caterpillar

    I just released 0.1.0 as a first version with a very small set of features, but I'm really glad it is finally out there!

    Big thanks go out to #nonlinearlabs for being so patient with this project and funding the work!
    If you're into #synthesizer hardware you should check them out:
    nonlinear-labs.de/

    #rustlang #embedded #linux #boot #update #udisks2 #dbus

  18. I created a tool for automatically discovering and installing #RAUC update bundles from attached block devices: crates.io/crates/caterpillar

    I just released 0.1.0 as a first version with a very small set of features, but I'm really glad it is finally out there!

    Big thanks go out to #nonlinearlabs for being so patient with this project and funding the work!
    If you're into #synthesizer hardware you should check them out:
    nonlinear-labs.de/

    #rustlang #embedded #linux #boot #update #udisks2 #dbus

  19. I created a tool for automatically discovering and installing #RAUC update bundles from attached block devices: crates.io/crates/caterpillar

    I just released 0.1.0 as a first version with a very small set of features, but I'm really glad it is finally out there!

    Big thanks go out to #nonlinearlabs for being so patient with this project and funding the work!
    If you're into #synthesizer hardware you should check them out:
    nonlinear-labs.de/

    #rustlang #embedded #linux #boot #update #udisks2 #dbus

  20. Dug my way into a deep rabbithole last night, while working on an A/B update system based on #RAUC .
    Turns out #efibootmgr 18 changed its default output to be more verbose and broke the assumptions made by #RAUC

    Patching up a C codebase was not on my list of things for last night, but alas, here we are:
    github.com/rauc/rauc/pull/1197

  21. Dug my way into a deep rabbithole last night, while working on an A/B update system based on #RAUC .
    Turns out #efibootmgr 18 changed its default output to be more verbose and broke the assumptions made by #RAUC

    Patching up a C codebase was not on my list of things for last night, but alas, here we are:
    github.com/rauc/rauc/pull/1197

  22. Dug my way into a deep rabbithole last night, while working on an A/B update system based on #RAUC .
    Turns out #efibootmgr 18 changed its default output to be more verbose and broke the assumptions made by #RAUC

    Patching up a C codebase was not on my list of things for last night, but alas, here we are:
    github.com/rauc/rauc/pull/1197

  23. Dug my way into a deep rabbithole last night, while working on an A/B update system based on #RAUC .
    Turns out #efibootmgr 18 changed its default output to be more verbose and broke the assumptions made by #RAUC

    Patching up a C codebase was not on my list of things for last night, but alas, here we are:
    github.com/rauc/rauc/pull/1197

  24. Dug my way into a deep rabbithole last night, while working on an A/B update system based on #RAUC .
    Turns out #efibootmgr 18 changed its default output to be more verbose and broke the assumptions made by #RAUC

    Patching up a C codebase was not on my list of things for last night, but alas, here we are:
    github.com/rauc/rauc/pull/1197

  25. I've released #golang #rauc go-rauc library version v0.2.1, with support for writing custom pre and post install handlers, as well as for the handler-to-rauc messaging protocol.

    pkg.go.dev/gitlab.com/zygoon/g

  26. I've released go-rauc library version v0.2.1, with support for writing custom pre and post install handlers, as well as for the handler-to-rauc messaging protocol.

    pkg.go.dev/gitlab.com/zygoon/g

  27. I've released #golang #rauc go-rauc library version v0.2.1, with support for writing custom pre and post install handlers, as well as for the handler-to-rauc messaging protocol.

    pkg.go.dev/gitlab.com/zygoon/g

  28. I've released #golang #rauc go-rauc library version v0.2.1, with support for writing custom pre and post install handlers, as well as for the handler-to-rauc messaging protocol.

    pkg.go.dev/gitlab.com/zygoon/g

  29. Yep, turns out you currently can't sign #rauc update bundles with ed25519 keys, but the error message is quite misleading imho. No mention of unsupported key algorithms only a vague mention of "mismatched keys". With RSA4096 keys everything suddenly works as expected.

  30. Yep, turns out you currently can't sign #rauc update bundles with ed25519 keys, but the error message is quite misleading imho. No mention of unsupported key algorithms only a vague mention of "mismatched keys". With RSA4096 keys everything suddenly works as expected.

  31. Yep, turns out you currently can't sign #rauc update bundles with ed25519 keys, but the error message is quite misleading imho. No mention of unsupported key algorithms only a vague mention of "mismatched keys". With RSA4096 keys everything suddenly works as expected.

  32. Yep, turns out you currently can't sign #rauc update bundles with ed25519 keys, but the error message is quite misleading imho. No mention of unsupported key algorithms only a vague mention of "mismatched keys". With RSA4096 keys everything suddenly works as expected.

  33. Hmm, is it possible that #rauc doesn't support ed25519 for signing update bundles and I have to recreate my whole CA for update signing with RSA? #linuxembedded #linux

  34. Hmm, is it possible that #rauc doesn't support ed25519 for signing update bundles and I have to recreate my whole CA for update signing with RSA? #linuxembedded #linux

  35. Hmm, is it possible that #rauc doesn't support ed25519 for signing update bundles and I have to recreate my whole CA for update signing with RSA? #linuxembedded #linux

  36. Hmm, is it possible that #rauc doesn't support ed25519 for signing update bundles and I have to recreate my whole CA for update signing with RSA? #linuxembedded #linux

  37. Hmm, #rauc seems really great, but there seems to be not much open source stuff around to actually identify updated bundles on a remote server. Might need to build a small tool checking github (gitea) releases for compatible updates #embedded #linux

  38. Hmm, #rauc seems really great, but there seems to be not much open source stuff around to actually identify updated bundles on a remote server. Might need to build a small tool checking github (gitea) releases for compatible updates #embedded #linux

  39. Hmm, #rauc seems really great, but there seems to be not much open source stuff around to actually identify updated bundles on a remote server. Might need to build a small tool checking github (gitea) releases for compatible updates #embedded #linux

  40. Hmm, #rauc seems really great, but there seems to be not much open source stuff around to actually identify updated bundles on a remote server. Might need to build a small tool checking github (gitea) releases for compatible updates #embedded #linux

  41. Finally got #rauc based updates working on my #craftbeerpi firmware. Now doing some quality of life improvements for users and then I will probably try to create something which can feed GitHub-Releases to rauc, essentially using GitHub as an update server for my #buildroot based firmware.

  42. Finally got #rauc based updates working on my #craftbeerpi firmware. Now doing some quality of life improvements for users and then I will probably try to create something which can feed GitHub-Releases to rauc, essentially using GitHub as an update server for my #buildroot based firmware.

  43. Finally got #rauc based updates working on my #craftbeerpi firmware. Now doing some quality of life improvements for users and then I will probably try to create something which can feed GitHub-Releases to rauc, essentially using GitHub as an update server for my #buildroot based firmware.

  44. And back to #rauc and #uboot .

    Let's get a custom build done today!

  45. And back to #rauc and #uboot .

    Let's get a custom build done today!