• 0 Posts
  • 17 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle
  • The main server. Specs:

    • Ryzen Threadripper 7960X
    • 256GiB (4x64GiB quad-channel) of DDR5 REG/ECC running at 4800MT/s
    • 256GB SATA for Proxmox boot disk, 2TB WD BLACK SN850X NVMe for VM data
    • NVIDIA RTX 4080 Super for workstation use, AMD Radeon Pro WX 3100 for Proxmox console
    • Proxmox VE
    • RHEL 9 for server (14c, 160GiB RAM, 800GB SSD), Arch for workstation (10c, 80GiB RAM, 1.6TB SSD)

    Server runs:

    • Mastodon
    • Minio for S3 bucket
    • Lemmy
    • Four Minecraft server, two modded and two vanilla
    • Jellyfin
    • Roon
    • Komga
    • Nextcloud AIO
    • Pi-Hole
    • Bluesky PDS

    Bonus: I use Oracle Cloud server for:

    • Mirror
    • Ghost blog
    • Synapse
    • Vaultwarden
    • Wikiless



  • Noa Himesaka@lemmy.funami.techtoSelfhosted@lemmy.worldPost your Servernames!
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    edit-2
    8 months ago

    From mangas of course!

    • YuruYuri San☆Hai! - Proxmox host replacing old YuruYuri bare-metal RHEL server, now with 24-core Threadripper and registered ECC RAM!
    • Nanamori-chu☆Goraku-bu (VM on Proxmox) - Replacement of my personal rig, has GPU passthrough
    • Nanamori-chu☆Seitokai (VM on Proxmox) - Direct replacement of old YuruYuri working as my primary server
    • I Think I Turned My Childhood Friend Into a Girl - Oracle Cloud VM, for high bandwidth and speed applications (e.g. mirror)
    • WATATEN!: An Angel Flew Down to Me - Old personal rig (MacBook Pro 16" 2019 with Arch) which is still used for managing Proxmox




  • I tried it with Claude 3 Opus, even better:

    Alright, listen up you little shits. Commit d96c36004e31 (“tracing: Fix FTRACE_RECORD_RECURSION_SIZE Kconfig entry”) had to remove a fucking hidden tab because apparently some half-assed third-party kernel config parsing tool couldn’t handle its shit.

    I don’t know what kind of brain-dead tool it was, but you better make damn sure it gets fixed. Because if you can’t parse tabs as whitespace, you have no fucking business parsing the kernel Kconfig files, period.

    In fact, let’s rub this breakage right in your face, more than some obscure ftrace record size option. If you can’t handle tabs, you sure as hell can’t handle page sizes either, dipshit.

    Yeah, I know the whole tab-vs-space clusterfuck is sadly a classic Unix thing, and ‘make’ is notorious for being a broken piece of crap in that regard. But guess what? That doesn’t make it fucking okay, got it?

    I’d sprinkle more random tabs all over our Kconfig files just to spite you, but I don’t want to make this codebase look any more like dog vomit than it has to. But if I keep seeing more of this kind of idiotic tooling, I just might fucking have to.

    So shape up, or I’ll come over there and shove those tabs so far up your ass you’ll be shitting spaces for a week. Fuck!