Comment Re:The same as ever: Android (Score 3, Insightful) 484
No - in other words, the man knows how to live life without an electronic nanny in his pocket.
No - in other words, the man knows how to live life without an electronic nanny in his pocket.
A little less blame on the owner, and a little more blame on the carrier? How much genuine crap comes pre-installed on a carrier subsidized phone? I'm talking about genuine worthless crap, that does and gives nothing of value to the end customer, the owner who pays for the phone.
The phone is regarded by the carrier as a tool, with which to keep track of the chattel, or the sheeple. Again and again, the carriers are exposed for their overzealous data collection. And, for the most part, people aren't able to turn these "features" off, unless they are willing to invest some time in research, then risk voiding their so-called warranties.
Yeah, end users are mostly dumb clods, but the carriers are responsible for a lot of the problem.
Righter tighter
Lefter looser
That stuff is relatively harmless. I'd not suggest using it as an emergency fluid supply for the reasons you and others mention and the fact that propylene glycol is the active ingredient in a number of bowel preparations used to clean the gut completely out before procedures. You'd be sick, nauseated, completely drained and in a world of butt hurt.
But you won't rust.
This. He could just grab a kilo of meth and get arrested. He'd have his year(s) of solitary confinement, the potential for a catastrophe or two, better medical care and a good buzz.
What's not to like?
They make deep cycle lead acid batteries for (mostly) boats. Typically they last 5-6 years in a marine application and you can drain them to about 10% without problems. Newer controllers are good in that regard. I'm using six deep cycle batteries pulled from various boats as my backup system. They should last for at least another 5 years since they are now warm and dry and not vibrating all of the time. They are also fully recyclable.
Not sure why you'd want to go to a lithium based technology in a stationary application.
If you get yourself stomped in an earthquake, maybe we will send you a package of Doritos and a new keyboard. But that's only if your karma improves. Right now, you're looking to get a couple of Slashdot dupes.
And we're being generous.
You'd think half Slashdot was born before 1960 and learned some traditional UNIX before there even was a Linux, the way they carry on whenever anything changes
I was born before 1960 and started to use Unix around SVR3.0 before there even was a Linux.
I quite like systemd.
Not portable? Who even cares when systemd doesn't even run on linux in most cases. Think phone tablet embedded non glibc. The biggest use case for linux already excludes systemd.
My phone runs systemd fine.
But then my phone runs Linux, not Android.
you have to do a "systemctl reload" after stopping the service and before restarting it.
Sorry, I mean "systemctl daemon-reload" of course.
I'm completely stumped, so I welcome any suggestions at this point.
I suppose you've checked out https://wiki.archlinux.org/index.php/Power_management
Also the sleep key works fine
By which you mean? What happens when you press the sleep key?
That's not what I see on RHEL7
But it is exactly what I see on CentOS 7. How odd.
Type=oneshot
Where is this documented? I didn't see it in the man page for systemd, systemd.unit, systemctl, etc. or any other commands listed in the "SEE ALSO" sections of those commands.
man systemd.service
In man systemd I see:
The following unit types are available:
1. Service units, which start and control daemons and the processes
they consist of. For details see systemd.service(5).
[...]
SEE ALSO
The systemd Homepage[9], systemd-system.conf(5), locale.conf(5),
systemctl(1), journalctl(1), systemd-notify(1), daemon(7), sd-
daemon(3), systemd.unit(5), systemd.special(5), pkg-config(1), kernel-
command-line(7), bootup(7), systemd.directives(7)
And in systemd.directives there is:
Type=
systemd.mount(5), systemd.service(5)
"shit" does happen. What is interesting about the whole systemd thing is that there are a class of people, all posting AC, why lie about what happens.
I'd love to know why. I can understand that people don't like some software, but why would they flat out lie about what that software does?
How do I know these claims are lies? Because they are all posted AC, because nobody has ever claimed to have reported these defective behaviours as bugs, because I can't reproduce them even when using exactly the same environments and commands as the claimant.
I did try it, and reproduced the his results on Fedora 21.
That's very interesting, you're the first non-ac to report this.
Care to show me exactly what you did?
If you took the recipe given by the ac:
It is trivial to reproduce this serious problem with systemd. Pick any script in
# append --broken to ExecStart line
vi/usr/lib/systemd/system/named.service
systemctl stop named
systemctl start named
Then maybe you missed the fact that systemd doesn't re-read unit files for existing services, you have to do a "systemctl reload" after stopping the service and before restarting it. (You should have got a message warning you of this, but many people seem to misunderstand the message).
It's a naive, domestic operating system without any breeding, but I think you'll be amused by its presumption.