Home
Time Box
Calculator
Snake
Blogs
Hacks

Linux Shell and Bash • 59 min read

Description

A Tech Talk on Linux and the Bash shell.


Bash Tutorial

A brief overview of Bash, on your way to becoming a Linux expert. When a computer boots up, a kernel (MacOS, Windows, Linux) is started. This kernel provides a shell, or terminal, that allows user to interact with a most basic set of commands. Typically, the casual user will not interact with the shell/terminal as a Desktop User Interface is started by the computer boot up process. To activate a shell directly, users will run a “terminal” through the Desktop. VS Code provides ability to activate "terminal" while in the IDE.

Variable Prerequisites

Setup bash shell dependency variables for this page. Variables are one of the first aspects of programming. Variables have "name" and a "value".

Define variable

The following code cell defines 3 variables and assigns each a value. There are some extra command, called a HERE document, that write these variables to a file. This is so we can use these variables over and over below.

%%script bash

# Dependency Variables, set to match your project directories

cat <<EOF > /tmp/variables.sh
export project_dir=$HOME/vscode  # change vscode to different name to test git clone
export project=\$project_dir/stud  # change teacher to name of project from git clone
export project_repo="https://github.com/nighthawkcoders/teacher.git"  # change to project of choice
EOF

Output the value of a variable

The following code cell outputs the value of the variables, using the echo command. For visual understanding in the output, each echo command provide a title before the $variable

%%script bash

# Extract saved variables
source /tmp/variables.sh

# Output shown title and value variables
echo "Project dir: $project_dir"
echo "Project: $project"
echo "Repo: $project_repo"
Project dir: /home/finnc/vscode
Project: /home/finnc/vscode/teacher
Repo: https://github.com/nighthawkcoders/teacher.git

Project Setup and Analysis with Bash Scripts

The bash scripts that follow automate what was done in the setup procedures. The purpose of this is to show that many of the commands we performed can be added to a script, then performed automatically.

Pull Code

Pull code from GitHub to your machine. This is a bash script, a sequence of commands, that will create a project directory and add the “project” from GitHub to the vscode directory. There is conditional logic to make sure that clone only happen if it does not (!) exist. Here are some key elements in this code…

%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Using conditional statement to create a project directory and project"

cd ~    # start in home directory

# Conditional block to make a project directory
if [ ! -d $project_dir ]
then 
    echo "Directory $project_dir does not exists... makinng directory $project_dir"
    mkdir -p $project_dir
fi
echo "Directory $project_dir exists." 

# Conditional block to git clone a project from project_repo
if [ ! -d $project ]
then
    echo "Directory $project does not exists... cloning $project_repo"
    cd $project_dir
    git clone $project_repo
    cd ~
fi
echo "Directory $project exists." 
Using conditional statement to create a project directory and project
Directory /home/finnc/vscode exists.
Directory /home/finnc/vscode/teacher exists.

Look at files Github project

All computers contain files and directories. The clone brought more files from cloud to your machine. Review the bash shell script, observe the commands that show and interact with files and directories. These were used during setup.

%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Navigate to project, then navigate to area wwhere files were cloned"
cd $project
pwd

echo ""
echo "list top level or root of files with project pulled from github"
ls

Navigate to project, then navigate to area wwhere files were cloned
/home/finnc/vscode/teacher

list top level or root of files with project pulled from github
Gemfile
LICENSE
Makefile
README.md
_config.yml
_data
_includes
_layouts
_notebooks
_posts
assets
csa.md
csp.md
csse.md
images
index.md
indexBlogs.md
scripts

Look at file list with hidden and long attributes

Most linux commands have options to enhance behavior. The enhanced listing below shows permission bits, owner of file, size and date.

ls reference

%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Navigate to project, then navigate to area wwhere files were cloned"
cd $project
pwd

echo ""
echo "list all files in long format"
ls -al   # all files -a (hidden) in -l long listing
Navigate to project, then navigate to area wwhere files were cloned
/home/finnc/vscode/teacher

