IF he keeps the phone at home, AND he can guarantee that any fire damage will be confined to his own property AND he doesn't have guests come over without warning them of the risk, then yes.
He will also need to be prepared to continue making his mortgage payments on the burned out shell.
Actually, if I sent something to someone using MS it would most definitely be an invasion of my privacy if MS read it unless they managed somehow to first present ME with the TOS and I agree to it.
I may certainly continue to feel it is an invasion of my privacy even if I reluctantly agree to their terms.
Personally, I'm of two minds on this. On one hand, I don't like the idea of any foreign government attempting to screw with our elections. On the other, they didn't make the information up, they just shone a light into some shadows. In that sense, they did us a public service. If what we saw in those shadows cost the Dems the election, they have only themselves to blame.
At this point though, now that a number of Congressmen have called for his head (not necessarily following a trial), he has no reason to believe he would get a fair trial if he returned voluntarily. I don't see Russia reversing their position anytime soon so his involuntary return isn't looking all that likely..
So, the closest approximation of justice at this point would be a pardon.
That goes all the way back to the telegraph where you could interrupt the sender by opening the circuit.
RS-232 maintains it in the form of the break signal which just pulls the line low for not less than one symbol's time (ass opposed to ctrl-c that just transmits character value 3).
I can tell. There's one scenario where a specific order applies, boot time.
If you can tell, one might expect ypu to make an effort to communicate more clearly. If you find you cannot, then you should clerify your own thinking first.
Boot time is also the only scenario where initializing the system is relevant. All those other systems failed to catch on, probably because non-deterministic system initialization is problematic.
By who?
By the kernel configuration, SuSE, Facebook, Tripadvisor, and a number of other operations using it in production.
Either way, systemd needs to be flexible enough to deal with this sort of thing. It isn't.
Nope the problem was udev...
SysVinit with udev doesn't have this problem. Beyond that, the absorberthon that is systemd claims udev for itself, so it's their problem now. This was udev's behavior before there was systemd and it is still udev's behavior. It's not like it popped up as a surprise. Pure and simple, systemd neither took that into account nor changed udev to no longer behave that way. Thus, the blame falls squarely on systemd.
Initrd? You mean the thing that is supposed to assemble rootfs devices...
/home is not root. Actually, at one time systemd was supposed to aldo take care of things in the intird/initramfs. It doesn't now because it isn't capable of it due to it's inability to deal with RAID and other systems where some failures are OKish. This is just an example of something very fundamental they didn't think of, didn't build in enough flexibility to make it fixable in configuration, and didn't make it open and modular enough to allow something else to take care of this task for it.
Don't care.
So you don't care about the philosophy that made Linux superior to Windows? You are happy to degrade the usefulness of Linux so you can switch to the losing strategy born from insufficient understanding??
Now there's an appeal to authority...
Referring to one's own relevant experience is in no way an appeal to authority. Particularly after a claim that one lacks relevant knowledge or experience. In other words, you went there and got shot down. In response, for some reason you smashed an egg on your face.
Actually it means that no one was happy with the original.
Sure, it is the most disliked init system ever, other than all of the others.
I'm going to assume you didn't RTFM if you're having problems with modules and when they get plugged.
Not KERNEL modules, init system modules.
The right order is stable during one scenario only, a controlled boot.
You prefer an out of control boot? Not sure what you mean there.
BTRFS hasn't been listed as experimental for some time now. It is considered usable in production now. The problem wasn't BTRFS, the problem was systemd trying to be clever when it really isn't. It would refuse to even attempt to mount btrfs until all disks showed present. It offered no timeout. I did have the degraded option set, such that when systemd inevitably dropped me to a shell, I could just type mount/home and POOF, there it was.
systemd never did solve the problem for MD RAID devices, it's just that the initrd now assembles the RAID before systemd gets a chance to screw it up.
The Unix philosophy has always been small tools that do one job well combined to do nearly anything. That's how it's SUPPOSED to be.
Systemd COULD have been designed to play well with others. It's whole process management thing could have been called by/sbin/init to take care of whatever was configured under it and leave everything else to the rc scripts (or whatever other modules might be called by init). Instead, it's a hairball. It reminds me of Robin Williams joke about God getting stoned and creating the Platypus just to fuck with us.
Since I actually wrote an init system for bproc nodes, I probably know a hell of a lot more about it than you do.
You know what it usually means when dozens of "new and improved" replacements fail to replace the original? It means the original is actually a lot better than you think it is.
Actually, I want to to use other tools to help boot the system. With sysvinit, I can easily plug modules at will.
because something was done in the wrong order.
I know it sounds like a really radical idea, but howsabout just specifying the right order?
But here's an example: I was testing a system with BTRFS doing mirroring. As part of the test, I dropped one of the disks to simulate a failure. Systemd flatly refused to start in degraded mode. It dropped to the shell every time. There was no way to tell it "Just mount the damned thing and let me worry about it". So much for high availability. Under sysV, I just added the degraded option and it worked every time. If I want to wait an arbitrary amount of time for all the drives to spin up, I can do that in the mount script with no difficulty.
Literally anything systemd can do could already be done using simple helpers called by sysV. You even provided an example yourself.
Yes, there is government, but try that in the private sector. I doubt there are enough government jobs open. All the same, it's fine for you personally now and until someone decides to downsize the government.
If you're self employed, one day your body may decide you will slack off or else.
Agreed, the retirement age may need to rise, but someone better tell that to employers as well. You may be 60 with 20 more good years in you but it doesn't matter if HR starts round filing resumes at 49.
I didn't say incompetent health care, I said affordable. For example, when people really do need a course of antibiotics, they should be able to afford the full course to make sure the bugs are dead. They certainly should not save half so the next time they don't have to scrape up money for a doctor and crazy expensive prescription. They certainly shouldn't have to tough it out and spread the infection while they pray that their immune system will eventually win.
I'm referring to thinking you'll make it to 120. You'll also be somewhat exceptional if you're still employed at 77. The mandatory retirement age (and the de-facto retirement age) hasn't been going up as fast as lifespans.
The U.S's continuing failure to provide affordable healthcare to a growing portion of it's population will turn our cities into breeding grounds for all manner of new and exciting infectious bacteria.
There's a lot to that. Many infections acquired in hospitals are traceable to unwashed hands, unsanitized surfaces and (of all things), doctors' ties dragging over everything.
Lose the ties, break out the bleach and Lysol, and consider cold plasma hand cleaning stations.
Yes, in the end the industrial revolution lifted all boats. The problem was that portion of it where it swamped as many boats as it lifted. That the next generation will be OK is little comfort to those in the midst of suffering.
If you were in howling pain in the ER and the doc said it'll quit hurting in a week or two, so no pain medication for you, how might you feel about that? No local from the dentist because he only needs to drill for a few minutes?
It's the old political shuffle. The people who want no regulations call that the Free Market. Then they point to obviously working markets and declare them to be "free", carefully ignoring the regulations that make it work.
Of course, given the madness over the last decade or so, I would say the financial markets could be working a lot better with more regulation.
Nevertheless, any Market requires adequate information available to the buyer. Look what happened with CDOs when that was polluted with disinformation from corrupt ratings.
Most market regulations revolve around preventing fraud and suppression of information.
Slashdot Mirror
IF he keeps the phone at home, AND he can guarantee that any fire damage will be confined to his own property AND he doesn't have guests come over without warning them of the risk, then yes.
He will also need to be prepared to continue making his mortgage payments on the burned out shell.
That might be a bit too obvious even for Trump and Putin.
Actually, if I sent something to someone using MS it would most definitely be an invasion of my privacy if MS read it unless they managed somehow to first present ME with the TOS and I agree to it.
I may certainly continue to feel it is an invasion of my privacy even if I reluctantly agree to their terms.
If it came one week later, it definitely wasn't a copy. It takes a lot longer than a week to design a smartphone.
Personally, I'm of two minds on this. On one hand, I don't like the idea of any foreign government attempting to screw with our elections. On the other, they didn't make the information up, they just shone a light into some shadows. In that sense, they did us a public service. If what we saw in those shadows cost the Dems the election, they have only themselves to blame.
At this point though, now that a number of Congressmen have called for his head (not necessarily following a trial), he has no reason to believe he would get a fair trial if he returned voluntarily. I don't see Russia reversing their position anytime soon so his involuntary return isn't looking all that likely..
So, the closest approximation of justice at this point would be a pardon.
I have every right to consider it a violation of privacy. I can also decide I will not agree to a violation of my privacy and skip MS entirely.
And therein lies the answer. We choke ISIS out with an army of deadwood patent attorneys.
That goes all the way back to the telegraph where you could interrupt the sender by opening the circuit.
RS-232 maintains it in the form of the break signal which just pulls the line low for not less than one symbol's time (ass opposed to ctrl-c that just transmits character value 3).
Cut the wire is as good as any I suppose.
ctrl-c once known as break on old TTYs has been around since the mainframe days.
Later keyboards got a special break key but ctrl-c was retained for killing the foreground process.
I can tell. There's one scenario where a specific order applies, boot time.
If you can tell, one might expect ypu to make an effort to communicate more clearly. If you find you cannot, then you should clerify your own thinking first.
Boot time is also the only scenario where initializing the system is relevant. All those other systems failed to catch on, probably because non-deterministic system initialization is problematic.
By who?
By the kernel configuration, SuSE, Facebook, Tripadvisor, and a number of other operations using it in production.
Either way, systemd needs to be flexible enough to deal with this sort of thing. It isn't.
Nope the problem was udev ...
SysVinit with udev doesn't have this problem. Beyond that, the absorberthon that is systemd claims udev for itself, so it's their problem now. This was udev's behavior before there was systemd and it is still udev's behavior. It's not like it popped up as a surprise. Pure and simple, systemd neither took that into account nor changed udev to no longer behave that way. Thus, the blame falls squarely on systemd.
Initrd? You mean the thing that is supposed to assemble rootfs devices...
/home is not root. Actually, at one time systemd was supposed to aldo take care of things in the intird/initramfs. It doesn't now because it isn't capable of it due to it's inability to deal with RAID and other systems where some failures are OKish. This is just an example of something very fundamental they didn't think of, didn't build in enough flexibility to make it fixable in configuration, and didn't make it open and modular enough to allow something else to take care of this task for it.
Don't care.
So you don't care about the philosophy that made Linux superior to Windows? You are happy to degrade the usefulness of Linux so you can switch to the losing strategy born from insufficient understanding??
Now there's an appeal to authority...
Referring to one's own relevant experience is in no way an appeal to authority. Particularly after a claim that one lacks relevant knowledge or experience. In other words, you went there and got shot down. In response, for some reason you smashed an egg on your face.
Actually it means that no one was happy with the original.
Sure, it is the most disliked init system ever, other than all of the others.
I'm just demanding that the fruits actually go to those who have labored.
Since Jobs was inspired to the rounded rectangle design when he saw a street sign, shouldn't they be paying the DOT?
I'm going to assume you didn't RTFM if you're having problems with modules and when they get plugged.
Not KERNEL modules, init system modules.
The right order is stable during one scenario only, a controlled boot.
You prefer an out of control boot? Not sure what you mean there.
BTRFS hasn't been listed as experimental for some time now. It is considered usable in production now. The problem wasn't BTRFS, the problem was systemd trying to be clever when it really isn't. It would refuse to even attempt to mount btrfs until all disks showed present. It offered no timeout. I did have the degraded option set, such that when systemd inevitably dropped me to a shell, I could just type mount /home and POOF, there it was.
systemd never did solve the problem for MD RAID devices, it's just that the initrd now assembles the RAID before systemd gets a chance to screw it up.
The Unix philosophy has always been small tools that do one job well combined to do nearly anything. That's how it's SUPPOSED to be.
Systemd COULD have been designed to play well with others. It's whole process management thing could have been called by /sbin/init to take care of whatever was configured under it and leave everything else to the rc scripts (or whatever other modules might be called by init). Instead, it's a hairball. It reminds me of Robin Williams joke about God getting stoned and creating the Platypus just to fuck with us.
Since I actually wrote an init system for bproc nodes, I probably know a hell of a lot more about it than you do.
You know what it usually means when dozens of "new and improved" replacements fail to replace the original? It means the original is actually a lot better than you think it is.
Actually, I want to to use other tools to help boot the system. With sysvinit, I can easily plug modules at will.
because something was done in the wrong order.
I know it sounds like a really radical idea, but howsabout just specifying the right order?
But here's an example: I was testing a system with BTRFS doing mirroring. As part of the test, I dropped one of the disks to simulate a failure. Systemd flatly refused to start in degraded mode. It dropped to the shell every time. There was no way to tell it "Just mount the damned thing and let me worry about it". So much for high availability. Under sysV, I just added the degraded option and it worked every time. If I want to wait an arbitrary amount of time for all the drives to spin up, I can do that in the mount script with no difficulty.
Literally anything systemd can do could already be done using simple helpers called by sysV. You even provided an example yourself.
The old pile of shit was willing to keep its fingers out of other people's pies if you wanted to try something else along side it.
It also understood imperatives. If you tell it run something NOW, it does just that, every time.
Yes, there is government, but try that in the private sector. I doubt there are enough government jobs open. All the same, it's fine for you personally now and until someone decides to downsize the government.
If you're self employed, one day your body may decide you will slack off or else.
Agreed, the retirement age may need to rise, but someone better tell that to employers as well. You may be 60 with 20 more good years in you but it doesn't matter if HR starts round filing resumes at 49.
I didn't say incompetent health care, I said affordable. For example, when people really do need a course of antibiotics, they should be able to afford the full course to make sure the bugs are dead. They certainly should not save half so the next time they don't have to scrape up money for a doctor and crazy expensive prescription. They certainly shouldn't have to tough it out and spread the infection while they pray that their immune system will eventually win.
As I understand it, it is mostly symptom less. Those who are bothered are generally advised to take chill pills as needed.
I'm referring to thinking you'll make it to 120. You'll also be somewhat exceptional if you're still employed at 77. The mandatory retirement age (and the de-facto retirement age) hasn't been going up as fast as lifespans.
The U.S's continuing failure to provide affordable healthcare to a growing portion of it's population will turn our cities into breeding grounds for all manner of new and exciting infectious bacteria.
There's a lot to that. Many infections acquired in hospitals are traceable to unwashed hands, unsanitized surfaces and (of all things), doctors' ties dragging over everything.
Lose the ties, break out the bleach and Lysol, and consider cold plasma hand cleaning stations.
Yes, in the end the industrial revolution lifted all boats. The problem was that portion of it where it swamped as many boats as it lifted. That the next generation will be OK is little comfort to those in the midst of suffering.
If you were in howling pain in the ER and the doc said it'll quit hurting in a week or two, so no pain medication for you, how might you feel about that? No local from the dentist because he only needs to drill for a few minutes?
It's the old political shuffle. The people who want no regulations call that the Free Market. Then they point to obviously working markets and declare them to be "free", carefully ignoring the regulations that make it work.
Of course, given the madness over the last decade or so, I would say the financial markets could be working a lot better with more regulation.
Nevertheless, any Market requires adequate information available to the buyer. Look what happened with CDOs when that was polluted with disinformation from corrupt ratings.
Most market regulations revolve around preventing fraud and suppression of information.