jake-stewart

Terminals should generate the 256-color palette from the user's base16 theme.

If you've spent much time in the terminal, you've probably set a custom base16 theme. They work well. You define a handful of colors in one place and all your programs use them.

The drawback is that 16 colors is limiting. Complex and color-heavy programs struggle with such a small palette.

niklasfrick

apiVersion: kubectl.config.k8s.io/v1beta1
kind: Preference

# Default output and behavior
defaults:
  - command: get
    options:
      - name: output
        default: wide
  - command: delete

kotarou3

# lm-sensors configuration for the Asus Pro WS TRX50-SAGE WIFI motherboard
#
# Recommended drivers: asus-ec-sensors, nct6775, spd5118

chip "nct6798-isa-0290"
    # Voltage labels are from HWiNFO, except Core0/1 and VDD_11_S3 are from the BIOS
    label in0 "CPU Core0"
    compute in0 @*1.11, @/1.11
    label in1 "+5V"
    compute in1 @*5, @/5

gdesatrigraha

Compiled from various sources:

• https://forum.level1techs.com/t/vfio-pass-through-working-on-9070xt/227194/44
• https://forum.level1techs.com/t/solved-vfio-vm-some-games-do-not-run/237677

Disable ROM BAR on the GPU hostdev definition with <rom bar="off"/>. Do for both, VGA and Audio, For example:

<hostdev mode="subsystem" type="pci" managed="yes">
  <source>
 

sovajri7

Install vGPU & Bypass NVIDIA License on Proxmox using FastAPI-DLS and Patched Drivers

This guide explains how to run NVIDIA vGPU on Proxmox using FastAPI-DLS and patched drivers, without relying on the official NVIDIA License Server.

It is intended for users with supported or partially supported GPUs (such as RTX A4000 / A5000 / A6000) who want to unlock vGPU functionality in their virtual machines (Ubuntu or Windows) for AI (Ollama, vLLM), compute, or media workloads.

You need to check if your GPU is supported : https://docs.nvidia.com/vgpu/gpus-supported-by-vgpu.html

If not, you can still use vGPU by following this tutorial and mine to enable vGPU on consumer GPUs : https://gitlab.com/polloloco/vgpu-proxmox

scottisloud

sudo mkdir /etc/1password
echo vivaldi-bin | sudo tee /etc/1password/custom_allowed_browsers
sudo chown root:root /etc/1password/custom_allowed_browsers
sudo chmod 755 /etc/1password/custom_allowed_browsers

thesamesam

FAQ on the xz-utils backdoor (CVE-2024-3094)

This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.

Update: I've disabled comments as of 2025-01-26 to avoid everyone having notifications for something a year on if someone wants to suggest a correction. Folks are free to email to suggest corrections still, of course.

Background

lobuhi

apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
  name: disallow-proc-self-fd-workingdir
spec:
  validationFailureAction: enforce
  background: true
  rules:
    - name: check-workingDir
      match:

aatizghimire

--------------------------------------------
Xrdp Server (Remote Desktop) Installation:
--------------------------------------------

Tested in Ubuntu 22.04.03 LTS

1. Update Environment

$ sudo apt-get update
$ sudo apt-get upgrade

sharadhr

$HOME, Not So Sweet $HOME

• Preface
• 1 What is $HOME to you?
• 2 Setup
  • 2.1 Linux
    • 2.1.1 $HOME
    • 2.1.2 Dot-files and dot-directories
    • 2.1.3 XDG Base Directories
• 2.1.4 xdg-user-dirs