1,885
edits
Changes
→Sudo Access
== Available Servers ==
{{Admon/important|Server Changes for Fall 2019|The server configuration for Fall 2019 has configurations have changed several times changed -- previous mentions of these systems by name may have referred to different hardware. Note that additional servers may be added or removed as the semester proceeds.}}
=== AArch64: aarchie ===
A main AArch64 system is available, known as''aarchie''. This machine has a lot of weak cores. You can access this system at the hostname aarchie.cdot.systems; if you're using a command-line ssh system, you can access aarchie with a command such as this:
ssh ''username''@aarchie.cdot.systems
=== AArch64: bbetty ===
If you're using a command-line ssh system, you can issue a command such as this:
ssh -p 2200 ''username''@ehl.cdot.systems
=== AArch64: ccharlie ===
Another AArch64 system similar to bbetty is named ''ccharlie''. This is a system that is currently located inside the [[EHL]]. To connect to this system, you have to go through the EHL gateway on port 2205.
If you're using a command-line ssh system, you can issue a command such as this:
ssh -p 2205 ''username''@ehl.cdot.systems
=== AArch64: israel ===
A different AArch64 system is ''israel''. This machine has a good number of mid-level cores. This system is located outside of the EHL and can be reached directly:
ssh ''username''@israel.cdot.systems
user "YourUserID"
port 2200
Host "ccharlie"
hostname "ehl.cdot.systems"
user "YourUserID"
port 2205
Host "israel"
hostname "israel.cdot.systems"
user "YourUserID"
Host "xerxes"
ssh aarchie
ssh bbetty
ssh ccharlie ssh israel
ssh xerxes
{{Admon/caution|Danger! Use Superuser privilege at your Own Risk.|Note that the use of the superuser account via <code>sudo</code> removes almost all restrictions on what you can do. It is easily possible for you to completely destroy the operating system! Take your time, double-check your commands, and if in doubt, ask. Be aware that your actions may affect other users and vice-versa.}}
{{Admon/caution|Do Not Build or Install Software Except Via RPM (dnf/yum) or DEB (apt)|Do not build or install software as the root user (using <code>sudo</code>), except in RPM or DEB form using the <code>dnf</code>/<code>yum</code> or <code>yumapt</code> commands(as appropriate to the system). Building or installing software as root may overwrite system files and be very difficult to track down.<br /><br />It is OK to install software into your own directories (e.g., <code>~/bin</code> or <code>~/local</code>), which can be done without root privilege.}}
In order to use <code>sudo</code>, you will need to know your password. An initial random password is provided in the file <code>~/password.txt</code> (note that your password will be different on each server). Feel free to change this with the <code>passwd</code> command -- not by editing the file, which is provided only for your information!
== Multiuser Access ==
