And there's the problem. By sabotaging a fair trial, we are left unsure that the right people are being convicted. Trust in law enforcement, the courts, and government in general is eroded.
No, I just see no reason someone should beat their head against a wall when the answer is cheap and easy. If that's not for you, pound away. Perhaps your time isn't worth more than $5 an hour.
The reason is simple. Practically every distro is available in DVD iso format.
In my case, I've used both, but I do a number of different installs with different distros. One cheap drive and a collection of dirt cheap DVDs is a good answer.
It is absolutely not legal to ask under an NSL. Otherwise they can lie and make vague threats (the latter is a gray area) but there is only so far they can go. The NSL is over the line.
But anything that information leads to is fruit from a poison tree and so should not be usable to indict or convict. They are knowingly pulling the wool over a judge's eyes and that is illegal.
Don't we have enough criminals out there without giving some of them a government paycheck?
Given the history, generally the DOJ is happy with contorting the law into fascinating new shapes to claim something is legal for law enforcement when objective legal scholars say otherwise. So if even the DOJ can't get behind this use of a NSL, that suggests the FBI is way over the line.
As for criminals walking, I notice that over three years after the lab tech in Massachusetts got caught outright fabricating evidence, only a small percentage have walked. Perhaps the FBI likes their odds.
Yes, and now the editor suddenly needs specialized code in order for state saving to not be a disaster. Seems like it would be better to just send it SIGHUP.Best solution, run the editor in screen if the connection is at all likely to be broken in mid-session. Have the system honor the well known and long documented API.
The netcat example will fail. Remember, the other end of that connection didn't save state.
If the simple program is talking to a remote server, it can't necessarily save state at all. How would you save state for netcat, for example?
If a file might change while the process is saved off, havoc could result. What do you suppose happens if vi (or emacs, or whatever) gets saved off just as it is about to write out a changed file? Then the file changes, later the editor wakes up and overwrites the committed changes.
It's not at all hard. A and E don't need to care because they weren't attached to the dead process. They haven't lost state with their dependent or their dependency.
In case they aren't properly designed though, that's what SIGUSR1 and SIGUSR2 are for. Or any failed process causes a script to be called that tears it all down and re-starts it. Set the starter scripts to trap any abend.
You said:
Done really?
and since my only use of the word was in a one liner script, I concluded you referred to that.
It's the old laptop, more than adequate for video though. So it stays behind the TV. If I didn't just happen to have a spare laptop, I'd get a Pi or something like that.
I'm with you one the remotes. This isn't the '70s anymore, why haven't remotes gotten any better?
Certainly, I did no such thing. It didn't help that Gnome drank the cool aid and started depending wherever it could. Personally I'm fully ready to dump gnome if that's what it takes.
If you're claiming I should be maintaining my own private distro, I'll just say give that a try and report back, I could use a laugh.
Perhaps for Samsung (I don't have one). Some vendors do not offer the choice. Even if firmware must be manually updated, sometimes you get sturk with either leaving features broken by server side changes or do the upgrade warts and all. Either way, you end up with less than you paid for.
The user doesn't necessarily get a choice. The vendors don't bother to produce updates that benefit the consumer, but they won't hesitate to produce and force one that benefits them. If a corporation could be sent to kindergarten, they would flunk.
Personally, I won't have a TV that requires an internet connection. I get a dumb TV and use my own hardware/software for anything over the network. A TV should have a tuner and a good set of aux inputs ONLY.
The reason checkpointing is typically done by the program itself is that there is sufficient complexity involved that it is a rather specialized operation. There is no generalized way to save a program's state (including system state and potentially, the world's state) such that it can be restored successfully. That is exactly why I rejected it as a solution.
Checkpointing *IS* saving state. I hope you now see that not only is there no process manager that saves state, no process manager CAN arbitrarily save state.
I have worked on systems such as bproc that narrowed the parameters down enough to *OFTEN* work, but there were always corner cases.
Obviously, C knows because it gets restarted after the crash. The ENOTCONN is the notifier for B and the new instance of C connecting to D is the notifier to D. How hard is that?
BTW, ":done" is clearly part of the do..done block associated with "while" in the script. The semicolons are the give away there.
If any further notifications are needed (they normally shouldn't be necessary in a good design), the script can fire them off.
But honestly, all of that is really just papering over bugs in C. Programs shouldn't crash.
Society is under no obligation to grant incorporation or any other form of limited liability. Even though it is apparently never enforced, incorporation requires that the incorporation be in the public interest. Anti-social behavior is the opposite.
That's the problem. This nastiness wasn't part of the deal. The TV they bought didn't do this. Samsung are altering the deal and telling people to pray they don't alter it further.
This is why I insisted on a dumb TV with a VGA input and no network connection last time.
Slashdot Mirror
Perhaps that's the origin of the bermuda triangle and other phenomenology, it's just people slipping through cracks in the map.
And there's the problem. By sabotaging a fair trial, we are left unsure that the right people are being convicted. Trust in law enforcement, the courts, and government in general is eroded.
No, I just see no reason someone should beat their head against a wall when the answer is cheap and easy. If that's not for you, pound away. Perhaps your time isn't worth more than $5 an hour.
The reason is simple. Practically every distro is available in DVD iso format.
In my case, I've used both, but I do a number of different installs with different distros. One cheap drive and a collection of dirt cheap DVDs is a good answer.
They're using it to take down people anyway. Since they're willing to try fooling a judge in court, all bets are off.
It is absolutely not legal to ask under an NSL. Otherwise they can lie and make vague threats (the latter is a gray area) but there is only so far they can go. The NSL is over the line.
But anything that information leads to is fruit from a poison tree and so should not be usable to indict or convict. They are knowingly pulling the wool over a judge's eyes and that is illegal.
Don't we have enough criminals out there without giving some of them a government paycheck?
Given the history, generally the DOJ is happy with contorting the law into fascinating new shapes to claim something is legal for law enforcement when objective legal scholars say otherwise. So if even the DOJ can't get behind this use of a NSL, that suggests the FBI is way over the line.
As for criminals walking, I notice that over three years after the lab tech in Massachusetts got caught outright fabricating evidence, only a small percentage have walked. Perhaps the FBI likes their odds.
It is legal for them to ASK for data. It is NOT legal for them to DEMAND data under the cover of a National Security Letter.
They did the latter as documented by the now released NSL they gave to Yahoo.
Don't know and don't care. Someone reported that it didn't work, I suggested a cheap workaround to get the job done.
Yes, and now the editor suddenly needs specialized code in order for state saving to not be a disaster. Seems like it would be better to just send it SIGHUP.Best solution, run the editor in screen if the connection is at all likely to be broken in mid-session. Have the system honor the well known and long documented API.
The netcat example will fail. Remember, the other end of that connection didn't save state.
The AC said no H1-B, not no immigrants.
Sure, but if it's not working, cheaper isn't much good.
Get a USB DVD burner for under $30.
If the simple program is talking to a remote server, it can't necessarily save state at all. How would you save state for netcat, for example?
If a file might change while the process is saved off, havoc could result. What do you suppose happens if vi (or emacs, or whatever) gets saved off just as it is about to write out a changed file? Then the file changes, later the editor wakes up and overwrites the committed changes.
It's not at all hard. A and E don't need to care because they weren't attached to the dead process. They haven't lost state with their dependent or their dependency.
In case they aren't properly designed though, that's what SIGUSR1 and SIGUSR2 are for. Or any failed process causes a script to be called that tears it all down and re-starts it. Set the starter scripts to trap any abend.
You said:
Done really?
and since my only use of the word was in a one liner script, I concluded you referred to that.
It's the old laptop, more than adequate for video though. So it stays behind the TV. If I didn't just happen to have a spare laptop, I'd get a Pi or something like that.
I'm with you one the remotes. This isn't the '70s anymore, why haven't remotes gotten any better?
So far it's mostly the deniers whose pants are on fire.
Certainly, I did no such thing. It didn't help that Gnome drank the cool aid and started depending wherever it could. Personally I'm fully ready to dump gnome if that's what it takes.
If you're claiming I should be maintaining my own private distro, I'll just say give that a try and report back, I could use a laugh.
I solve that by plugging my laptop into the TV.
Perhaps for Samsung (I don't have one). Some vendors do not offer the choice. Even if firmware must be manually updated, sometimes you get sturk with either leaving features broken by server side changes or do the upgrade warts and all. Either way, you end up with less than you paid for.
The user doesn't necessarily get a choice. The vendors don't bother to produce updates that benefit the consumer, but they won't hesitate to produce and force one that benefits them. If a corporation could be sent to kindergarten, they would flunk.
Personally, I won't have a TV that requires an internet connection. I get a dumb TV and use my own hardware/software for anything over the network. A TV should have a tuner and a good set of aux inputs ONLY.
Grab the process via PTRACE, for example.
The reason checkpointing is typically done by the program itself is that there is sufficient complexity involved that it is a rather specialized operation. There is no generalized way to save a program's state (including system state and potentially, the world's state) such that it can be restored successfully. That is exactly why I rejected it as a solution.
Checkpointing *IS* saving state. I hope you now see that not only is there no process manager that saves state, no process manager CAN arbitrarily save state.
I have worked on systems such as bproc that narrowed the parameters down enough to *OFTEN* work, but there were always corner cases.
Obviously, C knows because it gets restarted after the crash. The ENOTCONN is the notifier for B and the new instance of C connecting to D is the notifier to D. How hard is that?
BTW, ":done" is clearly part of the do..done block associated with "while" in the script. The semicolons are the give away there.
If any further notifications are needed (they normally shouldn't be necessary in a good design), the script can fire them off.
But honestly, all of that is really just papering over bugs in C. Programs shouldn't crash.
Society is under no obligation to grant incorporation or any other form of limited liability. Even though it is apparently never enforced, incorporation requires that the incorporation be in the public interest. Anti-social behavior is the opposite.
That's the problem. This nastiness wasn't part of the deal. The TV they bought didn't do this. Samsung are altering the deal and telling people to pray they don't alter it further.
This is why I insisted on a dumb TV with a VGA input and no network connection last time.