I demand a KoChauffeur+ button. How are we supposed to login to our computer without a slopchatbox!?

It works, but the memory allocator implementation is way too slower compared to glibc. This especially becomes a performance bottleneck if application does a lot of heap allocation/deallocation.

I think Musl is a better choice when you work on embedded, low-end devices, or statically linked/self-contained applications. For high performance workstation usage, I still prefer glibc.

https://mermaid.live/, makes you learn a new syntax that works like a markdown, but it’s pretty good. Especially, if you don’t like working with GUI applications.

For media files (bad idea for databases), I’m using Kubernetes CronJobs with restic. It mounts PVC to the cron job pod and backups target directories to S3 storage.

Plot twist: The handed fishes are highly contained with inorganic arsenic, and they’re trying to kill humans with more sophisticated methods.

jmpd(jump directory): fuzzy finds and opens directory with fzf

# fish shell
function jmpd
    set _selection $(fzf --walker=dir);
    if test -n "$_selection"
        cd "$_selection";
    end
end

Biggest one: Aldnoah Zero

Some potential contenders are: The Detective Is Already Dead, Akame ga Kill, and Shield Hero.

Whenever I see the name of Aldnoah Zero, certain part of my unconscious memory unlocks and I get angry because of the season 2.

I don’t think its rpi or network switch, unless you’ve overclocked rpi with liquid nitrogen 😅. So, I assume its TrueNas device.

If it were a significant power difference, say 20-30 watts, you could easily find the process using htop/iotop. However, 6 watt difference is a relatively small value for a device with ~25 watts of idle power . It might be a process using just 1% system resources. That’s why I would look for systemd timers, cronjobs etc. to find scheduled tasks on specific times. Another possibility is automated S.M.A.R.T. self-tests. Those tests don’t show up in htop or iotop.

LinkedIn.

Imagine Twitter and Facebook teaming up for a Dragon Ball style fusion, turning into this cringe fake business guru with a Ghibli style profile picture, spitting out AI generated posts and running impression based non-sense polls.

UPS devices normally uses wall (input) power, and switches to battery when input voltage is out of the target thresholds. So, input.load should represent the percentage of current wall power (in VA) relative to UPS’s max rated input power (VA). If your devices uses more power, input power from wall should increase as well.

If it’s peaking in certain times, it could be due some scheduled job temporarily increase CPU frequency, or automated tasks like file system snapshot might power-up/spin drives longer than regular usage.

• 2x18k - mirrored ZFS pool.
• 1x47k - 2.5" drive from an old laptop used for torrents, temp data, non-critical pod volumes, application logs etc.
• 1x32k - automated backups from ZFS pool. It’s kinda partial mirror of the main pool.
• 1x18k - (NVME) OS drive, cache volumes for pods.

Instead of single pool, I simply split my drives into tiers: cache, storage, and trash due to limited drive counts. Most R/W goes to the cheap trash and cache disks instead of relatively new and expensive NAS drives.

I think it’s not PIxel only issue. Some Samsung S series devices also suffer from the same screen green tint issue.

LinkedIn?

I’m currently using InfluxDB + Telegraf + Grafana combination to monitor Linux systems and k3s pods. It’s basically same as Prometheus, but InfluxDB uses push model, which makes it easier to develop tools for collecting custom time series data.

For alerts and dashboards, I think Grafana is the simplest and most hassle free solution available at the moment.

I have a APC Back-UPS 1600VA. It powers two desktop PC/Server, a monitor, and router. So far, it gets the job done.

The biggest downside is; battery is not user replaceable, at least it’s not straight forward like the other models. If possible, prefer a UPS with the easy battery replacement option.

Road to success (2024 AI Hype Edition):

1. Clone VSCode.
2. Rename it as LSCode, squash all history, and create some random commits with --author="Linus Torvalds <[email protected]>".
3. Add a character AI that calls your code garbage.
4. Profit.

‘Soon’ is a questionable claim from a CEO who sells AI services and GPU instances. A single faulty update caused worldwide down time recently. Now, imagine all infrastructure is written with today’s LLMs - which are sometimes hallucinate so bad, they claim ‘C’ in CRC-32C stands for ‘Cool’.

I wish we could also add a “Do not hallucinate” prompt to some CEOs.

If that happens, I’ll create a preemptive PR on KilledByGoogle.

DuckDuckGo also uses Bing under the hood.