Mastering EOS Release 1.0

Mastering EOS Release 1.0

Mastering EOS Release 1.0 Sean Fisk and Ira Woodring May 12, 2015 CONTENTS 1 Introduction 3 1.1 Physical Access (Keycards) ....................................... 3 1.2 Computer Access (Credentials) ..................................... 3 2 Rules and Procedures 5 2.1 Disk Space ................................................ 5 2.2 Copyrighted Material ........................................... 5 2.3 Food and Drink .............................................. 6 2.4 Overnight Parking ............................................ 6 2.5 Living in the Lab ............................................. 6 2.6 Malicious Activity ............................................ 6 2.7 Games .................................................. 6 3 Using the Command Line 7 3.1 Command-Line Basics .......................................... 7 3.2 Available Shells ............................................. 7 3.3 Interactive Shell Use ........................................... 10 3.4 Shell Scripting .............................................. 24 4 Remote Access (SSH/VNC) 27 4.1 Inter-EOS SSH .............................................. 27 4.2 Microsoft Windows ........................................... 28 4.3 Mac OS X ................................................ 36 4.4 GNU/Linux ................................................ 49 5 User-level Software Installation 65 5.1 The Standard Hierarchy ......................................... 65 5.2 Manual Installation ............................................ 66 5.3 Linuxbrew ................................................ 71 5.4 User-level Hierarchies .......................................... 72 6 System and Software Information 75 6.1 System .................................................. 75 6.2 Software ................................................. 77 6.3 Web Server ................................................ 78 7 Winserv 79 7.1 Common Settings ............................................ 79 7.2 Microsoft Windows ........................................... 79 7.3 Mac OS X ................................................ 80 7.4 GNU/Linux ................................................ 82 i 8 Databases 83 8.1 MySQL .................................................. 83 8.2 Oracle .................................................. 83 8.3 Oracle APEX ............................................... 83 8.4 MSSQL .................................................. 84 8.5 SQLite .................................................. 84 8.6 Remote Database Connections ...................................... 84 9 Editors 85 9.1 Basic Text Editors ............................................ 85 9.2 Advanced Text Editors .......................................... 86 9.3 Integrated Development Environments ................................. 88 9.4 EditorConfig ............................................... 93 10 GUI Toolkits 95 10.1 Choosing a Toolkit ............................................ 95 10.2 Qt ..................................................... 95 10.3 wxWidgets ................................................ 96 10.4 GTK+ ................................................... 96 10.5 Tk ..................................................... 97 10.6 Swing ................................................... 97 10.7 SWT ................................................... 97 10.8 Native Toolkits .............................................. 98 11 Miscellaneous 99 11.1 Kill the X Server ............................................. 99 11.2 Directory Navigation ........................................... 99 11.3 xdg-open ................................................. 99 11.4 uptime .................................................. 100 11.5 User Interactions ............................................. 100 12 Contributing to Mastering EOS 101 12.1 Repository Setup ............................................. 101 12.2 Pre-requisites ............................................... 102 12.3 Using the Build System ......................................... 105 12.4 Editing the Manual ............................................ 107 12.5 Making a Pull Request .......................................... 109 12.6 Writing Guidelines ............................................ 109 12.7 Reviewing Pull Requests ......................................... 111 12.8 Maintenance Tasks ............................................ 112 13 Environment Variables 115 14 About This Documentation 117 14.1 People .................................................. 117 14.2 Licensing ................................................. 117 14.3 Special Thanks .............................................. 117 Index 119 ii Mastering EOS, Release 1.0 Mastering EOS is an initiative to produce better documentation for the Grand Valley State University School of Com- puter and Information Systems Exploratory Operating System Labs (GVSU CIS EOS Labs). It is intended to augment the original EOS documentation located on the School of CIS website. Mastering EOS is written by: • Sean Fisk, BS and MS in Computer Science from GVSU • Ira Woodring, GVSU EOS Lab system administrator Contents: CONTENTS 1 Mastering EOS, Release 1.0 2 CONTENTS CHAPTER ONE INTRODUCTION The Exploratory Operating Systems Labs (EOS Labs) are a collection of computer labs maintained by the GVSU School of Computing and Information Systems. Some are for general CIS student use, and others are specific to certain courses, labs, or applications. The labs within the EOS Lab umbrella include: Name Location Purpose Exploratory Operating Systems Lab MAK studying operating systems; general CIS computing (EOS Lab) A-1-171 use Architecture Lab (Arch Lab) MAK studying computer architectures; general CIS A-1-101 computing use Data Communications Lab (Datacomm MAK studying networking Lab) 1-1-167 Hardware Lab MAK studying hardware; multi-purpose 1-1-105 When addressing this collections of labs, we often refer to it simply as EOS. Though the EOS Lab is only one of the CIS department’s computing labs, it was the original lab and other labs are largely based upon it. It is also the one most often used by the greatest variety of students. 1.1 Physical Access (Keycards) The EOS Labs contain equipment specific to the CIS majors and are therefore closed to the general public. To access the labs, you are required to obtain a keycard. To be eligible for a keycard, you must be currently enrolled in a course which utiltizes the lab you’d like to access. After registration, visit the computing office in MAK C-2-100 to receive your card. A $25 deposit paid from your student account is charged upon receipt of the card. When the card is returned in acceptable condition, the deposit will be refunded. Please note that once the $25 deposit has been posted to your student account you must pay the balance, otherwise you will be charged a late fee. The late fee will not be refunded once you return the keycard. To then gain entry to a lab to which you have been granted access, simply swipe the card at the reader next to the door to unlock it. In addition to room access, the card grants 24-hour access to Mackinac Hall. The courtyard door which is closest to the Architecture Lab possesses a reader which will open when the key is swiped. No other building doors are equipped with readers. It is important that you do not allow anyone else to use your card. In addition, do not keep the card in your wallet, as the cards contain tiny hair-like wires that break easily when the card is flexed. 1.2 Computer Access (Credentials) The EOS system uses separate user accounts from the general university computing infrastructure. EOS uses the same network ID given by GVSU’s IT department, but authenticates against the CIS department’s own LDAP server. The 3 Mastering EOS, Release 1.0 accounts are not interchangeable and administrators for one account cannot reset passwords for the other. If you are registered for one or more eligible CIS courses [#eligible-cis-courses], you qualify for an EOS account. On the Friday before the semester starts, an account will be automatically created for you and a temporary password sent to your GVSU email address. To activate your account, you need to log in to the system once, either at a physical machine or remotely using SSH, and follow these steps: • Enter your username. • Enter the temporary password you have been given. • If the temporary was entered correctly, you will be asked for the Current Password again. Enter the temporary password again. • If the two temporary passwords match, you will be asked to create a new password. Note the following rules when creating a new password: • Your password must be at least 7 characters. • Your password must not be based on a dictionary word. • Your password should not be all numbers. The system will accept such a password, but it is incredibly insecure. Additionally, the system will often prevent login with such a password. Please take the time to memorize your password! Password resets are available by contacting Ira Woodring, but it often takes a day to get to it. Professors are also able to reset passwords via an SSH reset mechanism, though some are unaware of this mechanism. 4 Chapter 1. Introduction CHAPTER TWO RULES AND PROCEDURES It is important that some basic rules and procedures be established to help maintain the lab and aid in its shared use. To those ends, please be aware of the following guidelines: 2.1 Disk Space You are given 8 gigabytes (GB) of disk space. Once you exceed this limit, you can no longer

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    123 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us