You either have absurdly low speed limits, a bunch of extreme athletes, or perhaps you've mistaken something motor-assisted for a bicycle.
He did say "in a school zone", which is not uncommon to have a speed limit of 15-20 at the start and end of the school day, when the sidewalks and streets are going to be lousy with buses, cars, and pedestrians.
So an audit performed by a closed group of corporates who have, no doubt, been thoroughly vetted and has never, ever, ever gotten a phone call from anyone in a suit offering them the choice of a bag of cash to play ball, or an increased probability of "accidents" and "unfortunate data leaks."
Given the farewell address we got from the TC devs, which I'm sure most of us remember, and the laughable suggestions of "alternatives," there are two strong possibilities for why the project was shuttered:
1. The developers all suffered a massive psychotic break at the same time.
2. A canary so big and obvious that it's more of a "warrant roc."
They may have ended the "silence", but the "uncertainty" is still alive and well, AFAIC.
As a fat guy, I call that "dirty pool!"
Sure they will, he's just doing it one dev at a time
And people wonder why we're moving to FreeBSD instead of making our "reasoned arguments" to get systemd's flaws fixed...
And even in the spots you DO want it, odds are they used a ready-made library to hide the ugly bits. I'm no crypto expert, but I know enough to know that rolling your own would probably be a disqualification right there.
... it's an assumption that he's looking for an additional or extra method of notification.
But not an unreasonable one, if he's conscientious enough to reach the point where he's looking for something like this.
Jesus, why would you even think about using Ubuntu in a server anyway? Everywhere I ever worked or heard of used RHEL, Centos or occasionally Debian. Since I discovered Mint I would not even waste my time using Ubuntu on a desktop.
I wouldn't, the decision was made 10 years ago before I came on board for the project. Back then, the server release hadn't gone full dumbfuck yet, so it was just a matter of "meh, whatever." As it's gotten more ridiculous, it's just been a matter of overcoming inertia. Now it has done, and we're scraping it out of the network.
I'd rather have a smart-assed car, myself.
Which, again, has nothing to do with the original BSD licensed code.
Which still has nothing to do with the originally released code. If you want to make a point about not being allowed/able/whatever to fix code, then make it without falling back on the decades-old half-facts. It only makes you look full of it.
The simple fact is that anyone who releases code under BSD or similar licenses is absolutely okay with that code being used that way - if they weren't, they wouldn't use that license.
If you prefer that others NOT be allowed to use your code in closed systems, that's also okay, but it's a matter of preference, not morality, and the kind of twisted doublethink that's been bouncing around the tubes for the last 20+ years trying to make it so is what's gotten RMS and his acolytes their well-earned "netkook" reputation.
But equally, thousands of companies now trust systemd to run enterprise servers since centos or RHEL is pretty much the defacto linux distribution in this regard. The fact that this is the case does indicate that it must be pretty stable when correctly configured.
Are you new to this industry, or just pushing an agenda? Deployment numbers certainly do NOT indicate stability - 20 years of Windows' dominance is your counter-evidence there - at best, it's implied.
If there are bugs in systemd, then report them and maybe even help diagnose them to make it better. It has huge traction now so there is zero chance of it disappearing.
I'll pass. I'm of the opinion that systemd is fatally flawed at the design level, probably even at the conceptual level - i.e., it can't be "fixed."
We've already started the process of migrating our infrastructure from Ubuntu Server LTSes back to FreeBSD. The devs behind the former have been making lots of questionable decisions the past few years, so we just needed a back-breaking straw, and the wide adoption only helped us to pick a destination. If Ian's GR had gone through and we wouldn't have had to worry about some random package "upgrading" our Debian installs down the line, we would have gone that way, instead.
I don't care whether it disappears entirely. Once we've finished the move, I don't need to care whether Linus makes the kernel itself require systemd, or if Linux chokes to death on it - my horse will be out of the race.
Well, it is, but it does sod all to protect that openness, so BSDed software often ends up less open by the time you actually get a copy of it.
Are you guys still spewing this BS meme? Letting someone use open code in a closed project does "sod all" to close off the original code.
once-in-a-lifetime events such as weddings.
This immediately brought the Robin Williams "WHAT YEAR IS IT???" image macro into my mind.
If that were the only reason people didn't like/want/trust it, you might have a point. Considering that the "crash" complaint is one of the more minor ones, however, it just comes across as ignoring the legitimate problems and concerns for the sake of keeping it a politicized issue and/or delusions of persecution.
The cost of feathers has risen, even down is up!
