This is a CentOS-themed /etc/issue w/ hooks to update IP address and OS release upon ifup/ifdown. My motivation was that I was tired of logging into an otherwise headless box just to find the IP of the system so I can SSH to it.
|
Note
|
The issue.in file actually contains control characters to do the color
in the text. The easiest way to preserve that is to clone this gist and run
the install.sh script w/ sudo, which will copy the file and set the SELinux
|
| @ | |
| @# | |
| @## | |
| ,#### | |
| #####b | |
| ,####### | |
| ,##M`@#### | |
| , s###" ]#### | |
| ,sm###M""` ,s###M" ,####` | |
| ,m##M"^ ,s####M" ,#### |
| # Operation Home Lab | |
| This document serves as a guide to getting started with building a home lab environment | |
| ### Scale | |
| A home lab can mean anything from a hosting a few virtual machines all the way to purchasing hardware to practice with basic NSM infrastructure. | |
This document is a list of hardware that has been used for development and home use as a ROCK sensor. The first option would be to repurpose a machine if possible (minimum specs below). If your budget permits you can build a powerful system in a small form factor for under $1000.
Some of the more important aspects to look for are IPMI for baremetal remote management, dual Intel NICs, quiet, and relatively low-power. You don't want to have to wear hearing protection while sitting next to your infrastructure.
| # E & K on RHEL | |
| These are high level instructions to get a simple stack up and running. Logstash not included. | |
| ## Installation | |
| ### Elasticsearch |
I hereby claim:
To claim this, I am signing this object:
or how I learned to stop worrying and get things done with python
focusing on "weapon-system" macOS cross-platform, including windows to some extent https://github.com/pyenv/pyenv
| #!/bin/bash | |
| #set -eux | |
| # Create Profile Directories | |
| mkdir ~/{bin,code,dev} | |
| # Install CLI Tools | |
| clear |