5,838
edits
MX on Linux: Difference between revisions
m
→Preparing for an install: Correction of another contributor's edit that made all commands run together
m (→install: Correction) |
m (→Preparing for an install: Correction of another contributor's edit that made all commands run together) |
||
| Line 173: | Line 173: | ||
Before we do an install of a new package, we typically use this series of commands to ensure our computer is in the best state to work out dependencies of what we are about to install: | Before we do an install of a new package, we typically use this series of commands to ensure our computer is in the best state to work out dependencies of what we are about to install: | ||
<code> | |||
sudo apt update | :<code>sudo apt update</code> | ||
sudo apt -y upgrade | |||
sudo apt autoremove | :<code>sudo apt -y full-upgrade</code> | ||
</code> | |||
Each of those can be understood from information in previous section. | :<code>sudo apt autoremove</code> | ||
Each of those can be understood from information in [[#install|previous section]]. | |||
If you are installing onto a Pi zero, or similar slow computer, please ensure the size of the swapfile is as big as possible, as the mono-complete we will install is large. In linux, we type <code>free -m</code> to see our RAM size and our swapfile size. | If you are installing onto a Pi zero, or similar slow computer, please ensure the size of the swapfile is as big as possible, as the mono-complete we will install is large. In linux, we type <code>free -m</code> to see our RAM size and our swapfile size. | ||