Raymond P. Burkholder - Things I Do

When you purchase a Treasury note you are lending money to the government for a specified period of time (i.e. 30 days to 30 years) at a fixed rate of interest or yield. The risk of default on Treasuries has generally been considered nonexistent.

The federal government, with assistance from the Federal Reserve, can always print money to pay its debts. But this isn’t without risks. Because printing dollars to pay debts devalues the existing stock of dollar. So while the nominal return is preserved…the inflation adjusted return goes negative.

In short, inflation destroys Treasury values for investors. To account for expectations of rising inflation, yields rise. But this presents another problem for long term Treasury investors.

When Treasury yields go up, Treasury prices go down. Over the last eight months, the yield on the 10-Year Treasury note has increased from 0.5 percent to over 1.54 percent – or 104 basis points.

Treasury investors stand to face major losses. Moreover, as interest rates rise, and borrowing costs become more expensive, several other things happen.

High priced stocks become less attractive. In addition, higher borrowing costs make it harder for over leveraged zombie corporations, state governments, municipalities, and Washington to roll over their debts.

... the great monetary inflation has already happened. The great price inflation is picking up, regardless of what the Bureau of Labor Statics’ bogus CPI report says. Thus, it is certainly possible that the yield on the 10-Year Treasury note could increase another 50-basis points come summer.

There could be corporate debt, hedge fund, and pension fund financial blow ups galore. But this is exactly what the Fed is trying to avoid. The Fed wants inflation without higher interest rates.

-- Fifty Basis Points To Disaster - ZeroHedge

Bringing this back to security—instead of thinking “I need a firewall,” you should be thinking “I need a Policy Enforcement Point that can control network traffic, and a way to define that policy across my infrastructure.” Or, from another angle—instead of thinking “I need to deploy an IDS here to examine my web app traffic for SQL injections,” you should be thinking “I need to make sure that the web application traffic is scanned for SQL injections before it is processed by the app. I have several PEPs in my architecture that may be able to accomplish this goal.” -- Zero Trust Security, An Enterprise Guide, p51

In fact, where is the Clifford Chance call to investigate the fact that a trading strategy of buying at the New York close silver price and selling at the New York open silver price (New York Overnight Index) would have returned 12,000% since 1970 (or 120 times), whereas a strategy of buying at the New York open and selling at the New York close (New York Intraday Index) would have lost nearly 90% of your investment since 1970.

$ lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 029: ID 03f0:1a47 HP, Inc USB2.1 Hub
Bus 001 Device 028: ID 03f0:1a47 HP, Inc USB2.1 Hub
Bus 001 Device 006: ID 03f0:1a47 HP, Inc USB2.1 Hub
Bus 001 Device 004: ID 03f0:1a47 HP, Inc USB2.1 Hub
Bus 001 Device 003: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0424:3fb7 Microchip Technology, Inc. (formerly SMSC) Babyface (23509439)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Device are mainly identified using a pair of hexadecimal numbers, like 04b3:3108.

The 4 first hexadecimal digits are the Vendor ID (04b3 = IBM). The 4 last hexadecimal digits are the Device ID (3108 = ThinkPad 800dpi Optical Travel Mouse).

$ sudo cat /sys/kernel/debug/usb/devices | grep -E "^([TSPD]:.*|)$"

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh=16
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 5.10
S:  Manufacturer=Linux 5.10.0-3-amd64 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=0000:00:14.0

....

And reduced the size of global negative-yielding debt (reducing the attractiveness of zero-yielding crypto)...

“The move in precious metals prices is most often in direct correlation with the direction of interest rates, particularly on sovereign interest rates, and particularly on U.S. sovereign interest rates. So, any firming in the interest rate is good for the precious metals price. Speculators need to determine whether this move higher in interest rates will continue.” - Historic Washout in Bond Market Clearly Impacts Precious Metals

From USB drive that contains a partition table, when installing firmware from a USB drive, there is the following note:

   - Workaround is to format the USB drive without a partition table,
     e.g. "mkfs.vfat -I /dev/sdc" (mkfs.vfat actually expects a
     partition table, -I override forces it to use the entire device)

Miscellaneous:

• Mounting the root filesystem via NFS (nfsroot) - n order to use a diskless system, such as an X-terminal or printer server for example, it is necessary for the root filesystem to be present on a non-disk device. This may be an initramfs (see Documentation/filesystems/ ramfs-rootfs-initramfs.txt), a ramdisk (see Documentation/admin-guide/initrd.rst) or a filesystem mounted via NFS.

