1,122
edits
Preparing your Linux computer for MX: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
Preparing your Linux computer for MX (view source)
Revision as of 20:22, 8 October 2022
, 20:22, 8 October 2022→Installing Mono instruction
mNo edit summary |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 62: | Line 62: | ||
== Checking if mono-complete is in Source List == | == Checking if mono-complete is in Source List == | ||
The "source list" [[#The various components to commands for installation|mentioned | The "source list" [[#The various components to commands for installation|mentioned later]] may not contain all the repositories we need for our installations. | ||
Consequently, [[#The_various_components_to_commands_for_installation|type]] <code>apt search mono-complete</code>, to find out whether the mono package is available from one of the repositories already in our source list, and if the version available is compatible with MX (Release announcements for MX should specify which versions of Mono will work). | Consequently, [[#The_various_components_to_commands_for_installation|type]] <code>apt search mono-complete</code>, to find out whether the mono package is available from one of the repositories already in our source list, and if the version available is compatible with MX (Release announcements for MX should specify which versions of Mono will work). | ||
| Line 109: | Line 109: | ||
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. | 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]: | The latest release of Mono, for a variety of Linux distributions, can always be downloaded from the mono project web site [https://www.mono-project.com/download/stable/#download-lin mono-project.com] (the macOS versions are here [https://www.mono-project.com/download/stable/#download-mac mono-project.com]): | ||
# follow step 1 there, | # follow step 1 there, | ||
# but in step 2 replace ‘’’mono-devel‘’’ by ‘’’mono-complete’’’ | # but in step 2 replace ‘’’mono-devel‘’’ by ‘’’mono-complete’’’ | ||
The complete mono package includes a component (mono-xsp4) that creates a simple web server to run ASP.NET 4.0 applications. MX does not need this, so type <code>sudo update-rc.d mono-xsp4 disable</code>, to stop it being used (without needing to do a <code>sudo apt remove</code> followed by the name of component you no longer want). | The complete mono package includes a component (mono-xsp4) that creates a simple web server to run ASP.NET 4.0 applications. MX does not need this, so type <code>sudo update-rc.d mono-xsp4 disable</code>, to stop it being used (without needing to do a <code>sudo apt remove</code> followed by the name of component you no longer want). | ||
=Moving from Microsoft Windows to Linux= | =Moving from Microsoft Windows to Linux= | ||
| Line 259: | Line 258: | ||
==Package tool== | ==Package tool== | ||
For the purposes of keeping this Wiki page simple, the package manager described | You can add extra programs to your Linux computer. Programs written to run in multiple operating systems are usually downloaded as ''*.tar.gz'' files, although other file compressions may be used (.zip is effectively Windows specific, but as we shall see in [[MX on Linux]] can be used on Linux). Programs written for Linux distributions like "Red Hat", "Fedora", and "centOS" are supplied as ''*.rpm'' files. | ||
For the purposes of keeping this Wiki page simple, the package manager described here is the modern debian one “apt” meaning “Advance Package Tool” e.g. <code>sudo ''apt'' install package_name</code>. | |||
In simple terms, the inclusion of "apt" runs the “package manager” used in Linux. That is certainly true if you use the Raspberry Pi operating system, and it appears it is true for almost all modern Linux operating systems. | In simple terms, the inclusion of "apt" runs the “package manager” used in any modern Linux based on a Debian, or Ubuntu, distribution where programs are written in files ''*.deb''. That is certainly true if you use the Raspberry Pi operating system, and it appears it is true for almost all modern Linux operating systems. | ||
Some online tutorials refer to “apt-get” or "apt-cache" in examples they quote. My online research suggests using those directly is no longer advisable, and therefore you should leave off the part starting with a hyphen, i.e. it should be safe to replace these older package managers with "apt". I have included [[#Package Manager – a brief technical aside|a little technical explanation]] after this subsection, if this really worries you, it appears that in some variants "apt" is just a more user friendly way to call the older package. | Some online tutorials refer to “apt-get” or "apt-cache" in examples they quote. My online research suggests using those directly is no longer advisable, and therefore you should leave off the part starting with a hyphen, i.e. it should be safe to replace these older package managers with "apt". I have included [[#Package Manager – a brief technical aside|a little technical explanation]] after this subsection, if this really worries you, it appears that in some Linux variants "apt" is just a more user friendly way to call the older package. | ||
If you are using an older operating system, it appears the tool available depends on the variant of Unix you have installed. The contributor of this section has done some online research, but is not familiar with all the Unix variants, so other contributors with fuller technical expertise may need to edit this section to make its applicability wider. | If you are using an older operating system, it appears the tool available depends on the variant of Unix you have installed. The contributor of this section has done some online research, but is not familiar with all the Unix variants, so other contributors with fuller technical expertise may need to edit this section to make its applicability wider. | ||
According to online documentation seen, some UNIX variants use | According to online documentation seen, some UNIX variants use '''RPM packets'''. The modern package manager for these is "dnf" and in general you can substitute "dnf" for "apt" in my descriptions. However, there is an older package manager for RPM packets called "zypper", again in general you can replace "apt" in my notes with "zypper" and it should work e.g. <code>sudo zypper install package_name</code>. Other package managers used with "*.rpm" files include 'yum' (standard with "Fedora" distributions) which does not use the same syntax as "apt", and 'rpm' (which can only install packages that are already on your computer but currently dormant) again using a different syntax. | ||
== Package Manager – a brief technical aside== | == Package Manager – a brief technical aside== | ||
