Agreed. I've done this in the past and starting as close to the original analog telemetry stream as possible is essential. Even if the noise is so bad that analog filtering doesn't recover any new data in the preD, simply knowing where there is missing data and exactly how much can help tremendously in reconstructing the data. Their raw mpeg files don't provide any of that information.
Two days? TWO? We would submit our cards and then wait for the lesson THE NEXT WEEK to find out if the program had compiled. To be fair, it did encourage one to try be a very, very careful programmer. The rest of you are all whippersnappers by the way.
Same here. I tried TurboTax one year and it didn't save me any money, didn't really save me any time, and had annoying DRM. You have to research what you can deduct on your own anyway in advance anyway so you can preserve documentation throughout the year, and that is the time consuming part. So paying money just to have software fill out and submit the form doesn't seem worth it for me.
"Never attribute to malice that which can be explained by incompetence." -- Hanlon's Razor
Ok, seems like you're trying to do things the windows way, i.e. blocking outbound connections based which application is running. Things are not done that way on Linux. Outbound connections are open and most of us are fine with it.
The Window Firewall, the original BlackIce for Windows, and AVG as well, I believe, all fall in the category of Application Firewalls, as they base their actions with knowledge of the application holding the IP connection endpoint. IPtables is a Stateful Firewall, so named because it relies solely on the connection's state, without regard to the application at the sending or receiving end of the connection.
The Application Firewall link above actually does have some suggestions about how such things can be handled on Linux using utilities others have described. Mandatory Access Control tools such as SELinux and grsecurity can allow or deny access to resources (such as the network interface) to applications, but I don't believe they have fine-grained controls for conditional access based on IPs or ports.
None of these are as easy to use as AVG for Windows is.. (This could be the new definition of "understatement!") In fact, I would like to think I know Linux quite well, have used it as a desktop and server platform for years, have written patches for kernel modules, and can configure a solid IPtables firewall ruleset from scratch, but AppArmor and SELinux still scare me...
There's a link here describing how to mark packets based on an application's uid (user). This might be a basis for controlling permissions per app, but you're talking about a very complex IPtables ruleset. Definitely not for someone only two days into their Linux journey.
But if they *quit* their job, they must get a new visa, which means leaving the US and re-entering. That's why they're indentured servants. They can't voluntarily leave their job without getting a new visa.
This is exactly correct. Plus, H1B visa holders are tied to the company that issues the visa. If they leave the company, they must return to their home country. Tech companies like Facebook like to have such indentured servants.
H1B visas serve only to drive down wages for US employees. Additionally, they end up training foreign talent that are later kicked out of the country (after 3 or 6 years, depending upon whether the visa is renewed). They don't help the nation's interests, nor the public's interest. They serve only to increase the profit margins of the large firms.
Get rid of the H1B, and increase the green card slots available to foreign workers, especially the Indians. I've very pro-immigrant, but the H1B visa only provides for indentured servitude.
And it should be the law: If you use the word `paradigm' without knowing what the dictionary says it means, you go to jail. No exceptions. -- David Jones
