mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-08-01 21:23:51 -09:00
9320989053
The logic behind making /var/lib/mender a symlink to itself is to
detect if a filesystem is read-only. However, this creates a few problems:
1) The logic confusing.
2) The official mender documentation suggests four partitions minimum:
- boot
- rootfs A
- rootfs B
- data
If a user is to follow the official documentation, which they should,
then there is no need for any additional logic for a system setup with
a read-only filesystem, as the data partition is always read-write.
3) The post-build.sh script in the board/mender/x86_64 directory removes
the symlink.
- Remove symlinking /var/lib/mender to itself
- Remove the difficult to understand logic dealing with the symlinks
in S42mender, mender-client.service.
- Remove the logic dealing with the symlink in
board/mender/x86_64/post-build.sh
Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
14 lines
206 B
Desktop File
14 lines
206 B
Desktop File
[Unit]
|
|
Description=Mender OTA update service
|
|
After=systemd-resolved.service
|
|
|
|
[Service]
|
|
Type=idle
|
|
User=root
|
|
Group=root
|
|
ExecStart=/usr/bin/mender daemon
|
|
Restart=on-abort
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|