mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Enrico Joerns <ejo@pengutronix.de>
To: Djalal Harouni <tixxdz@opendevices.io>
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] Rauc in Commercial Product - Open Devices
Date: Mon, 1 Oct 2018 14:50:33 +0200	[thread overview]
Message-ID: <95e65bc4-a2be-fdf6-5573-6c420d07f0b3@pengutronix.de> (raw)
In-Reply-To: <CAO5TF-Bz+sXGPosppoRKt=TCJurrdypu46z3WQaVnb4JoqtcGA@mail.gmail.com>

Hi Dajalal,

On 10/1/18 12:33 PM, Djalal Harouni wrote:
> Hi Rauc hackers, Pengutronix,
> 
> I am Djalal Harouni I met you guys at several conferences, I am one of
> the maintainers of systemd project, linux kernel security contributor
> etc.
> 
> We did launch a startup in Berlin opendevices.io/ and we are going to
> announce a beta version of our IoT Platform that targets Linux IoT
> Devices. I have a hacky system updater experimental based on scripts,
> but we are planning to use Rauc in our production solution.

sounds like a good plan to replace your script-based solution with RAUC ;)

> I see that Rauc is under LPGL where we can use it, but as an Open
> Source Software Developer, I have to inform you before. If our
> business succeed, we may contribute patches back and even maybe
> finance and help Rauc, as right now and unless you do not agree, our
> long-term plan for system updates will be based solely on Rauc!  We
> will produce updates, host them using simple nginx solution and
> distribute notification and bundles using one of our agents, then
> apply with Rauc. I think that should work.
> 
> Please if you have any comment or note do not hesitate!

There is really nothing that forces you to inform us when you plan to use RAUC in a product.
Anyway, great for us to hear that you plan to do and personally I am always interested in which fields of application RAUC is used and where it helps people to ease and secure their device updates.

We really appreciate contribution of features you were missing or any other support.
This always adds a benefit on both sides.

> The only thing that I can say: thank you for producing such robust
> Software and making it Open Source!
> 
> Much appreciated!

Thank you very much and the best wishes for your business.


Best regards

Enrico

-- 
Pengutronix e.K.                           | Enrico Jörns                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


_______________________________________________
RAUC mailing list

      reply	other threads:[~2018-10-01 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 10:33 Djalal Harouni
2018-10-01 12:50 ` Enrico Joerns [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=95e65bc4-a2be-fdf6-5573-6c420d07f0b3@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=rauc@pengutronix.de \
    --cc=tixxdz@opendevices.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox