@mwl You were awesome.
@xenotrope It was a few days before!
@gumnos Well, YOU'VE got swag. (As the cool kids say)
I don't see those "other" comments below! Shame on you! A Mastodon dies every time you answer an "other" poll question without adding a comment. (Ignoring the fact that they all died out long ago...)
#mlmmj 2.2.0 is out!
- new control/subreleaseall: release all held mail from a sender in one go (great for patch series)
- $disarmedfrom$ is now RFC 2047 encoded, so mail clients display the disarmed address
- control/replyto and mlmmj-receive-strip are deprecated
- build fixed for GNU make and OpenBSD's make, iconv is now detected by configure
- memory fixes, French and Czech translations updated
@oxy @dexter @joel
https://www.getac.com/us/products/laptops/
GeTac laptops also take a beating and they run *BSDs:
https://dmesgd.nycbug.org/dmesgd?do=index&fts=GeTac
Completely over engineered for abuse. They are NOT light weight however.
Anybody running lots of #FreeBSD 15.x systems who could run
netstat -nxptcp | grep -
And report back a % of machines that report any lines in addition to the header?
More details at https://reviews.freebsd.org/D58484 which is in STABLE but not RELEASE
Instead of:
A hill I'm willing to die on
I'm gonna start saying:
A hill I'm having a picnic on
Just... spreading out a nice blanket with a basket of food and staying on that hill for a long long time
✅ too many ppl dying already
✅ picnics are cozy n nice
✅ nobody wants to eject someone having a nice picnic on a hillside, so you will probably win
Holy moly, #GNU sed was immensely faster than #FreeBSD's #sed with the exact same command.
The BSD sed was taking minutes and not finishing at all, only writing about 64KiB of the file per second.
GNU sed finished the entire 34MiB file in a few seconds.
Weird.
rld@Intrepid:tmp$ cat access_log* |sed 's/^.*"\([^"][^"]*\)"$/\1/' >agents.txt
^C
rld@Intrepid:tmp$ cat access_log* |gsed -E 's/^.*"([^"]+)"$/\1/' >agents.txt
rld@Intrepid:tmp$
``
@sng @mwl Worse, I sat down to document the disk replacement process by setting up a pool and… ejecting a drive.
“Weird. Maybe that one’s not part of the pool.”
Pop another one… “Um, wrong again? No kernel messages?”
Suddenly… perhaps upon a read: POOL FAULTED
So… the kernel has no notion of ZFS either?
@mwl Well, Ubuntu, on a good day.
Ahem. TrueNAS.
Dexter's Law: Only proprietary software vendors want proprietary software and only fascists want fascism. Toots are my own. Self-employed. Father of three.
I aim to keep this to technical topics relating to bhyve and OpenZFS, and the occasional humor and Latvia.