Wireless is certainly a bottleneck for me, but i generate a lot of LAN traffic... That's why i wired my house with cat6a, so that everything which can practically be wired, is wired. Even my laptop when i'm sat at my desk is wired, although it will switch to wireless when i disconnect it and move it.
The problem is that wireless spectrum is shared with close neighbors, and lots of people use wireless for everything because cabling the house is too inconvenient or expensive. I have a bunch of devices which support wireless (tv, audio receivers, set top boxes etc) but otherwise never move anywhere and some of them are quite bandwidth heavy (e.g. streaming video to the stb), having such devices on wireless reduces the available bandwidth not only for your own wireless devices but also your neighbors.
And that's the effect of competition... They actually have to compete in the mobile market, while on desktops they take their customer base for granted.
People frequently tailgate instead of moving into the next lane to pass, they frequently tailgate people who are in the outside lane but due to other traffic conditions cannot pull over. If i'm in a passing lane i will move out of it once i have completed passing the slower vehicles, and it will not be possible to pull over as there will be other vehicles on the inside. Tailgating such a vehicle is stupid and dangerous, there is clearly nowhere it can go so wait for it to complete what its doing. If someone is sitting in the outside lane for no reason then it's still stupid to tailgate them as they clearly aren't paying attention to the road properly, and could easily be surprised causing them to brake suddenly.
I will leave the passing lane(s) when it is safe to do so, sitting close behind me is dangerous and it can't make me move over more quickly because there's nowhere to go, at most it will cause me to slow down in order to reduce the impact of a crash and increase the distance to the vehicle in front so i wouldn't need to brake so hard if something happened.
Something else i find extremely annoying, when you are following the rules and pulling in to the inside lane when not overtaking, you approach a slower vehicle ahead and want to move out, but there is another vehicle sitting alongside you or passing very slowly in the middle lane and the outside lane is clear. They should move out into the outside lane so that you can move into the middle lane, but they usually don't so you are boxed in and forced to slow down.
That's why they tailgate, to put pressure on you to move out of their way... If you let them past, you are encouraging that behaviour by demonstrating that it works.
My point about source compatibility was to emphasize why binary backwards compatibility is a rarely used feature.
Binary compatibility on linux is actually much better than windows too, it's just required far less often and thus not enabled by default in most distros. Providing you have the appropriate libs (and these libs often wont be installed by default because they waste space if not required), even very early linux binaries will still run on the latest kernels. Windows does include backwards compatibility libs, and its more common for applications to come bundled with third party libs rather than using the system provided ones, which is horribly inefficient.
The default linux approach of system wide libraries with only the current versions installed is far more efficient, but this approach only works if all of your applications are compiled and linked against current library versions. This approach is practical with linux because virtually all software comes with sourcecode, it is not practical if you are going to be running old precompiled software. As always, linux gives you the choice, and the default option is superior. Very few linux users ever have the need to run old precompiled software.
Not really, it's enough to know that a user from your line retrieved at least one file from squidporn.jp, but you cant tell if they actually visited the site or visited another site which had an advertising banner or included script.
If the pin is only kept on a bank server then sure, but if the pin is on a mobile handset which you've stolen then you do have a local copy of the password data.
You can protect against *online* attacks in that way as it can keep track of how many attempts have been made, but if you find a way to perform an offline attack then the 4 digit pin becomes very weak.
In the UK, there is already the right to have various other services (power, water, phone) at the same price anywhere in the country, so wether you live in london or the highlands of scotland you still get these services. All they're changing, is "phoneline" now means that you must be able to get 10mbps internet access, ie they're just raising the minimum standard of what's already required.
Currently if you want a phoneline in a remote location, BT must install it for you and charge no more than they would for someone in a city, and that phoneline must be capable of carrying voice calls. This will result in an extremely long piece of copper that's not capable of handling ADSL at all.
Economies of scale... A national healthcare system has a lot more buying power than a small independent hospital, and drug companies cannot afford to lose such large customers.
As it was leased to the russians, they would be responsible for its maintenance during the lease period. Even the most reliable of aircraft require regular maintenance to keep them airworthy, and the russians could have cut corners there. Of course this is all speculation, we don't yet know what actually happened.
A list of domains is also fairly useless, for instance advertising banners often reside on different domains to the site displaying the ads so the logs will show that you visited the domain on which the banner is hosted.
I see these advisories too, but it's very hard to compare windows to linux by number of vulnerabilities reported...
Linux (and most application software for it) is developed in the open, so issues discovered during development are publicised, microsoft dont publish any vulnerabilities discovered during internal development. A typical linux distribution supplies far more software than microsoft do, there are hundreds of applications any of which could have vulnerabilities discovered. The linux package managers typically cover a huge range of software like this, and can update it centrally. Linux is more modular so although all this software is available, almost all of it can be removed if you dont want it. There are multiple linux distros, so a single vulnerability is often covered by multiple distro announcements. Most software is cross platform, but vulnerabilities in something like apache will only be announced by linux distros, microsoft wont announce it even if the same issue is exploitable when running apache on windows. The linux kernel includes drivers, whereas windows generally does not - vulnerabilities in drivers will usually be counted against linux but not windows.
Based on my own experiences, my linux servers which have had unnecessary software removed very rarely require updates, in most cases i dont need to update all of them at once and usually dont need to reboot (i dont use ksplice or similar). windows on the other hand almost always requires updating and rebooting at least once a month, even a core install.
Linux has very good backwards compatibility as peppepz pointed out... The fact that most distros don't include the necessary ancient libraries is because this backwards compatibility is very rarely needed, so those using it are a very small niche who still have the option to install the libs.
The vast majority of linux software comes with sourcecode, and almost all of it has already been compiled for 64bit systems as well as other architectures like arm or mips. It's extremely rare that you would need to be using an old linux binary, and even if you are running old software there is usually nothing stopping you from recompiling it assuming someone else hasn't already done so. I regularly run several applications which date from as early as 1994, recompiled for a 64bit host. They compile and run fine on 64bit, as 64bit hardware (alpha/mips) was available in 1994 anyway.
Any software that doesn't compile and run cleanly on 64bit hosts is usually fairly easily fixed and is very rare as the unix world has had access to 64bit cpus for a long time now.
I run several 64bit linux servers with custom kernels, they have support for 32bit (and a.out) binaries turned off because i have absolutely no use for this feature.
By contrast, most windows software comes only as 32bit (or 16) binaries and cannot be recompiled or easily modified. To get a 64bit binary you are relying on the goodwill (and continued existence) of the original vendor, and quite often even if a 64bit version is available it will only be the more recent versions which is no good if you're stuck with an old version for whatever reason.
Backwards compatibility is essential for windows, if you're going to ditch compatibility you might as well just switch to linux anyway. Backwards compatibility is a tiny niche for linux, hardly anyone ever uses it.
Existing organisations in developed countries have years of IT failure and legacy cruft to deal with... It's very difficult to make significant improvements because replacing existing systems is expensive, time consuming and often meets resistance. People dislike change, and most people are simply unwilling to challenge the status quo and/or don't understand the improvements that change could bring. IT in most places is horrendously insecure, buggy and unreliable. Things don't work well, and businesses end up having to adapt to how their software is designed rather than the other way round. Data is locked in to proprietary formats, and companies are stuck on the upgrade treadmill or faced with systems that suffer from major problems but cannot be replaced.
However what is even more disturbing, is that new companies and developing countries want to copy what big organisations in developed countries are doing... They absolutely refuse to learn from our mistakes, and instead are trying to repeat them!
Also by the time you can buy a game on sale, it will already have gotten as many updates as it's going to, so it will either be bugfixed and playable or you'll know that its buggy and never going to get fixed so you can make an informed buying choice.
Aside from there being less bloat on a console, the environment is also more predictable... You don't need to deal with crap running in the background, don't need to worry about different hardware and drivers etc... Consoles are much more efficient, so requiring 33% less ram is not unusual.
The problem is the "updaters", and these only exist because windows doesn't provide a centralised update system for applications to hook into.
You end up with a load of background updater processes wasting resources at all times, so they end up getting turned off. And because the update process happens in userland, unprivileged users (ie most corporate installs) cannot apply the updates or run the updater. Most corporate deployments won't update these applications centrally because doing so is a painful process.
My whole point is summed up in your quote "anyone else that he thought he could get away with killing"...
If there was no existing anti semitic feeling, he couldn't have got away with killing jews and would have needed to pick another target. Jews had already become sufficiently unpopular that a significant proportion of the population were willing to tolerate or even support hitler.
He did use the jews as workers, they were forced to do slave labor in concentration camps.
Putting them on the front line likely wouldn't have worked out very well for the nazi cause, although it would have given them more soldiers and got a few jews killed it's likely that many more would have used the opportunity to join the enemy and fight back against the nazis.
Make sure you use the host as a tunnel rather than a jump off point (ie you dont login to an interactive shell and then start a new instance of ssh to connect to internal boxes)... Otherwise if someone owns the jump box they can quickly get everything.
Slashdot Mirror
Wireless is certainly a bottleneck for me, but i generate a lot of LAN traffic...
That's why i wired my house with cat6a, so that everything which can practically be wired, is wired. Even my laptop when i'm sat at my desk is wired, although it will switch to wireless when i disconnect it and move it.
The problem is that wireless spectrum is shared with close neighbors, and lots of people use wireless for everything because cabling the house is too inconvenient or expensive. I have a bunch of devices which support wireless (tv, audio receivers, set top boxes etc) but otherwise never move anywhere and some of them are quite bandwidth heavy (e.g. streaming video to the stb), having such devices on wireless reduces the available bandwidth not only for your own wireless devices but also your neighbors.
And that's the effect of competition...
They actually have to compete in the mobile market, while on desktops they take their customer base for granted.
You can drive wearing a helmet with a visor which obscured visibility of your face, and many people (like racing drivers) do just that...
People frequently tailgate instead of moving into the next lane to pass, they frequently tailgate people who are in the outside lane but due to other traffic conditions cannot pull over. If i'm in a passing lane i will move out of it once i have completed passing the slower vehicles, and it will not be possible to pull over as there will be other vehicles on the inside.
Tailgating such a vehicle is stupid and dangerous, there is clearly nowhere it can go so wait for it to complete what its doing. If someone is sitting in the outside lane for no reason then it's still stupid to tailgate them as they clearly aren't paying attention to the road properly, and could easily be surprised causing them to brake suddenly.
I will leave the passing lane(s) when it is safe to do so, sitting close behind me is dangerous and it can't make me move over more quickly because there's nowhere to go, at most it will cause me to slow down in order to reduce the impact of a crash and increase the distance to the vehicle in front so i wouldn't need to brake so hard if something happened.
Something else i find extremely annoying, when you are following the rules and pulling in to the inside lane when not overtaking, you approach a slower vehicle ahead and want to move out, but there is another vehicle sitting alongside you or passing very slowly in the middle lane and the outside lane is clear. They should move out into the outside lane so that you can move into the middle lane, but they usually don't so you are boxed in and forced to slow down.
That's why they tailgate, to put pressure on you to move out of their way... If you let them past, you are encouraging that behaviour by demonstrating that it works.
My point about source compatibility was to emphasize why binary backwards compatibility is a rarely used feature.
Binary compatibility on linux is actually much better than windows too, it's just required far less often and thus not enabled by default in most distros. Providing you have the appropriate libs (and these libs often wont be installed by default because they waste space if not required), even very early linux binaries will still run on the latest kernels.
Windows does include backwards compatibility libs, and its more common for applications to come bundled with third party libs rather than using the system provided ones, which is horribly inefficient.
The default linux approach of system wide libraries with only the current versions installed is far more efficient, but this approach only works if all of your applications are compiled and linked against current library versions.
This approach is practical with linux because virtually all software comes with sourcecode, it is not practical if you are going to be running old precompiled software.
As always, linux gives you the choice, and the default option is superior. Very few linux users ever have the need to run old precompiled software.
Not really, it's enough to know that a user from your line retrieved at least one file from squidporn.jp, but you cant tell if they actually visited the site or visited another site which had an advertising banner or included script.
If the pin is only kept on a bank server then sure, but if the pin is on a mobile handset which you've stolen then you do have a local copy of the password data.
You can protect against *online* attacks in that way as it can keep track of how many attempts have been made, but if you find a way to perform an offline attack then the 4 digit pin becomes very weak.
No, that's 57.4% where they don't know what the site is using. It could be none, or it could just be something they don't recognise.
In the UK, there is already the right to have various other services (power, water, phone) at the same price anywhere in the country, so wether you live in london or the highlands of scotland you still get these services.
All they're changing, is "phoneline" now means that you must be able to get 10mbps internet access, ie they're just raising the minimum standard of what's already required.
Currently if you want a phoneline in a remote location, BT must install it for you and charge no more than they would for someone in a city, and that phoneline must be capable of carrying voice calls. This will result in an extremely long piece of copper that's not capable of handling ADSL at all.
Economies of scale...
A national healthcare system has a lot more buying power than a small independent hospital, and drug companies cannot afford to lose such large customers.
As it was leased to the russians, they would be responsible for its maintenance during the lease period. Even the most reliable of aircraft require regular maintenance to keep them airworthy, and the russians could have cut corners there.
Of course this is all speculation, we don't yet know what actually happened.
A list of domains is also fairly useless, for instance advertising banners often reside on different domains to the site displaying the ads so the logs will show that you visited the domain on which the banner is hosted.
I see these advisories too, but it's very hard to compare windows to linux by number of vulnerabilities reported...
Linux (and most application software for it) is developed in the open, so issues discovered during development are publicised, microsoft dont publish any vulnerabilities discovered during internal development.
A typical linux distribution supplies far more software than microsoft do, there are hundreds of applications any of which could have vulnerabilities discovered. The linux package managers typically cover a huge range of software like this, and can update it centrally.
Linux is more modular so although all this software is available, almost all of it can be removed if you dont want it.
There are multiple linux distros, so a single vulnerability is often covered by multiple distro announcements.
Most software is cross platform, but vulnerabilities in something like apache will only be announced by linux distros, microsoft wont announce it even if the same issue is exploitable when running apache on windows.
The linux kernel includes drivers, whereas windows generally does not - vulnerabilities in drivers will usually be counted against linux but not windows.
Based on my own experiences, my linux servers which have had unnecessary software removed very rarely require updates, in most cases i dont need to update all of them at once and usually dont need to reboot (i dont use ksplice or similar). windows on the other hand almost always requires updating and rebooting at least once a month, even a core install.
Linux has very good backwards compatibility as peppepz pointed out... The fact that most distros don't include the necessary ancient libraries is because this backwards compatibility is very rarely needed, so those using it are a very small niche who still have the option to install the libs.
The vast majority of linux software comes with sourcecode, and almost all of it has already been compiled for 64bit systems as well as other architectures like arm or mips. It's extremely rare that you would need to be using an old linux binary, and even if you are running old software there is usually nothing stopping you from recompiling it assuming someone else hasn't already done so. I regularly run several applications which date from as early as 1994, recompiled for a 64bit host. They compile and run fine on 64bit, as 64bit hardware (alpha/mips) was available in 1994 anyway.
Any software that doesn't compile and run cleanly on 64bit hosts is usually fairly easily fixed and is very rare as the unix world has had access to 64bit cpus for a long time now.
I run several 64bit linux servers with custom kernels, they have support for 32bit (and a.out) binaries turned off because i have absolutely no use for this feature.
By contrast, most windows software comes only as 32bit (or 16) binaries and cannot be recompiled or easily modified. To get a 64bit binary you are relying on the goodwill (and continued existence) of the original vendor, and quite often even if a 64bit version is available it will only be the more recent versions which is no good if you're stuck with an old version for whatever reason.
Backwards compatibility is essential for windows, if you're going to ditch compatibility you might as well just switch to linux anyway.
Backwards compatibility is a tiny niche for linux, hardly anyone ever uses it.
Existing organisations in developed countries have years of IT failure and legacy cruft to deal with... It's very difficult to make significant improvements because replacing existing systems is expensive, time consuming and often meets resistance. People dislike change, and most people are simply unwilling to challenge the status quo and/or don't understand the improvements that change could bring.
IT in most places is horrendously insecure, buggy and unreliable. Things don't work well, and businesses end up having to adapt to how their software is designed rather than the other way round. Data is locked in to proprietary formats, and companies are stuck on the upgrade treadmill or faced with systems that suffer from major problems but cannot be replaced.
However what is even more disturbing, is that new companies and developing countries want to copy what big organisations in developed countries are doing... They absolutely refuse to learn from our mistakes, and instead are trying to repeat them!
Also by the time you can buy a game on sale, it will already have gotten as many updates as it's going to, so it will either be bugfixed and playable or you'll know that its buggy and never going to get fixed so you can make an informed buying choice.
Aside from there being less bloat on a console, the environment is also more predictable... You don't need to deal with crap running in the background, don't need to worry about different hardware and drivers etc... Consoles are much more efficient, so requiring 33% less ram is not unusual.
Doesn't work if you're running the applications as an unprivileged user...
The problem is the "updaters", and these only exist because windows doesn't provide a centralised update system for applications to hook into.
You end up with a load of background updater processes wasting resources at all times, so they end up getting turned off.
And because the update process happens in userland, unprivileged users (ie most corporate installs) cannot apply the updates or run the updater.
Most corporate deployments won't update these applications centrally because doing so is a painful process.
My whole point is summed up in your quote "anyone else that he thought he could get away with killing"...
If there was no existing anti semitic feeling, he couldn't have got away with killing jews and would have needed to pick another target. Jews had already become sufficiently unpopular that a significant proportion of the population were willing to tolerate or even support hitler.
He did use the jews as workers, they were forced to do slave labor in concentration camps.
Putting them on the front line likely wouldn't have worked out very well for the nazi cause, although it would have given them more soldiers and got a few jews killed it's likely that many more would have used the opportunity to join the enemy and fight back against the nazis.
Make sure you use the host as a tunnel rather than a jump off point (ie you dont login to an interactive shell and then start a new instance of ssh to connect to internal boxes)... Otherwise if someone owns the jump box they can quickly get everything.
And blackhats frequently do have illegal access to closed source code, putting whitehats (and every other user) at a significant disadvantage.