mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Andreas Kurzkurt <Kurzkurt@m-tronic-dt.de>
To: Enrico Joerns <ejo@pengutronix.de>
Cc: "rauc@pengutronix.de" <rauc@pengutronix.de>
Subject: Re: [RAUC] Porting RAUC to OpenWRT
Date: Mon, 10 Dec 2018 13:17:38 +0000	[thread overview]
Message-ID: <c2994c78af534b58b9a7274f73ae8f12@m-tronic-dt.de> (raw)
In-Reply-To: <d6e955db-7a94-93df-8fa2-1de8ebb1d08a@pengutronix.de>

Hi Enrico

As far as we can see now the RAUC client is working OK.
Thanks for your help. Maybe we have further questions in the future.

Best regards
Andreas

-----Ursprüngliche Nachricht-----
Von: RAUC [mailto:rauc-bounces@pengutronix.de] Im Auftrag von Enrico Joerns
Gesendet: Freitag, 7. Dezember 2018 13:48
An: Andreas Kurzkurt
Cc: rauc@pengutronix.de
Betreff: Re: [RAUC] Porting RAUC to OpenWRT

Hi Andreas,

(please keep the list in CC)

On 12/7/18 1:18 PM, Andreas Kurzkurt wrote:
> Hi Enrico
> 
> Now we are one big step ahead. We managed to compile the RAUC client.
> But now we get an error message when we start the RAUC client.
> Our Linux Distribution has no Systemd. The RAUC client should run without systemd.
> We also managed to install DBUS on our linux system.
> 
>> rauc -c /etc/rauc/rauc.conf status
> Failed to resolve realpath for '/dev/nfs'

ok, thus this is an NFS boot?
RAUC should be able to detect NFS boots and handle properly.
Which version do you use?

> Failed to obtain name de.pengutronix.rauc

Did you start the service before, too?
Are you sure it is compiled with D-Bus support?

Not that this mainly needs the configuration file.
At least with 1.0-rc1 the client will fully communicate over D-Bus.

Normally this can be done using D-Bus activation. We have Make source files for this in the data/ folder.
Calling `make install` should place all this files properly with the right content set.

Maybe it's also worth looking at what build systems do with it, such as Yocto / OE or PTXdist.

We mainly use systemd for testing, but InitV is basically supported, too.

> 
> Our config file is:
> [system]
> compatible=rauc-demo-x86
> bootloader=uboot
> mountprefix=/mnt/rauc
> 
> [keyring]
> path=demo.cert.pem
> 
> [slot.rootfs.0]
> device=/dev/mtdblock3
> type=ubifs
> bootname=A
> 
> [slot.rootfs.1]
> device=/dev/mtdblock5
> type=ubifs
> bootname=B


The config looks fine basically and should have nothing to do with the issues you see.


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
_______________________________________________
RAUC mailing list

  reply	other threads:[~2018-12-10 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 13:45 Andreas Kurzkurt
2018-12-06 14:00 ` Enrico Joerns
     [not found]   ` <5adce2d88bac42bc9ac4f713554573f6@m-tronic-dt.de>
2018-12-06 14:17     ` Enrico Joerns
     [not found]       ` <89a7cd07207b4d318aa55628f177f3c0@m-tronic-dt.de>
2018-12-07 12:48         ` Enrico Joerns
2018-12-10 13:17           ` Andreas Kurzkurt [this message]
2018-12-10 13:22             ` Enrico Joerns

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=c2994c78af534b58b9a7274f73ae8f12@m-tronic-dt.de \
    --to=kurzkurt@m-tronic-dt.de \
    --cc=ejo@pengutronix.de \
    --cc=rauc@pengutronix.de \
    /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