How do you expect the keyboard is attached? USB. I've actually seen this, in person. A machine with sealed USB ports... and a USB keyboard and mouse. Really. What was IT thinking?
I bet the IT guy who did the job was a contractor. 'Uh yeah, here's a work order to seal up all the open USB ports.' "What about the keyboard?" "Doesn't say. Don't ask questions: its 20 hours of easy work at $60/hr."
If there are super specific timing requirements then invent a new standard with the commands you need. Then put a little microprocessor on the serial port end in charge of waiting for some particular signal and responding in precisely 23 milliseconds. Or whatever.
Well, if I was really into industrial espionage I might do something like bring a USB stick loaded with my zipper program, but instead of storage set to look like a keyboard. Plug it in, open Notepad and have it type the executable out into a file.
I've noticed that a lot of places disable USB storage but don't disable file execution from writable directories.
Sounds like the real answer to this problem is an improved USB to serial dongle. If this is a serious problem for electronics engineers, they are the perfect people to fix it. Whatever the problem with the USB to serial interface is, fix it. Then sell your improved serial port adapter for $100. Profit!
Windows 8 doesn't slow anything down. Check some benchmarks. It is faster than XP in most things. Here's one from a casual Google: http://itnews2day.com/2013/02/...
Windows XP is 32-bit only. Windows XP does not like hyperthreading or quad core CPUs. XP doesn't perform well on high bandwidth WAN connections. Its old SMB file transfer speeds are atrocious on gigabit LANs. It doesn't allow threaded GPU accesses and only supports old DirectX versions. It doesn't understand Advanced Format hard drives or SSDs. USB 3 on XP is buggy as hell. (in my experience)
If you installed a super modern GPU with 3 GB video RAM on XP, it would fall over and die because it has to map those 3 GB into 4 GB of space.
So, in at least this case, the OS didn't slow down. And without it new hardware wouldn't work at all.
Of course you have rights. So does your employer. And using your employer's network gives your employer the right to see what is traveling over his network.
They shouldn't. A simple second level of encryption such as an encrypted ZIP file defeats any automatic scanning for confidential keywords or anything similar.
Eh. Except that a blue screen or if you have to do a forced power-off will lose data and require a chkdsk run. I ran my desktop that way for a little while (with a UPS) but it had problems.
What a racist term. As if it is white people that keep an area valuable and crime free.
It's actually middle class and upper class flight, as well-off black, asian and hispanic people don't want to live in a blighted crime-ridden area either.
While it is an interesting technology with cool potential, a lot of folks don't want to be constantly filmed by Google Glass wearers for privacy issues. Like, the thought that all that Google Glass data will belong to the NSA on a whim of a secret court judge. Google doesn't give a rat's ass about people's privacy. They just want to sell their glasses, and they'll do it. And it's their right to do so, but don't expect people to love them for it.
People are in general, morons. Worried about Google Glass? People can be recording video from a cell phone in a pocket RIGHT NOW. I walked around with mine recording for 3.5 hours just to see what it was like. (Boring and bounced worse than the Blair Witch video.) People have dash cams in their cars. People have their houses and offices wired with security cameras that do motion detection and upload 1080p high-def video to the cloud.
Every store you walk into, every car you walk in front of, anybody holding a cell phone...
If you aren't alone inside a building that you control, you have no privacy and your face can end up on Youtube at any moment. Get over it.
Directly providing the power to vaporize a person is not the elegant way to do it. The correct, elegant mad scientist method is to use the power contained in the vaporized mass to power the vaporization.
Consider if you develop a means to "program" a plasma such that it generates a contracting magnetic field that causes fusion inside the vaporizing object and then absorbs some of the energy from this fusion reaction to power itself.
Now you're talking! Now you've got an effect that can vaporize any object provided you can provide the initial energy requirement.
There could be variants on this. Perhaps you've got an effect that flips matter into antimatter and absorbs some of the released energy to continue the effect.
If this is an expanding effect instead of a collapsing effect you've got a world killer like the weapons in Ender's Game.
Except that on a LAN FTP is almost the only protocol I can rely on to get high speed data transfers. SFTP blocks at about 30 MB/s when FTP can easily get 90.
If the Linux distros would be reasonable and enable the "none" crypto on SSH it would be a good thing. If I explicitly ask for no crypto then why are they making it hard for me to get what I want?
Yes, I know I can recompile OpenSSH for "none" crypto but it is easier to set up FTP, or even use tar and netcat.
What workarounds? Even if I install the original Windows 7 with no updates on top of it, ACPI works flawlessly on most machines, both old and brand new (which didn't even exist when Win7 was released).
You will sometimes see motherboard driver files for Windows which are simply ugly hacks to fix things without doing a BIOS update by hot-patching the board's ACPI, or overriding some Windows default so it works properly with the buggy board.
The right thing to do would be to issue a BIOS update or recall the board. But no, as long as they can hack in a software fix for Windows they go ahead and ship it.
The main reason is so that your company is equally vulnerable to the ridiculous patent system.
Just being in business using computers and the Internet and writing software opens up your company to hundreds of potential patents. Most of which are OBVIOUS! Really.
Another reason to be a producer is something that every inventor knows. Coming up with an idea is 10% of the effort. Actually making it work is much more difficult and 90% of the work. Sitting around and coming up with wild ideas that might be possible and writing patents on them and then waiting for someone else to do the 90% work before suing them is a very bad taste for the people who really did the work.
"Rocket science is easy. Rocket engineering is hard."
You know, to someone just reading the law your argument seems like the only reasonable result. And I agree with you.
But the Supreme Court doesn't. Oh no. A while back they decided that Interstate Commerce comes into effect if what you do in your state might somehow affect people in other states. Like by reducing the demand for the wheat in other states by growing too much wheat in your state and selling it, in your state.
Yup. Perfectly ludicrus. But that's the law for you.
I don't think it affects the unrecoverable read error rate. But patrol-scrub does find those unrecoverable read errors as it goes and rewrites the block. If you don't scrub then those read errors will just invisibly accumulate over time.
So during a RAID5 rebuild you'd be limited to any read errors that occurred during that last week. Hopefully.
I do think that RAID6 or other systems that allow 2 disks to fail are more reliable.
You should be scrubbing your RAID at least once a week. That will detect and fix most of the creeping errors that would have prevented a successful rebuild.
Yes you lose IOPS during the scrub but if you didn't care about data correctness you'd be using RAID0.
From what I've read in the last few months, the Linux kernel and glibc will both be adding transaction lock support. The performance benefits are pretty nice even when limited to backwards compatibility with existing lock methods.
Also, libraries like Intel's (of course) TBB will add support.
But all of that will be done with feature detection and fall back to using existing code.
It's like saying that nobody codes for MMX, SSE, Altivec or 3DNow. Or that nobody uses a particular Nvidia OpenGL extension only available on the newest cards. Yes, if it gains that extra 15% speed boost they will code for it.
It is super-easy if the contents of that wallet were created by a credit card purchase and the transfer from a Bitcoin exchange wallet. The exchange then has the identity of the credit card holder linked to the wallet.
Slashdot Mirror
How do you expect the keyboard is attached? USB. I've actually seen this, in person. A machine with sealed USB ports ... and a USB keyboard and mouse. Really. What was IT thinking?
I bet the IT guy who did the job was a contractor. 'Uh yeah, here's a work order to seal up all the open USB ports.' "What about the keyboard?" "Doesn't say. Don't ask questions: its 20 hours of easy work at $60/hr."
No the problem is in the hardware.
If there are super specific timing requirements then invent a new standard with the commands you need. Then put a little microprocessor on the serial port end in charge of waiting for some particular signal and responding in precisely 23 milliseconds. Or whatever.
Mine never has.
Well, if I was really into industrial espionage I might do something like bring a USB stick loaded with my zipper program, but instead of storage set to look like a keyboard. Plug it in, open Notepad and have it type the executable out into a file.
I've noticed that a lot of places disable USB storage but don't disable file execution from writable directories.
Sounds like the real answer to this problem is an improved USB to serial dongle. If this is a serious problem for electronics engineers, they are the perfect people to fix it. Whatever the problem with the USB to serial interface is, fix it. Then sell your improved serial port adapter for $100. Profit!
Windows 8 doesn't slow anything down. Check some benchmarks. It is faster than XP in most things. Here's one from a casual Google: http://itnews2day.com/2013/02/...
Windows XP is 32-bit only. Windows XP does not like hyperthreading or quad core CPUs. XP doesn't perform well on high bandwidth WAN connections. Its old SMB file transfer speeds are atrocious on gigabit LANs. It doesn't allow threaded GPU accesses and only supports old DirectX versions. It doesn't understand Advanced Format hard drives or SSDs. USB 3 on XP is buggy as hell. (in my experience)
If you installed a super modern GPU with 3 GB video RAM on XP, it would fall over and die because it has to map those 3 GB into 4 GB of space.
So, in at least this case, the OS didn't slow down. And without it new hardware wouldn't work at all.
Sure you can. But what is Chrome on iOS? It is a user interface skin over Safari is all it is. Not actually Chrome.
Of course you have rights. So does your employer. And using your employer's network gives your employer the right to see what is traveling over his network.
They shouldn't. A simple second level of encryption such as an encrypted ZIP file defeats any automatic scanning for confidential keywords or anything similar.
Eh. Except that a blue screen or if you have to do a forced power-off will lose data and require a chkdsk run. I ran my desktop that way for a little while (with a UPS) but it had problems.
"White Flight"
What a racist term. As if it is white people that keep an area valuable and crime free.
It's actually middle class and upper class flight, as well-off black, asian and hispanic people don't want to live in a blighted crime-ridden area either.
While it is an interesting technology with cool potential, a lot of folks don't want to be constantly filmed by Google Glass wearers for privacy issues. Like, the thought that all that Google Glass data will belong to the NSA on a whim of a secret court judge. Google doesn't give a rat's ass about people's privacy. They just want to sell their glasses, and they'll do it. And it's their right to do so, but don't expect people to love them for it.
People are in general, morons. Worried about Google Glass? People can be recording video from a cell phone in a pocket RIGHT NOW. I walked around with mine recording for 3.5 hours just to see what it was like. (Boring and bounced worse than the Blair Witch video.) People have dash cams in their cars. People have their houses and offices wired with security cameras that do motion detection and upload 1080p high-def video to the cloud.
Every store you walk into, every car you walk in front of, anybody holding a cell phone...
If you aren't alone inside a building that you control, you have no privacy and your face can end up on Youtube at any moment. Get over it.
Directly providing the power to vaporize a person is not the elegant way to do it. The correct, elegant mad scientist method is to use the power contained in the vaporized mass to power the vaporization.
Consider if you develop a means to "program" a plasma such that it generates a contracting magnetic field that causes fusion inside the vaporizing object and then absorbs some of the energy from this fusion reaction to power itself.
Now you're talking! Now you've got an effect that can vaporize any object provided you can provide the initial energy requirement.
There could be variants on this. Perhaps you've got an effect that flips matter into antimatter and absorbs some of the released energy to continue the effect.
If this is an expanding effect instead of a collapsing effect you've got a world killer like the weapons in Ender's Game.
Except that on a LAN FTP is almost the only protocol I can rely on to get high speed data transfers. SFTP blocks at about 30 MB/s when FTP can easily get 90.
If the Linux distros would be reasonable and enable the "none" crypto on SSH it would be a good thing. If I explicitly ask for no crypto then why are they making it hard for me to get what I want?
Yes, I know I can recompile OpenSSH for "none" crypto but it is easier to set up FTP, or even use tar and netcat.
What workarounds? Even if I install the original Windows 7 with no updates on top of it, ACPI works flawlessly on most machines, both old and brand new (which didn't even exist when Win7 was released).
You will sometimes see motherboard driver files for Windows which are simply ugly hacks to fix things without doing a BIOS update by hot-patching the board's ACPI, or overriding some Windows default so it works properly with the buggy board.
The right thing to do would be to issue a BIOS update or recall the board. But no, as long as they can hack in a software fix for Windows they go ahead and ship it.
I assume you would like security bugs specially marked so that you can prioritize fixing them and releasing the changes.
Look at the number of bugs found and fixed which have much later been discovered to be security bugs.
So now you didn't push "non-security" bug fixes to your production servers and they get owned by bad guys.
The lesson is that you should treat all bugs as security bugs.
Microsoft got so sick of those calculator jokes that in Windows 95 it was rewritten to use arbitrary precision math.
The main reason is so that your company is equally vulnerable to the ridiculous patent system.
Just being in business using computers and the Internet and writing software opens up your company to hundreds of potential patents. Most of which are OBVIOUS! Really.
Another reason to be a producer is something that every inventor knows. Coming up with an idea is 10% of the effort. Actually making it work is much more difficult and 90% of the work. Sitting around and coming up with wild ideas that might be possible and writing patents on them and then waiting for someone else to do the 90% work before suing them is a very bad taste for the people who really did the work.
"Rocket science is easy. Rocket engineering is hard."
You know, to someone just reading the law your argument seems like the only reasonable result. And I agree with you.
But the Supreme Court doesn't. Oh no. A while back they decided that Interstate Commerce comes into effect if what you do in your state might somehow affect people in other states. Like by reducing the demand for the wheat in other states by growing too much wheat in your state and selling it, in your state.
Yup. Perfectly ludicrus. But that's the law for you.
I don't think it affects the unrecoverable read error rate. But patrol-scrub does find those unrecoverable read errors as it goes and rewrites the block. If you don't scrub then those read errors will just invisibly accumulate over time.
So during a RAID5 rebuild you'd be limited to any read errors that occurred during that last week. Hopefully.
I do think that RAID6 or other systems that allow 2 disks to fail are more reliable.
You should be scrubbing your RAID at least once a week. That will detect and fix most of the creeping errors that would have prevented a successful rebuild.
Yes you lose IOPS during the scrub but if you didn't care about data correctness you'd be using RAID0.
From what I've read in the last few months, the Linux kernel and glibc will both be adding transaction lock support. The performance benefits are pretty nice even when limited to backwards compatibility with existing lock methods.
Also, libraries like Intel's (of course) TBB will add support.
But all of that will be done with feature detection and fall back to using existing code.
It's like saying that nobody codes for MMX, SSE, Altivec or 3DNow. Or that nobody uses a particular Nvidia OpenGL extension only available on the newest cards. Yes, if it gains that extra 15% speed boost they will code for it.
In the states where it is legal (sorta) now, I predict this will happen, like beer kegs.
"Gimme a kilo man. It's for the party."
It is super-easy if the contents of that wallet were created by a credit card purchase and the transfer from a Bitcoin exchange wallet. The exchange then has the identity of the credit card holder linked to the wallet.
Another Windows Metro/Modern fan I see. Big news for you! Windows Blue will allow you to choose your tile sizes!