linux-surface/contrib
Nicola Fiori aedbc17ecc
Replace suggestion of using systemctl edit
Editing `ExecStart=` with `systemctl edit` did
not work for me. Running
`systemctl restart thermald.service` afterwards
was giving errors every time with reason "Unit
thermald.service has a bad unit file setting".

By running `systemctl status thermald.service`,
I was reading this error:

    redis.service has more than one ExecStart=
    setting, which is only allowed for
    Type=oneshot services. Refusing.

By looking through the Internet for answers,
I found a suggestion from a user saying that
"The `ExecStart=` line cannot be modified with
`systemctl edit`"
(https://unix.stackexchange.com/questions/409354).

What worked was replacing the thermald.service file
directly to `/etc/systemd/system/` and
`/usr/lib/systemd/system` worked, as suggested
in the README.md present in the folder containing
example configurations for Surface Pro 5 from
this repository.
2022-10-20 18:19:24 +01:00
..
fedora-default-kernel contrib: Add Fedora default-kernel scripts 2021-04-20 18:37:47 +02:00
rotate-screen Adds MIT license to the rotate-screen script. 2021-11-28 13:05:49 +00:00
thermald Replace suggestion of using systemctl edit 2022-10-20 18:19:24 +01:00
README.md Add contrib directory 2021-04-20 15:48:26 +02:00

Scripts, Tweaks, and Configuration Bits

This directory contains scripts, tweaks, and configuration examples aiming to improve your Linux experience on Surface devices. Any config files in these directories should be treated as examples and basis for adapting your own config files. Feel free to send us a pull-request if you feel that something is missing or can be improved.

Layout and Structure

Entries should be put into individual directories with a README.md. This readme should state the purpose of that tweak/script and, if there are any config files, where those files should be placed (or any other installation instructions and hints). Ideally, it should, for config files, also give an explanation of what is/has to be changed and why. In general, config files should be kept minimal, if possible contain comments, and users should be encouraged to modify their config file instead of simply copying the one provided.

The overall structure should look something like this:

contrib
 │
 ├─ some-script
 │ ├─ the-script.sh
 │ └─ README.md
 │
 └─ some-tweak
   ├─ a.conf
   ├─ b.conf
   └─ README.md