Slackware was my first distro decades ago, and I have lots of fond memories learning Linux with it. How is it these days? What makes it your distro of choice at home in 2023?
Not OP, but: stable, with up-to-date packages. Configuration and maintenance does not change drastically between versions (there's a paper manual, it's on its second revision).
I can be heads-down on something for months and not run updates, and then run them and they apply fine and don't hose anything.
Long support for releases, both officially and on slackbuids.org
From my end user perspective Slackware 15.0 works fine - up to date(ish) packages with what might be described as 'conservative' (old school) administration. For server use it might be best to have a look at the Slackware forum...
I’m an admin for our organisation’s Microsoft 365 account and while I haven’t checked the notices recently, the tone of this is consistent with the “admin only notices” on the admin website.
I wonder as well. I've really enjoyed reading about all of the findings that have come out of Pompeii and Herculaneum in recent years: the graffiti[0], the fast food joint that looks like it could be a Chipotle or a Subway[1], and articles like this. It all feels pretty _recent_, even though it was 2000 years ago.
I think that people 2000 years from now will have a lot more information about our time to go on, though. We disseminate and preserve information at a scale that did not exist back then. The sole surviving written record of the Mt. Vesuvius eruption -- and perhaps the earliest written record of any volcanic eruption -- comes from two letters written by Pliny the Younger.[2] Today, news of the event would be spread near-instantaneously (and presumably preserved in multiple locations), like news of the 2020 Beirut explosion. Back then, there was just the dissemination of paper(-like) copies.
In a lot of ways roman civilization fits much better into “nearly industrialized” than “millennia old” and you have to remember that a whole lot of what became western civilization was invented by romans.
Really there were only a few missing big ideas and a few organizational failures in the way of, say, someone landing on the moon a thousand years ago. The fall of the empire set the species back perhaps as much as 1500 years.
i fear a lot of our data will be lost, in particular digital data. it's already getting difficult to access data in formats/form-factors from within a single lifetime. from the decay of the magnetization to the details of encoding.
If you think decay of magnetization is the limiting factor to digital longevity, I'm sorry to report that intentional bitrot will destroy any hope of retrieval long before the spinning platters fail. I'd suggest an experiment: Think of some major news event you can remember from even 10 years ago, find a news story about it online, and then just follow the links contained therein. Not only is Google shaping what you can see, but so is everyone else. God bless the Internet Archive.
> Even if 99.9% is lost, that still leaves behind far more than we have about the Romans.
Indeed, and due to complex historical factors, we have much more Roman writing than we have writing from other civilizations. It's important to remember that there are entire swathes of history and entire regions from where we have no actual history, only circumstantial writing by other peoples such as trading partners.
A lot of that information will be lost it costs a lot of money to store data on the internet nowadays when nobody's paying the bill it just gets lost.
We bought an old tobacco farm in South Indiana almost every building it has these weird metal rings. historians said they were for tying up cattle and horses. But we found out recently that they were actually for farming equipment they would tether steam engines to ropes and then use these steel rings attached to buildings and trees to pull plows around with the steam engines.
In my experience tc is only designed to work in one direction, so I had to use a separate VM, place that machine between the test host and the rest of the network, then enable TC on both interfaces.
My understanding us that typically you'd create a minimal router out of a minimal server distro installation (either physical or virtual) and make a couple of scripts to automate standard settings.
Source: At some point I was part of a team that used a setup like this for testing.
It is still infrastructure that you run, this is a real cost for lots of people. If you're running other people's terraform or whatever it's also a black box of software YOU are on the hook for but that you don't know anything about until you have to (3-5 hours after the service has been down).
But nobody's saying to run "other people's terraform or whatever," or that you should be running a sensitive service that you "don't know anything about until you have to." Common sense doesn't go out the window just because we're talking about hosting Vault within your infrastructure.
You would think, but that's exactly what tons of people do. Many people who do not include the cost of running a service in the cost. It's very easy when the install is nice and easy to just say "sweet it's running" and pat hands "it's done". Then you realize you have no idea what's going on when it's totes on fire. At least with hashi products they're open source so you have a chance. And there's enterprise support, but you're still bleeding till you can get them in to help you out and understand what insanity you did with their product.
This is why saas is preferable in a lot of situations. If you're not great at ops and make bad decisions, hopefully the SAAS folks are better at this than you. If you're really good at ops and think a ton about this stuff, then running it yourself makes sense a lot of time. And yes with SAAS now you have lockin and other problems which has their own set of solutions you should make sure you are doing, like layers of abstraction.
Then you get into the self-fulfilling-infrastructure scenario. We're a vault shop, everyone use vault even for stuff that makes no sense to use vault for. Then rinse and repeat.
Or you get into the sunk cost fallacy with your ops team... "what will they do if we replace this with a SAAS", so you keep services around just to not fire people, not because they're the best solution anymore.
You aren't, you're espousing a sane policy of actually understanding what you're doing; I agree with you.
I'm pointing out the whole "just run my pod" thing with tfn, or kube, leads people to thinking they're installing a phone app, not a multi-host, multi-protocol piece of software.
We're in violent agreement. We're just disagreeing about what the average person assumes.
Edit: when I think of a conniption fit I think of someone being angry or upset, but maybe OP meant being excited.