@@ -33,6 +33,27 @@ Packages are build and available here: https://github.com/mooltipass/moolticute/
3333 - Requires the qt-dbus module
3434 - Requires to install [ udev rule] ( https://github.com/mooltipass/mooltipass-udev ) for it
3535
36+ Moolticute comes in two part on Linux:
37+ - A daemon that runs in background named moolticuted that proxy
38+ command between device and GUI
39+ - A GUI application for user to interact with the device using moolticuted
40+
41+ One way of using Moolticute is allowing systemd to manage the daemon
42+ as a system service and your desktop environment execing the GUI when
43+ you need it. In such setup it is best to disable the option found in
44+ the GUI called "Start Moolticute with the computer"
45+ The default build recipe will drop a systemd system unit
46+ ` moolticuted.service ` , after build and installation:
47+
48+ ``` bash
49+ systemctl daemon-reload
50+ systemctl enable --now moolticuted.service
51+ ```
52+
53+ At this point the Moolticute daemon should be running. As the build
54+ also drop an ` moolticute.desktop ` you should be able to launch the GUI
55+ using your environment application launcher and searching for "moolticute".
56+
3657##### Ubuntu 16.04
3758``` bash
3859sudo apt install libqt5websockets5-dev qt-sdk qt5-qmake qt5-default libudev-dev
@@ -41,11 +62,10 @@ sudo udevadm control --reload-rules
4162```
4263
4364##### Arch Linux
44- ``` bash
45- sudo pacman -S --needed qt5-websockets qt5-base
46- curl https://raw.githubusercontent.com/mooltipass/mooltipass-udev/master/udev/69-mooltipass.rules | sudo tee /etc/udev/rules.d/69-mooltipass.rules
47- sudo udevadm control --reload-rules
48- ```
65+
66+ There are packages in AUR both for udev rules and for the Moolticute:
67+ - [ udev rules] ( https://aur.archlinux.org/packages/mooltipass-udev/ )
68+ - [ Moolticute] ( https://aur.archlinux.org/packages/moolticute/ )
4969
5070##### Fedora Linux
5171``` bash
0 commit comments