This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chronyd_enable=YES | |
dnsmasq_enable=YES | |
sshd_enable=YES | |
hostname=stelleri.netcrave.network | |
powerd_enable=YES | |
moused_nondefault_enable=NO | |
dumpdev=NO | |
zfs_enable=YES | |
gateway_enable=YES | |
ipv6_gateway_enable=YES |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/usr/bin/env bash | |
set -e | |
# Function to handle cleanup on exit | |
cleanup() { | |
local exit_code=$? | |
echo "Cleaning up..." | |
# First try to exit chroot if we're in it |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I would like to understand a few things: | |
What actually precipitated this? | |
Why did it take so long for the problem to be addressed? | |
What will be done (if anything) to avoid making such an impactful mistake again? | |
Among the things that I've been letting slide that I would like to understand are: | |
Who are the people who actually have write access to this repository; what actually endorses their trustworthiness and sets them apart from for example a state sponsored actor who's intention is to distribute malware? To be perfectly fair, I've made pull requests myself but who I am is pretty up front and I've been nothing short of generous in making available a means to reach me for professional inquiries. I don't really see that in the accounts that actually maintain Void. I suppose I'd just take somebody at their word that there's some level of discretion but who's word would that be? Who is actually willing to endorse this? |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/usr/bin/env bash | |
set -e | |
# Function to handle cleanup on exit | |
cleanup() { | |
local exit_code=$? | |
echo "Cleaning up..." | |
# First try to exit chroot if we're in it |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"output": { | |
"blocklist": [], | |
"compressor#0": { | |
"attack": 20.0, | |
"boost-amount": 6.0, | |
"boost-threshold": -72.0, | |
"bypass": false, | |
"dry": -100.0, | |
"hpf-frequency": 10.0, |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"output": { | |
"blocklist": [], | |
"compressor#0": { | |
"attack": 15.0, | |
"boost-amount": 8.0, | |
"boost-threshold": -72.0, | |
"bypass": false, | |
"dry": -100.0, | |
"hpf-frequency": 10.0, |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"output": { | |
"blocklist": [], | |
"equalizer#0": { | |
"balance": 0.0, | |
"bypass": false, | |
"input-gain": 0.0, | |
"left": { | |
"band0": { | |
"frequency": 22.409377607517197, |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(nrf) ➜ hci_usb rm -rf build | |
(nrf) ➜ hci_usb west build --board=nrf52840dk/nrf52840 --no-sysbuild | |
-- west build: generating a build system | |
Loading Zephyr default modules (Zephyr base). | |
-- Application: /home/netcraveos/hci_usb | |
-- CMake version: 3.31.6 | |
-- Found Python3: /usr/bin/python3 (found suitable version "3.13.2", minimum required is "3.10") found components: Interpreter | |
-- Cache files will be written to: /home/netcraveos/.cache/zephyr | |
-- Zephyr version: 4.0.99 (/home/netcraveos/.oh-my-sdk/dist/nrf/zephyr) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/usr/bin/env python3 | |
import argparse | |
import sys | |
import time | |
import logging | |
import os | |
# Add pynrfjprog to Python path | |
pynrfjprog_path = os.path.join(os.path.dirname(os.path.dirname(os.path.dirname(os.path.dirname(__file__)))), |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
'_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ | |
'_/ Portions generated by MASH - Microsoft Agent Scripting Helper, version 7.5 | |
'_/ by BellCraft Technologies, http://www.bellcraft.com/mash | |
'_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ | |
' * Agent Object | |
Dim AgentControl | |
' * Character Objects | |
Dim Peedy |
NewerOlder