Entries by Raymond P. Burkholder

• Chapter 4. Common kernel-related tasks - Debian Handbook

• BitZuma - blog and link to bitcoin book

• The Ultimate List of SANS Cheat Sheets - General IT Security, Digital Forensics and Incident Response, Penetration Testing, All Around Defender Primers (Linux, PowerShell, Network)
• Blueprint: MEF-SDN/NFV Certification Exam - more for the references to SDN sources
• spam resource
• MS SNDS
• infrapedia
• Canadian Numbering
• NANPA
• small mailserver bcp
• mta-sts
• data247 - paid service

Some SSH advanced features:

• SSH Emergency Access - design a break glass procedure for reaching SSH hosts in an emergency, using security keys that you can store offline
• How to SSH Properly - a few different ways to easily improve the security of the SSH model without needing to deploy a new application or make any huge changes to user experience - certificates, bastion hosts, 2-factor authentication
• SSH Handshake Explained
• gravitational / teleport - from How Uber, Facebook, and Netflix Do SSH

Is Parallel Programming Hard, And, If So, What Can You Do About It? - The purpose of this book is to help you program shared-memory parallel machines without risking your sanity.

It provides in-depth analysis of parallel programming at the cpu level of programming. A downloadable, git versioned, pdf.

Seen on the IQFeed Developer Support 2020/04/21. A solution for allowing ICMP packets.

iqconnect.exe does a ping round trip against its DTN servers (you can see the ping results at IQConnect.log when you stop the feed and iqconnect.exe exits). Thing is, ping uses ICMP protocol, which in linux is somewhat privileged.

So, you need to give wine the appropiate permissions in order to be able to use ICMP. Running wine as root in order to circumvent this problem would be overkill (besides a very bad thing to do!), but fortunately you can use setcap in order to grant permissions in a much more granular way.

First, locate where your wine-preloader file is. In my case, it's on /usr/bin/wine-preloader . Then, type (yoo will need to sudo for this):

sudo setcap cap_net_raw+epi /usr/bin/wine-preloader

and that's all. Now wine is allowed to use ICMP protocol, which in turn will allow IQconnect.eze to make its "ping things" without complaining

In a follow on post to my previous GUI From an LXC Container on the Host entry, here are some notes on linking sound in an LXC container to the host's sound system.

The primary reason for this was to get around Interactive Broker's broken sound requirements for really old libav libraries. Which is back to the version x53 libraries from the Debian Jessie / Ubuntu Precise 12.04 days. Long story short, I don't have this working yet. The basic issue I have is that, when running TWS in an LXC container, all the configuration menu options but one work. When I click on the 'Sound Manager' menu item, TWS locks up, and I don't see any log messages anywhere as to why this might happen. So there is something special in an LXC container environment which is locking up sound in TWS.

But I did get sound from FireFox / Youtube to work.

This on a Debian Bullseye system.

The basic solution is, in the LXC container configuration file, to mount the Pulse Audio socket from the user's account of the host into the container and set an environment for the user in the container. In this case, the user has UID of 1000:

lxc.mount.entry = /run/user/1000/pulse/native tmp/pulse/native none rw,bind,create=file 0 0
lxc.environment = PULSE_SERVER=unix:/tmp/pulse/native

For completeness, these can be added (helps with ALSA):

lxc.mount.entry = /dev/snd dev/snd none bind,optional,create=dir
lxc.cgroup.devices.allow = c 116:* rwm

That is about all to make it all work. Some or all of the following package installs in the container might help:

sudo apt install \
  pulseaudio \
  pulseaudio-utils \
  pavucontrol \
  gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-pulseaudio \
  mpg123

I am almost embarrassed to say that I missed a good night's sleep sifting through erroneous out of date misinformation, missing some subtle distinctions, and winnowing out the chafe.

This all started when I wanted to give Krita a try for editing photographs. It is said it is the next best thing in open source when compared to PhotoShop. When installed on my Debian Linux workstation, all I could get out of it was crashes of one form or another. I'm not really surprised as my workstation has been through various combinations of buster, testing, bullseye, sid and experimental. Some package is out of sync somewhere.

So.. since I know how to run LXC containers, I figured I'd give that a try. That was successful, to a point. I used X2Go for remote console. But when my images are Nikon NEF files at 24Megapixels at 14bits each, file size, computation, and visualization are a bit of challenge (the screen updates being the main challenge). A wide erasure brush was slow, even on my speedy machine.

There are sites which vehemently say that there is no direct way to see the GUI from a container on a workstation host. Sigh. Misinformation. Then there are the five year old sites which show how it is done, but have extra commands, missing commands, or missing options. More sigh.

After much trial and error and trying the same things over again, with minor variations on the theme, in the hopes something might fix itself, it was a long night.

For the record, here is my research on a Debian Bullseye system with LXC '1:3.1.0+really3.0.4-3' Continue reading "GUI From an LXC Container on the Host" »

Some C++ libraries I've encountered for managing currency manipulation:

• vpiotr / decimal_for_cpp - this is the one I use for my currency work, is header based, succinct, and easy to use.
• I was wondering if boost.multiprecision could be used, and came up with mariusbancila / moneycpp - a bit too much for me as it also handles currency codes. There is a a blog entry: moneycpp – a C++ library for handling monetary values.
• General Decimal Arithmetic goes into some detail about the related IEEE 754 standard, as well as a link to a C language implementation.

