That's why almost everything is done using "improved waterfall." (which is the actual original system, the waterfall book author just didn't realize that people had to be explicitly told to correct mistakes and update requirements when needed)
A lot of people don't realize it, because it is how people organize complex projects by default, so if you don't know you made a choice, it was probably waterfall. So the word gets used mostly by fans of other processes.
It is related to these things called "schedules" that are an externally shared resource.
You're welcome.
Oh, and yes, in the case of having borders bisect your area of concern, you would simply specific which side of the line the schedule was reporting. When you walk across the line, nothing changed, the schedule didn't change, and the time on your clock didn't change. As long as you know which side of the line you clock is programmed for, and which side of the line the schedule references, then nothing at all changes by wandering back and forth across it.
Oh, so you're just an entitled but powerless asshole, who is doing shift work on the best shift but still wants to bump swing shift and graveyard around so that you can squat on the entire range of "business hours" at non-shift businesses. Got it.
when you run a computer system then you shall always make sure that timestamps are stored in a "neutral" way by using UTC.
LOL your documentation has a bug. It says "shall" where it should say "may" or "should," and the word "always" is a redundancy of the bug.
It is a great idea, but if you expect that it shall be the case, then any application you write that consumes external resources will have date/time bugs.
FTP use by State and local employees at that level wouldn't have dedicated infrastructure, so accessing it from the wifi provided by coffee shops and hotels would be totally expected.
So yes, you can be 100% certain that many involved routers are easily infiltrated.
If you found a sucker to take that sort of bet; switch to sales. You have a gift and don't need to take chances.
It is just standard basic precautions, not a major attack vector.
The fear isn't so much related to that it might be compromised, but that it isn't encrypted and so everybody on your subnet can read the traffic, and if somebody p0wned your router they could also alter that traffic. And the router in question really might be a consumer wifi router!
Personally, I think election systems demand even stronger security than banks, but if we could at least get the security up to the level the local public library has it would be a great start!
It wasn't an argument, Rei was only providing you some very basic 101-level information that you could easily look up on the internet, if you were fully literate.
Fun fact about English; words are allowed to have more than one definition. Additional fact: most do. Including the word battery.
There is no such thing as a common mistake except where people making the purported mistake are being widely misunderstood. If a word used to mean one thing, and then it gets commonly used to mean another thing, now it means both things! 100 years ago, a single cell battery was not a battery. In modern times, a single battery cell is also a "battery" if it is packaged with electrodes intended for end-use. That isn't wrong. Even in technical jargon, that is how the words are used.
The lawsuit alleging that stuff about the production numbers was already dismissed. It was fucking stupid, and lacks the details you'd need to believe in something like that; like what is the actual accusation? It is hand-waving that includes percentages of affected vehicles, but no reason for that percentage, and no idea what it is a percentage of; as if cars can't easily be counted, or something.
Automobiles are not a virtual resource. They are very countable.
You're exceptionally credulous, but only depending on your feelies about the people involved.
Exactly, there is a real bug report that says nothing like the bullshit you puked up above.
Binary package hint: linux-source-2.6.22
When compared with 2.6.15 in feisty, heavy disk I/O causes increased iowait times and affects desktop responsiveness in 2.6.22
this appears to be a regression from 2.6.15 where iowait is much lower and desktop responsiveness is unaffected with the same I/O load
See, I was wrong to believe you that your system was locking up now that you've been very specific about what bug you're talking about. IF you were being honest above, then you're lying now about this being the related bug. OTOH, if you were telling the truth above, then you're lying that this bug report is related.
Furthermore, this was a bug in Ubuntu, a sucky distro, where your comments were about Linux and the story was specifically about RedHat Linux. Furthermore, it was a bug reversion! LOL Yeah, ubuntu is a hobby OS, and comes with extra bug reversions. As that bug report discusses, a fresh install would have fixed the problem, because it was distro related. If you had been using Fedora/RHEL/CentOS you would never have had that problem. The thing about RHEL/CentOS is that they are very stable, they don't change kernels all the time, and they're only using well-tested ones. Why the fuck would a user as touchy about a bug as you are being using Ubuntu in the first place?!
I'm glad you have Windows, and I'm glad you like it. Thank fucking goodness users like you eventually realize that Linux isn't right for everybody.
Never use Linux, or any open source at all, unless you know you want to use it! If you're not sure what to use, choose a consumer product that comes with the hardware you purchase, or is highly recommended. Open source is given away to the people who want it, there is no other reason to use it. If you hate things that are named in a similar way to other things that you hate, avoid all Free Software or Open Source because it allows forks and there will always be buggy things that are different versions of the thing you chose.
Well, yeah, I can see how somebody dressed as a tragically naive almost-nazi would be at risk of being confused for a real nazi.
OTOH, when people are getting pepper sprayed it sounds like it was worn to a political event. And now I'm really wondering if you are, in fact, a nazi.
The problem is, they designed different ones, and the ones people like most turn out to suck, and the ones that are good cost more than expected. The other ones are fine, but might leave pre-order snobs disappointed compared to waiting for the good ones. So the roll-out is going very slowly.
They're only selling it to early adopters right now, they're not trying to actually sell it to the public yet. That comes later.
Plus, car sales are so good, they don't have batteries for the powerwalls. So they can't actually deliver the full experience yet, they're just a high end solar roof panel without the powerwall.
Slashdot Mirror
I've met programmers who still didn't get it even after years of dealing with time changes.
IME it usually means they don't understand caching in the front end, and they think they're being pragmatic.
Additional training is unlikely to remedy the problem.
But what can you do about it?
I propose we model the solution on the novel A Clockwork Orange by Anthony Burgess.
That's why almost everything is done using "improved waterfall." (which is the actual original system, the waterfall book author just didn't realize that people had to be explicitly told to correct mistakes and update requirements when needed)
A lot of people don't realize it, because it is how people organize complex projects by default, so if you don't know you made a choice, it was probably waterfall. So the word gets used mostly by fans of other processes.
And as a result it gets light at 430am in the summer. You're not even up at 6am and it is full daylight outside.
Yeah, the inconvenience for sport fishing is at least 99% of my complaint about the system!
It is related to these things called "schedules" that are an externally shared resource.
You're welcome.
Oh, and yes, in the case of having borders bisect your area of concern, you would simply specific which side of the line the schedule was reporting. When you walk across the line, nothing changed, the schedule didn't change, and the time on your clock didn't change. As long as you know which side of the line you clock is programmed for, and which side of the line the schedule references, then nothing at all changes by wandering back and forth across it.
The main problem with your thesis is that the word "technically" does not mean "makes pedantic sense according to me."
Semantics doesn't work that way. The meaning has been fixed on account of being given a technical definition.
Philosophical interpretations of the semantics of the etymology are entirely non-technical.
Oh, so you're just an entitled but powerless asshole, who is doing shift work on the best shift but still wants to bump swing shift and graveyard around so that you can squat on the entire range of "business hours" at non-shift businesses. Got it.
I know you're Mindless by definition, but it is not physically possible for Cyndi Lauper's record label to lack value.
when you run a computer system then you shall always make sure that timestamps are stored in a "neutral" way by using UTC.
LOL your documentation has a bug. It says "shall" where it should say "may" or "should," and the word "always" is a redundancy of the bug.
It is a great idea, but if you expect that it shall be the case, then any application you write that consumes external resources will have date/time bugs.
It is a good idea to also use uMatrix so that even if you turn on JS for a site, the third party stuff still can't load.
Why would a non-mutable, cryptographically signed data store not be part of the solution?
Wouldn't success largely depend on the key management scheme?
FTP use by State and local employees at that level wouldn't have dedicated infrastructure, so accessing it from the wifi provided by coffee shops and hotels would be totally expected.
So yes, you can be 100% certain that many involved routers are easily infiltrated.
If you found a sucker to take that sort of bet; switch to sales. You have a gift and don't need to take chances.
It is just standard basic precautions, not a major attack vector.
The fear isn't so much related to that it might be compromised, but that it isn't encrypted and so everybody on your subnet can read the traffic, and if somebody p0wned your router they could also alter that traffic. And the router in question really might be a consumer wifi router!
Personally, I think election systems demand even stronger security than banks, but if we could at least get the security up to the level the local public library has it would be a great start!
Not even going to read your attempt to `splain shit.
I did read up to the `splain part.
But that's really fucking stupid. Was I speaking down to you? Of course I was. Do I care how you identify? No, I do not.
It wasn't an argument, Rei was only providing you some very basic 101-level information that you could easily look up on the internet, if you were fully literate.
Fun fact about English; words are allowed to have more than one definition. Additional fact: most do. Including the word battery.
There is no such thing as a common mistake except where people making the purported mistake are being widely misunderstood. If a word used to mean one thing, and then it gets commonly used to mean another thing, now it means both things! 100 years ago, a single cell battery was not a battery. In modern times, a single battery cell is also a "battery" if it is packaged with electrodes intended for end-use. That isn't wrong. Even in technical jargon, that is how the words are used.
Go and read a fucking datasheet, golly.
The lawsuit alleging that stuff about the production numbers was already dismissed. It was fucking stupid, and lacks the details you'd need to believe in something like that; like what is the actual accusation? It is hand-waving that includes percentages of affected vehicles, but no reason for that percentage, and no idea what it is a percentage of; as if cars can't easily be counted, or something.
Automobiles are not a virtual resource. They are very countable.
You're exceptionally credulous, but only depending on your feelies about the people involved.
LOL, no, that's not what I said at all.
When you say dinosaurs, do you mean birds?
I don't really care if people make two categories, as long they understand that T-rex still ends up on the bird side of the chart.
The birds are still here, too.
Right, but did you consider: when you go to a political event and express yourself and people think you're a nazi... maybe you are one?
Just a thought.
Exactly, there is a real bug report that says nothing like the bullshit you puked up above.
Binary package hint: linux-source-2.6.22
When compared with 2.6.15 in feisty, heavy disk I/O causes increased iowait times and affects desktop responsiveness in 2.6.22
this appears to be a regression from 2.6.15 where iowait is much lower and desktop responsiveness is unaffected with the same I/O load
See, I was wrong to believe you that your system was locking up now that you've been very specific about what bug you're talking about. IF you were being honest above, then you're lying now about this being the related bug. OTOH, if you were telling the truth above, then you're lying that this bug report is related.
Furthermore, this was a bug in Ubuntu, a sucky distro, where your comments were about Linux and the story was specifically about RedHat Linux. Furthermore, it was a bug reversion! LOL Yeah, ubuntu is a hobby OS, and comes with extra bug reversions. As that bug report discusses, a fresh install would have fixed the problem, because it was distro related. If you had been using Fedora/RHEL/CentOS you would never have had that problem. The thing about RHEL/CentOS is that they are very stable, they don't change kernels all the time, and they're only using well-tested ones. Why the fuck would a user as touchy about a bug as you are being using Ubuntu in the first place?!
I'm glad you have Windows, and I'm glad you like it. Thank fucking goodness users like you eventually realize that Linux isn't right for everybody.
Never use Linux, or any open source at all, unless you know you want to use it! If you're not sure what to use, choose a consumer product that comes with the hardware you purchase, or is highly recommended. Open source is given away to the people who want it, there is no other reason to use it. If you hate things that are named in a similar way to other things that you hate, avoid all Free Software or Open Source because it allows forks and there will always be buggy things that are different versions of the thing you chose.
Well, yeah, I can see how somebody dressed as a tragically naive almost-nazi would be at risk of being confused for a real nazi.
OTOH, when people are getting pepper sprayed it sounds like it was worn to a political event. And now I'm really wondering if you are, in fact, a nazi.
Or alternatively, my point went over your head.
Dude, like, do you think it is only people in a small part of California who use that word?
I assume you're one of those upside down people, or maybe even Eurotrash.
If you were American you'd like, totally know that everybody on the west coast talks that way.
You don't get to go all Valley Girl until they say "Gag me with a spoon" or something.
Nope. Panasonic is making the cells, Tesla is making the batteries.
Americans suck, I know. But we're smart. And we can read.
The problem is, they designed different ones, and the ones people like most turn out to suck, and the ones that are good cost more than expected. The other ones are fine, but might leave pre-order snobs disappointed compared to waiting for the good ones. So the roll-out is going very slowly.
They're only selling it to early adopters right now, they're not trying to actually sell it to the public yet. That comes later.
Plus, car sales are so good, they don't have batteries for the powerwalls. So they can't actually deliver the full experience yet, they're just a high end solar roof panel without the powerwall.