I will have to remember to use that tactic as a way to spoil a database in the event that it is compromised. If it would embarrass clients, make sure that any entry could have been falsified and provide obvious evidence that many were.
Bridge mode is definitely the way to go although that does not solve the problem of them blocking traffic. It also does not solve the problem of their modem/router not operating as a true bridge; it still maintains a state table of connections which is absurdly small but if you set the UDP and TCP timeouts to their minimum values, that may not be a problem.
This form factor is specifically designed to be difficult to stack things on or cram into a corner with no airflow
Doing this isn't a bad idea but I usually take it to mean that the design was marginal to begin with if stacking can cause overheating.
As far as integrated antennas, having used and gotten much better performance out of directional patch antennas like Ubiquiti uses, I shy away from access point hardware which is omnidirecitonal. And if your wifi antennas are installed at opposite corners of your house facing in, then external interference is not as big a problem.
At this point I do not trust any embedded network hardware as far as security or reliability. For a home router I use a 10 year old system with a BX motherboard which started out as a Celeron 300A to run FreeBSD and it has a higher up-time than any of the DSL or cable modems I have used and much better security since AT&T has the habit of resetting my U-Verse modem settings when they do an update leaving my network open.
The only time my PC based router has failed is when the ice machine on the floor above sprung a leak and water dripped into it. I had it replaced with another box in 15 minutes running the same image and cleaned it up and put it back into service within a day.
Neither Chromecast nor a specific router needs to deal with infinite combinations of hardware (and drivers) of varying quality.
It does not take unusual hardware to cause a problem.
I have not allowed automatic Windows updates since a couple of incidents (one of which was mine) where Windows destroyed itself and it was not because of unusual hardware; it was because Microsoft fucked up and as far as I know they have never fixed this.
Some Windows updates install during system shutdown so as not to interrupt the user which is fine until your UPS backed up system loses main power, the USP sends the shutdown signal to Windows, and Windows precedes to install 15+ minutes of updates allowing the UPS to lose power during the installation process. That only had to happen to me once to never again allow automatic updates on Windows or any other operating system.
Like with most things, there are pros and cons for this sort of thing. If you leave the automatic updates "OFF" by default, majority or users will not bother with updates on routers and when a vulnerability is discovered, crackers have a field day. By leaving them "ON" by default, but allowing concerned users to turn them off, perhaps you get to a reasonable medium.
On the Gripping hand, AT&T enforces automatic updates on my U-Verse router and when they do, they reset the configuration and leave the WiFi open. Further they used the enforced automatic updates to block traffic and features.
Having had a similarly bad experience with Windows automatic updates, I am firmly in the disable and review camp.
The problem for Bill, was that he built his OS bounded on two sides. Bottom was 0, and the top was hard bounded to 640k, because that is where they put the Video (IIRC) and Bios Memory. Had they put that memory next to 0, and freed up 384 to 1 MB, then we wouldn't have a lot of the problems we have today.
I think Bill thought that the computer would be designed for a short period, and replaced with a new kind. The problem was the new kind came, and it was still hard bounded by 640k limit (with some fancy hacking to get around it). Anyone running a memory manager at that time knows what a cluster it all was, as we couldn't use more than 640k.
Short sighted people make short sighted errors.
This had nothing to do with Bill or his operating system or even with the IBM PC design; it has to do with how the 8086 works.
The 8086 interrupt vector table starts at 00000h so that area has to be RAM if the system is going to be flexibly programmable. The 8086 reset vector is located at FFFF0h (16 bytes before the end of the 1MB address space) so that area has to be ROM.
Given the above, the most natural memory arrangement is to have a continuous block of RAM start at the beginning of the address space and have a ROM located at the end of address space with memory mapped I/O located toward the end of the address space before the ROM which is exactly what they ended up with.
If I had the option for desktop computers I would be buying ECC ram.
If you build your own, then ECC support is not difficult to come by although it is much easier and less expensive with AMD than with Intel who uses it as a market segmentation feature. Every one of my desktops going back 10+ years has had ECC RAM and the last three going back to the Celeron 300A still run.
For many loads however using a bipolar transistor is more economical than a MOSFET simply because of economics. Current density of a bipolar transistor is higher allowing less die area making them less expensive. Insulated gate bipolar transistors have the same advantage over MOSFETs.
This becomes more important at higher voltages where MOSFET die size scales by the square of the voltage but it still applies at low voltages.
I have not encountered this problem myself although I might not have noticed and I tend to be paranoid about interface circuits anyway. My guess is that the excessive reverse transfer capacitance of the MOSFET allows the high dV/dT from the inductive kickback to get into the microcontroller. This would be exasperated by a drive circuit intended for the "high impedance" input of the MOSFET compared to a bipolar transistor where the low impedance drive circuit would just absorb it.
Like people using ua741 opamps that are older than me. At least move into 1980 and use an LM358 or something. Same price or cheaper, and the input actually goes to one rail. Still very old junk, but significantly less so.
The 358 is not always a good replacement for the 741 although in most circuits it would not matter. It's input bias current is the opposite, it has no input offset voltage adjustment, and single operational amplifiers are more useful in circuits where the power supply is bootstrapped.
There are lots of superior replacements for the 741 but on a practical level, many circuits would not benefit.
Incidentally, I actually prefer the even older 301A which can do things that the 358/324 cannot . . . it has a common mode input range which includes the positive supply. Today that is no big deal as there are lots of operational amplifiers which that characteristic but in the past it was rare outside of some JFET designs.
JFETs are not inherently low current devices, it's just unusual for them to be made physically large enough to take high current / high power.
JFETs will always be low power devices compared to MOSFETs or bipolars because they have limited enhancement range do to the clamping of the gate to source voltage by the inherent gate to source diode. They did make higher power JFETs in the past but even then they were pretty low power.
TO-3 and TO-204 power MOSFETs are rare and expensive these days so it is best to avoid them in new designs. Neither Mouser nor Digi-key have any available. I have a bag filled with NOS IRF351s.
The TIP devices, being bipolar technology, are inherently less efficient than their modern cousins, which are mostly CMOS FET technology.
They are less efficient in most although not all hard switching applications but most power MOSFETs now are not suitable for linear applications.
Further, the older devices tend to be physically larger than modern equivalents, which is a natural consequence of the lower efficiency demanding more surface area to radiate waste heat.
And if your application calls for high power dissipation, the die size which controls the Tja becomes more important than the voltage and current rating and high efficiency MOSFETs lose their advantages.
I've had cases where I'm downloading a lot of stuff (either in the browser's download manager or something external like fedora's yum reposync) and foreground web browsing slows to a crawl.
I do not have this problem and there are at least two ways to solve it:
The uTP protocol includes monitoring of the connection latency and is suppose to throttle itself if latency becomes excessive. Maybe this is set wrong on your bittorrent client.
Using a traffic shaper will also fix this problem.
I disabled automatic updates because they managed to destroy a system. I do the updates manually.
During a power outage the UPS signaled the computer to shutdown like normal but then it started doing its automatic update thing because of the shutdown which lasted longer than the UPS could keep the computer running. The result was a destroyed Windows installation.
The last time Windows suspend didn't work reliably for me I was using Windows ME.
I have never had Windows suspend work reliably on any laptop or any of my desktops so it is one of the first things I completely disable along with automatic updates. I consider it one of the many broken features which has never worked correctly.
Back before the NSA and FBI implemented their current all encompassing digital surveillance plan, one of the considerations raised was that if it became known, then it would encourage opportunistic and ubiquitous encryption which they had been fighting for years and would have a dire effect on lawful surveillance. Well guess what? All of that has come to pass and ubiquitous and opportunistic encryption of lawful traffic and storage is starting to happen leading to the current cries from law enforcement about not being able to lawfully obtain plaintext.
They brought this on themselves by disregarding the 4th amendment, denying due process, and repeatedly lying about it to everybody including Congress and the courts who share the blame for authorizing it and not following up.
My ears of deaf to everything they say because none the branches of government can be trusted.
A number of years ago Orange County had a problem with birds congregating and pooping in their open reservoirs which was causing water quality problems including things like worms coming out of the faucets. People did not like that very much so they were going to cover the reservoirs until Lemon Heights which overlooked the reservoirs sued to stop them because they liked the view of the artificial lake and covering it would reduce their property values.
We have a recent history of "extraordinary rendition": ie. kidnapping people we don't like and sending them off to third-world crapholes to be tortured and murdered by the CIA so it doesn't technically happen on our own soil.
I would have wrote "continuing history of extraordinary rendition and torture" instead of recent history.
So Sweden should have had no problems guaranteeing Assange that they would not extradite him to the US but of course they would not.
Given how the US has persecuted its war on terror, I consider Assange properly paranoid over the issue. I am sure that either the US and Sweden had a non-extradition extradition planned for Assange or the US was prepared to act without Sweden which of course could still be the case. Assange will just vanish at some point into one of our friendly foreign interrogation centers.
Do people have troubles making phone calls nowadays? Is the US telephone network so fragile?
I forget what it is called but some carriers deliberately misroute calls when they will lose money on them resulting in the caller getting an unending number of fast busy signals and other errors. For instance I cannot reach any government numbers located in California from Missouri.
In addition, sound quality has gotten worse. In many cases it is so bad that I do not bother to continue the call. Part of this is do to the low bit rate digital compression and it is *not* only an issue with wireless.
So ya, at this point I consider voice calls in the US unusable and less reliable an email.
Slashdot Mirror
Since the deaths did not occur *during* the commission of the felony and the act of hacking or releasing the data is not violent, I doubt it:
https://en.wikipedia.org/wiki/...
I will have to remember to use that tactic as a way to spoil a database in the event that it is compromised. If it would embarrass clients, make sure that any entry could have been falsified and provide obvious evidence that many were.
Bridge mode is definitely the way to go although that does not solve the problem of them blocking traffic. It also does not solve the problem of their modem/router not operating as a true bridge; it still maintains a state table of connections which is absurdly small but if you set the UDP and TCP timeouts to their minimum values, that may not be a problem.
Doing this isn't a bad idea but I usually take it to mean that the design was marginal to begin with if stacking can cause overheating.
As far as integrated antennas, having used and gotten much better performance out of directional patch antennas like Ubiquiti uses, I shy away from access point hardware which is omnidirecitonal. And if your wifi antennas are installed at opposite corners of your house facing in, then external interference is not as big a problem.
At this point I do not trust any embedded network hardware as far as security or reliability. For a home router I use a 10 year old system with a BX motherboard which started out as a Celeron 300A to run FreeBSD and it has a higher up-time than any of the DSL or cable modems I have used and much better security since AT&T has the habit of resetting my U-Verse modem settings when they do an update leaving my network open.
The only time my PC based router has failed is when the ice machine on the floor above sprung a leak and water dripped into it. I had it replaced with another box in 15 minutes running the same image and cleaned it up and put it back into service within a day.
It does not take unusual hardware to cause a problem.
I have not allowed automatic Windows updates since a couple of incidents (one of which was mine) where Windows destroyed itself and it was not because of unusual hardware; it was because Microsoft fucked up and as far as I know they have never fixed this.
Some Windows updates install during system shutdown so as not to interrupt the user which is fine until your UPS backed up system loses main power, the USP sends the shutdown signal to Windows, and Windows precedes to install 15+ minutes of updates allowing the UPS to lose power during the installation process. That only had to happen to me once to never again allow automatic updates on Windows or any other operating system.
On the Gripping hand, AT&T enforces automatic updates on my U-Verse router and when they do, they reset the configuration and leave the WiFi open. Further they used the enforced automatic updates to block traffic and features.
Having had a similarly bad experience with Windows automatic updates, I am firmly in the disable and review camp.
This had nothing to do with Bill or his operating system or even with the IBM PC design; it has to do with how the 8086 works.
The 8086 interrupt vector table starts at 00000h so that area has to be RAM if the system is going to be flexibly programmable. The 8086 reset vector is located at FFFF0h (16 bytes before the end of the 1MB address space) so that area has to be ROM.
Given the above, the most natural memory arrangement is to have a continuous block of RAM start at the beginning of the address space and have a ROM located at the end of address space with memory mapped I/O located toward the end of the address space before the ROM which is exactly what they ended up with.
Or if you build your ownn ECC support is not hard to come by.
For AMD the additional cost is just that of the RAM. For Intel the motherboard and processor will be 2 to 3 times more expensive.
If you build your own, then ECC support is not difficult to come by although it is much easier and less expensive with AMD than with Intel who uses it as a market segmentation feature. Every one of my desktops going back 10+ years has had ECC RAM and the last three going back to the Celeron 300A still run.
For many loads however using a bipolar transistor is more economical than a MOSFET simply because of economics. Current density of a bipolar transistor is higher allowing less die area making them less expensive. Insulated gate bipolar transistors have the same advantage over MOSFETs.
This becomes more important at higher voltages where MOSFET die size scales by the square of the voltage but it still applies at low voltages.
I have not encountered this problem myself although I might not have noticed and I tend to be paranoid about interface circuits anyway. My guess is that the excessive reverse transfer capacitance of the MOSFET allows the high dV/dT from the inductive kickback to get into the microcontroller. This would be exasperated by a drive circuit intended for the "high impedance" input of the MOSFET compared to a bipolar transistor where the low impedance drive circuit would just absorb it.
The 358 is not always a good replacement for the 741 although in most circuits it would not matter. It's input bias current is the opposite, it has no input offset voltage adjustment, and single operational amplifiers are more useful in circuits where the power supply is bootstrapped.
There are lots of superior replacements for the 741 but on a practical level, many circuits would not benefit.
Incidentally, I actually prefer the even older 301A which can do things that the 358/324 cannot . . . it has a common mode input range which includes the positive supply. Today that is no big deal as there are lots of operational amplifiers which that characteristic but in the past it was rare outside of some JFET designs.
JFETs will always be low power devices compared to MOSFETs or bipolars because they have limited enhancement range do to the clamping of the gate to source voltage by the inherent gate to source diode. They did make higher power JFETs in the past but even then they were pretty low power.
TO-3 and TO-204 power MOSFETs are rare and expensive these days so it is best to avoid them in new designs. Neither Mouser nor Digi-key have any available. I have a bag filled with NOS IRF351s.
They are less efficient in most although not all hard switching applications but most power MOSFETs now are not suitable for linear applications.
And if your application calls for high power dissipation, the die size which controls the Tja becomes more important than the voltage and current rating and high efficiency MOSFETs lose their advantages.
I do not have this problem and there are at least two ways to solve it:
The uTP protocol includes monitoring of the connection latency and is suppose to throttle itself if latency becomes excessive. Maybe this is set wrong on your bittorrent client.
Using a traffic shaper will also fix this problem.
I disabled automatic updates because they managed to destroy a system. I do the updates manually.
During a power outage the UPS signaled the computer to shutdown like normal but then it started doing its automatic update thing because of the shutdown which lasted longer than the UPS could keep the computer running. The result was a destroyed Windows installation.
So no, I no long use automatic updates.
I have never had Windows suspend work reliably on any laptop or any of my desktops so it is one of the first things I completely disable along with automatic updates. I consider it one of the many broken features which has never worked correctly.
Back before the NSA and FBI implemented their current all encompassing digital surveillance plan, one of the considerations raised was that if it became known, then it would encourage opportunistic and ubiquitous encryption which they had been fighting for years and would have a dire effect on lawful surveillance. Well guess what? All of that has come to pass and ubiquitous and opportunistic encryption of lawful traffic and storage is starting to happen leading to the current cries from law enforcement about not being able to lawfully obtain plaintext.
They brought this on themselves by disregarding the 4th amendment, denying due process, and repeatedly lying about it to everybody including Congress and the courts who share the blame for authorizing it and not following up.
My ears of deaf to everything they say because none the branches of government can be trusted.
Yes, or worse.
https://www.eff.org/deeplinks/...
A number of years ago Orange County had a problem with birds congregating and pooping in their open reservoirs which was causing water quality problems including things like worms coming out of the faucets. People did not like that very much so they were going to cover the reservoirs until Lemon Heights which overlooked the reservoirs sued to stop them because they liked the view of the artificial lake and covering it would reduce their property values.
Maybe covering the reservoirs was not an option.
I would have wrote "continuing history of extraordinary rendition and torture" instead of recent history.
So Sweden should have had no problems guaranteeing Assange that they would not extradite him to the US but of course they would not.
Given how the US has persecuted its war on terror, I consider Assange properly paranoid over the issue. I am sure that either the US and Sweden had a non-extradition extradition planned for Assange or the US was prepared to act without Sweden which of course could still be the case. Assange will just vanish at some point into one of our friendly foreign interrogation centers.
https://en.wikipedia.org/wiki/...
I forget what it is called but some carriers deliberately misroute calls when they will lose money on them resulting in the caller getting an unending number of fast busy signals and other errors. For instance I cannot reach any government numbers located in California from Missouri.
In addition, sound quality has gotten worse. In many cases it is so bad that I do not bother to continue the call. Part of this is do to the low bit rate digital compression and it is *not* only an issue with wireless.
So ya, at this point I consider voice calls in the US unusable and less reliable an email.