hdiutil attach /Applications/Install\ macOS\ Sierra\ Public\ Beta.app/Contents/SharedSupport/InstallESD.dmg -noverify -nobrowse -mountpoint /Volumes/install_app
hdiutil create -o /tmp/Sierra.cdr -size 7316m -layout SPUD -fs HFS+J
hdiutil attach /tmp/Sierra.cdr.dmg -noverify -nobrowse -mountpoint /Volumes/install_build
asr restore -source /Volumes/install_app/BaseSystem.dmg -target /Volumes/install_build -noprompt -noverify -erase
rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages
cp -rp /Volumes/install_app/Packages /Volumes/OS\ X\ Base\ System/System/Installation/
cp -rp /Volumes/install_app/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System/BaseSystem.chunklist
package main | |
import ( | |
"net/http" | |
"Regexp" | |
) | |
type route struct { | |
pattern *regexp.Regexp | |
handler http.Handler |
$HTTP["url"] =~ "/shorewall" { | |
proxy.server = ( | |
"/" => ( | |
"/" => ( "host" => "127.0.0.1", "port" => 5000 ) | |
) | |
) | |
} |
# ssh key generator data source expects the below 3 inputs, and produces 3 outputs for use: | |
# "${data.external.ssh_key_generator.result.public_key}" (contents) | |
# "${data.external.ssh_key_generator.result.private_key}" (contents) | |
# "${data.external.ssh_key_generator.result.private_key_file}" (path) | |
data "external" "ssh_key_generator" { | |
program = ["bash", "${path.root}/../ssh_key_generator.sh"] | |
query = { | |
customer_name = "${var.customer_name}" | |
customer_group = "${var.customer_group}" |
The LSI Blueprint (.blueprint) file specification follows. This file format is used by LSI to build an arbitrary number of binary packages out of source code releases for AltimatOS and other UNIX-like operating systems.
Initially, LSI packages started as a wrapper over shell code for trying to formally build from-source software into a build root. This unfortunately, has limitations with regards to tracking, verifying, and managing installed dependencies. To help create a package format that can be used for managing software on the systems, it has become clear that a defined grammar for the blueprint (the package's specification and build scripts) should be created to ensure correctness of the build.
The specification below is a pseudo BNF format and should not be considered proper ABNF, BNF, or EBNF syntax.
I hereby claim:
- I am greeneg on github.
- I am greeneg (https://keybase.io/greeneg) on keybase.
- I have a public key whose fingerprint is AF83 F5FA 478C F72F F518 0BB8 E3E9 FD62 EFCF 76D8
To claim this, I am signing this object: