fn main() {
unsafe {
do str::as_c_str(~"The answer is %d.\n") |c| {
let a = 42;
asm!("mov $0, %rdi\n\t\
mov $1, %rsi\n\t\
xorl %eax, %eax\n\t\
call _printf"
:
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
* Ingredients * | |
Crusts for pans of some sort; I used 4" dollarama pot pie pans | |
Crust recipe: https://gist.github.com/h4xnoodle/7296343 | |
~2 cups frozen mixed veggies | |
Almost all of a grocery rotisserie chicken, shredded | |
1 red potato, cubed | |
2+ tbsp butter -- don't go beyond 1/3 cup, fatty | |
one medium cooking onion, diced | |
as much garlic as you want, minced |
On Twitter the other day, I was lamenting the state of OCSP stapling support on Linux servers, and got asked by several people to write-up what I think the requirements are for OCSP stapling support.
-
Support for keeping a long-lived (disk) cache of OCSP responses.
This should be fairly simple. Any restarting of the service shouldn't blow away previous responses that were obtained. This doesn't need to be disk, just stable - and disk is an easy stable storage for most server