From Debian Misc Developer News (#51):

Steve McIntyre created[3] a debian-preseed[4] service that extracts all of the debconf templates in the Debian archive and lists each of the possible preseed options available along with their descriptions. If you want to repeat the extractions, you can use Steve's new Perl script or the existing tools on the preseed wiki page[5].

-- Paul Wise

• [3] https://blog.einval.com/2020/02/24#what_can_you_preseed
• [4] https://jack.einval.com/debian-preseed/
• [5] https://wiki.debian.org/DebianInstaller/Preseed

When one doesn't know the keystroke to get into the BIOS, one handy command to reboot from Linux:

# systemctl reboot --firmware-setup

zram, formerly called compcache, is a Linux kernel module for creating a compressed block device in RAM, i.e. a RAM disk, but with on-the-fly “disk” compression. Debian has a init system file for it.

I'm one of those who use zsmalloc as a module - mainly because I use zram as a compressing general purpose block device, not as a swap device. I create zram0, mkfs, mount, checkout and compile code, once done - umount, rmmod. This reduces the number of writes to SSD. Some people use tmpfs, but zram device(-s) can be much larger in size. That's a niche use case and I'm not against the patch.

Running out of RAM in Ubuntu? Enable ZRAM -

When using some relatively inexpensive parts to build a test three server Ceph solution, it seems that drive controllers and SSD drive combinations are finicky. Specifically, it seems that a Dell H310 controller may have issues with some or all Samsung SSD drives.

At Slow writes PERC H700 and Samsung 850 PRO SSD, a Dell response indicates:

The Samsung 850 Pro SSDs are not validated or certified to work with Dell controllers and as such there is a communication mismatch between the drives and the controller at the firmware level. As a result, you are bound to realize unexpected poor Read and Write performance regardless of controller cache settings.

It said that the Samsung 840 drive will work with the controllers. With Broadcom taking over LSI, they've removed old links, so documents are hard to find now. In trying to follow a document trail:

• Dell PowerEdge RAID Controller (PERC) H310, H710, H710P, and H810User’s Guide on page 9 says the H310 has an LSI2008 chipset. I'm looking at the H310 as it provides for direct passthrough to the drives with out RAID. The card has no caching.
• LSI SAS 2008 RAID Controller/ HBA Information - An H310 is similar to the LSI9211-8i
• Check Interoperability and Compatibility

To use the H310 for non-cache passthrough, it is recommended to flash the card in IT mode. I'll try this once I obtain the card. In the meantime, some possibly relevant links to the drivers and process:

• Disk Controller features and Queue Depth? - from 2014, discusses queue depth and diagnostic commands.
• Flashing the H310 Mono Mini to IT mode has a link to probably the best link to a flashing tutorial. But is complicated for flashing the mini H310. From the notes: the R610 is an 11th generation server, and when the mini H310 is reflashed to IT mode, the server probably won't reboot.
• Crossflashing the Dell PERC H200 and H310 to the LSI 9211-8i (from year 2018) implies that the H310 is the equivalent of an LSI 9211-8i. Also, a Dell H200 and an H310 must be similar from a firmware perspective.
• Flashing IT Firmware to the LSI SAS9211-8i HBA - 2012 - flash to a pci card
• How to crossflash PERC H310 to IT mode LSI 9211-8i firmware (HBA for FreeNAS, UnRAID) - an article from 2017 with better, more native instructions
• Crossflash Dell PERC H310 to LSI 9211-8i IT Mode Using Legacy (DOS) and UEFI Method (HBA Firmware + BIOS)
• PERC H310 - LSI 9211-8i - $50 - notes on purchase, install, and upgrade of card.
• Problems Flashing Dell Perc H310 - discusses H310 in PCI slot instead
• How-to Flash Dell Perc H310 with IT Firmware To Change Queue Depth from 25 to 600
• Updated: SAS HBA crossflashing or flashing to IT mode, Dell Perc H200 and H310 from 2016 where is is suggested that "Integrated, Mini or Mini Mono Perc H310 do NOT try to crossflash with these steps".
• DELL PERC H310/H710/H710P/H810 Controllers driver version 5.1.112.64,A00 - a starting point for the search of appropriate drivers
• LINUX PERCCLI Utility For All Dell HBA/PERC Controllers - and the starting point for command line utilities
• LSI MegaRAID SAS - some notes on the CLI utilities
• Doing battle with a Dell R620 and Ubuntu - has some remarks on H310 testing.
• H310 and Fan Noise
• Low random read/write on samsung 840 250gb ssd - spectre bios upgrades can destroy random read/write times

Drive Information:

• Don't do it: consumer-grade solid-state drives (SSD) in Storage Spaces Direct
• Ceph: how to test if your SSD is suitable as a journal device?
• High-performance cluster storage for IOPS-intensive workloads

Cluster test:

rados bench -p vm_storage 10 write -b 4M -t 16"

It is said that fruits and vegetables need to be washed prior to use. Yes, washing can probably get rid of most dirt and grind, but does washing actually make vegetables and fruit safer? Is there a better way to remove pathogenic microorganisms?

I came across How to eat raw beet greens safely? where there is a section discussing "Vinegar, salt, warm water to fight pathogens":

Vinegar has an antibacterial action, inhibiting bacterial growth.

In a study, scientists combined the use of vinegar and sodium chloride (salt). This solution was effective for the prevention of bacterial food poisoning.

Another study measured the effectiveness of vinegar against bacteria, such as Escherichia coli.

Researchers measured the antibacterial action of vinegar depended to:

• presence of sodium chloride (the common salt) and
• temperature

When scientists used 2.5% acetic acid (vinegar) at 20°C, they had to wait 739 min for the inactivation of pathogens.

This time shortened to 5.27 min by just adding 5% sodium chloride (salt).

Amazing…Just by adding salt, the time shortened to 1/140.

The results were even more astonishing when scientists used warm water.

Only with the use of 2.5% vinegar and warm water at 40 ^oC, the inactivation time was just 14.4 min. Less than a quarter of an hour…

What happened when scientists combined vinegar, salt, and warm water?

The inactivation time was only 0.89 min… Less than a minute…