- Design config UI
- Use daemon config api to modify crc configuration
- Create a progress window and animate icon
- Prompt user for pull secret bundle if not configured
- Reduce the number of UAC prompts during setup
$tempDir = $args[0] | |
$startUpFolder = "$Env:USERPROFILE\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup" | |
function RemoveUserFromServiceLogon | |
{ | |
# security template to modify SeServiceLogonRight | |
$securityTemplate = @" | |
[Unicode] | |
Unicode=yes | |
[Version] |
Many users of Git are curious about the lack of delta compression at the object (blob) level when commits are first written. This efficiency is saved until the pack file is written. Loose objects are written in compressed, but non-delta format at the time of each commit.
A simple run though of a commit sequence with only the smallest change to the image (in uncompressed TIFF format to amplify the observable behavior) aids the understanding of this deferred and different approach efficiency.
Create the repo:
CRC has a daemon, which can be used to do some basic CRC operations, to start the daemon run crc daemon
or with debug logging crc daemon --log-level debug
In case of macOS and Windows, crc setup --enable-experimental-features
will start the daemon but it'll also start the tray.
The daemon when started, listens on a Unix socket at $CRC_HOME/crc.sock, (~/.crc/crc.sock in linux and macOS) for commands/requests.. After connecting to the socket, it accepts commands as a JSON.
It understands a subset of the crc CLI commands:
CLI commands | Daemon api | Response |
---|
import urllib2 | |
import json | |
def rpc_call(url, method, args): | |
data = json.dumps({ | |
'id': 1, | |
'method': method, | |
'params': [args] | |
}).encode() |
var E_PREFIX_RATE = 0.25; | |
// All of our word lists: | |
var _word_lists = { | |
verb : [ | |
"implement", "utilize", "integrate", "streamline", "optimize", "evolve", "transform", "embrace", | |
"enable", "orchestrate", "leverage", "reinvent", "aggregate", "architect", "enhance", "incentivize", | |
"morph", "empower", "envisioneer", "monetize", "harness", "facilitate", "seize", "disintermediate", |
# -*- mode: ruby -*- | |
# vi: set ft=ruby : | |
Vagrant.configure("2") do |config| | |
config.vm.box = "generic/fedora28" | |
config.vm.network "public_network" | |
config.vm.synced_folder ".", "/vagrant", type: "nfs" | |
config.vm.provider "vmware_desktop" do |v| | |
v.ssh_info_public = true | |
v.vmx["numvcpus"] = "2" |
#IRC Reference
Not intended as a guide for newbies, more like a "cheat sheet" for the somewhat experienced IRC user, especially one who wields some power over a channel.
##The Basics
/join #channel
/part #channel
#!/usr/bin/env bash | |
vol_list=$(sudo virsh vol-list --pool default | grep test1 | awk '{print $1}') | |
for vol in $vol_list | |
do | |
sudo virsh vol-delete $vol --pool default | |
done | |
sudo virsh net-destroy test1 | |
sudo virsh net-undefine test1 |