These are my notes on instaling NixOS 16.03 on a Lenovo ThinkPad X1 Carbon (4th generation) with an encrypted root file system using UEFI.
Most of this is scrambled from the following pages:
substitutions: | |
# Device Naming | |
devicename: sump-pump | |
friendly_name: Sump Pump | |
device_description: Sump Pump Level Sensor, Counter, and Alarm | |
# Limits for pump levels and alarm levels | |
primary_pumpout_below_height: '0.100' #meters; the primary pump will empty the sump to below this level | |
primary_pumpout_reset_height: '0.140' #meters; primary pump counter is reset when water rises above this level (enabling it to be triggered again) | |
primary_pumpout_duration_limit: '60.0' #seconds; maximum duration for the primary pump to drop the level from 'reset_height' to 'below_height' (otherwise the sump level dropped by some other means e.g. evaporation) |
# This script will manually rip out all VMware Tools registry entries and files for Windows 2008-2019 | |
# Tested for 2019, 2016, and probably works on 2012 R2 after the 2016 fixes. | |
# This function pulls out the common ID used for most of the VMware registry entries along with the ID | |
# associated with the MSI for VMware Tools. | |
function Get-VMwareToolsInstallerID { | |
foreach ($item in $(Get-ChildItem Registry::HKEY_CLASSES_ROOT\Installer\Products)) { | |
If ($item.GetValue('ProductName') -eq 'VMware Tools') { | |
return @{ | |
reg_id = $item.PSChildName; |
{ lib ? null, ... }: | |
let | |
net = { | |
ip = { | |
# add :: (ip | mac | integer) -> ip -> ip | |
# | |
# Examples: |
These are my notes on instaling NixOS 16.03 on a Lenovo ThinkPad X1 Carbon (4th generation) with an encrypted root file system using UEFI.
Most of this is scrambled from the following pages:
// | |
// Results+Rx.swift | |
// | |
// Make Realm auto-updating Results observable. Works with Realm 0.98 and later, RxSwift 2.1.0 and later. | |
// | |
// Created by Florent Pillet on 12/02/16. | |
// Copyright (c) 2016 Florent Pillet. All rights reserved. | |
// | |
import Foundation |
import Foundation | |
// Why bytesView rather than just extending NSData directly? | |
// Because this way we can keep our extension internal and not conflict | |
// with someone who imports us and has also extended NSData. | |
// If you're top-level code, you can just hoist everyting up to NSData directly. | |
internal extension NSData { | |
var bytesView: BytesView { return BytesView(self) } | |
} |
* { | |
font-size: 12pt; | |
font-family: monospace; | |
font-weight: normal; | |
font-style: normal; | |
text-decoration: none; | |
color: black; | |
cursor: default; | |
} |
tell application "Safari" | |
repeat with theSafariWindow in windows | |
tell application "Google Chrome" to set theChromeWindow to make new window | |
repeat with theSafariTab in theSafariWindow's tabs | |
set theURL to URL of theSafariTab | |
tell application "Google Chrome" | |
set theChromeTab to make new tab at end of tabs of theChromeWindow | |
set URL of theChromeTab to theURL | |
end tell | |
end repeat |
Prerequisites:
Software components used: