Difference between revisions of "SPO600 Host Setup"
Chris Tyler (talk | contribs) |
Chris Tyler (talk | contribs) |
||
| Line 17: | Line 17: | ||
'''Initial software to install:''' | '''Initial software to install:''' | ||
| − | * Development tools and libraries (on Fedora: <code> | + | * Development tools and libraries (on Fedora: <code>dnf groupinstall "Development Tools" "Development Libraries"</code>). |
* A GUI is optional and may not be required (especially if the system is being accessed remotely). | * A GUI is optional and may not be required (especially if the system is being accessed remotely). | ||
* You may want to consider setting up [[AArch64 QEMU User Space Emulation]]. | * You may want to consider setting up [[AArch64 QEMU User Space Emulation]]. | ||
Revision as of 09:47, 25 November 2016
For SPO600, remote access to Linux systems is provided. Howerver, it is strongly recommended that you have access to a personal x86_64 (64-bit AMD/Intel) system. I recommend running the latest release of Fedora (or, optionally, CentOS).
This system could be set up:
- On your laptop
- As a virtual machine on your laptop
- On a computer at your home, ideally with SSH access (so you can connect to your home system from class)
- On a removable disk pack (note: this is not preferred, because you will not be able to use it during class in the ALC)
You may want to installing virtual machine/emulation/simulation software on this machine, in which case a fast/large system is desirable.
Recommended system configuration (especially if using emulation):
- x86_64 (avoid installing a 32-bit version of the OS or using a 32-bit-only computer)
- Minimum 2GB RAM
- Minumum 50GB disk space
Initial software to install:
- Development tools and libraries (on Fedora:
dnf groupinstall "Development Tools" "Development Libraries"). - A GUI is optional and may not be required (especially if the system is being accessed remotely).
- You may want to consider setting up AArch64 QEMU User Space Emulation.
