How to retrieve the current user's home directory from either Command Prompt or PowerShell:
C:\> cmd /c "echo %homedrive%%homepath%"
C:\Users\andrew
PS C:\> cmd /c "echo %homedrive%%homepath%"
C:\Users\andrew
How to retrieve the current user's home directory from either Command Prompt or PowerShell:
C:\> cmd /c "echo %homedrive%%homepath%"
C:\Users\andrew
PS C:\> cmd /c "echo %homedrive%%homepath%"
C:\Users\andrew
Unix: which <program>
Windows: where.exe <program>
The .exe
requirement is due to where
being a token of the PowerShell language
PS C:\Users\andrew\Downloads> .\fciv.exe -both .\BootCamp5.1.5621.zip | |
// | |
// File Checksum Integrity Verifier version 2.05. | |
// | |
MD5 SHA-1 | |
------------------------------------------------------------------------- | |
b32fce2718918a7ada6e2153b95c2d1f 72c71be259474836c17ddd400aca2218660b8aac .\bootcamp5.1.5621.zip |
The latest BootCamp drivers fail to support Function keys on Apple internal laptop keyboards in Windows 10. To fix this, one can use an older driver.
BootCamp5.1.5621\BootCamp\Drivers\Apple
, run AppleKeyboardInstaller64.exe
.The driver situation with Apple Bluetooth wireless keyboards and Windows 10 is horrible, even with the latest BootCamp drivers. Fortunately, a workaround is available, if you're patient.
Command + w
until the keyboard light begins blinking, indicating the keyboard is ready to pair.123456 Enter
) on both internal and external keyboards.Pairing the keyboard is very trial and error. 9/10 times, Windows will complain that the keyboard is not available for pairing. Just keep trying.
shell:startup
curl --include \ | |
--no-buffer \ | |
--header "Connection: Upgrade" \ | |
--header "Upgrade: websocket" \ | |
--header "Host: example.com:80" \ | |
--header "Origin: http://example.com:80" \ | |
--header "Sec-WebSocket-Key: SGVsbG8sIHdvcmxkIQ==" \ | |
--header "Sec-WebSocket-Version: 13" \ | |
http://example.com:80/ |
ansible-playbook --connection=local 127.0.0.1 playbook.yml
127.0.0.1 ansible_connection=local
node { | |
echo 'Results included as an inline comment exactly how they are returned as of Jenkins 2.121, with $BUILD_NUMBER = 1' | |
echo 'No quotes, pipeline command in single quotes' | |
sh 'echo $BUILD_NUMBER' // 1 | |
echo 'Double quotes are silently dropped' | |
sh 'echo "$BUILD_NUMBER"' // 1 | |
echo 'Even escaped with a single backslash they are dropped' | |
sh 'echo \"$BUILD_NUMBER\"' // 1 | |
echo 'Using two backslashes, the quotes are preserved' | |
sh 'echo \\"$BUILD_NUMBER\\"' // "1" |
Services declared as oneshot
are expected to take some action and exit immediatelly (thus, they are not really services,
no running processes remain). A common pattern for these type of service is to be defined by a setup and a teardown action.
Let's create a example foo
service that when started creates a file, and when stopped it deletes it.
Create executable file /opt/foo/setup-foo.sh
: