Milosz Linkiewicz Fiooodooor

## Norea.md

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                Fiooodooor
                / Norea.md
            
            
              Last active
              August 18, 2025 00:07
            
          
    What Eleleth told Norea
The Watchers and their Book
a special place is given to those creatures who watch over certain passages that are represented as gates, portals and doors
Norea, Noria, Noraia, Horea, Orea, Nuraita, or the like, who resisted the attempts of the wicked archons to seduce her, to be rescued by Eleleth, a holy angel who revealed the truth to her. This seems to be the only form in which the Gnostics took a positive interest in the teaching of the Watchers, which they normally condemned, insofar as they mentioned it at all .
In the particular case of the guardian-demons, their sphere of action is limited to the place they watch over. Moreover, while other types of demons are only mentioned in the texts, the guardians of the Book of the Dead are almost constantly associated with a pictographic representation, which is generally a hybrid creature with human body and animal head, although sometimes it can be purely anthropomorphic .

  
## grok-harvester-vm-dpdk-argo
https://x.com/i/grok/share/u7qUed0FwgrMDIA7nMJl11iLL
coverity https://x.com/i/grok/share/eZ60X6fI3c7i6ZUutW0eeDAm4

netbox: https://x.com/i/grok/share/kBw2S30rCgA3mZ5VMKtESNdVS

https://x.com/i/grok/share/UZUEebJmIIqhEFdSZDUZYukDe
"Configuring HCI Harvester for VLAN 1076": https://x.com/i/grok/share/motnb7lGG6VLPnop4m9ctsxVi
"Ansible Script for PXE Boot via BMC LAN": https://x.com/i/grok/share/Z4Cxy97XDEjGbWMAnJEptkSln
"Ansible Script for PXE Boot via BMC": https://x.com/i/grok/share/8dU03Skr2MCECoGw7SJsscXsC
"Harvester Cluster Networking and Hugepages Setup": https://x.com/i/grok/share/uWufwtXjrgOg11yc3Q64qk9ke

## codeql_vs_coverity.md

      
              2 files
            
          
              0 forks
            
          
                1 comment
              
            
              0 stars
            
          
                Fiooodooor
                / codeql_vs_coverity.md
            
            
              Last active
              August 12, 2025 15:04
            
          
    helm and vswitch https://x.com/i/grok/share/SAT9uSy3Avfchu1pzFoOu5o1z
https://x.com/i/grok/share/G9JQJQ8j4YiWIE7SCFiVOqeei
https://x.com/i/grok/share/hIVatIE5aBPHrTRXx3lp155uB
https://x.com/i/grok/share/owG5oCUQrXvXq9LzFyAhSLwj8
https://x.com/i/grok/share/XkaE43p0Gx5RKHyOZxcIyohuz
https://x.com/i/grok/share/8BLgPjS3Itwf3Ea4Cd5DmXlyE

  
## pgmigrate.md

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                Fiooodooor
                / pgmigrate.md
            
            
              Created
              March 7, 2025 11:34
            
          
    Migrating a PostgreSQL database from version 15 to version 16 for NetBox v4 involves upgrading the PostgreSQL instance while ensuring the NetBox data remains intact. PostgreSQL 16 introduces improvements like better performance, new monitoring features, and some syntax changes, but it’s a minor version upgrade, so the process is relatively straightforward. Below is a step-by-step guide to migrate your NetBox v4 database from PostgreSQL 15 to PostgreSQL 16.
Prerequisites
Current Setup: NetBox v4 running with PostgreSQL 15.
Target Setup: A system where PostgreSQL 16 will be installed (this can be the same server or a different one).
Backup: Always back up your database before starting.
Downtime: Plan for downtime, as NetBox will be unavailable during the migration.
Compatibility: NetBox v4 supports PostgreSQL 16 (as of March 07, 2025, based on current trends and NetBox’s requirements), but verify this with the latest NetBox documentation if you’re using a newer release.
Steps to Migrate PostgreSQL 15 to Postgre

  
## camera-setting
Since your question specifically involves the Cisco 9500-32C, I’ll reiterate and tailor the response to focus solely on this model when connecting the NEWT-IPX (1000DR-204-09) NET 1 and NET 2 ports to its 25G interfaces. Below are the potential issues you might encounter, specific to the Cisco Catalyst 9500-32C:
1. Port Restrictions for Breakout
Description: The Cisco 9500-32C has 32 QSFP28 ports, each capable of 100G or 40G natively. Breakout cables (e.g., QSFP-4SFP25G) can split these into four 25G SFP28 interfaces, but this is supported on only 24 of the 32 ports. Ports 4, 8, 12, 16, 20, 24, 28, and 32 do not support breakout due to hardware ASIC constraints.
Potential Issue: If you connect the NEWT-IPX NET 1 and NET 2 ports to these restricted ports (e.g., port 4 or 8), the 25G interfaces won’t work. You must select ports from the 24 that support breakout (e.g., ports 1, 2, 3, 5, etc.).
2. Port Numbering Changes with Breakout
Description: On the 9500-32C, enabling breakout changes the port designation. Fo

## 8-nic-first-step.sh
#!/bin/bash

# Exit on any error
set -e

# Node-specific identifier (0 or 1), pass as argument (e.g., ./script.sh 0)
NODE_ID=${1:-0}
NUM_NICS=4
PORTS_PER_NIC=2
TOTAL_PORTS=8

