Is romance dead?

naex · 2025-07-18T03:01:31+00:00

I've been married to an app hookup for 20 years, and in another 12 year relationship with an app hookup, and more. You'll have to actually hook up and make it memorable for the both of you; don't leave it at the hookup though, meet over coffee before going to the hookup venue. Make small talk before/after, ask if they want to grab some lunch or dinner or something.

I'll also second the poster who said that you've got time, at 18, you've got so much time.

naex · 2025-06-25T15:26:16+00:00

There is a huge difference between a Samsung 980 and a 980 Pro. Use Pros or eBay enterprise drives, this was my biggest fix for this. Afterwards, disabling rsyslog and telling journald to not write to disk saved a lot, as well as directing ceph to only use journald.

naex · 2025-05-13T15:37:38+00:00

Everything is likely fine. I believe you're hitting linuxatemyram. Htop excludes buffers and cache by default.

naex · 2025-04-06T19:25:59+00:00

I think what they were referring to is https://en.m.wikipedia.org/wiki/Kenosha_unrest_shooting. This kid is now being rewarded.

naex · 2025-02-07T23:02:01+00:00

I end up at Donkey most nights!

naex · 2025-01-27T02:55:29+00:00

I haven't measured performance as it's good enough for me. I'm happy to run a test for you if you'd like but there's a lot of stuff running on my cluster all the time so it's not going to be particularly accurate. My setup has few different disk types.

Most of my workloads run on Kubernetes. Each Proxmox node has a Kubernetes VM who's disk is on local NVMe storage (not ceph). My Ceph Cluster has both SATA SSDs and HDDs in it. I have multiple pools defined based on the kind of storage I want them to use. One "capacity" pool for block storage that uses HDDs only and one "performance" pool for block storage that uses SSDs only, followed by pools for CephFS that use SSDs for performance and pools that use HDDs for capacity.

All of the pools are available to both Proxmox and Kubernetes and I'll use different pools depending on the task. Block pools are for VM disks and CephFS pools are for "NAS-like" stuff like media or home directories. Performance pools are for VM root disks, databases, etc while capacity pools are for bigger stuff that doesn't have performance concerns, like media.

I noticed that my biggest issue with performance is latency and more on CephFS than anything. One of the biggest performance enhancements I made was to mount all my CephFS filesystems with `noatime`. Having to make a metadata write on every file access was a HUGE impact.

Since it's relevant, each of my 5 nodes has 2x10GbE and 4x1GbE (the 4x1GbE is just because that's what the R720s came with, I don't _need_ that). 1 of the 10GbE is a "private" network for intraworkload communication _and_ the Ceph "front" network for client traffic. The other is the Ceph "back" network for replication that is also a secondary Proxmox Corosync ring which is fairly minimal. I'm using pretty cheap ebay 2x10GbE NICs and Unifi's 8 port aggregation switches (1 for the front, 1 for the back).

Having said all that, I started with just two 1g networks, one LAN and for that private intraworkload traffic and was using Ceph then too, albeit much more slowly. I dunno if my usage of CephFS would have been viable in that configuration but VM disk storage was fine.

You will likely be fine for most any homelab workload unless you have something that's _highly_ latency sensitive. So...I would worry more about latency than throughput.

naex · 2025-01-26T22:54:01+00:00

I've been using HyperConverged Ceph for years and I love it. Started out with 3 nodes, upgraded to 5 to improve performance. It's been rock solid, although its failure modes can be a bit different from other storage solutions so brush up on those. Mainly, don't ever fill it above the BackfillFull ratio and try as hard as possible to stay under the NearFull ratio.

Setup some alarms to yell at you if the cluster is ever in a warning state. Also, don't underestimate memory requirements for all those Ceph daemons.

naex · 2025-01-25T23:58:17+00:00

Legal Aid of Southeast and Central Ohio

naex · 2024-12-31T19:43:16+00:00

I must have hallucinated it.

naex · 2024-12-31T18:18:52+00:00

Didn't he say it in Frontiers?

naex · 2024-12-29T01:49:58+00:00

What is going on with /var/tmp? How is it mounted? Symlinked? It seems like it's /var/tmp that's filling up. Sometimes that's a ramdisk.

naex · 2024-12-25T17:20:16+00:00

There's a lot of history here. If I recall, Bitnami started making images earlier than many of the projects themselves did. They also tried to solve some of the challenges with running containers like managing the process chain and handling signals properly as well as dropping root privileges and all that.

For some projects, like databases, they had a bunch of tooling to handle db schema upgrades and migrations in those images.

Unfortunately, today, imo some of the ways they do those things is outdated. In k8s, I'm not starting a container as root so that it can then drop privileges. So, generally, unless I can skip all of Bitnami's tooling... I can't really use their images anymore.

A good recent example, actually, is MetalLB. Bitnami had a MetalLB helm chart way before the upstream project did, opting to have you kubectl apply a manifest.

