We're missing a lot of information here. Did Cisco email them in Russian? Did they ask nicely or post demands? Did they provide any evidence in the email?
Depending on the nature of the bad guys, we also have to consider that there could be consequences well beyond loss of a few accounts if they shut them down.
Trump claims he's great at building things, I say we find out. Give him a bag of cement, bricks and a trowel and tell him to get to it. Let's see how he does.
Otherwise, what he really means is that he's good at telling other people to build so he doesn't have to.
That's a great deal of effort to downplay the whole thing, but doesn't change my statement even a jot. Even if it was the smallest and weakest weather event ever measured, it's existence doesn't contradict a prediction that there would be more strong storms, it just doesn't support it.
However, it was rather large in a place where they don't typically get that large. That could be a fluke or part of a trend, but it certainly doesn't HARM the case for stronger storms.
As for the larger case of storm activity, the correct measure would be energy expenditure but those figures would be hard to come up with.
I am quite familiar with the scripts under/etc/init.d. The bazillion config files for systemd aren't intimidating, they're horrifying. They actually use "come from" (a popular programming language joke) style logic! I don't just mean the ones under/etc, I mean the ones under/lib (under the rug?).
The kernel and btrfs work just fine when systemd isn't there to muck it up. I tested that by setting up a system under sysV, testing, and then under systemd. The sysV system booted up fine in degraded mode (after I specified that I wanted that behavior). The systemd system refused to boot in degraded mode in spite of me specifying that I wanted degraded mode when necessary.
System tools are supposed to provide the mechanism to enforce the admin's policy. They are not to dictate policy to the admin.
Backups are supposed to prevent data loss. RAID either hard, soft, or implemented within the filesystem is helpful there but the primary purpose is to improve the machine's availability. Sitting at an emergency shell prompt in the initramfs is anathema to availability. The correct behavior is often mount it anyway and email the admins. If my policy for the server is that it shouldn't mount the degraded volume, I can certainly do that with or without systemd. If it should mount the volume anyway, I can only do it without systemd.
I doubt you want to use your experience in a dick measuring contest here. Just do it is also sometimes used by people good enough to actually just sit down and do it.
While I do recognize that sysV is limited in a dynamic setup, I also recognize that whatever the real solution is, systemd will hinder it's development and actively fight it's implementation through tightly coupled dependencies, poor documentation, and unstable APIs If the systemd project would put up real walls between "moduiles" such that it becomes truly modular and drop it's all things to everyone but it's our way or the highway attitude, parts of it might actually figure in the solution. It really needs to get divorced from freedesktop.org.
Those were more based on the need for a plot than a full imagining. That was robot's work, but robots wouldn't highlight one of today's problem in a futuristic setting designed to bypass a kneejerk reaction.
Not to mention that the data had to be encoded so that the strings of 1s and 0s wouldn't be too long in order to be able to read it again. So if you just spin it at the right RPM and read it out, you won't get recognizable data.
Constant checking in will kill battery life, but the problem is that they don't remain in the alarm state. That would also cause battery wear, but only in the event of a break in.
A wired system is more secure but not always practical as a retrofit. Of course, most home alarms depend on most criminals being dumb.
The problem isn't that it won't report a problem while interference has the radio links down (that is an issue with any wireless system). The problem is that once the interference clears up, it will continue to believe all's well for some time after.
What's Windows 10 got to do with it, IPv6 has been supported since XP. A lot of the v4 only hardware at the ISP and carrier level is already slated for replacement if it hasn't already been replaced. My cable modem that didn't support v6 failed years agio and got replaced with one that did (and that failed and got replaced too).
You must spend hours in the morning winding up your old hardware.
Not even close, though it may see reduced application.
Arduino (AVR) can operate at a wide range of voltages and doesn't need terribly close regulation. It can go down to extremely low power if the regulator and power LED is removed (The pro-mini offers a solder link that can be cut to do that easily). It is more robust than the Pi.
Where more computation power is wanted and the above aren't as important, the Pi comes into play.
That is absolutely NOT what AMD did. AMD negotiated in good faith with Intel when Intel needed there to be a second source for x86 in order to make some big government sales.
If you have a disease that WILL kill you in 5 years, the risk that the cure might give you a disease that might kill you in 6 years probably seems worth while.
Yes, for things that confound the breathalyser, they do need to do a more reliable followup. I thought you meant when someone turns up a bottle of cough medicine.
However, it can be argued that if you drink the cough medicine you SHOULD have known it would raise your BAC. That also covers the lame excuses of I lost track, or I felt OK (you should know alcohol makes you overestimate your abilities). A blind person certainly knows they're blind. This lady has a medical condition that very few even know exists.
There is a growing list of laws that claim struct liability, but I would say those are ethically questionable at best.
Shell scripts are junior admin material already. To a degree, they're power user material. If your admins aren't even up to power user level then my point stands. They're not even really admins, why do you let them have root access to your boxes?
Perhaps more to the point, it's not like init scripts need to be constantly messed around with. Surely there must be an actual admin somewhere in the enterprise that can deal with it the once a year (if your enterprise is large enough) it is needed?
A lot of people with long experience regularly dump their databases into CSV files to maximize their odds of meaningful recovery of the data should something go wrong.
Slashdot Mirror
We're missing a lot of information here. Did Cisco email them in Russian? Did they ask nicely or post demands? Did they provide any evidence in the email?
Depending on the nature of the bad guys, we also have to consider that there could be consequences well beyond loss of a few accounts if they shut them down.
Trump claims he's great at building things, I say we find out. Give him a bag of cement, bricks and a trowel and tell him to get to it. Let's see how he does.
Otherwise, what he really means is that he's good at telling other people to build so he doesn't have to.
That's a great deal of effort to downplay the whole thing, but doesn't change my statement even a jot. Even if it was the smallest and weakest weather event ever measured, it's existence doesn't contradict a prediction that there would be more strong storms, it just doesn't support it.
However, it was rather large in a place where they don't typically get that large. That could be a fluke or part of a trend, but it certainly doesn't HARM the case for stronger storms.
As for the larger case of storm activity, the correct measure would be energy expenditure but those figures would be hard to come up with.
So you take the most powerful hurricane ever to be evidence AGAINST a prediction of super hurricanes?
I am quite familiar with the scripts under /etc/init.d. The bazillion config files for systemd aren't intimidating, they're horrifying. They actually use "come from" (a popular programming language joke) style logic! I don't just mean the ones under /etc, I mean the ones under /lib (under the rug?).
The kernel and btrfs work just fine when systemd isn't there to muck it up. I tested that by setting up a system under sysV, testing, and then under systemd. The sysV system booted up fine in degraded mode (after I specified that I wanted that behavior). The systemd system refused to boot in degraded mode in spite of me specifying that I wanted degraded mode when necessary.
System tools are supposed to provide the mechanism to enforce the admin's policy. They are not to dictate policy to the admin.
Backups are supposed to prevent data loss. RAID either hard, soft, or implemented within the filesystem is helpful there but the primary purpose is to improve the machine's availability. Sitting at an emergency shell prompt in the initramfs is anathema to availability. The correct behavior is often mount it anyway and email the admins. If my policy for the server is that it shouldn't mount the degraded volume, I can certainly do that with or without systemd. If it should mount the volume anyway, I can only do it without systemd.
I doubt you want to use your experience in a dick measuring contest here. Just do it is also sometimes used by people good enough to actually just sit down and do it.
While I do recognize that sysV is limited in a dynamic setup, I also recognize that whatever the real solution is, systemd will hinder it's development and actively fight it's implementation through tightly coupled dependencies, poor documentation, and unstable APIs If the systemd project would put up real walls between "moduiles" such that it becomes truly modular and drop it's all things to everyone but it's our way or the highway attitude, parts of it might actually figure in the solution. It really needs to get divorced from freedesktop.org.
Those were more based on the need for a plot than a full imagining. That was robot's work, but robots wouldn't highlight one of today's problem in a futuristic setting designed to bypass a kneejerk reaction.
It is more likely to assist a lawyer than be one.
Possible responses:
It would have to be a similar model. There was a lot of variation in encoding at the time.
Why is that a problem? You also don't need people to work.
There are interesting things that are a value to society but you can get people to do them because they are interesting.
Not to mention that the data had to be encoded so that the strings of 1s and 0s wouldn't be too long in order to be able to read it again. So if you just spin it at the right RPM and read it out, you won't get recognizable data.
Constant checking in will kill battery life, but the problem is that they don't remain in the alarm state. That would also cause battery wear, but only in the event of a break in.
A wired system is more secure but not always practical as a retrofit. Of course, most home alarms depend on most criminals being dumb.
The problem isn't that it won't report a problem while interference has the radio links down (that is an issue with any wireless system). The problem is that once the interference clears up, it will continue to believe all's well for some time after.
Yes. An AVR microcontroller has very few requirements for support circuitry.It makes transitioning to a custom board much easier.
In the very worst case, the ISP gives you a /64 which is enough to support every possible ethernet address 64K times over.
What's Windows 10 got to do with it, IPv6 has been supported since XP. A lot of the v4 only hardware at the ISP and carrier level is already slated for replacement if it hasn't already been replaced. My cable modem that didn't support v6 failed years agio and got replaced with one that did (and that failed and got replaced too).
You must spend hours in the morning winding up your old hardware.
Not even close, though it may see reduced application.
Arduino (AVR) can operate at a wide range of voltages and doesn't need terribly close regulation. It can go down to extremely low power if the regulator and power LED is removed (The pro-mini offers a solder link that can be cut to do that easily). It is more robust than the Pi.
Where more computation power is wanted and the above aren't as important, the Pi comes into play.
They both have their place.
That is absolutely NOT what AMD did. AMD negotiated in good faith with Intel when Intel needed there to be a second source for x86 in order to make some big government sales.
I'm not so sure the concern is even valid in this case given that the germline is already compromised.
If you have a disease that WILL kill you in 5 years, the risk that the cure might give you a disease that might kill you in 6 years probably seems worth while.
So you really do think you can design a workplace for monkeys and somehow get a decent work product out of them.
You actually do prefer something too inflexible to be fixed in the event of a problem over something that requires a minimum of competence.
Do you also hire sales people with no social skills and accountants who flunked arithmetic?
Did your lawyers pass the bar?
The real WTF is that you can possibly run up a bill that large in just 6 days with a free to pay game.
Yes, for things that confound the breathalyser, they do need to do a more reliable followup. I thought you meant when someone turns up a bottle of cough medicine.
However, it can be argued that if you drink the cough medicine you SHOULD have known it would raise your BAC. That also covers the lame excuses of I lost track, or I felt OK (you should know alcohol makes you overestimate your abilities). A blind person certainly knows they're blind. This lady has a medical condition that very few even know exists.
There is a growing list of laws that claim struct liability, but I would say those are ethically questionable at best.
Shell scripts are junior admin material already. To a degree, they're power user material. If your admins aren't even up to power user level then my point stands. They're not even really admins, why do you let them have root access to your boxes?
Perhaps more to the point, it's not like init scripts need to be constantly messed around with. Surely there must be an actual admin somewhere in the enterprise that can deal with it the once a year (if your enterprise is large enough) it is needed?
A lot of people with long experience regularly dump their databases into CSV files to maximize their odds of meaningful recovery of the data should something go wrong.