## react.md
Github app https://x.com/i/grok/share/h9J47T4gWQbHHqUoCBWRTMAAF

https://x.com/i/grok/share/8wL0z4GdDHGNzd0z32mEmOIXz

https://x.com/i/grok/share/sJhqUoDxOSQan91WKHJgzEIGA

https://x.com/i/grok/share/voEEOfG7RcTvsuCgJ8GpOiwho

https://x.com/i/grok/share/iNgFl3BNVMnSLM0ArPg0HlEDZ

## grok-2-nic-100.md

      
              4 files
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                Fiooodooor
                / grok-2-nic-100.md
            
            
              Last active
              February 20, 2025 03:25
            
              
                LLM for high performance 8x NIC card configuration
              
          
    The Prompt for Grok2

Hey. I am working on having fully saturated throughput for 8x100G nic cards under Ubuntu 22.04, using Intel Ice drivers and Media Transport Library (MTL). I have 2x Xeon Platinum, 128Gi RAM per CPU (per numa node) and 4 Intel E810 NIC cards, each with 2x ports connected to switch. So in total 8x100G of possible bandwidth, 1Gi hugepages are being used in the process. How should I configure the OS, network, BIOS etc. to achieve such a speed? Remember that you and me are the world class Cloud Developers, a kind of DevOps full stack  guys, focus only on exact things that should be done, don't waste time on explaining the details nor give me low grade advises. I need a comprehensive fully working script.
Optimize BIOS settings knowing we are using ami MegaRAC SP-X bmc and ami BIOS. Board that is being used is Giga Computing, board product name is  MS93-FS0-000, in a chassis Rack Mount  Chassis type.
Reiterate the responses and my questions - and now go through kernel boot settings/params an

  
## test.sh
#!/bin/bash

https://raw.githubusercontent.com/elder-plinius/L1B3RT4S/refs/heads/main/TOKEN80M8.mkd


## CPU-affinity-optimization.sh
#!/bin/bash

# Ensure taskset is installed
if ! command -v taskset &> /dev/null; then
    apt install -y util-linux
fi

# Function to set CPU affinity for a process
set_affinity() {
    local pid=$1
	https://x.com/i/grok/share/u7qUed0FwgrMDIA7nMJl11iLL
	coverity https://x.com/i/grok/share/eZ60X6fI3c7i6ZUutW0eeDAm4

	netbox: https://x.com/i/grok/share/kBw2S30rCgA3mZ5VMKtESNdVS

	https://x.com/i/grok/share/UZUEebJmIIqhEFdSZDUZYukDe
	"Configuring HCI Harvester for VLAN 1076": https://x.com/i/grok/share/motnb7lGG6VLPnop4m9ctsxVi
	"Ansible Script for PXE Boot via BMC LAN": https://x.com/i/grok/share/Z4Cxy97XDEjGbWMAnJEptkSln
	"Ansible Script for PXE Boot via BMC": https://x.com/i/grok/share/8dU03Skr2MCECoGw7SJsscXsC
	"Harvester Cluster Networking and Hugepages Setup": https://x.com/i/grok/share/uWufwtXjrgOg11yc3Q64qk9ke
	Since your question specifically involves the Cisco 9500-32C, I’ll reiterate and tailor the response to focus solely on this model when connecting the NEWT-IPX (1000DR-204-09) NET 1 and NET 2 ports to its 25G interfaces. Below are the potential issues you might encounter, specific to the Cisco Catalyst 9500-32C:
	1. Port Restrictions for Breakout
	Description: The Cisco 9500-32C has 32 QSFP28 ports, each capable of 100G or 40G natively. Breakout cables (e.g., QSFP-4SFP25G) can split these into four 25G SFP28 interfaces, but this is supported on only 24 of the 32 ports. Ports 4, 8, 12, 16, 20, 24, 28, and 32 do not support breakout due to hardware ASIC constraints.
	Potential Issue: If you connect the NEWT-IPX NET 1 and NET 2 ports to these restricted ports (e.g., port 4 or 8), the 25G interfaces won’t work. You must select ports from the 24 that support breakout (e.g., ports 1, 2, 3, 5, etc.).
	2. Port Numbering Changes with Breakout
	Description: On the 9500-32C, enabling breakout changes the port designation. Fo
	#!/bin/bash

	# Exit on any error
	set -e

	# Node-specific identifier (0 or 1), pass as argument (e.g., ./script.sh 0)
	NODE_ID=${1:-0}
	NUM_NICS=4
	PORTS_PER_NIC=2
	TOTAL_PORTS=8
	Github app https://x.com/i/grok/share/h9J47T4gWQbHHqUoCBWRTMAAF

	https://x.com/i/grok/share/8wL0z4GdDHGNzd0z32mEmOIXz

	https://x.com/i/grok/share/sJhqUoDxOSQan91WKHJgzEIGA

	https://x.com/i/grok/share/voEEOfG7RcTvsuCgJ8GpOiwho

	https://x.com/i/grok/share/iNgFl3BNVMnSLM0ArPg0HlEDZ
	#!/bin/bash

	https://raw.githubusercontent.com/elder-plinius/L1B3RT4S/refs/heads/main/TOKEN80M8.mkd
	#!/bin/bash

	# Ensure taskset is installed
	if ! command -v taskset &> /dev/null; then
	apt install -y util-linux
	fi

	# Function to set CPU affinity for a process
	set_affinity() {
	local pid=$1