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 ===
If you're using a command-line ssh system, you can issue a command such as this:
ssh -p 2200 ''username''@ehl.cdot.systems
ssh -p 2205 ''username''@ehl.cdot.systems
ssh ''username''@xerxes.cdot.systems
== Simplified SSH Access ==
Host "aarchie"
hostname "aarchie.cdot.systems"
user "YourUserID"
Host "bbetty"
hostname "ehl.cdot.systems"
user "YourUserID"
port 2200
Host "ccharlie"
hostname "ehl.cdot.systems"
user "YourUserID"
port 2205
Host "israel"
hostname "israel.cdot.systems"
user "YourUserID"
ssh aarchie
ssh bbetty ssh ccharlie ssh israel
ssh xerxes
You can similarly configure simplified access in most other SSH client programs.
== SSH Access from Other Client Systems ==
{{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 ==
Remember that these machines are multi-user systems. Use the <code>w</code> or <code>who</code> commands to see who else is using them; you can also try using the <code>write</code> command to communicate with another user if required.
== OS Versions ==
Note that the servers may have different operating system releases.
== Backup Your Accounts ==
With other SSH clients:
# Your key must be in OpenSSH format when you send it to your professor; this format is used by the default SSH client on Mac OS/X and Linux as well as PuTTY. If it is in SSH2 format, used by some other client programs, you can convert it with this command on a Linux system with OpenSSH (such as Matrix):
ssh-keygen -i -f ~/.ssh/''SSH2_PUBLIC_KEY_FILE''.pub > ~/.ssh/''OPENSSH_PUBLIC_KEY_FILE''.pub
Your professor will do this automatically as part of the key processing; however, you will need to manually perform this step for any keys that you append to your <code>~/.ssh/authorized_keys</code> file(s).
== Disconnect/Reconnect Ability ==
The [[Screen Tutorial|screen]] utility provides disconnect/reconnect capability, which is very useful for unstable network connections, long interactive operations, and changing your work location.