5,838
edits
MX on Linux: Difference between revisions
m
no edit summary
mNo edit summary |
|||
|
<big>This page needs further contributions, can you help?</big> It is too Raspberry Pi focused at present.
There is a lot of content on this page, because of requests to cover more, can you redesign this page, with a shorter novice introduction, or can you split it into two pages? Feel free to split it differently, but it needs improvement. Perhaps it needs to be parts 1, 2 and 3, one page for install, another for run, and a final page for tailoring/technical content?
Some of the content was previously separate, on a page for MX generally, but that text had to be moved, with small modifications into this page and also into the Windows page, because it was not exactly same on the two operating systems.
Also the information on moving from Cumulus 1 or from MX on windows, was originally elsewhere, but another contributor added it to this page!
{{Template:WorkInProgressBanner}}
By default, a Linux user should log in as a default user with limited rights.
For example, the Raspberry Pi (Stretch 9, or Buster 10) Operating System has a single default user "
The limited rights mean that a standard user cannot even see (read) some files, cannot execute some commands, and cannot edit (write to) some files. For full access to files, the <code>sudo</code> instruction gives you (just for the command that follows) the same read/write/execute access that the system root user has.
Optionally, read about [https://cumulus.hosiene.co.uk/viewtopic.php?p=107913#p107913 Fine Offset] issues, and the optional symbolic file link instructions (those apply if you only have an earlier libudev shared library version, and wish MX to use that).
== Checking if mono-complete is in Source List ==
The "source list" [[#The various components to commands for installation|mentioned earlier]] may not contain all the repositories we need for our installations.
:Please note that if you just specify “mono”, you will get ‘’’mono-devel’’’ (the developer edition) that does not include all the components required by each of the Cumulus executables.
Please note that a particular MX build might specify it needs a particular version of Mono. Hence, although normally you can upgrade any (CumulusMX.exe, ExportToMySQL.exe, CreateMissing.exe, proposed CreateRecords.exe) cumulus package without upgrading Mono, sometimes you will need to upgrade Mono, and that means following above install instructions again.
The latest release of Mono, for a variety of Linux distributions, can always be downloaded from [https://www.mono-project.com/download/stable/#download-lin]:
Welcome back anybody who has skipped the technical sections above, everybody needs to read this section.
Note use of plural in section name above, the following
==Handling zip files==
#* '''ExportToMySQL.exe''' is not (at the time this was written) documented in this Wiki although [[MX_Administrative_Interface#MySQL_settings]] does describe a similar utility (written by Steve Loft) that was actually included within early CumulusMX zip downloads.
As at 9 March 2020, another utility, '''CreateRecord''', has been initialised in the Github areas managed by the developer where Cumulus is worked on, although it appears to be just a concept
===Alternative download link for older MX releases===
# The new line will then read something like '''ExecStart=/usr/bin/mono-service -d:CHOSEN PATH/CumulusMX CumulusMX.exe -service -debug'''
If you are a technical user, you may want to read the next few
If you are a novice user, then you are advised to skip the technical sub-sections that follow, and proceed directly to numbered steps below that save the file and make it usable by "systemd".
Three
If you already have the file open in an editor because of doing the edits in previous
Otherwise open the file at ''CHOSEN PATH/CumulusMX/MXutils/linux/cumulusmx.service'' using an editor. On a Raspberry Pi, use the file manager to navigate to this file, right click the file named, and select "Geany's Programmers Editor".
| |||