Yes, but it will have systemD...
Yes, but it will have systemD...
It's a source that nobody knowledgeable appears to have contradicted. Challenging the source is reasonable if the information is untested. If it isn't challenged (and I notice you didn't challenge it) then it gains plausibility.
P.S.: Your attack is an actual ad hominem attack, admittedly against a dubious character. But just because the source is unreliable doesn't mean the information is wrong. And it was presented to a vocal audience with many knowledgeable individuals in it. So I tend to think that systemd does provide root services to users without rights to use those services. And this does sound like a dangerous weakness.
My sudoers file is empty. (I suppose I *could* remove it, but it's already unusable.) su is necessary. This is an unnecessary hole.
With regard to the issue of dealers, I'm not sure that it's just electric cars they don't want to sell.
In 2013 I was in the market for a gasoline-powered automobile. Did my research, selected a make and model. It wasn't the most common car on the planet, but it also wasn't extremely rare (a mainstream Japanese car). I identified three dealerships in the metropolitan area that, according to their websites, had a model on the lot.
I could not for the life of me get them to give me a test drive. The first dealership I visited, the salesman said they'd "lost the key" to that particular car and I couldn't test drive it or buy it that day, I'd have to come back "later." (He couldn't tell me just when "later" was.) But he put on the *very* hard sell for two other models.
The second dealership, they claimed to have lost the car, period. No, not on the lot, they said. The third dealership, they claimed that I didn't really want that model, it wasn't reliable. When I pressed, they told me that their (brand new 2013) instance was in the shop, that's how bad it is. "Honestly," they didn't want to sell me the marque's "worst model." *They* were looking out for *me*, you see. Which is why they really, really wanted to put me in this *other* model in the showroom....
I finally bought one online and had it driven in from out of state. It's been a great car and performed as expected with the features I needed.
I don't know exactly what was going on when I was trying to make my vehicle purchase, but to me it screamed "conflict of interest" as they clearly didn't want to serve me, the customer, by selling me a product that I came for and that they clearly *had*.
... missing UTC support in cron that is.
changing the system time & date without root or sudo? HELLO? How is that a good idea? ntpdate then ntpd for that and the user can set the TZ environment variable in
not that the old ways are perfect, how many years have we gone without support for UTC or just no daylight savings adjustment?
FWIW, I have not seen any advantages to systemd, and I have not heard of any advantages that I would personally find advantageous. And there do seem to be potential problems.
E,g, faster boot times don't impress me at all. I'd be more impressed by longer up times. I find binary logs dubious, and many people have reported problems with them. Etc.
I have not personally had any actual problems with systemd, but it's not clear how I'd resolve them were they to occur.
So I'm both dubious about the advantages and worried about possible disadvantages. Sufficiently so that if a BSD supported the ext4 file system I would have a test installation running. But not yet sufficiently to reformat my file systems.
With documentation like that I tend to wonder whether idiot is the correct term, or whether malice should be assumed.
Yii! That sounds extremely dangerous, as in local malware == root control.
I had been apathetic (disliking, but apathetic) about systemd, but now I'm thinking I should switch to something that doesn't have it.
First, only an idiot would want a monoculture, particularly in the Linux world, so to those saying "just to systemd full bore or go to (someplace else)" the rest of us need to respond with a very loud and resounding: Fuck You.
That said, things aren't nearly as dire as this post implies. Reading from the responses to the bug he himself linked to, I find the following:
> Unless KDE is prepared to make a statement that it depends on systemd
of course not. Powerdevil recently also gained support for ConsoleKit2, see: http://commits.kde.org/powerde...
Which turns it into a distro problem. Your distribution configured the system in a way that suspend/hibernate is broken. It doesn't come with any of the supported solutions Plasma provides. Which makes it a distro problem. The distro integrates various parts of the software stack. This includes it's the distro's task to ensure that components work together. It failed here by ripping out systemd and replace it with well nothing.
So while I'm sure the systemd zealots would love to see KDE, Gnome3, etc. only work with systemd and drop support for all other distros, this doesn't appear to be happening. In the case of KDE, ConsoleKit2 is supported (and therefor Funtoo, Gentoo, Arch with OpenRC, etc. will continue to work just fine).
... and lost her mind.
Which is a very typical path for religious converts (they tend to start out a bit unbalanced and vulnerable to begin with, get sucked into one religion or another, convert and become the worst, most zealous Godbotherers around)
Only at incompetent companies.
If the CIO is making a decision on the OS to use, then get the hell out of that place now.
People have been saying similar things on this web site for more than 15 years. Good luck with that.
Reality check, ALL network video cameras stay powered up, how do you think you re-enable it over the network? by keeping the processor running, and you might as well keep the camera module powered as well because whiney people wont pay $500 for a full features camera.
One picture is worth 128K words.