A key resource to keep: Part-UUID - Persistent device naming for block devices has been made possible by the introduction of udev and has some advantages over the use of traditional bus-based names.

A basic overview of which devices are associated with which persistent names simply by invoking:

$ ls -lR /dev/disk

When in the grub prompt, these two commands provide good situational awareness:

• run the 'set' command to see what the current boot and network variables are.
• run the 'ls' command to see what devices and partitions are available

Then something like 'ls (hd0,gpt1)/boot' can show files in that partition

When running manual boot operations in the grub menu on a Dell Wyse 3040, something along the lines of the following might be used:

grub> linux (hd0,gpt2)/vmliunz root=/dev/mmcblk0p2 ro
grub> initrd (hd0,gpt2)/initrd.img
grub> boot

At Grub not loading config file or booting into linux automatically shows the trick of starting the grub menu:

grub> configfile (hd0,gpt4)/boot/grub/grub.cfg

• iPXE installation and EFI - building menus
• 4.1 Installing GRUB using grub-install - from the Grub manual
• iPXE and Debian PreSeed
• netboot.xyz is a way to PXE boot various operating system installers or utilities from one place within the BIOS without the need of having to go retrieve the media to run the tool. iPXE is used to provide a user friendly menu from within the BIOS that lets you easily choose the operating system you want along with any specific types of versions or bootable flags.
• Index of boot.ipxe.org - up to date files for for use, note the iso is for legacy boot only
• Debian UEFI - intended to describe UEFI for Debian purposes
• Emedded scripts -
• Debian Debootstrap - is a tool which will install a Debian base system into a subdirectory of another, already installed system - uses chroot to make and modify images
• ipxe-scripts/boot/linux/debian.ipxe -
• Booting CoreOS Container Linux via iPXE - many descriptive details
• Automated Install with Debian Preseed - well documented preseed for a number of scenarios
• -
• -
• -

Some items to look into:

• Linux Terminal Server Project (LTSP) -

For the life of me, even though there is a menu option the Dell Wyse ThinClient 3040 to EFI PXEBoot, it pulls DHCP information, but never requests the boot files from the PXE server.

Probably the most detailed account of innards of the Wyse 3040 (N10D): Hardware.

Instead, as a work around, the goal is to keep a USB stick inserted into the 3040 to act as a PXE boot mechanism to install Debian on to the local drive.

After building a USB filesystem, Install IPXE files (as a side effect, it adds an ipxe menu item to grub.cfg):

$ apt install ipxe

Mount the partition:

$ mkdir mnt
$ sudo mount /dev/sda1 mnt

Create the EFI BOOT directory:

$ sudo mkdir -p mnt/EFI/BOOT/

Copy the IPXE EFI boot file natively, and as a required name:

$ sudo cp /usr/lib/ipxe/ipxe.efi mnt/EFI/BOOT/
$ sudo cp /usr/lib/ipxe/ipxe.efi mnt/EFI/BOOT/BOOTX64.EFI
$ ls mnt/EFI/BOOT/
BOOTX64.EFI  ipxe.efi

The rename to BOOTX64.EFI is required as this is hardcoded in the boot menus for the Wyse 3040. During the tail end of a Debian Expert install, there is a question of whether to install into a legacy EUFI boot directory. This performs that /EFI/BOOT/... build.

