You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How I initialized the irtnog/salt-states repository
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Installing Ubuntu 15.04 on MacBookPro5,1 with root-on-ZFS-on-LUKS (dual boot with Mac OS X 10.10 via rEFInd)
Connect the Ethernet NIC to the LAN, since WiFi doesn't work in Ubuntu
until after installing the bcmwl-kernel-source package.
From the Mac OS X 10.10.2 (Yosemite) installer:
Create a new two-partition layout, with the first partition named
"Macintosh HD", formatted as Mac OS Extended (Journaled), and
sized to 40 GB; and with the second partition formatted as free
space.
Install OS X on "Macintosh HD".
Skip signing in with your Apple ID. (Otherwise, take all of the
I disabled any hardware RAID features, preferring instead to rely on ZFS. The eServer's ServeRAID controller wouldn't let me export its attached hard disk drives without creating a new single-drive RAID-0 array for each one.
FreeBSD's boot loader can access USB mass storage devices only if supported by the computer's BIOS. To test this I connected a USB flash drive to the server prior to powering it up, and then I booted the FreeBSD 9.0-RELEASE installation CD. From the boot menu I exited to the loader prompt (menu option 2) and issued the lsdev command to review the BIOS device list. In my case both servers listed only their floppy disk, CD, and hard disk drives, meaning that I couldn't boot them via USB nor could I access encryption keys stored on a USB mass storage device. (This is why I chose to boot from CD instead of USB.)
To continue with the installation, I entered the "boot" command to start FreeBSD and chose the option to use the live CD (log in as user `root
Dual-boot Mac OS X (FileVault2) and Ubuntu (OpenZFS/LUKS)
Dual-boot Mac OS X (FileVault2) and Ubuntu (OpenZFS/LUKS)
This procedure results in a computer that runs both Mac OS X and
Ubuntu in a dual-boot configuration, each operating system using full
(whole) disk encryption, and with the Ubuntu root file system stored
on a ZFS pool encrypted using LUKS. The specific hardware and
software versions used to document this procedure are:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Recipe for Getting Strange Binaries Running in AWS Lambda
Recipe for running strange binaries in AWS Lambda
In general, the command ldd and the environment variable LD_LINKER_PATH is your best friend when running new, untested binaries in Lambda. My process (which I want to get around to automating one day, maybe using Packer), goes like this:
Run an EC2 instance with the official AWS Lambda AMI.
Get binary you want to run in AWS Lambda running on the instance (either by installing from a package manager or compiling).
Run ldd -v ./the-binary. Note all of the shared libraries it requires. You’ll need to remember these.
Copy the binary to your local machine. Upload the binary with your AWS Lambda function code that runs the ldd command inside the handler function using the process execution library from your language of choice. In node, this works just fine: console.log(require('child_process').execSync('ldd -v ./the-binary'))
Note any shared libraries that are missing in the function output. Copy those over from the EC2 instance to a direct
Example Shibboleth IdP 3.x configuration for use with Active Directory
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a TRAMP method named `sudosu` that runs `sudo su - <USERNAME>`
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters