#diskRipper.sh by Leif Messinger

#For use on debian, where your cds aren't immediately mounted
wall "CD inserted boss"
set -x	#echo on

cdDrivePath=$(ls -l /dev/cdrom | awk '{print $NF}')

#CD could have no label, so that's why I need awk
cdLabel=$(lsblk -n "/dev/$cdDrivePath" -o label)
if [[ ! -z "$cdLabel" ]]; then	#CD has label
folderName=$cdLabel
echo "The cd label is ${folderName}"
if mkdir ./cds/"${folderName}"; then	#Folder didn't exist before
sudo mount /dev/cdrom ./.cdmountpoint

sudo cp -r ./.cdmountpoint/* "./cds/${folderName}"
sudo chmod -R 777 "./cds/${folderName}"

sudo umount ./.cdmountpoint
eject
wall "CD done and ejecting"
else
wall "Already read that cd, skipped"
fi
else
wall "CD had no label, skipped"
fi

for region in `aws ec2 describe-regions --output text | cut -f4`
do
     echo -e "\nListing Instances in region:'$region'..."
     aws ec2 describe-instances --query 'Reservations[*].Instances[*].{Instance:InstanceId,Subnet:SubnetId}' --region $region
done
#This script is to be used with any AWS CLI configured environment, it will list any EC2 instances and their associated subnet network ID's in JSON format

#!/bin/sh

BAT_LOW=15
BAT_CRITICAL=5

if [ "$1" = "--help" ]
then
    printf "
    Usage:
    \tbattery_check.sh warning%% hibernate%%

    Description:
    \tA script for notifying the user via dunst and logging when
    \tthe battery is low and the system is going to hibernate.
    \tCan be supplied arguments for the battery low warning and
    \thibernation percentage thresholds as the first and second arguments.

    \t Default behavior is to warn at 15% and hibernate at 5%."
    exit
fi

if [[ -n "$1" && -n "$2" && $1 -gt $2 ]]
then
    BAT_LOW=$1
    BAT_CRITICAL=$2
fi

acpi -b | awk -F'[,:%]' '{print $2, $3}' | {

    read -r status capacity
    echo Low threshold: $BAT_LOW, Hibernate threshold: $BAT_CRITICAL
    echo Status: $status, Capacity: $capacity

    if [ "$status" = Discharging -a "$capacity" -le $BAT_CRITICAL ]; then
        echo Battery critical threshold.
        dunstify -u critical "Critical battery threshold, hibernating..."
        logger "Critical battery threshold, hibernating..."
        sleep .5
        systemctl hibernate
        exit
    fi

    if [ "$status" = Discharging -a "$capacity" -le $BAT_LOW ]; then
        echo Battery low threshold.
        dunstify -u critical 'Battery low! System will hibernate at 5%.'
        logger 'Battery low! System will hibernate at 5%.'
        sleep .5
        light -S 15
        exit
    fi
}

#Leif Messinger

#For when you want to search a lot of words in a file fast


#Arg 1 is the argument the list of words you want to search

#Arg 2 is the file you want to search


#-z means that it looks at the file as a whole, just treating newlines a characters.

#-r is regex. Needed for $, even tho the documentation says you don't need it. They are liars.

#First command replaces all . with \. and all - with \-

#Second command takes all newlines and replaces them with )|(

#Third command takes the trailing |( and deletes it

#Forth command puts a /( at the start

#Fith command puts /!d at the end. This tells it to not delete any lines that match the pattern.


#The second sed takes the output of the first sed as a command that searches any of the combined words

#-f - takes a command from the input
sed -z -r -e 's/\./\\\./g ; s/\-/\\\-/g' -e 's/\n/\)\|\(/g' -e 's/\|\($//' -e 'i/\(' -e 'a/!d' $1 | sed -r -f - $2

#pinger.sh by Leif Messinger

#./pinger.sh [ADDRESS] to search

#./pinger.sh [ADDRESS] & to search in the background

#https://serverfault.com/a/42382
ping_cancelled=false # Keep track of whether the loop was cancelled, or succeeded
until ping -c1 "$1" >/dev/null 2>&1; do :; done & # The "&" backgrounds it
trap "kill $!; ping_cancelled=true" SIGINT
wait $! # Wait for the loop to exit, one way or another
trap - SIGINT # Remove the trap, now we're done with it
if [ "$ping_cancelled" == true ] #https://stackoverflow.com/a/21210966/10141528
then
	printf "The pinger for $1 just closed bro.\n"
else
	printf "$1 IS UP BROOO\a\n"
fi

# Run "test" script on all packages
npm run test --workspaces


# Tip - this also works:
npm run test  -ws

----------------------------------------------------


# Runs "test" only on package-a
npm run test --workspace package-a


# Tip - this also works:
npm run test -w package-a

----------------------------------------------------


# Install `lodash` on `package-a`
npm install lodash --workspace package-a


# Install `tap` on `package-b` as a dev dependency
npm install tap --workspace package-b --save-dev


# Install `package-a` on `package-b`
npm install package-a --workspace package-b


# Install `eslint` in all packages
npm install eslint --workspaces