2026-10-20

So, recently i bought a HP Proliant Dl380 Gen 6 server A pretty solid choice and at a cheap price. I paid 750,00 BRL (150 USD Approx.), installed Proxmox and i'm running it as a lab. It's been a few days since it got delivered and since then i ran some good software in it. From LLMs with Ollama, Wazuh and some game servers. It ran Minecraft, Killing Floor and GTA IV Servers really great, no issues at all. But i had an idea, what about try to run llms fully on both cpus? I know, everyone already have done this before, no news here. My point is: My laptop has an i5 13th gen, 32gb ddr5 ram and a RTX 3050, even so, when i tried running local models, i wasn't fully satisfied, like, i used it for writing code, but quality of the code wasn't good enough. I did some research and the main reason for this is due to my GPU low VRAM, it has only 6gb VRAM. Then this idea came to my mind: why gpus power llms? it's due to their parallel processing, which makes it faster, this is why llms don't rely mainly on CPU, which requires RAM instead of VRAM. Now, think with me: if graphics card with high VRAM that deliver a good llm experience are horrendously expensive, what if i go full cpu-powered? It's slower, BUT with more ram, i can allocate for memory for better context and better answers from models, after all, my server runs two CPUs, yes, it's from a older server model, slower ram and older CPU, however, i'm willing to trade speed for better response (and cheaper hardware). Information wise, my server is a HP Proliant Dl380 Gen 6, it has two Xeon 5606, 16gb DDR3 and two SATA Hard Drives. I never had a server before and never touched one, so i instantly got attracted to it's shiny metal case, absolutely stunning. And i managed to buy two of these

2026-10-06

I've been quite pissed lately regarding all the issues with VSCodium and VSCode extensions. So i decided to try something: Installing VSCodium inside a container, and running a local git server for managing my website code files. I already did the first part: i ran distrobox create --name [container-name] --image registry.fedoraproject.org/fedora:latest --home [container-home-path] --additional-flags "--security-opt label=disable" --unshare-all Distrobox is a tool that allows running any Linux distro inside a container seamlessly integrated with my host, in other words, i can run GUI software inside any container without going through the pain of manually installing graphical tools inside the container.

2026-10-06

Writing this from another day, i need to finish this distrobox setup, my original idea was to got VSCodium running inside a distrobox container, integrated to a local git server.


2026-09-23

It's been quite some time since my last entry, my bad. Job has taken so much time from me. Anyways, i promised to talk about the Unicage method, and should do it soon. The last great thing related to OpenBSD i've done lately was to create a chroot directory bounded to a ssh user which becomes unable to use any commands upon authentication, very cool.

2026-07-13

Today i have gone to a close Educational Institute from "Instituto Janela Para o Mundo" I was there to support a network engineer on installing a new Network Switch. It was fun. This is the first time in my life i ever put my hands in an actual Switch, but it took quite long to install the new hardware.Btw, i need to talk about the Unicage Method, on the next entry i'll be talking about it.

2026-07-11

Lately i've been quite interested on BSD systems. On the last weeks, quite some LPE vulnerabilities have been found on the Linux Kernel: Copy Fail, Dirty Frag, Pedit COW, Dirty Clone, Ghostlock. I honestly think this is bad. So, i decided to give a try to BSD systems, mostly OpenBSD and FreeBSD. Reading about OpenBSD i found about pledge, unveil, secure levels, W^X, KARL and many other interesting features!

2026-07-10

Well, i guess this is the first of many of my notes