MapToolOS: Difference between revisions
(Created page with "=MapToolOS= Ready to use Linux images preconfigured to run MapTool. These are community maintained images, designed to get up and running with maptool quickly, and uniformly....") |
No edit summary |
||
| Line 27: | Line 27: | ||
* P: maptool@maptool | * P: maptool@maptool | ||
* Root: root@maptool | * Root: root@maptool | ||
If you want to use the whole area of a larger-than-4gb flash drive, there are two steps. | |||
First, use parted to change the second partition to use the whole drive. (You will need to determine which drive is your root drive, which you can do by running <code>mount | grep btrfs</code>. Look for the entry mounted on <code>/</code>. If that reads <code>/dev/sda2</code> than your root device is <code>/dev/sda</code> | |||
<code> | |||
su -c "parted /dev/$root" | |||
resizepart 2 100% | |||
q | |||
</code> | |||
Then reboot. The second step requires resizing the live btrfs filesystem. | |||
<code> | |||
btrfs filesyste resize max / | |||
</code> | |||
This does not require a reboot. | |||
Updating the installed image will require a larger disk (8GB minimum), and rolling back some space saving USE flags. The basic sequence to update packages is as follow. | Updating the installed image will require a larger disk (8GB minimum), and rolling back some space saving USE flags. The basic sequence to update packages is as follow. | ||
Revision as of 16:31, 16 August 2021
MapToolOS
Ready to use Linux images preconfigured to run MapTool.
These are community maintained images, designed to get up and running with maptool quickly, and uniformly. For support, come ask in Discord.
Installation
Download the disk image file for the image you want to run. It can be extracted via 7zip or similar unarchiving tool. If you are going to run it via a Virtual Machine (VM), just point your VM software at the extracted disk image, and select the correct boot type (UEFI vs legacy). To run from a USB drive, a tool like balenaEtcher can write the image to a drive. Minimum drive sizes, CPU type, and other requirements are listed in each image's section.
Flashing an image file to a USB drive (or other drive) will erase and reformat the drive!
GenTool
Based on Gentoo Linux, this boots to a KDE/plasma or XFCE desktop, with a fairly comprehensive list of installed utilities (the core KDE meta packages).
Requirements
- 4GB or larger drive (16GB recommended)
- 1 GB RAM (2GB strongly recommended)
- x86_64 CPU with AVX2 (Intel Haswell or newer, or AMD Excavator or newer)
- UEFI based boot
If it fails to boot to GRUB, verify your bios is set to boot either to UEFI or UEFI+legacy.
Notes
- New binary package updates roughly weekly
- Username: maptool
- P: maptool@maptool
- Root: root@maptool
If you want to use the whole area of a larger-than-4gb flash drive, there are two steps.
First, use parted to change the second partition to use the whole drive. (You will need to determine which drive is your root drive, which you can do by running mount | grep btrfs. Look for the entry mounted on /. If that reads /dev/sda2 than your root device is /dev/sda
su -c "parted /dev/$root"
resizepart 2 100%
q
Then reboot. The second step requires resizing the live btrfs filesystem.
btrfs filesyste resize max /
This does not require a reboot.
Updating the installed image will require a larger disk (8GB minimum), and rolling back some space saving USE flags. The basic sequence to update packages is as follow.
eix-sync && emerge --update -avbkg1 --deep --newuse --with-bdeps=y --usepkgonly --autounmask @world
It will offer to make some mask or USE changes. Hit yes, then run
dispatch-conf
to review the changes. Y will accept the changes, then re-run the first command.
GenTool - Minimal
Based on GenTool, with fewer packages, and with some core files removed. Same requirements as GenTool, except it will fit on a 2GB drive, and is half the download size. Due to the removed files, updating this image is not supported, and some normal Linux features may behave oddly (or be missing). It is possible to convert it to a normal image, by downloading the second file, mounting it under linux, and copying the files to the root partition (cp -ra $mount_point/* /).