- TFTP server
- IPXE Make sure ipxe.lkrn is in the TFTP root.
- iSCSI target (Server) Assume we have an iSCSI target "1:net.cszombie.au:windows" that is ready to be connected. 1 is LUN id, "net.cszombie.au:windows" is the target name.
- HTTP server (To speed up loading boot.wim, http is faster than tftp, http is supported by IPXE, however this is optional)
Discover gists
#!/bin/bash | |
# Receives your Windows username as only parameter. | |
curl -LO https://storage.googleapis.com/kubernetes-release/release/v1.16.0/bin/linux/amd64/kubectl | |
chmod +x ./kubectl | |
sudo mv ./kubectl /usr/local/bin/kubectl | |
windowsUser=$1 |
Imagine you are building a simple project management application that has follwing simple features
- Manage projects (your organisation may have multiple projects running)
- Manage work packages related to a project
- Manage members in your organisation that may need to have access to projects in your organisation.
zkCoins is a novel blockchain design with strong privacy and scalability properties. It combines client-side validation with a zero-knowledge proof system. The chain is reduced to a minimum base layer to prevent double spending. Most of the verification complexity is moved off-chain and communicated directly between the individual sender and recipient of a transaction. There are very few global consensus rules, which makes block validation simple. Not even a global UTXO set is required.
In contrast to zk-rollups there is no data availability problem, and no sequencer is required to coordinate a global proof aggregation. The protocol can be implemented as an additional layer contained in Bitcoin's blockchain (similar to RGB[^5] or Taro[^6]) or as a standalone sidechain.
The throughput scales to hundreds of transactions per second without sacrificing decentralization.
The core design principle is to *"use the chain for what the chain is good for, which is an immutable order
// Remember to install mini-svg-data-uri | |
// Follow me on twitter for memes @jordienr | |
import { type Config } from "tailwindcss"; | |
const { | |
default: flattenColorPalette, | |
} = require("tailwindcss/lib/util/flattenColorPalette"); | |
const svgToDataUri = require("mini-svg-data-uri"); | |
export default { |
# pacman aliases | |
alias pac='pacman -S' # install | |
alias pacu='pacman -Syu' # update, add 'a' to the list of letters to update AUR packages if you use yaourt | |
alias pacr='pacman -Rs' # remove | |
alias pacs='pacman -Ss' # search | |
alias paci='pacman -Si' # info | |
alias paclo='pacman -Qdt' # list orphans | |
alias pacro='paclo && sudo pacman -Rns $(pacman -Qtdq)' # remove orphans | |
alias pacc='pacman -Scc' # clean cache | |
alias paclf='pacman -Ql' # list files |
I've recently tested on how to move the custom domain catch all email from G Suite to the new iCloud+ Catch All feature and wanted to share my experience.
The end result is having Custom Domain email and Catch All routing, that can be fully used via Gmail, including receiving and sending emails.
- Setup your Custom Domain (or subdomain) with iCloud+