Both are applicable. The former is for people who are tired of being told to RTFM. The latter is for people who are tired of things not working as they should when the do RTFM.
While you're technically correct (a watt is the power equivalent to one joule for one second), electricity is generally measured in kilowatt hours, as that's how it's sold. I expect that the "per day" was added by the reporter who had no clue. It probably puts out 120MW continuously (i.e., 120MW-hours per hour) or at peak operation.
What's obvious is that the writer didn't have a technical understanding.
Yes, but the Mini is still Core 1, not Core 2. And the graphics on the Mini make playback of HDTV problematic. Put in a low-end nVidia 5200 and make it Core 2 Duo, and I would buy a Mini.
Intel has announced the Core 2 Duo chips for laptops, but they aren't shipping yet. I expect Apple is waiting to announce laptops that use them until they can actually ship them, allowing them to continue to sell laptops that they can ship now until that happens. And it wouldn't surprise me if they'll update the iMac and Mac Mini at about that same time (possibly also using the laptop version of the Core 2, depending on the heat issues).
Obviously the story was intended as a slam on Wikipedia, but I read it as just the opposite. The story was breaking, and within a very short time, the Wikipedia article evolved into something respectable. Sure, it took some wrong turns, but they didn't last for more than a few minutes. Reuters described Wikipedia working exactly the way it is supposed to work.
I doubt that the encryption overhead is really all that significant. For a site like Slashdot, discussions about performance have always been about the backend database, not the frontend web servers, which is where the encryption would be handled.
What I really want is opportunistic VPN on all connections. If two systems support the protocol, then all communications (web, irc, ftp, VoIP, etc.) are encrypted. This could be accomplished by adding a text record with a public key into DNS much like how SPF is handled. If such a system became widely-deployed, then monitoring at the ISP level would only be of use for traffic analysis (and use of services provided by the ISP, such as @isp.com email).
This is another good reason to use https instead of http. Unfortunately, most web sites will only use https for commerce. If Google used https by default, then the government would have to subpoena them directly to find out what a particular user searched for. Likewise, if Slashdot used https by default, then the government would have a lot more trouble figuring out who an anonymous coward was.
I would certainly consider an EMC Clariion. The Symmetrix is probably overkill for your needs and budget. (Disclaimer: I work for EMC on the Symmetrix side.) I suspect that Clariion also supports iSCSI. (You could check with Dell's or EMC's web sites.)
Also, don't forget about backup. Sure, you're protected by RAID, but with the more advanced systems, you can send a single command to the storage system and make a copy of everything within the array to allow you to recover from user errors (or virus destruction). As you grow, you may consider replication to a second array. So consider your growth needs, and get something that will fit into the long-term plan.
The F-16 is purely fly-by-wire. If you loose the wires, you bail out.
The system here, at least in theory, could be built without mechanical backups. (And you don't have such systems in most larger modern aircraft to begin with, I believe--not that there aren't redundancies.)
And forcing a pilot to use a backup system is dangerous--if you do it at just the right time, the pilot might not respond in time to avert a crash.
This could be useful for combat aircraft, as you don't have to worry about losing control of a flap or other system because the cable was severed by enemy fire.
Also, with combat aircraft, you might be able to shield the interior of the aircraft such that it would be immune to jamming. That might be necessary anyway to prevent signal leakage that might give away the aircraft's location, either defeating stealth advanatages or allowing for another type of weapons lock.
Obviously the first thing they need to address is the possibility of a passenger hacking their wireless network and taking control of the plane. Or simply jamming the system to crash the plane.
Securing the network should be doable, but preventing jamming may be the problem that prevents this from becoming a real system.
When I told my supervisor that I was having wrist pain and could use a keyboard tray, instead of just getting a keyboard tray, they called in an ergonomics specialist to evaluate my work environment. Ultimately, what I got was the keyboard tray that I had asked for.
I found out later that the company had just been sued by an employee for disability over a similar issue (though apparently that was someone with a history of questionalbe lawsuits).
With Platypus, you can easily create Greasemonkey scripts to strip junk out of your favorite sites. You don't have to use JavaScript to strip out those unwanted sidebars at your favorite sites, and you don't have to search for scripts that others have written to see if someone else wanted to make the same changes.
It's not a big deal for SDTV. You just use the analog ouput of the cable box and digitize it just like you would with analog cable. You have to use a serial cable or IR blaster to control the cable box, which can be a pain, and it means you have to have multiple cable boxes to record multiple digital cable channels.
It is a big deal for HDTV. You can use a QAM tuner to record the raw bitstream off of digital cable, but they generally encrypt everything except the broadcast channels. Comcast even encrypts the public access channels. That's where the cable card would be really nice. Or a way to break the encryption.
The computer died last September, but I bought another on eBay. Last night I was adding new features to my disk utility program. I'm in the middle of re-writing one of the assembly language routines to be more efficient.
Granted, most of my Atari activities I now do using an emulator, and when I use the real one, I use my Linux box as a file server (SIO2PC cable). I've just gone through my shoebox full of disks and copied them onto my PC. I was surprised that most of them still work just fine.
Why stock? People bet on all sorts of things. I would be shocked if you couldn't bet on the Sundance winners. So the real question is, if they had used their predictions as a betting strategy, what would their return on investment be?
That would give a good indicator of how much they're simply predicting the favorites (not much return) or accurately predicting surprises.
There are a bunch of missing episodes, but they have still photos and the audio tracks to all of them, so you can find reconstructions where they put up photos along with the sound tracks, using subtitles to explain actions that are missing when necessary. It's not the same as watching a real episode, but you can follow the story.
Yup, something is configured wrong, but it only munges the MBR if I boot Windows; it can repeatedly boot Linux just fine, so it's something that happens after the BIOS passes control to the OS. The Windows installation is a corporate standard image, which is probably significantly tweaked in weird ways.
So there's probably something I could have fixed, but I used the tools that I knew, and now it works just fine.
I had a similar problem with Grub and VMWare. I had a dual boot system, and I wanted to be able to also boot the Windows side in VMWare when I was running Linux. (Note, that's not a recommended way of doing it.)
Anyway, the problem was that I tried to deny access to my Linux partitions in VMWare, but most of grub actually lived there, so it wasn't able to load it.
There are also a number of other possible issues, as other posters have mentioned.
One thing I never did figure out was how to get grub to detect if it's a virtual machine and boot Windows by default instead of Linux. There should be a way to do that based on partition access permissions or existence of certain hardware. It's not relevant now, as I've wiped my Windows partition and now just use a giant file system image file with VMWare.
Slashdot Mirror
"Q&A" is Question and Answer.
"QA" is Quality Assurance.
Both are applicable. The former is for people who are tired of being told to RTFM. The latter is for people who are tired of things not working as they should when the do RTFM.
While you're technically correct (a watt is the power equivalent to one joule for one second), electricity is generally measured in kilowatt hours, as that's how it's sold. I expect that the "per day" was added by the reporter who had no clue. It probably puts out 120MW continuously (i.e., 120MW-hours per hour) or at peak operation.
What's obvious is that the writer didn't have a technical understanding.
No, it's Core Duo, not Core 2 Duo. That's 32-bit, not 64-bit, which may be an issue with future OS upgrades.
And it's still the Intel on-board graphics.
Note the subject, we're talking about the Mini, not the iMac, which is Core 2.
And no Core 2.
And no improved graphics.
So the Mini is still stuck with a 32-bit processor and graphics that can't handle HDTV playback.
Yes, but the Mini is still Core 1, not Core 2. And the graphics on the Mini make playback of HDTV problematic. Put in a low-end nVidia 5200 and make it Core 2 Duo, and I would buy a Mini.
Intel has announced the Core 2 Duo chips for laptops, but they aren't shipping yet. I expect Apple is waiting to announce laptops that use them until they can actually ship them, allowing them to continue to sell laptops that they can ship now until that happens. And it wouldn't surprise me if they'll update the iMac and Mac Mini at about that same time (possibly also using the laptop version of the Core 2, depending on the heat issues).
Obviously the story was intended as a slam on Wikipedia, but I read it as just the opposite. The story was breaking, and within a very short time, the Wikipedia article evolved into something respectable. Sure, it took some wrong turns, but they didn't last for more than a few minutes. Reuters described Wikipedia working exactly the way it is supposed to work.
I doubt that the encryption overhead is really all that significant. For a site like Slashdot, discussions about performance have always been about the backend database, not the frontend web servers, which is where the encryption would be handled.
What I really want is opportunistic VPN on all connections. If two systems support the protocol, then all communications (web, irc, ftp, VoIP, etc.) are encrypted. This could be accomplished by adding a text record with a public key into DNS much like how SPF is handled. If such a system became widely-deployed, then monitoring at the ISP level would only be of use for traffic analysis (and use of services provided by the ISP, such as @isp.com email).
So while the government complained about the Minutemen watching the border, they're now creating what is essentially the same thing, only online.
This is another good reason to use https instead of http. Unfortunately, most web sites will only use https for commerce. If Google used https by default, then the government would have to subpoena them directly to find out what a particular user searched for. Likewise, if Slashdot used https by default, then the government would have a lot more trouble figuring out who an anonymous coward was.
I would certainly consider an EMC Clariion. The Symmetrix is probably overkill for your needs and budget. (Disclaimer: I work for EMC on the Symmetrix side.) I suspect that Clariion also supports iSCSI. (You could check with Dell's or EMC's web sites.)
Also, don't forget about backup. Sure, you're protected by RAID, but with the more advanced systems, you can send a single command to the storage system and make a copy of everything within the array to allow you to recover from user errors (or virus destruction). As you grow, you may consider replication to a second array. So consider your growth needs, and get something that will fit into the long-term plan.
That's not necessarily true.
The F-16 is purely fly-by-wire. If you loose the wires, you bail out.
The system here, at least in theory, could be built without mechanical backups. (And you don't have such systems in most larger modern aircraft to begin with, I believe--not that there aren't redundancies.)
And forcing a pilot to use a backup system is dangerous--if you do it at just the right time, the pilot might not respond in time to avert a crash.
This could be useful for combat aircraft, as you don't have to worry about losing control of a flap or other system because the cable was severed by enemy fire.
Also, with combat aircraft, you might be able to shield the interior of the aircraft such that it would be immune to jamming. That might be necessary anyway to prevent signal leakage that might give away the aircraft's location, either defeating stealth advanatages or allowing for another type of weapons lock.
Obviously the first thing they need to address is the possibility of a passenger hacking their wireless network and taking control of the plane. Or simply jamming the system to crash the plane.
Securing the network should be doable, but preventing jamming may be the problem that prevents this from becoming a real system.
When I told my supervisor that I was having wrist pain and could use a keyboard tray, instead of just getting a keyboard tray, they called in an ergonomics specialist to evaluate my work environment. Ultimately, what I got was the keyboard tray that I had asked for.
I found out later that the company had just been sued by an employee for disability over a similar issue (though apparently that was someone with a history of questionalbe lawsuits).
Note: not my current employer
Platypus!
With Platypus, you can easily create Greasemonkey scripts to strip junk out of your favorite sites. You don't have to use JavaScript to strip out those unwanted sidebars at your favorite sites, and you don't have to search for scripts that others have written to see if someone else wanted to make the same changes.
No, the public access (not PBS, but local government stuff) is encrypted.
It's not a big deal for SDTV. You just use the analog ouput of the cable box and digitize it just like you would with analog cable. You have to use a serial cable or IR blaster to control the cable box, which can be a pain, and it means you have to have multiple cable boxes to record multiple digital cable channels.
It is a big deal for HDTV. You can use a QAM tuner to record the raw bitstream off of digital cable, but they generally encrypt everything except the broadcast channels. Comcast even encrypts the public access channels. That's where the cable card would be really nice. Or a way to break the encryption.
Same here, only I started with a disk drive.
The computer died last September, but I bought another on eBay. Last night I was adding new features to my disk utility program. I'm in the middle of re-writing one of the assembly language routines to be more efficient.
Granted, most of my Atari activities I now do using an emulator, and when I use the real one, I use my Linux box as a file server (SIO2PC cable). I've just gone through my shoebox full of disks and copied them onto my PC. I was surprised that most of them still work just fine.
Why stock? People bet on all sorts of things. I would be shocked if you couldn't bet on the Sundance winners. So the real question is, if they had used their predictions as a betting strategy, what would their return on investment be?
That would give a good indicator of how much they're simply predicting the favorites (not much return) or accurately predicting surprises.
I thought the threat of a lawsuit shut them down before it was distributed.
There are a bunch of missing episodes, but they have still photos and the audio tracks to all of them, so you can find reconstructions where they put up photos along with the sound tracks, using subtitles to explain actions that are missing when necessary. It's not the same as watching a real episode, but you can follow the story.
"The Fifth Element" is an example of humor in American science fiction.
Yup, something is configured wrong, but it only munges the MBR if I boot Windows; it can repeatedly boot Linux just fine, so it's something that happens after the BIOS passes control to the OS. The Windows installation is a corporate standard image, which is probably significantly tweaked in weird ways.
So there's probably something I could have fixed, but I used the tools that I knew, and now it works just fine.
I had a similar problem with Grub and VMWare. I had a dual boot system, and I wanted to be able to also boot the Windows side in VMWare when I was running Linux. (Note, that's not a recommended way of doing it.)
Anyway, the problem was that I tried to deny access to my Linux partitions in VMWare, but most of grub actually lived there, so it wasn't able to load it.
There are also a number of other possible issues, as other posters have mentioned.
One thing I never did figure out was how to get grub to detect if it's a virtual machine and boot Windows by default instead of Linux. There should be a way to do that based on partition access permissions or existence of certain hardware. It's not relevant now, as I've wiped my Windows partition and now just use a giant file system image file with VMWare.