a simple utility to quickly identify the cheapest spot location for an instance type
❯ AWS_PROFILE=redbeard python3.11 lspot.py --help
usage: lspot.py [-h] [--json] [--table] [-v] [-1] [-r REGION] instance_type
# make CTRL+a the 'prefix' ala screen. | |
bind C-a send-prefix | |
set -g prefix C-a | |
# get rid of the tmux standard of CTRL+b | |
unbind C-b | |
set -s escape-time 1 | |
set -g base-index 1 | |
setw -g pane-base-index 1 | |
# make it easy to reload the config (CTRL+r) |
>>> Explain how the vector extension for RISC-V works. Provide definitions of key concepts and components, how it works, and it's benefits. [S][default] | |
╭─────────────────────────────────────────────────────────────────────────────────────────────── merlinite-7b-lab-Q4_K_M ────────────────────────────────────────────────────────────────────────────────────────────────╮ | |
│ The vector extension for RISC-V is an enhancement to the RISC-V Instruction Set Architecture (ISA) that allows multiple operations to be performed on multiple data elements in parallel, thereby increasing the │ | |
│ throughput of calculations and improving performance in data-intensive applications. This extension introduces new vector registers, vector instructions, and data alignment concepts to optimize the processing of │ | |
│ vector data. |
After a bit of hunting far and wide I have achieved success. For anyone who's been to Wheatsville Co-op in Austin, Texas knows that it's the bomb. It's received enough of a following that it has it's own Facebook page. The problem is that it's a closely guarded secret with only sparse smatterings of it to be found. At one point I found a recipe in a book
kind: Secret
#!/bin/bash | |
# This tool can be used to sync down Red Hat based packages from RHN using only Red Hat shipped tools | |
# Brian "Red Beard" Harrington <brian@dead-city.org> | |
# Copyright 2013 | |
# | |
# To satisfy the pre-reqs for this script install the following two rpms: | |
# yum-utils | |
# createrepo_c (in RHEL 8 createrepo and createrepo_c have been combined) | |
# See https://github.com/rpm-software-management/createrepo_c#differences-in-behavior-between-createrepo_c-and-createrepo |
❯ picocom -b 115200 /dev/ttyUSB0 | |
picocom v3.1 | |
port is : /dev/ttyUSB0 | |
flowcontrol : none | |
baudrate is : 115200 | |
parity is : none | |
databits are : 8 | |
stopbits are : 1 | |
escape is : C-a |
Traditionally virtual machines and containers are exposed on a bridge which is solely available behind a single IP address exposed behind network/port address translation (NAT/PAT). This is, in general an acceptable practice but leads to some configuration challenges when testing out technologies like network booting of hosts, firewalling, equal cost multipath, etc.
This configuration will allow a user to move the IP address of the host to an internal bridge
### Current Directory Structure (micropython submodule pruned) | |
❯ tree --gitignore | |
. | |
├── CMakeLists.txt | |
├── components | |
│ └── micropython | |
├── main | |
│ ├── CMakeLists.txt | |
│ ├── idf_component.yml | |
│ └── mp-test.c |
AWS provides a mechanism for temporarily assuming another role within their API system. While it is not a technically hard process it can be convoluted and hard to understand. This document aims to both make it easier to follow along with as well as give an in depth explanation of some of the underpinnings of the Bourne Again Shell (aka BASH) which can make this easier to utilize on a day to day basis.
Below is an overexplained version of the following process:
~/.aws/credentials
as a "profile" which are then understood by the AWS command line tools