- No lab Week 01
- New Version:
- Lab 01 Parts 1 - 3 (still do web edit of lab template?)
- AWS Setup
- clone repo to instance? (or wait until Lab 02?)
- put warning note that this will be needed in Lab 2 and beyond?
- AWS Setup
- Create account / register
- hook in to classroom
- create ssh key
- put private key in proper spot
- change permissions
- create an instance
- sign in to system with public ip
- GitHub classrooms setup
- hook in to github classroom
- create ssh key for authentication
- give github public key(s)
- Try git commands
- create key pair on AWS system (use defaults)
- clone to AWS system
- use markdown template
- plug in answers from txt file
- New version:
- Lab 03 Part 3 - .ssh/config
- work with cloned repo
- Lab 01 parts 4-6
- files
- folders
- permissions
- other users
- using groups
- playing with root and sudo
- aliases
- IO redirection
- scripting intro
- regex intro
- ec is colorize text
- regex
- add sed OR grep exercise for cleaning up a file?
- scripting
- PATH, .profile, and export
- parsing data
- emails from list of output
- from survey, has mix of emails. Want just @wright.edu emails
- data from csv? - data needs to be formatted columar style
- emails from list of output
- FUTURE?
- use usernames from emails to bulk do something?
- create files with username
- put a
fortune
in each file
- ec is check for contents before overwrite
- explore your own hardware
- explore the VM resources on AWS
- script to scrape for info on linux / bash
- install VirtualBox
- Mac M1 peeps - UMT is free, Parallels discounted through Cats
- install OS on VM
- On Linux VM
- change desktop background
- open browser and navigate to site
- install VSCode
- ssh in to AWS instance
- Mount xvdb, create partition table, create partition, add to /etc/fstab? - NEW
- use strings to explore what "deletion" means on something on a disk
- inodes & hard / symbolic links
- ec: Create a folder and layer on a filesystem
- create a script that runs infinitely
- run the script "normally" and kill via PID
- run the script with bg and kill via job ID
- run in screen
- create a branch, update content, merge branch after
- Write source code
- compile source code
- write a makefile
- ec is install ninvaders
- ec is add dependent file (function / library that "main" relies on)
- explore your internet connection and the AWS internet connection
- Run a python web server on port 4141, play with firewalls
- Use lsof to find port service is running on, kill process
- scan version of service running on instance
- EC - echo a message over a port, access message via public IP or curl localhost
- MINICONDA?
- tar'ing
- ~/.ssh/config
- create key pair for bob (authorized_keys)
- sftp
- checksums
- EC - solve a merge conflict
marco/polo script- pay attention to PATH and file locations
- EC - hello world in jupyter notebook
- play with port forwarding using jupyter notebooks