Search results

https://zazolabs.com/odirect-the-problem-that-grew-up/

On FreeBSD, with go125 installed, the path should be /usr/local/go125/bin/go

She-bangs are weird! The only issue is you can't use /usr/bin/env https://lorentz.app/blog-item.html?id=go-shebang TL;DR: /*usr/local/go/bin/go run "$0" "$@"; exit; */ package main import "fmt" func main() { fmt.Println("Hello world") }

Don't purchase from the GMKTec store. They tell you they take care of VAT. They don't. It's a fucking mess and they don't send an invoice but charge your credit card nonetheless.

I could reproduce with NFSv4 & ZFS.

This is really obscene. I had to sell or give away mine. And Kindle sucks.

LOL we have like 3 threads of hardcore hardware pr0n. Why not merge them all?

There's an argument that this doesn't achieve much: https://isopenbsdsecu.re/mitigations/karl/ Note: I don't condone the above site given the garbage reasons for targeting OpenBSD (not having a CoC and so on).

I had the Phenom X3. The urban legend was that they were triple-core because they failed QA for quad-core. And Windows had to patch their OS so it could run on this processor.

This is only the login manager, which itself is a fork of SDDM. KDE helped with OpenBSD support: > Improved and fixed support for OpenBSD in multiple places. https://blogs.kde.org/2026/01/03/this-week-in-plasma-new-year-new-accessibility-features/#notable-in-performance--technical

Let Linus Torvalds himself dispel this myth for you: https://social.kernel.org/notice/B1cCcICHNmA0mcvUSe

There was a time I used the tty exclusively, before having a job while at the univ. I don't see myself checking the smartphone everytime. It's the less exciting piece of hardware I have. I prefer checking Whatsapp/Telegram from my laptop.

You may want to check what util-linux wipefs does or even call it with `wipefs -a -f $DEV` because I remember dd at the beginning not being enough sometimes. =/

Using CoW filesystems on devices like USB pendrives and SD cards with no wear leveling is a bad idea due to the write amplification. Someone should tell the NomadBSD guys to add this warning.

We kinda discussed it in this thread: https://forums.freebsd.org/threads/from-the-39c3-escaping-containment-a-security-analysis-of-freebsd-jails.100969/

Install smartmontools and run `smartctl -x /dev/$disk` LLM's like ChatGPT turn out to be very good at interpreting the results.

To avoid reinventing the wheel, there are the 3 workflows I know of: 1. Illumos pkg creates a new BE by default except when installing new packages. 2. openSUSE's zypper creates a Btrfs snapshot everytime, even when removing packages, keeping a configurable maximum of 10 snapshots. 3. GhostBSD...

I know modern SSD's resist a bit more but I dunno about eMMC's. It's also faster to download to RAM. I'm even tempted to symlink /var/cache/pkg to /tmp which is already tmpfs in my case but want to do it in a secure way.

I'm experimenting with this wrapper around pkg(8) to automatically mount the pkg cache in tmpfs and create a ZFS boot environment. The reason for using tmpfs is to prevent a eMMC/SSD from wearing. Any suggestions for improvements are welcome. #!/bin/sh # # Wrapper around FreeBSD pkg(8) to...

You can't go wrong with the classics. In addition to The UNIX Programming Environment recommended above I'd also add Advanced Programming in the UNIX Environment by Richard W. Stevens. Any book by this author is a collectible item. Both explain the concepts as well as the implementation...