VirtualTam's bookmarks

  1. Standard library:

    • unicode - Data and functions to test some properties of Unicode code points

    Extra libraries:

    Third-party libraries:

    • anyascii/go - Converts Unicode characters to their best ASCII representation

    RFCs:

    Resources:

  2. He was the protege of James Trussart, who recognized his art was beyond anything that had ever been done. He was completely brilliant, maybe too much for sanity, as he would spend months building one a kind creations and built every single detail by hand. He would build the knobs, the saddles, the control plates all from solid blocks of brass. He also built his own revolutionary pickups hiding the secret of his custom design by integrating them inside the body, he also built his own cases, but even down to the smallest of details like the hinges and the handle, also built by hand from solid brass. The guitar bodies are made from resin.

    1. Blocking TCP port 53 traffic leads to very strange failures. Don't.
    2. The source you're looking at is not the code running in production.
    3. "Prod" is just another name for "staging".
  3. Vim: Function copy 2022-01-05
    va{Vy
    
    1. Place the cursor somewhere in my method,
    2. va{ to visually select the the code block,
    3. V to turn the selection from character-wise to line-wise,
    4. y to yank
  4. Here are the steps I used to migrate a CentOS 7 VM from (presumably?) an ESXi server, to a local VirtualBox environment.

    The LVM volumes were not detected at boot, and after the boot timeout, the OS fell back to the Dracut emergency shell.

    • get a CentOS minimal installation CD
    • check the VM's resources and peripherals:
      • ensure there are no floppy drives (!)
      • setup CPU and RAM resources
      • check virtual drives
      • add an SCSI optical drive if needed
    • optional: convert the virtual drive images from VMDK to VDI
    • mount the CentOS installation disc
    • boot on the installation disc:
      • select "Troubleshooting", then "Rescue"
      • let the rescue utility detect filesystems and mountpoints
    • $ chroot to the detected environment
    • backup files:
      • /etc/fstab
      • /boot/grub/grub.cfg
    • under /boot, backup the initrd and initramfs for the current configuration (these will be overwritten)
    • compare the current /etc/fstab with the output of $ lsblk and $ blkid
    • if needed, manually edit /etc/fstab to use the appropriate block device UUIDs, identifiers and mountpoints
    • regenerate GRUB configuration:
      • $ grub2-mkconfig -o /boot/grub2/grub.cfg
    • if needed, reinstall GRUB:
      • $ grub-install /dev/sda
    • rebuild initrd:
      • $ mkinitrd --force /boot/<initrd_image> <kernel_version>
    • rebuild initramfs:
      • $ dracut --force <kernel_version>
    • exit the chroot
    • unmount the installation disc
    • reboot
    • optional but highly recommended: cross your fingers
    • ...
    • profit!
  5. Literate DevOps 2016-03-29

    """ Instead of opening up a terminal to my virtual machine, I pop into Emacs and load this sprint’s /note file/1, create a new header, and enter the shell and ruby commands in this text file.

    What good is this? Unlike a traditional terminal, this allows me to log, document and execute each command.

    As an old bear with very little brains, my prose can explain the background and purpose of each command. Clicking the hyperlink refreshes my memory of previous discoveries. A keychord executes the code block… """