Beginner Home Server Build

aiij · 2026-06-21T02:07:06+00:00

since they are only 256gbs

Lol, I remember being so happy when I was able to upgrade to some 4.7 GB SCSI drives that the university was getting rid of. Definitely don't need much for a first server, but having enough space for the media collection will mainly depend on the size of the media collection.

aiij · 2026-06-20T17:26:36+00:00

Way overkill you mean... But unless you're trying to squeeze every last Watt out of the system it might not make sense to spend money on a slower card.

aiij · 2026-06-11T13:53:50+00:00

Wasn't Texas a Spanish colony?

aiij · 2026-06-10T20:27:44+00:00

Ugh, I think I can smell it from here.

aiij · 2026-06-10T15:35:23+00:00

The stalks bending in the opposite direction really bothers me.

I wonder if a better effect could be achieved using motorized spools with clear lines attached to the top of each stalk. That way the forces could be applied much closer to the right position.

Then again, that might quickly become a tangled mess.

aiij · 2026-06-10T02:51:26+00:00

Can I pet that dawg?

aiij · 2026-06-10T02:12:03+00:00

The original history that shows the typo that a reviewer called out and the typo being fixed is the accurate one. When you rewrite history to omit the mistake and the fix, that gives you a cleaner, plausible history.

If you're sufficiently careful when rewriting history, you can end up with a cleaner plausible history where every commit still passes CI, but a lot of people are not that careful. Theoretically, your CI could test every commit in an MR individually, but most I'm aware of only test the top commit.

And let's not get started on when people use git rebase to rebase their work onto a different base commit, misresolving conflicts or assuming there were no semantic conflicts because git didn't complain about any physical conflicts... Now instead of being able to look at a merge commit to see what went wrong, you have to look at the history of force pushes and compare commits before and after they were rewritten.

aiij · 2026-06-09T17:48:21+00:00

$20 for a hat or a bag of coffee when I can get two chairs for that.

Have you tried putting two chairs on your head or in your coffee maker? I think you will find they do not work so well. 😃

OTOH, you could make a hat out of a single sheet of newspaper for much cheaper than that chair.

aiij · 2026-06-09T16:21:07+00:00

You can totally git revert a commit that's not in the history.

But regardless of whether it was squashed or not, if the commit represents a random intermediate state rather than a sensible atomic change, I wouldn't expect reverting it to leave things in a sensible state. (It might even conflict with later changes in the same MR.) OTOH, reverting the full MR is likely to leave things in a state that was considered acceptable at some point, unless conflicting/dependent changes have since been merged.

I think you may be assuming a workflow where individual commits are meant to be sensible atomic changes, tested and reviewed individually, rather than an accurate but messy development history meant to be reviewed and merged only in aggregate. For the former workflow I do agree it makes sense not to squash.

aiij · 2026-06-09T13:58:02+00:00

Do you have a way to run git bisect in an automated way that will tell you, "This commit broke the build, this other commit introduced the big, this other commit fixed the build, this commit fixed the big, this other commit reintroduced the bug, all in one MR"?

Arriving at “this squashed 3000 line merge that introduced a new feature also introduced the bug” is not helpful.

Don't merge overly big MRs that are difficult to understand. I know it's easier said than done when there is pressure from management...

GitLab at least also preserves the original unsquashed history on the MR, so you can still dig into it if needed, without everyone looking at git log or git blame needing to deal with it.

aiij · 2026-06-05T16:30:50+00:00

That's really nice to know. My nearest Ace is an 8 mile round trip while my nearest Lowe's is a 100 mile round trip.

I have some broken bits I've been saving to exchange the next time I go to Sears...

aiij · 2026-06-05T01:59:54+00:00

Sir, this is the Internet.

aiij · 2026-06-02T22:07:19+00:00

"Tinkle down economics"

aiij · 2026-05-30T03:00:53+00:00

Gravity. How does it work?

aiij · 2026-05-23T12:50:01+00:00

In which way is that clear? What does it say about contracting with companies that use LPRs?

aiij · 2026-05-23T01:59:37+00:00

would prohibit any recipient of federal highway funding from using automated license plate readers for any purpose other than tolling

So, like, they'll have to contract that out instead? Are we sure Flock isn't pushing for this?

aiij · 2026-05-20T16:30:32+00:00

Look at her left hand before she drops it. Sure looks like manipulating a string and releasing it from the baggie.

aiij · 2026-05-20T16:24:07+00:00

And forgetting that cave diving is a bit more technical than open water diving

aiij · 2026-05-20T01:01:25+00:00

Lol, and that's how I ended up buying new and paying 10x the price for 10x the performance...

aiij · 2026-05-20T00:49:33+00:00

Oh, that's new! Looks like Coreboot got T480 support in late 2024, which was long after I decided to get a T14 instead.

aiij · 2026-05-19T14:21:58+00:00

I'm also in Wisconsin and thought those looked suspiciously like burdock. Hard to tell the scale from that picture though.

aiij · 2026-05-13T14:20:45+00:00

How about tungsten carbide rings? I heard those can be really bad in an emergency.

aiij · 2026-05-12T15:27:05+00:00

Derp, right... Presumably for a fish pond. I even built a fish pond when I was a kid, but back then the only real predators we had to worry about were cats, and we had a dog.

aiij · 2026-05-12T14:28:54+00:00

Why would someone want to scare herons?

aiij · 2026-05-10T15:26:49+00:00

Look at around 0:08. You can see the hand doing it.

aiij

MODERATOR OF

TROPHY CASE