list all files in long format
total 100
drwxr-xr-x 12 finnc finnc 4096 Aug 21 11:27 .
drwxr-xr-x  6 finnc finnc 4096 Aug 19 17:19 ..
drwxr-xr-x  8 finnc finnc 4096 Aug 21 11:27 .git
drwxr-xr-x  3 finnc finnc 4096 Aug 17 20:39 .github
-rw-r--r--  1 finnc finnc  157 Aug 17 20:39 .gitignore
-rw-r--r--  1 finnc finnc  122 Aug 17 20:39 Gemfile
-rw-r--r--  1 finnc finnc 1081 Aug 17 20:39 LICENSE
-rw-r--r--  1 finnc finnc 3131 Aug 21 11:27 Makefile
-rw-r--r--  1 finnc finnc 6853 Aug 21 11:27 README.md
-rw-r--r--  1 finnc finnc  607 Aug 17 20:39 _config.yml
drwxr-xr-x  2 finnc finnc 4096 Aug 17 20:39 _data
drwxr-xr-x  2 finnc finnc 4096 Aug 17 20:39 _includes
drwxr-xr-x  2 finnc finnc 4096 Aug 17 20:39 _layouts
drwxr-xr-x  3 finnc finnc 4096 Aug 21 11:27 _notebooks
drwxr-xr-x  2 finnc finnc 4096 Aug 21 11:27 _posts
drwxr-xr-x  4 finnc finnc 4096 Aug 17 20:39 assets
-rw-r--r--  1 finnc finnc   92 Aug 17 20:39 csa.md
-rw-r--r--  1 finnc finnc   98 Aug 17 20:39 csp.md
-rw-r--r--  1 finnc finnc  108 Aug 17 20:39 csse.md
drwxr-xr-x  2 finnc finnc 4096 Aug 17 20:39 images
-rw-r--r--  1 finnc finnc 5149 Aug 17 20:39 index.md
-rw-r--r--  1 finnc finnc   53 Aug 17 20:39 indexBlogs.md
drwxr-xr-x  2 finnc finnc 4096 Aug 21 11:27 scripts
%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Look for posts"
export posts=$project/_posts  # _posts inside project
cd $posts  # this should exist per fastpages
pwd  # present working directory
ls -l  # list posts
Look for posts
/home/finnc/vscode/teacher/_posts
total 88
-rw-r--r-- 1 finnc finnc  7685 Aug 17 20:39 2023-08-16-Tools_Equipment.md
-rw-r--r-- 1 finnc finnc  4650 Aug 17 20:39 2023-08-16-pair_programming.md
-rw-r--r-- 1 finnc finnc  7137 Aug 21 11:27 2023-08-17-markdown-html_fragments.md
-rw-r--r-- 1 finnc finnc  6659 Aug 21 11:27 2023-08-23-javascript-calculator.md
-rw-r--r-- 1 finnc finnc 10642 Aug 17 20:39 2023-08-30-agile_methodolgy.md
-rw-r--r-- 1 finnc finnc  3849 Aug 21 11:27 2023-08-30-javascript-music-api.md
-rw-r--r-- 1 finnc finnc  5312 Aug 17 20:39 2023-09-06-javascript-motion-mario-oop.md
-rw-r--r-- 1 finnc finnc  4812 Aug 17 20:39 2023-09-13-java-free_response.md
-rw-r--r-- 1 finnc finnc 13220 Aug 17 20:39 2023-10-16-java-api-pojo-jpa.md
-rw-r--r-- 1 finnc finnc  6819 Aug 17 20:39 2023-11-13-jwt-java-spring.md
%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Look for notebooks"
export notebooks=$project/_notebooks  # _notebooks is inside project
cd $notebooks   # this should exist per fastpages
pwd  # present working directory
ls -l  # list notebooks
Look for notebooks
/home/finnc/vscode/teacher/_notebooks
total 740
-rw-r--r-- 1 finnc finnc  13014 Aug 17 20:39 2023-08-01-cloud_database.ipynb
-rw-r--r-- 1 finnc finnc   8992 Aug 17 20:39 2023-08-01-mario_player.ipynb
-rw-r--r-- 1 finnc finnc  43705 Aug 17 20:39 2023-08-02-cloud-workspace-automation.ipynb
-rw-r--r-- 1 finnc finnc  22060 Aug 17 20:39 2023-08-03-mario_block.ipynb
-rw-r--r-- 1 finnc finnc  11791 Aug 17 20:39 2023-08-03-mario_platform.ipynb
-rw-r--r-- 1 finnc finnc  19450 Aug 17 20:39 2023-08-03-mario_tube.ipynb
-rw-r--r-- 1 finnc finnc  24387 Aug 17 20:39 2023-08-04-mario_background.ipynb
-rw-r--r-- 1 finnc finnc   3496 Aug 21 11:27 2023-08-07-mario_lesson.ipynb
-rw-r--r-- 1 finnc finnc  10110 Aug 17 20:39 2023-08-15-java-hello.ipynb
-rw-r--r-- 1 finnc finnc  25624 Aug 21 11:27 2023-08-16-github_pages_setup.ipynb
-rw-r--r-- 1 finnc finnc  16156 Aug 21 11:27 2023-08-16-linux_shell.ipynb
-rw-r--r-- 1 finnc finnc  11466 Aug 17 20:39 2023-08-16-python_hello.ipynb
-rw-r--r-- 1 finnc finnc   9425 Aug 17 20:39 2023-08-23-github_pages_anatomy.ipynb
-rw-r--r-- 1 finnc finnc  22668 Aug 17 20:39 2023-08-23-java-console_games.ipynb
-rw-r--r-- 1 finnc finnc   9038 Aug 17 20:39 2023-08-23-python_tricks.ipynb
-rw-r--r-- 1 finnc finnc  10152 Aug 17 20:39 2023-08-30-javascript_top_10.ipynb
-rw-r--r-- 1 finnc finnc   9689 Aug 17 20:39 2023-08-30-showcase-S1-pair.ipynb
-rw-r--r-- 1 finnc finnc   7192 Aug 17 20:39 2023-09-05-python-flask-anatomy.ipynb
-rw-r--r-- 1 finnc finnc  22157 Aug 17 20:39 2023-09-06-AWS-deployment.ipynb
-rw-r--r-- 1 finnc finnc  14380 Aug 17 20:39 2023-09-06-java-primitives.ipynb
-rw-r--r-- 1 finnc finnc  11671 Aug 21 11:27 2023-09-06-javascript-input.ipynb
-rw-r--r-- 1 finnc finnc  13706 Aug 17 20:39 2023-09-12-java_menu_class.ipynb
-rw-r--r-- 1 finnc finnc   9562 Aug 17 20:39 2023-09-13-java_fibonaccii_class.ipynb
-rw-r--r-- 1 finnc finnc  44217 Aug 21 11:27 2023-09-13-javascript_output.ipynb
-rw-r--r-- 1 finnc finnc  43423 Aug 17 20:39 2023-09-13-python-pandas_intro.ipynb
-rw-r--r-- 1 finnc finnc  11578 Aug 17 20:39 2023-09-20-java-image_2D.ipynb
-rw-r--r-- 1 finnc finnc  26739 Aug 17 20:39 2023-09-20-javascript_motion_dog.ipynb
-rw-r--r-- 1 finnc finnc  13599 Aug 17 20:39 2023-10-02-java-spring-anatomy.ipynb
-rw-r--r-- 1 finnc finnc  12429 Aug 17 20:39 2023-10-09-java-chatgpt.ipynb
-rw-r--r-- 1 finnc finnc  15632 Aug 17 20:39 2023-10-09-javascript_api.ipynb
-rw-r--r-- 1 finnc finnc 113091 Aug 17 20:39 2023-10-09-python_machine_learing_fitness.ipynb
-rw-r--r-- 1 finnc finnc  16271 Aug 17 20:39 2023-11-13-jwt-python-flask.ipynb
-rw-r--r-- 1 finnc finnc  15951 Aug 17 20:39 2023-11-13-vulnerabilities.ipynb
-rw-r--r-- 1 finnc finnc  18328 Aug 17 20:39 2023-11-20-jwt-java-spring-challenge.md
-rw-r--r-- 1 finnc finnc  10745 Aug 17 20:39 2024-01-04-cockpit-setup.ipynb
drwxr-xr-x 2 finnc finnc   4096 Aug 17 20:39 files
%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Look for images in notebooks, print working directory, list files"
cd $notebooks/images  # this should exist per fastpages
pwd
ls -l
Look for images in notebooks, print working directory, list files


