The picture in TFA seems to show a modern full cutoff fixture (i.e. a fixture designed so that the light only projects down and sideways, not upward.) Hopefully they will resist the temptation of thinking "well, LED lights use less energy so lets put brighter LEDs in!" that has happened in other communities that replace their lighting with LEDs.
I spent 13 years in Tech Support. I had bad days, but I would _never_ have spoken to a customer in that fashion, even when they were abusive. The proper response to an abusive customer is to push them up the chain so my manager could defuse the situation. The mute button is your friend.
Most of the compensation is done in the optics of the scope, not on the pixels in the acquired image. In short, a laser is aimed at the sky and imaged, and the mirror itself (usually the secondary) is bent to compensate for the distortion to make the image of the laser as sharp as possible. Since you're aiming the scope at the same portion of the sky as the laser, the compensation works for the stars in that area of the sky. This happens hundreds of times a second (the atmosphere has this annoying habit of being turbulent). It's pretty amazing technology, but to say that it's "photoshopping" is like saying that focusing a camera is "photoshopping."
Yes, the image goes through some noise cleanup, but so does the image from your DSLR, your point-and-shoot or even your cellphone cam.
My parents had an HP-25C. I had a lot of fun with it (moon lander FTW!) Later they also bought a 19C and the 25C became mine. Don't know what happened to it. Now I have a 32S II at work (holdover from my college days) which is mostly used to convert between number bases, and a 48GX at home. I still think in terms of X Y Z T which makes using the 48GX a little tougher (Where's XY? Oh, it's called SWAP now!)
Nope. You don't get free XCode 4 unless you're paying $100 a year for either a Mac or iOS Developer. The newest version of XCode you can get for free with a free developer account is XCode 3.
Make also sells their own ARM-based MakeController board which is not Arduino based. If there would be any bias I'd expect it to be towards their own solution.
I'm just coincidentally going through an RMA on my 2 1/2 year old EVGA 8800GT card. Card broke on Friday, I contacted their tech support the same evening. On Saturday I got a reply from tech support saying to start the RMA process, I uploaded an image of my Newegg invoice and went through their web form. On Sunday (!!!) the RMA was approved. Sounds like pretty good service to me.
I had registered the card withing 30 days of buying it - I think that greases the wheels a lot.
Yes - the Apple iPhone SDK rules also specify that if you build anything using it, you cannot distribute it through any means other than the App Store, therefore violating the clause of the GPL that says there can be no other restrictions on distribution (section 6 of the GPL version 2, section 10 of the GPL version 3.)
At work, I got a shiny new machine. Since we need to certify some of our products with Windows Vista, we designated it the Vista certification machine. So far, so good.
We use the MKS Toolkit software suite to simplify several tasks while developing on Windows. Everything seemed to work fine, until I had to use patch to apply a diff to some sources. As soon as I typed
patch -p0 foo.diff
at the command prompt I got a pop-up window from Vista asking permission to run the executable. If I answered "yes, go ahead" instead of running the program in the same command prompt window it popped it up in another command prompt which promptly disappeared. And, apparently, did absolutely nothing to the files that were supposed to be patched. Experimentation shows that even
patch --help
pops up the dialog and fails, so it isn't a permissions problem on the files to patch. So I say to myself, "Myself, we're a revision or two back on MKS Toolkit, and this is not the Vista-certified version - let's try another patch.exe." So I go get the GnuWin32 version of patch.exe. I put it first on the PATH, and try again. Another pop-up. I answer yes, and not only does patch run in a window that disappears, but it GPFs as well.
At this point, I'm pissed. But suddenly the penny drops. I rename the MKS toolkit patch.exe to ptch.exe and type
ptch --help
which produces a nice help message. Trying on the original diff causes the required files to be patched correctly.
Apparently the Windows Vista User Access Control considers patch.exe to be a forbidden executable name. I investigated further and the only way to disable this functionality appears to be to completely turn off UAC, which I did immediately.
But there you have it - Windows Vista's vaunted security is about as logical and effective as banning water bottles in carry-on luggage.
Yes, but "below 50% charge" actually means "85% of the maximum voltage." For Lithium-Polimer batteries, the maximum voltage is 4.2V and 3.0V is "completely discharged" (in fact dropping lower than 3.0V runs the risk of permanently damaging the battery and causing "vent with flames" the next time you charge it.) 3.8V is considered the ideal storage voltage in R/C circles.
R/C circles probably have the largest percentage of failed Lithium Polymer batteries, because they are discharged at pretty high rates, and the protective circuits on most consumer lithium batteries are removed. Most failures are caused by the following:
- Overcharging due to the use of a bad charger or using the wrong settings on a Lithium-Polymer-capable charger.
- One cell of a multicell pack overcharging due to being at a higher initial voltage than the other cells in the pack. This is being mitigated with the use of "balancers" which connect to each cell and maintain equal voltages across the pack.
- Physical damage due to crashes.
- Shorting out the battery.
- Allowing the voltage of a cell to drop below 3.0V.
Many of these have been ameliorated due to technological improvements in the last two years - for example the aircraft-side electronics now cut off the motor at a point where the battery voltage is still safe, chargers have been much improved, and battery packs now come with special connections to allow checking and adjusting voltages on a cell-by-cell basis.
R/C enthusiasts tend to treat Lithium-Polymer batteries with quite a bit of respect as far as storage and charging is concerned. Many will set up a cinderblock on a concrete floor, place the battery in one of the holes of the cinderblock (the holes in the block are set vertically) and cover the top of the hole with a plastic bag full of sand. In case of a "vent with flame", the heat will melt the plastic allowing the sand to cover the battery and put out the fire. Compared to a couple of years ago, however, the incidence of Lithium-Polymer fires has greatly decreased even as use of Lithium-Polymer batteries has increased.
This forum thread has a lot of information about dangers and safe handling guidelines for Lithium-Polymer batteries.
The primary differentiator is not CPU power, but I/O bandwidth. Even with SATA drives, PC architectures still don't handle the I/O bandwidth that servers can handle. That's the same reason mainframes are still around - although raw CPU power on a mainframe is not as much as on a server or even a workstation, they can throw data around like nobody's business.
First I'd take a look at getting at least one mechanical automatic in your collection. You can get brand new mechanical Seikos using their 7S26 movement (a real workhorse) off eBay for around $50. These usually have glass backs so you can see the movement and the hairspring ticking. Another option is a skeletonized automatic - Swiss versions of these are quite expensive, but recently there have been a lot of lower-cost mechanical automatics available.
Another good option is an ana-digi - i.e. a watch with hands over an LCD dial - the LCD dial can show the time digitally while the hands show it as analog.
It's sort of embarassing to say this, but if you have the ShopNBC channel on your lineup, you might want to look for their watch shows. The guy who runs them (Jim Skelton) is knowledgeable about watches, and they often have interesting watches available. If you're looking for "funky", watch out for shows with Android Watches. Often they will have inexpensive (relatively - note that in the watch world anything under $1000 is considered a "poor man's watch") skeletonized automatics ($100 - $500 depending on the complications and the quality of the decoration on the movement.)
Interesting - I find KDE artwort to be much more consistent than GNOME artwork, at least in KDE 3.4/3.5. That's one of the things that made me switch to KDE recently.
I tried KTorrent and was unimpressed - went back to Azureus. Same with KSirc - I much prefer XChat for IRC. Other than those two, Openoffice, and Firefox, my desktop is pure KDE.
Sorry - this isn't the MPPE patches. This is support for PPTP packets being tracked through iptables. What I believe this will let you do is have multiple PCs behind a Linux firewall be able to use PPTP at the same time (prior to this PPTP through a Linux iptables firewall would work for only one PC at a time.)
So you like seeing microphone booms and such that were masked off the original negatives because the director composed the shot for widescreen, not fullscreen? See Matted Widescreen for examples.
The big questions to be answered before these make the big time are power requirements and hardening - if they use the same or less power than the current crop, and are resistant to environmental extremes like the current crop, then we're onto something.
F1 has been getting over 900BHP out of 3 liters...
on
The Bugatti Veyron
·
· Score: 1
That's with a normally aspirated (i.e. no turbo/superchargers) V10 engine. Of course, instead of revving at 6000RPM, they regularly hit over 19000RPM (6000RPM is idle for an F1 engine).
This would not be a good thing for IBM to do, and they know it. It opens them up for every failing company to bring trumped-up charges against them to try to get bought out or to raise their stock price. Better to smash SCO and keep those other lawsuits from happening.
As of the 2.38 ROM, they limit the addresses that are allowed to connect to the FTP port to only 192.168.129.1 or addresses that are provided by the Zaurus' internal DHCP server. So make sure that the PC endpoint of the usbndnet connection is either 192.168.129.1 or DHCP-provided.
Re:Wasn't this debunked on linux-kernel a 2 weeks
on
Linux Kernel Bugs
·
· Score: 1
Are you sure? On neither 2.2.19 nor 2.4.12 do I get a priviledged shell running the exploit.
Wasn't this debunked on linux-kernel a 2 weeks ago
on
Linux Kernel Bugs
·
· Score: 1
Wasn't this debunked on linux-kernel a 2 weeks ago
on
Linux Kernel Bugs
·
· Score: 1
See http://www.geocrawler.com/lists/3/Linux/35/2250/67 89857/ and related - according to the thread ptrace refuses to honor the setuid bit and even though the exploit program thinks it has succeeded, it just provides a non-priviledged shell.
The Sun plugin works great for me. Instead of downloading the plugin from Netscape.com, download and install the Sun 1.3.1 JDK or JRE, and then symlink/usr/java/jdk1.3.1/jre/plugin/i386/ns600/libjavapl ugin_oji.so into your Mozilla plugins directory. Next time you start Mozilla you will have Java.
Slashdot Mirror
The picture in TFA seems to show a modern full cutoff fixture (i.e. a fixture designed so that the light only projects down and sideways, not upward.) Hopefully they will resist the temptation of thinking "well, LED lights use less energy so lets put brighter LEDs in!" that has happened in other communities that replace their lighting with LEDs.
I spent 13 years in Tech Support. I had bad days, but I would _never_ have spoken to a customer in that fashion, even when they were abusive. The proper response to an abusive customer is to push them up the chain so my manager could defuse the situation. The mute button is your friend.
Most of the compensation is done in the optics of the scope, not on the pixels in the acquired image. In short, a laser is aimed at the sky and imaged, and the mirror itself (usually the secondary) is bent to compensate for the distortion to make the image of the laser as sharp as possible. Since you're aiming the scope at the same portion of the sky as the laser, the compensation works for the stars in that area of the sky. This happens hundreds of times a second (the atmosphere has this annoying habit of being turbulent). It's pretty amazing technology, but to say that it's "photoshopping" is like saying that focusing a camera is "photoshopping."
Yes, the image goes through some noise cleanup, but so does the image from your DSLR, your point-and-shoot or even your cellphone cam.
My parents had an HP-25C. I had a lot of fun with it (moon lander FTW!) Later they also bought a 19C and the 25C became mine. Don't know what happened to it. Now I have a 32S II at work (holdover from my college days) which is mostly used to convert between number bases, and a 48GX at home. I still think in terms of X Y Z T which makes using the 48GX a little tougher (Where's XY? Oh, it's called SWAP now!)
Nope. You don't get free XCode 4 unless you're paying $100 a year for either a Mac or iOS Developer. The newest version of XCode you can get for free with a free developer account is XCode 3.
Make also sells their own ARM-based MakeController board which is not Arduino based. If there would be any bias I'd expect it to be towards their own solution.
I'm just coincidentally going through an RMA on my 2 1/2 year old EVGA 8800GT card. Card broke on Friday, I contacted their tech support the same evening. On Saturday I got a reply from tech support saying to start the RMA process, I uploaded an image of my Newegg invoice and went through their web form. On Sunday (!!!) the RMA was approved. Sounds like pretty good service to me. I had registered the card withing 30 days of buying it - I think that greases the wheels a lot.
Or am I just not getting something?
Yes - the Apple iPhone SDK rules also specify that if you build anything using it, you cannot distribute it through any means other than the App Store, therefore violating the clause of the GPL that says there can be no other restrictions on distribution (section 6 of the GPL version 2, section 10 of the GPL version 3.)
At work, I got a shiny new machine. Since we need to certify some of our products with Windows Vista, we designated it the Vista certification machine. So far, so good.
We use the MKS Toolkit software suite to simplify several tasks while developing on Windows. Everything seemed to work fine, until I had to use patch to apply a diff to some sources. As soon as I typed
patch -p0 foo.diff
at the command prompt I got a pop-up window from Vista asking permission to run the executable. If I answered "yes, go ahead" instead of running the program in the same command prompt window it popped it up in another command prompt which promptly disappeared. And, apparently, did absolutely nothing to the files that were supposed to be patched. Experimentation shows that even
patch --help
pops up the dialog and fails, so it isn't a permissions problem on the files to patch. So I say to myself, "Myself, we're a revision or two back on MKS Toolkit, and this is not the Vista-certified version - let's try another patch.exe." So I go get the GnuWin32 version of patch.exe. I put it first on the PATH, and try again. Another pop-up. I answer yes, and not only does patch run in a window that disappears, but it GPFs as well.
At this point, I'm pissed. But suddenly the penny drops. I rename the MKS toolkit patch.exe to ptch.exe and type
ptch --help
which produces a nice help message. Trying on the original diff causes the required files to be patched correctly.
Apparently the Windows Vista User Access Control considers patch.exe to be a forbidden executable name. I investigated further and the only way to disable this functionality appears to be to completely turn off UAC, which I did immediately.
But there you have it - Windows Vista's vaunted security is about as logical and effective as banning water bottles in carry-on luggage.
Yes, but "below 50% charge" actually means "85% of the maximum voltage." For Lithium-Polimer batteries, the maximum voltage is 4.2V and 3.0V is "completely discharged" (in fact dropping lower than 3.0V runs the risk of permanently damaging the battery and causing "vent with flames" the next time you charge it.) 3.8V is considered the ideal storage voltage in R/C circles.
R/C circles probably have the largest percentage of failed Lithium Polymer batteries, because they are discharged at pretty high rates, and the protective circuits on most consumer lithium batteries are removed. Most failures are caused by the following:
- Overcharging due to the use of a bad charger or using the wrong settings on a Lithium-Polymer-capable charger.
- One cell of a multicell pack overcharging due to being at a higher initial voltage than the other cells in the pack. This is being mitigated with the use of "balancers" which connect to each cell and maintain equal voltages across the pack.
- Physical damage due to crashes.
- Shorting out the battery.
- Allowing the voltage of a cell to drop below 3.0V.
Many of these have been ameliorated due to technological improvements in the last two years - for example the aircraft-side electronics now cut off the motor at a point where the battery voltage is still safe, chargers have been much improved, and battery packs now come with special connections to allow checking and adjusting voltages on a cell-by-cell basis.
R/C enthusiasts tend to treat Lithium-Polymer batteries with quite a bit of respect as far as storage and charging is concerned. Many will set up a cinderblock on a concrete floor, place the battery in one of the holes of the cinderblock (the holes in the block are set vertically) and cover the top of the hole with a plastic bag full of sand. In case of a "vent with flame", the heat will melt the plastic allowing the sand to cover the battery and put out the fire. Compared to a couple of years ago, however, the incidence of Lithium-Polymer fires has greatly decreased even as use of Lithium-Polymer batteries has increased.
This forum thread has a lot of information about dangers and safe handling guidelines for Lithium-Polymer batteries.
The primary differentiator is not CPU power, but I/O bandwidth. Even with SATA drives, PC architectures still don't handle the I/O bandwidth that servers can handle. That's the same reason mainframes are still around - although raw CPU power on a mainframe is not as much as on a server or even a workstation, they can throw data around like nobody's business.
First I'd take a look at getting at least one mechanical automatic in your collection. You can get brand new mechanical Seikos using their 7S26 movement (a real workhorse) off eBay for around $50. These usually have glass backs so you can see the movement and the hairspring ticking. Another option is a skeletonized automatic - Swiss versions of these are quite expensive, but recently there have been a lot of lower-cost mechanical automatics available.
Another good option is an ana-digi - i.e. a watch with hands over an LCD dial - the LCD dial can show the time digitally while the hands show it as analog.
It's sort of embarassing to say this, but if you have the ShopNBC channel on your lineup, you might want to look for their watch shows. The guy who runs them (Jim Skelton) is knowledgeable about watches, and they often have interesting watches available. If you're looking for "funky", watch out for shows with Android Watches. Often they will have inexpensive (relatively - note that in the watch world anything under $1000 is considered a "poor man's watch") skeletonized automatics ($100 - $500 depending on the complications and the quality of the decoration on the movement.)
Of course, if you want really funky and price is no object, take a look at either the Ulysse Nardin Freak or the Harry Winston Opus V.
...Lack of consistent artwork...
Interesting - I find KDE artwort to be much more consistent than GNOME artwork, at least in KDE 3.4/3.5. That's one of the things that made me switch to KDE recently.
I tried KTorrent and was unimpressed - went back to Azureus. Same with KSirc - I much prefer XChat for IRC. Other than those two, Openoffice, and Firefox, my desktop is pure KDE.
I'm pretty sure patent concerns are part of it.
Sorry - this isn't the MPPE patches. This is support for PPTP packets being tracked through iptables. What I believe this will let you do is have multiple PCs behind a Linux firewall be able to use PPTP at the same time (prior to this PPTP through a Linux iptables firewall would work for only one PC at a time.)
So you like seeing microphone booms and such that were masked off the original negatives because the director composed the shot for widescreen, not fullscreen? See Matted Widescreen for examples.
The big questions to be answered before these make the big time are power requirements and hardening - if they use the same or less power than the current crop, and are resistant to environmental extremes like the current crop, then we're onto something.
That's with a normally aspirated (i.e. no turbo/superchargers) V10 engine. Of course, instead of revving at 6000RPM, they regularly hit over 19000RPM (6000RPM is idle for an F1 engine).
This would not be a good thing for IBM to do, and they know it. It opens them up for every failing company to bring trumped-up charges against them to try to get bought out or to raise their stock price. Better to smash SCO and keep those other lawsuits from happening.
As of the 2.38 ROM, they limit the addresses that are allowed to connect to the FTP port to only 192.168.129.1 or addresses that are provided by the Zaurus' internal DHCP server. So make sure that the PC endpoint of the usbndnet connection is either 192.168.129.1 or DHCP-provided.
Are you sure? On neither 2.2.19 nor 2.4.12 do I get a priviledged shell running the exploit.
See http://www.geocrawler.com/lists/3/Linux/35/2250/67 89857/ and related emails in the thread - the "exploit" just gives you a non-priviledged shell because ptrace() does not honor the setuid bit.
See http://www.geocrawler.com/lists/3/Linux/35/2250/67 89857/ and related - according to the thread ptrace refuses to honor the setuid bit and even though the exploit program thinks it has succeeded, it just provides a non-priviledged shell.
The Sun plugin works great for me. Instead of downloading the plugin from Netscape.com, download and install the Sun 1.3.1 JDK or JRE, and then symlink /usr/java/jdk1.3.1/jre/plugin/i386/ns600/libjavapl ugin_oji.so into your Mozilla plugins directory. Next time you start Mozilla you will have Java.