cornet

#!/usr/bin/env bash
#
# Based on https://github.com/corrupt952/ssm-session
#
# Requirements: 
#   - fzf (brew install fzf)
#
# Usage:
#   Designed to be used to with `aws-vault`:
#

andrewodri

FROM debian:10-slim

RUN apt-get update -y && \
  apt-get install -y awscli curl gnupg && \
  apt-key adv --fetch-keys "https://nginx.org/keys/nginx_signing.key" && \
  echo "deb http://nginx.org/packages/debian buster nginx" > /etc/apt/sources.list.d/nginx.list

RUN curl --silent --show-error --location --output /tmp/amazon-ssm-agent.deb "https://s3.us-east-1.amazonaws.com/amazon-ssm-us-east-1/latest/debian_amd64/amazon-ssm-agent.deb" && \
  dpkg -i /tmp/amazon-ssm-agent.deb

martok

Meta

This is @LucasWerkmeistr's #systemdTOTD thread, gathered using Spooler and reposted here with only some typographic adjustments by me.

• Part 1 begins here
• Part 2 begins here

Part 1

Alright everyone, how about some systemd Tip Of The Day goodness?

roadrunner2

Introduction

This is about documenting getting Linux running on the late 2016 and mid 2017 MPB's; the focus is mostly on the MacBookPro13,3 and MacBookPro14,3 (15inch models), but I try to make it relevant and provide information for MacBookPro13,1, MacBookPro13,2, MacBookPro14,1, and MacBookPro14,2 (13inch models) too. I'm currently using Fedora 27, but most the things should be valid for other recent distros even if the details differ. The kernel version is 4.14.x (after latest update).

The state of linux on the MBP (with particular focus on MacBookPro13,2) is also being tracked on https://github.com/Dunedan/mbp-2016-linux . And for Ubuntu users there are a couple tutorials (here and here) focused on that distro and the MacBook.

Note: For those who have followed these instructions ealier, and in particular for those who have had problems with the custom DSDT, modifying the DSDT is not necessary anymore - se

maikell

Kickstart driven CentOS 7 install from USB

None of what is written below is particularly original, however, I was unable to find a method documented on the internet at the time of writing that successfully created a kickstart driven CentOS 7 USB installer.

My interest was in doing this manually as I require this USB (image) to be created from a script. Therefore, I did not look into using ISO to USB applications - in addition, these typically do not allow custom kickstart files to be used.

References

Much of the process described below was found on the CentOS Wiki page on Installing from USB key, and from the Softpanorama page on the same subject. I thoroughly recommend reading all of the latter as it highlights the shortcomings/dangers associated with the steps below.

USB key preparation

datakurre

*.tar.gz
.sentinel.*

montanaflynn

package main

import (
    "log"
    "net/http"
    "net/http/httputil"
)

func main() {
    http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {

jjongsma

#!/usr/bin/python
#
# Usage: packer-config my-template.yaml | packer build -
#
# Constructs a Packer JSON configuration file from the specified YAML
# template file and writes it to STDOUT.
# 
# The YAML template format adds some flexibility and readability by
# adding comments and an !include directive, allowing for the
# following template syntax:

ei-grad

#!/bin/bash

[ "`whoami`" != "root" ] && echo "Should be run by root!" && exit 1

[ -e *.vmdk ] || ( echo Extracting VMDK image from *.ova ... ; tar xf *.ova )
[ -e github.img ] || ( echo Converting *.vmdk to raw image ... ; qemu-img convert *.vmdk github.img )

echo Preparing mounts ...
losetup -f github.img -P
vgchange -ay enterprise-11

cocagne

#!/usr/bin/python

import ctypes
import os
import sys

def err_exit( msg ):
    print >> sys.stderr, msg
    sys.exit(1)