mirrors/buildroot
0
0
Fork 0
mirror of https://git.busybox.net/buildroot.git synced 2024-11-23 13:33:28 +08:00
Code Issues Packages Projects Releases Wiki Activity
a30d577a4b
buildroot/package/mender
History
Angelo Compagnucci 097e85abfc package/mender: fixing init script naming 
Commit f88947c2fe (package/mender: adding systemv init file) added an init
script, but the installation logic referred to S04mender instead of S42mender.

Update the installation logic to match the file name.

Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
[Peter: expand commit message description]
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-02-05 15:37:05 +01:00
..
artifact_info package/mender: adding artifact_info file 2019-02-05 14:08:47 +01:00
Config.in
device_type package/mender: adding device_type file 2019-02-05 14:09:17 +01:00
mender.conf
mender.hash package/mender: bump version to 1.7.0 2018-12-26 22:33:27 +01:00
mender.mk package/mender: fixing init script naming 2019-02-05 15:37:05 +01:00
mender.service package/mender: adding a writable location 2019-02-05 13:40:10 +01:00
readme.txt package/mender: adding a readme file 2019-02-05 14:09:36 +01:00
S42mender package/mender: adding systemv init file 2019-02-05 13:45:07 +01:00
server.crt

readme.txt 

=== Notes on using Mender on Buildroot
======================================
Default configurations files
----------------------------

Buildroot comes with a default artifact_info and device_type configuration files
in /etc/mender. They contain default values, and thus they should be overridden
on a production system.

The simplest way to do it is to change these files in an overlay or in a post
build script.

Configuring mender with certificates
------------------------------------

Mender uses TLS to communicate with the management server, and if you use a
CA-signed certificate on the server, you should select the ca-certificates
package otherwise it doesn't work.