Install Grub (see --removable reference:

# sudo grub-install /dev/sda --removable  # may solve the above problem with BOOTX64.EFI, needs to be tried
$ sudo grub-install /dev/sda
Installing for x86_64-efi platform.
Installation finished. No error reported.

Unmount the drive for use:

$ sudo umount /dev/sda1

BIOS entries for the Dell Wyse 3040 to use with this iPXE USB (default password Fireport):

• General -> Boot Sequence -> disable both IP6&IP4 Realtek GBE
• System Configuration -> UEFI Network Stack -> uncheck Enable UEFI Network Stack
• System Configuration -> Integrated Nic -> Enabled (no PXE)
• System Configuration -> USB Configuration -> check Enable USB Boot Support
• Secure Boot -> Secure Boot Enable -> Disabled
• Power Management -> Wake on LAN -> LAN Only
• Virtualization Support -> Virtualization -> Enable

The key is the 'ether' specifier. The -e option shows the mac address in the output:

$ sudo tcpdump -n -i vlan50 ether host e4:54:e8:29:44:2d or ether host ff:ff:ff:ff:ff:ff -vv -e

I had this error when trying to EUFI boot with IPXE against a DNSMasq server:

Filename: bootnetx64.efi
tftp://10.x.x.x/bootnetx64.efi... ok
bootnetx64.efi : 1322936 byes [EFI]
Fetching Netboot Image
Malformed binary after Attribute Certificate Table
datasize: 4194034 SumOfBytesHashed: 1253376 SecDir->Sisze: 1392
hashsize: 2939536 SecDir->VirtualAddress: 0x00132000
Failed to load image: Invalid Parameter
start_image() returned Invalid Paramter
Could not boot image: Error 0x7f048282 (http://ipxe.org/7f048282)

The issue is that I had grubx64.efi and bootnetx64.efi incorrectly positioned in /etc/dnsmasq.d/local. This is the correct statement placement:

dhcp-match=set:efi-bc,option:client-arch,7
dhcp-boot=tag:efi-bc,grubx64.efi
pxe-service=tag:efi-bc,BC_EFI, "Install,bc", bootnetx64.efi,

WARNING: performing these operations can be dangerous to desired data. Be careful against which drives you apply these commands.

Acquire current geometry:

$ sudo sfdisk -d /dev/sda
label: dos
label-id: 0x1bc93b71
device: /dev/sda
unit: sectors
sector-size: 512

/dev/sda1 : start=        2048, size=      524288, type=b

$ sudo sfdisk -d /dev/sda > sda.txt

Kill the partition table (dangerous!):

$ sudo dd if=/dev/zero of=/dev/sda count=1 bs=512
1+0 records in
1+0 records out
512 bytes copied, 0.00642451 s, 79.7 kB/s

$ sudo fdisk -l /dev/sda
Disk /dev/sda: 57.73 GiB, 61984505856 bytes, 121063488 sectors
Disk model: DataTraveler 2.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Rebuild the drive, equally dangerous, but with some backup with the -O:

$ sudo sfdisk -O sfdisk.save /dev/sda < sda.txt
Checking that no-one is using this disk right now ... OK

Disk /dev/sda: 57.73 GiB, 61984505856 bytes, 121063488 sectors
Disk model: DataTraveler 2.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Created a new DOS disklabel with disk identifier 0x1bc93b71.
/dev/sda1: Created a new partition 1 of type 'W95 FAT32' and of size 256 MiB.
Partition #1 contains a vfat signature.
/dev/sda2: Done.

New situation:
Disklabel type: dos
Disk identifier: 0x1bc93b71

Device     Boot Start    End Sectors  Size Id Type
/dev/sda1        2048 526335  524288  256M  b W95 FAT32

The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

Check the partition tables;

$ sudo fdisk -l /dev/sda
Disk /dev/sda: 57.73 GiB, 61984505856 bytes, 121063488 sectors
Disk model: DataTraveler 2.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1bc93b71

Device     Boot Start    End Sectors  Size Id Type
/dev/sda1        2048 526335  524288  256M  b W95 FAT32

Format the filesystem:

$ sudo mkfs -t vfat /dev/sda1
mkfs.fat 4.1 (2017-01-24)

user manual for sfdisk, which learned about at How to run fdisk in non-interactive batch mode.

I used fdisk /dev/sda to create the initial flavour of the vfat 256MB drive. Not much space is required to build a disk for ipxe boot operations (using a Dell Wyse 3040 ThinClient which does not seem to know how to PXE boot natively).

$ mkdir mnt
$ sudo mount -o loop ~/Downloads/iso/debian-10.7.0-amd64-netinst.iso mnt
$ ls mnt
$ sudo umount mnt

The command wipefs can be used to examine the read partition boot-signatures, and possible 'kill' them.

# wipefs /dev/sda
DEVICE OFFSET      TYPE    UUID                   LABEL
sda    0x36        vfat    D14A-DCD7
sda    0x0         vfat    D14A-DCD7
sda    0x1fe       vfat    D14A-DCD7
sda    0x8001      iso9660 2020-02-25-20-44-34-00 ISOIMAGE
sda    0xe6e907e00 gpt

# dd if=/dev/zero of=/dev/sda bs=512 count=1
1+0 records in
1+0 records out
512 bytes copied, 0.00808424 s, 63.3 kB/s

# wipefs /dev/sda
DEVICE OFFSET      TYPE    UUID                   LABEL
sda    0x8001      iso9660 2020-02-25-20-44-34-00 ISOIMAGE
sda    0xe6e907e00 gpt

# wipefs -a /dev/sda
/dev/sda: 5 bytes were erased at offset 0x00008001 (iso9660): 43 44 30 30 31
/dev/sda: 8 bytes were erased at offset 0xe6e907e00 (gpt): 45 46 49 20 50 41 52 54
/dev/sda: calling ioctl to re-read partition table: Success

# wipefs /dev/sda

WipeFS Documentation