This changes everything...
- Posts
- 1
- Comments
- 481
- Joined
- 3 yr. ago
- Posts
- 1
- Comments
- 481
- Joined
- 3 yr. ago
Spin it fast enough and everyone gets a serving of something. It's the ultimate potluck meal serving system.
"Sure you can." Later on the druid fails a diplomacy check because they've got an ant stuck between their teeth.
Launch? Eldrich abominations from the dungeon dimensions may slither, crawl, shamble or even wriggle, but they don't launch. The missiles are just a government cover story to keep the public away from the horrors' lairs.
I agree with the sentiment regarding being woken up, but I used to look forward to being on call. I could go to bed happily, knowing I was earning a significant premium and I'd still get a good night's sleep because the systems just didn't go down. I had the advantage that most of the customers I supported had similar requirements, so I had their systems locked up pretty well. Minor problems (disk space. Why is it always disk space?) would self heal, catastrophic failures (hardware failures or the engineer who supposed to replace a component unplugging the wrong server) would fail over to the rest of the cluster. I never had much trouble with logging either, it was typically one of the first things set up, and I had most of the setup automated to avoid missing anything. I suppose the thing was I was supporting systems I'd built, and I'd built them to ensure I didn't have to be woken up.
I do a lot more troubleshooting and rescue type work nowadays, and the number of times I run into systemd components just not doing what they should is frustrating to say the least. Being able to pull the logs by knowing the service name would be nice, but a) you could already do that because you set up different services to log to different places and b) you don't always know the service name in question. Being able to just grep the log directory is a lifesaver. You can still do that, but only because distros set systemd up to log to file as well as it's binary format. I loathe the way systemd ends up spreading it's unit files over about a dozen different directories, with overrides increasing that even further. I just want to know what services I've got and what will start up, in exactly what order, on the next reboot, dammit! The last one is particularly tricky as, due to services being started in parallel, you can't predict exactly what order things will actually start between targets. That shouldn't matter, units should have all their dependencies properly listed, but it's no fun tracking down a race condition that only happens once every x reboots when a particular network service takes a few hundred milliseconds longer to come up. Give me sequential boot any day. It might take a few tens of seconds longer, but it happens the same way each time, and I only need to look in one place to know what that is.
As to systemd's dominance, once Redhat, where Mr Pottering worked, chose it, it became hard for other distros not to. Derivative distros obviously went with it, and if you look back through the various email discussions, it was far from a unanimous choice for distros like Debian to choose it. They did so eventually mostly, as far as I can see, because it would theoretically make packaging easier. Fortunately they still support sysvinit, so all is not lost for those of us who want a mainstream distro without systemd bloat.
Shifting stuff to kube is definitely goot for making things more robust, so long as you've got the underlying clustering working, and I quite like working with it too. Once you realise it's basically just a database and message queue with a bunch of controllers for managing storage, networking, containers and the like, and the ability to extend that, you can do all sorts of fun things with it.
Anyway, I've gone on for long enough. If you're a sysadmin and the number of trouble calls is going down, then you probably don't hear this often enough: well done, you're doing a great job.
Sure, they blew a hole in the building, but the pizza was perfectly cooked, so mission accomplished.
Ok, fair point on the capital D, I must have read it like that years ago and it stuck. I shall have to make an effort to unlearn it.
As to the rest, systemd has been a constant thorn in my side ever since L. Pottering published "Rethinking PID 1" back in 2010 or so. I found, and still find, that most of the assertions and actions in that document either don't really hold, or just aren't really relevant. Basically it's trying to solve a problem that really wasn't an issue in the real world, and does so in such a massively overbearing way that everything actually becomes more laborious than it otherwise would be. From my perspective it's an unnecessarily complex and poorly architected attempt to answer a need that was better served in different ways. That it's become a near mono-culture is deeply concerning.
I've also run into all sorts of awkward edge cases and misfeatures over the years, from the automounter that occasionally didn't to race conditions that only manifest at the worst moments, none of which would have occured had the basic tenet of "do one thing and do it well" been followed. The extreme verbosity of the configuration, and unnecessarily large number of places it can be spread just serve to make it even more unpleasant to deal with compared to the simplicity of init scripts, crontabs and the like.
The sad thing is, there's undoubtedly some good ideas buried in it, but they could all have been implemented much more lightly and in a way that worked with the rest of the ecosystem rather than fighting it. Things like starting daemons in what is essentially a repeatable sandbox, or being able to isolate logging per service. They could, and had both been implemented already, but systemd has a real "not invented here" problem, so everything was built again, with all the attendant bugs, and design issues that inevitably brings.
Ultimately clients pay good money for me to look after their systems, systemd or not, so I probably shouldn't grumble, but I miss the days when Linux was a clean and elegant system, without this multi-tentacled thing sitting on top of it.
It looks like he pretty much invented surfing tidal bores on rivers, rather than surfing in general, and did it on a board he'd made himself.
I quite like knowing there were and are people like that about, even if you probably shouldn't look too closely at their politics. Knowing the spirit of adventure is alive and well gives me a little hope that things will turn out ok, and laughing at their bizarre antics is always a bit of a boost.
I think 'mad as a sack full of badgers' might be a more appropriate fit, but I can see the psychopath accusation, although he seems to mostly not cared about his own safety rather than displayed an unusual level of psycopathy for a soilder. If you read about the rest of his life it looks like hus feeling of invulnerability continued.
SystemD is far too much of a poorly thought through mess to have anything like a sane GUI configuration, it doesn't even have a sane textfile based configuration. We're going to have to wait fir SystemD to crumble under it's own weight and be replaced with multiple, simple, cleanly designed components before we have any hope of a sane config again. Sort of like we used to have before a certain someone/some company (depending on how conspiratorial you're feeling) decided to come along and muck it all up.
/rant
Thank you for coming to my Ted
TalkRant. You may gather I dislike SystemD quite a lot.You challenged Grandma. Grandma doesn't fight fair, and she's heard about packing heat and made it her own. You have to see it through now. Eat enough of her food and you'll be inducted into a secret order of endorphin lovers.
I don't always agree with what you post, but you're spot on here.
That's the thing, you wouldn't have the power to do any of that before you were booted out. CEOs do have a lot of power over the board, and the board has power over the company. The net result is that if the CEO pushes too fast or too radically they get removed before any change occurs. As the poster above said, in situations like this the CEO is paid to be the fall guy; the people who wield the actual power are the board members and the large shareholders. The CEO deserves a chunk of the blame for being the face of the organisation and legitimizing it, but killing one, or even a few, off wont significantly change the direction these companies are headed in.
Possibly, but if you read about the rest of his life it seems like he just really enjoyed adventure, and, in common with many others, saw war as a thrilling, life-or-death, adventure.
That reminds my of the quote by "Mad" Jack Churchill on the end of the Second World War: “If it wasn’t for those damn Yanks, we could have kept the war going another 10 years!”
He was apparently a good leader, being promoted to Colonel, and clearly enjoyed his war. He's credited with the only confirmed kill with a long bow in the war, wore and used a Claybeg style sword and, on more than one occasion lead the charge in to battle whilst playing his bagpipes and hurling grenades.
In short, he well and truly earned his moniker.
Word for word what I was about to post.
Sit by the bedside of a loved one as they die in agony that can only be even partially controlled by keeping them comatose. You'll likely soon come to the conclusion that we shouldn't be trying to just live 'as long as we can', but as long as we can well.
There often comes a time when the rest of a person's life will consist only of barely managed pain, suffering, indignity and imminent death. It should be up to the person living that to decide if it is worth it, and and up to the medical profession to deliver a peaceful end if that is what they want.
There are plenty of issues that need to be worked through before it is possible, particularly around coercion, deliberate or accidental, and how it is delivered, but they must be worked through if we are to consider ourselves humane. When an animal we care about is suffering, with no hope of relief, we can make the choice to end their lives to alleviate the suffering, we should be able to do the same for ourselves.
It's uncanny isn't it, he's such a copycat that he even copied the original shooter's face!
It's likely that you're using a systemd based system and the admin hasn't enabled
lingerfor your user.