On 10/30/20 12:36 PM, Joe Golden wrote:
Anthony,
how's that refurbed server working out?
I haven't bought anything. Someone else talked to another supplier of
that HP SKU who said it probably doesn't have RAM/CPU/disk. That place
also lists it with the same Xeon-bronze+8G, so it seems like it is
probably a barebones SKU and HP has their listing messed up. Don't plan
to risk getting into a big hassle to find out for sure.
I just picked up one of these beauties:
https://www.amazon.com/HP-EliteDesk-800-Computer-3-20Ghz/dp/B07B8VX5HZ.
Nice. I'm interested in something with ECC ram though.
I do have an HP Z series workstation (ebay), and it is probably the best
desktop I've ever owned, I'm thinking I might just move the services
there and leave it on all the time. It is running NixOS, much better
than the CP/M I ran on the old Osborne 1. Don't worry Joe--still running
Debian here too though.
Any recommendations for long term server maintenance? I've got a
decade(ish) old server that just keeps running. Dell PowerEdge T105
(which isn't very powerful or near the edge of anything anymore!). I'm
gonna vacuum out the dust. What else do you do every decade? 5 years?
This is a quintessentially Linux question!
Right? I can't believe I'm still running on that old one, literally
something somebody sent it to me in a box when they moved a really long
time ago. I'd had an account on it for some reason.
Also, not sure if I saw this on the list: what's the go to Github
alternative? I don't wanna support MS, but Github is cool and just
works. What are my righteous alternatives that won't upset my precious
repositories?
For private stuff I run locally. If I want to push instead of pull I do
'git init --bare' on one machine to use as an 'origin'. I always
wondered if we (as a community) should have developed a workflow that
keeps issues /inside/ the repo, perhaps in a separate branch.
To be honest, for collaboration, the github workflow for submitting
patches to project is very convenient. I've done a couple of patches to
org-mode recently, and the (high traffic) mailing list just isn't enough
support to track them.
--
Anthony Carrico