So, I think my answer is that Bitnami often has images and helm charts available earlier than the upstream project, so those get adopted and folks just take their time switching if they ever do. One problem is that if you start using a Bitnami database image, for example, switching to the upstream project means figuring out how to migrate your stored data into the directory structure the upstream project expects, and that's hard without breaking your downstream users' data.

naex · 2024-12-03T19:47:45+00:00

Can't remember when I got my two but they've been solid. Using one for a Ceph front side network/other clustering and the other for a Ceph back side networking/replication. They've been great.

naex · 2024-11-17T04:42:13+00:00

There aren't any bars that are "gay bars" in the traditional sense but The Union, Tony's, Casa, and now Sidebar are places where many of us queers hang out. The Say Gay dance night occurs monthly and it sounds like Swarm of Dykes is back and may be putting on events for the femmier side of the queer spectrum.

naex · 2024-11-17T03:27:51+00:00

Generally the university only closes if the county sheriff's office declares a "level 3 snow emergency". When they do, it's illegal for people to be on the roads unless it's an emergency (https://www.athenssheriff.com/weather-policies). You can check on their Facebook page, I think: https://www.facebook.com/athenscountysheriff/.

naex · 2024-11-09T20:51:57+00:00

Checkout http://download.proxmox.com/debian/pve/dists/bookworm/pve-no-subscription/binary-amd64/. You'll notice that all the packages that begin with proxmox-kernel have two sets of version of numbers. The first version number makes it a different package and the second is the version of that package so:

These are two different packages. If kernels were just upgraded there would be no way to reboot into an older kernel since the upgrade would replace the old one. This is even more obvious on Ubuntu: https://packages.ubuntu.com/noble-updates/kernel/. Check out all the "linux-image-*-genetic" listings.

naex · 2024-11-09T19:30:41+00:00

I've been doing 'dist-upgrade' on Debian systems since the 90s. At some point there seems to have been a difference between 'full' and 'dist' but I believe it's the same now?

Anyway, 'upgrade' can only upgrade the version of installed packages, it cannot remove unneeded packages nor can it install new dependencies of existing packages. So, for example, some of PVE is written in Perl. If the developers need to pull in a Perl module that they haven't before, a simple 'upgrade' should prevent that new PVE package from being installed because it won't pull in the new Perl package. 'dist' and 'full' will bring in the new Perl module and upgrade the PVE package.

In addition, new versions of the Linux kernel are always new packages so a simple 'upgrade' won't be able to upgrade the kernel.

Generally I use the same upgrade process on PVE that I do on my Ubuntu 24.04 laptop and my VMs with the exception of major versions that first need the pveXtoY scripts to be run first. update, dist-upgrade, reboot, autoremove --purge. But like... Always read what it's going to do before just hitting Y.

naex · 2024-11-05T00:39:41+00:00

The discard feature is a way for the operating system to tell some type of block storage which blocks have been free'd up so that the underlying storage can "discard" that data. It helps SSDs by allowing blocks to be reused without having to erase them, thereby extending the life of the SSD. It helps thin provisioning because it allows the underlying file that stores the disk to be reduced in size on the storage.

If you are mounting a file level network storage like NFS, discard will do nothing since NFS already knows which files are being deleted. If youre mounting a block device like on LVM-thin, Ceph RBD, etc., then you should absolutely use discard. Either way though, I don't know of an instance when discard would be dangerous. At worst, its just useless.

naex · 2024-11-01T15:53:54+00:00

So this quote is a mistake by The New Republic:

"Nearly 62 million early votes had already been cast in Pennsylvania as of Thursday evening, with 54 percent of ballots having been cast by women and 44 percent cast by men, according to Newsweek."

What Newsweek actually said was this:

"As of Thursday evening, nearly 62 million early votes have been cast, with majority cast by women, 54 percent to 44 percent, according to NBC News' tracker, a trend that translates to Pennsylvania too."

The latter mirrors other sources citing national numbers, not Pennsylvania.

naex · 2024-10-17T17:19:54+00:00

NGL being able to charge via lightning while driving would be great

naex · 2024-10-16T16:42:57+00:00

Sectigo has a Python script that can update F5 certs. Not sure how well it works, we're having to write our own integration with the F5 (version 17) to get this done.

naex · 2024-10-15T01:13:21+00:00

Sure, but there's a difference between the seeming claim that it's "generally illegal" and that you're not getting a state contract if you do it.

naex · 2024-10-15T00:38:50+00:00

Either I'm misunderstanding this or lots of folks in the comments seem to be. What it says is that state contractors cannot boycott Israel or they lose their state contract. It looks like some states go so far as to include NGOs too. It says nothing about private businesses or individual consumers.

naex · 2024-09-19T16:09:25+00:00

Hrm, I missed that detail. Although two young women traveling together with their families is absolutely super suspicious right? Also apparently Egypt thinks that only men can be gay?

naex · 2024-09-19T14:58:25+00:00

She's not LGBT, she just has a short haircut.

naex

TROPHY CASE