bash: line 6: cd: /images: No such file or directory


/home/finnc/vscode/stud/_notebooks
total 28
-rw-r--r-- 1 finnc finnc 16159 Aug 22 18:00 2023-08-16-linux_shell.ipynb
-rw-r--r-- 1 finnc finnc  8619 Aug 21 16:19 2023-08-21-VSCode-GitHub_Pages.ipynb

Look inside a Markdown File

“cat” reads data from the file and gives its content as output

%%script bash

# Extract saved variables
source /tmp/variables.sh

echo "Navigate to project, then navigate to area wwhere files were cloned"

cd $project
echo "show the contents of README.md"
echo ""

cat README.md  # show contents of file, in this case markdown
echo ""
echo "end of README.md"

Navigate to project, then navigate to area wwhere files were cloned
show the contents of README.md

## Teacher Blog site
This site is intended for the development of Teacher content.  This blogging site is built using GitHub Pages [GitHub Pages](https://docs.github.com/en/pages/getting-started-with-github-pages/creating-a-github-pages-site).
- The purpose is to build lessons and distribute across different Computer Science sections (CSSE, CSP, CSA), a pathway that covers 3 years of High School Instruction.
- The primary languages and frameworks that are taught are `JavaScript/HTML/CSS`, `Python/Flask`, `Java/Spring`.  Read below for more details.
- In this course, Teacher content is not exclusively developed by Teachers.  In fact, many Students have been invited to develop and publish content into this repository.  Their names will appear as authors on the content which they aided in producing.
- This site has incorporated ideas and has radically modified scripts from the now deprecated [fastpages](https://github.com/fastai/fastpages) repository.
- This site includes assistance and guideance from ChatGPT, [chat.openai.com](https://chat.openai.com/) 

### Courses and Pathway
The focus of the Del Norte Computer Science three-year pathway is `Full Stack Web Development`.  This focus provides a variety of technologies and exposures.  The intention of the pathway is breadth and exposure.
- `JavaScript` documents are focused on frontend development and for entry class into the Del Norte Computer Science pathway.  JavaScript documents and materials are a prerequisites to Python and Java classes.
- `Python` documents are focused on backend development and requirements for the AP Computer Science Principles exam.
- `Java` documents are focused on backend development and requirements for the AP Computer Sciene A exam.
- `Data Structures` materials embedded into JavaScript, Python, or Java documents are focused on college course articulation.

### Resources and Instruction
The materials, such as this README, as well as `Tools`, `DevOps`, and `Collaboration` resources are integral part of this course and Computer Science in general.  Everything in our environment is part of our learning of Computer Science. 
- `Visual Studio Code` is key the code-build-debug cycle editor used in this course, [VSCode download](https://code.visualstudio.com/).  This is an example of a resource, but inside of it it has features for collaboration.
- `Tech Talks`, aka lectures, are intended to be interactive and utilize `Jupyter Notebooks` and Websites.  This is an example of blending instruction and tools together, which in turn provide additional resources for learning.  For instance, deep knowledge on  GitHub Pages and Notebooks are valuable in understanding principles behind Full Stack Development and Data Science. 

## GitHub Pages
All `GitHub Pages` websites are managed on GitHub infrastructure. GitHub uses `Jekyll` to tranform your content into static websites and blogs. Each time we change files in GitHub it initiates a GitHub Action that rebuilds and publishes the site with Jekyll.  
- GitHub Pages is powered by: [Jekyll](https://jekyllrb.com/).
- Publised teacher website: [nighthawkcoders.github.io/teacher](https://nighthawkcoders.github.io/teacher/)

## Preparing a Preview Site 
In all development, it is recommended to test your code before deployment.  The GitHub Pages development process is optimized by testing your development on your local machine, prior to files on GitHub

Development Cycle. For GitHub pages, the tooling described below will create a development cycle  `make-code-save-preview`.  In the development cycle, it is a requirement to preview work locally, prior to doing a VSCode `commit` to git.

Deployment Cycle.  In the deplopyment cycle, `sync-github-action-review`, it is a requirement to complete the development cycle prior to doing a VSCode `sync`.  The sync triggers github repository update.  The action starts the jekyll build to publish the website.  Any step can have errors and will require you to do a review.

### WSL and/or Ubuntu installation requirements
- The result of these step is Ubuntu tools to run preview server.  These procedures were created using [jekyllrb.com](https://jekyllrb.com/docs/installation/ubuntu/)
```bash
# 
# WSL/Ubuntu setup
#
mkdir mkdir vscode
git clone https://github.com/nighthawkcoders/teacher.git
# run script, path vscode/teacher are baked in script
~/vscode/teacher/scripts/activate_ubuntu.sh
#=== !!!Start a new Terminal!!! ===
#=== Continue to next section ===
```

### MacOs installation requirements 
- Ihe result of these step are MacOS tools to run preview server.  These procedures were created using [jekyllrb.com](https://jekyllrb.com/docs/installation/macos/). 

```bash
# 
# MacOS setup
#
mkdir mkdir vscode
git clone https://github.com/nighthawkcoders/teacher.git
# run script, path vscode/teacher are baked in script
~/vscode/teacher/scripts/activate_macos.sh
#=== !!!Start a new Terminal!!! ===
#=== Continue to next section ===
```


### Run Preview Server
- The result of these step is server running on: http://0.0.0.0:4100/teacher/.  Regeneration messages will run in terminal on any save and update site upon refresh.  Terminal is active, press the Enter or Return key in the terminal at any time to see prompt to enter commands.

- Complete installation
```bash
cd ~/vscode/teacher
bundle install
make
```
- Run Server.  This requires running terminal commands `make`, `make stop`, `make clean`, or `make convert` to manage the running server.  Logging of details will appear in terminal.   A `Makefile` has been created in project to support commands and start processes.

    - Start preview server in terminal
    ```bash
    cd ~/vscode/teacher  # my project location, adapt as necessary
    make
    ```

    - Terminal output of shows server address. Cmd or Ctl click http location to open preview server in browser. Example Server address message... 
    ```
    Server address: http://0.0.0.0:4100/teacher/
    ```

    - Save on ipynb or md activiates "regeneration". Refresh browser to see updates. Example terminal message...
    ```
    Regenerating: 1 file(s) changed at 2023-07-31 06:54:32
        _notebooks/2024-01-04-cockpit-setup.ipynb
    ```

    - Terminal message are generated from background processes.  Click return or enter to obtain prompt and use terminal as needed for other tasks.  Alway return to root of project `cd ~/vscode/teacher` for all "make" actions. 
        

    - Stop preview server, but leave constructed files in project for your review.
    ```bash
    make stop
    ```

    - Stop server and "clean" constructed files, best choice when renaming files to eliminate potential duplicates in constructed files.
    ```bash
    make clean
    ```

    - Test notebook conversions, best choice to see if IPYNB conversion is acting up.
    ```bash
    make convert
    ```
    
end of README.md

Env, Git and GitHub

Env(ironment) is used to capture things like path to Code or Home directory. Git and GitHub is NOT Only used to exchange code between individuals, it is often used to exchange code through servers, in our case deployment for Website. All tools we use have a behind the scenes relationships with the system they run on (MacOS, Windows, Linus) or a relationship with servers which they are connected to (ie GitHub). There is an “env” command in bash. There are environment files and setting files (.git/config) for Git. They both use a key/value concept.

%%script bash

# This command has no dependencies

echo "Show the shell environment variables, key on left of equal value on right"
echo ""

env
Show the shell environment variables, key on left of equal value on right

SHELL=/bin/bash
PYTHONUNBUFFERED=1
WSL2_GUI_APPS_ENABLED=1
CONDA_EXE=/home/finnc/anaconda3/bin/conda
_CE_M=
WSL_DISTRO_NAME=Ubuntu-20.04
ELECTRON_RUN_AS_NODE=1
VSCODE_AMD_ENTRYPOINT=vs/workbench/api/node/extensionHostProcess
NAME=LAPTOP-ROF47U2G
PWD=/home/finnc/vscode/stud/_notebooks
NIX_PROFILES=/nix/var/nix/profiles/default /home/finnc/.nix-profile
LOGNAME=finnc
CONDA_ROOT=/home/finnc/anaconda3
CONDA_PREFIX=/home/finnc/anaconda3
PYDEVD_IPYTHON_COMPATIBLE_DEBUGGING=1
MOTD_SHOWN=update-motd
HOME=/home/finnc
LANG=C.UTF-8
WSL_INTEROP=/run/WSL/12_interop
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
WAYLAND_DISPLAY=wayland-0
NIX_SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt
CONDA_PROMPT_MODIFIER=(base) 
PYDEVD_USE_FRAME_EVAL=NO
CLICOLOR=1
VSCODE_L10N_BUNDLE_LOCATION=
GEM_HOME=/home/finnc/gems
LESSCLOSE=/usr/bin/lesspipe %s %s
VSCODE_HANDLES_SIGPIPE=true
TERM=xterm-color
_CE_CONDA=
LESSOPEN=| /usr/bin/lesspipe %s
USER=finnc
GIT_PAGER=cat
PYTHONIOENCODING=utf-8
CONDA_SHLVL=1
DISPLAY=:0
SHLVL=2
PAGER=cat
VSCODE_CWD=/mnt/c/Users/Finn/AppData/Local/Programs/Microsoft VS Code
MPLBACKEND=module://matplotlib_inline.backend_inline
CONDA_PYTHON_EXE=/home/finnc/anaconda3/bin/python
XDG_RUNTIME_DIR=/mnt/wslg/runtime-dir
CONDA_DEFAULT_ENV=base
WSLENV=VSCODE_WSL_EXT_LOCATION/up
VSCODE_WSL_EXT_LOCATION=/mnt/c/Users/Finn/.vscode/extensions/ms-vscode-remote.remote-wsl-0.81.0
XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/snapd/desktop
PATH=/home/finnc/anaconda3/bin:/home/finnc/.vscode-server/bin/6c3e3dba23e8fadc360aed75ce363ba185c49794/bin/remote-cli:/home/finnc/.nix-profile/bin:/home/finnc/.local/bin:/home/finnc/gems/bin:/home/finnc/anaconda3/bin:/home/finnc/anaconda3/condabin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/mnt/c/Program Files (x86)/Common Files/Oracle/Java/javapath:/mnt/c/Windows/system32:/mnt/c/Windows:/mnt/c/Windows/System32/Wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0:/mnt/c/Windows/System32/OpenSSH:/mnt/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common:/mnt/c/Program Files/NVIDIA Corporation/NVIDIA NvDLISR:/mnt/c/WINDOWS/system32:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0:/mnt/c/WINDOWS/System32/OpenSSH:/mnt/c/Program Files/Docker/Docker/resources/bin:/mnt/c/Program Files/Git/cmd:/mnt/c/Users/Finn/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/Finn/AppData/Local/Programs/Microsoft VS Code/bin:/snap/bin
VSCODE_NLS_CONFIG={"locale":"en","osLocale":"en","availableLanguages":{}}
HOSTTYPE=x86_64
PULSE_SERVER=unix:/mnt/wslg/PulseServer
VSCODE_HANDLES_UNCAUGHT_ERRORS=true
VSCODE_IPC_HOOK_CLI=/mnt/wslg/runtime-dir/vscode-ipc-10a3713e-7e91-4765-a95d-ad2d895d78ff.sock
_=/usr/bin/env
%%script bash

# Extract saved variables
source /tmp/variables.sh

cd $project

echo ""
echo "show the secrets of .git"
cd .git
ls -l

echo ""
echo "look at config file"
cat config
show the secrets of .git
total 60
-rw-r--r-- 1 finnc finnc   102 Aug 21 11:27 FETCH_HEAD
-rw-r--r-- 1 finnc finnc    21 Aug 17 20:39 HEAD
-rw-r--r-- 1 finnc finnc    41 Aug 21 11:27 ORIG_HEAD
drwxr-xr-x 2 finnc finnc  4096 Aug 17 20:39 branches
-rw-r--r-- 1 finnc finnc   267 Aug 17 20:39 config
-rw-r--r-- 1 finnc finnc    73 Aug 17 20:39 description
drwxr-xr-x 2 finnc finnc  4096 Aug 17 20:39 hooks
-rw-r--r-- 1 finnc finnc 11702 Aug 21 11:27 index
drwxr-xr-x 2 finnc finnc  4096 Aug 17 20:39 info
drwxr-xr-x 3 finnc finnc  4096 Aug 17 20:39 logs
drwxr-xr-x 4 finnc finnc  4096 Aug 17 20:39 objects
-rw-r--r-- 1 finnc finnc   112 Aug 17 20:39 packed-refs
drwxr-xr-x 5 finnc finnc  4096 Aug 17 20:39 refs

look at config file
[core]
	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
[remote "origin"]
	url = https://github.com/nighthawkcoders/teacher.git
	fetch = +refs/heads/*:refs/remotes/origin/*
[branch "main"]
	remote = origin
	merge = refs/heads/main

Advanced Student Request - Make a file in Bash

This example was requested by a student (Jun Lim, CSA). The request was to make jupyer file using bash, I adapted the request to markdown. This type of thought will have great extrapolation to coding and possibilities of using List, Arrays, or APIs to build user interfaces. JavaScript is a language where building HTML is very common.

To get more interesting output from terminal, this will require using something like mdless (https://github.com/ttscoff/mdless). This enables see markdown in rendered format.

Output of the example is much nicer in “jupyter”

%%script bash

# This example has error in VSCode, it run best on Jupyter
cd /tmp

file="sample.md"
if [ -f "$file" ]; then
    rm $file
fi

tee -a $file >/dev/null <<EOF
# Show Generated Markdown
This introductory paragraph and this line and the title above are generated using tee with the standard input (<<) redirection operator.
- This bulleted element is still part of the tee body.
EOF

echo "- This bulleted element and lines below are generated using echo with standard output (>>) redirection operator." >> $file
echo "- The list definition, as is, is using space to seperate lines.  Thus the use of commas and hyphens in output." >> $file
actions=("ls,list-directory" "cd,change-directory" "pwd,present-working-directory" "if-then-fi,test-condition" "env,bash-environment-variables" "cat,view-file-contents" "tee,write-to-output" "echo,display-content-of-string" "echo_text_>\$file,write-content-to-file" "echo_text_>>\$file,append-content-to-file")
for action in ${actions[@]}; do  # for loop is very similar to other language, though [@], semi-colon, do are new
  action=${action//-/ }  # convert dash to space
  action=${action//,/: } # convert comma to colon
  action=${action//_text_/ \"sample text\" } # convert _text_ to sample text, note escape character \ to avoid "" having meaning
  echo "    - ${action//-/ }" >> $file  # echo is redirected to file with >>
done

echo ""
echo "File listing and status"
ls -l $file # list file
wc $file   # show words
mdless $file  # this requires installation, but renders markown from terminal

rm $file  # clean up termporary file

Hack Preparation.

Review Tool Setup Procedures and think about some thing you could verify through a Shell notebook.

  • Come up with your own student view of this procedure to show your tools are installed. It is best that you keep the few things you understand, add things later as you start to understand them.
  • Name and create blog notes on some Linux commands you will use frequently.
  • Is there anything we use to verify tools we installed? Review versions?
  • How would you update a repository? Use the git command line?
%%script bash

# Navigate to the home directory
cd ~

# Define the directories to check
directories=("anaconda3" "gems" "nltk_data" "vscode" "java")

# Loop through the directories
for i in "${directories[@]}"; do
    # Check if the current directory exists
    if [ -d "$HOME/$i" ]; then
        echo "$i directory exists"
        
        # If the current directory is "vscode"
        if [ "$i" == "vscode" ]; then
            # Check for the "teacher" directory inside "vscode"
            if [ -d "$HOME/$i/teacher" ]; then
                echo "teacher directory exists inside vscode"
            else
                echo "teacher directory does not exist inside vscode"
            fi
        fi
    else
        echo "$i directory does not exist"
    fi
done

anaconda3 directory exists
gems directory exists
nltk_data directory exists
vscode directory exists
teacher directory exists inside vscode
java directory exists