Yeah, I'll just add a DC to each of the 400 students scattered to Hell and gone all over the state. When I say geographically separated, I don't mean we have a stretch between buildings, I mean we have counties between each student and the next.
I know the suggestions are a healthy mix of 'how I'd do it' and 'UR DOIN IT RONG', but I'm really one of those cases where the MS Way simply will not work, no matter how much or little I'd like it to.
Yeah, cause Active Directory scales great over the internet, and EVERYONE has a 100Mb connection or better at their place of business.
We're physically discontiguous and your solution, while what I would do (and have done) in single site or robust WAN environments, simply does not work with the tools I have at hand and the geographical barriers I have to hurdle.
So yeah, you pass the MCSE exam but fail the Real Life test. Not everything can be solved by dropping WSUS onto an underutilized server and defining a new policy object.
Your computer got the fix yesterday, applied it this AM at 3:01AM, and then shut down again (I assume the last bit).
The problem is that lots of PCs don't automatically wake up as they're supposed to, and lots of users see updates as a Bad Thing, and actively work against them.
By the way, your OS would have pinged at you to reboot periodically yesterday if you had been using it.
Probably because it wasn't, and it wasn't for a VERY long time. It's only when the EU got serious about pushing for an IE-less Windows that MS suddenly started integrating the crap out of IE/Windows.
As recently as Windows 2000, you could have a fully functional machine with IE fully removed. MS would swear up and down that it wasn't possible, but folks all over did it every day.
With XP and onwards, MS used IE instead of the older Explorer cousin to render local folders and files. This was a gargantuan mistake in many opinions, mine included. It exposed myriad security holes in IE, most of which got patched, which is a net-good effect, but it also exposed a TON more attackable surface to the local filesystem.
I work for a school district, cyber-schooling. Ours may not be a scientifically valid cross-section either, but I'd say 6/10 or more machines either have WUAU turned off (the more advanced kids) or they simply hit the 'go away' button and never reboot to apply updates.
If you have pending updates, suspend/resume at night, and never manually reboot, WUAU will NOT apply further updates till the pending ones go on. I've had machines 6 months and more out of date (coming in today with XP SP2) on a regular basis.
I think one of the key things here is that Windows seems to require a reboot for EVERY LITTLE PATCH, which is a problem with the way they've hyper-integrated the kernel, the IE engine, and the shell. If things weren't tied together so tightly, a lot less reboots would be needed, and I'd imagine fewer people would be clicking 'later, go away' on WUAU notifications.
Hell, *I* am guilty. My work laptop applied the IE7 rush fix this AM and I told Vista to stuff it for 4 hours. When it pops up after lunch I'll tell it to stuff it for 4 again. I'm not using IE at all (never unless I have to), so I know I'm not running in a compromised state, but I'm sure the great majority of the 'later' clickers both do not know what they are postponing and further WOULD NOT CARE.
I've got a 360, and I've scratched discs with it. You do not need to tip it a great amount, 10-15 degrees would do it, maybe less with a little bad luck.
I installed three foam pads in the top of the DVD drive at a total cost of about.60$. My 360 no longer scratches discs, no matter how sharply tipped.
Microsoft having not done something similar is negligent. They had a noted defect and simply chose not to address it.
As someone who routinely runs all three OSes being discussed, and who has a great number of acquaintances running primarily just one, I will freely agree that most OSX users do not run games, and the few that do tend to run very low-end casual games.
However, the situation is much the same among the few Linux-only users I know. Most 'gamers' run at least two of the troika, usually Lin+Win or OSX+Win, and anything that won't run cleanly and easily under Wine/Crossover/Cedega/WTFever gets run in Windows natively.
I'm not an authority, but it certainly looks like the nay-sayers from 1999 were right. Windows can kill any serious Wine-based momentum, only native ports are beyond their influence.
IBM/Lenovo's passwords aren't set in the CMOS, they are stored in a single purpose non-volatile flash.
They've been a serious security device ever since IBM started doing it that way, back around 2000-2001 or so.
Yes, it'll probably be as secure as the Lenovo BIOS supervisor passwords.
(Hint: Supervisor password? Get a paperclip. The data pin goes to ground, boot laptop. Enter bios. Remove paperclip, set [new] supervisor password. It overwrites the old one. Which chip to mess with and which pins are which I leave to you and Google. Shouldn't take long.)
You have it backwards. The newest Apple HD crap will ONLY play on the newest hardware, which has HDCP and DPCP. Without the HARDWARE copy prevention, you get NO VIDEO PLAYBACK.
Replying to the intent and not the awkward wording:
Neither.
Multi-GPU on Linux works, but doesn't have the profiling and per-app settings that make it really work. If you look back over Windows driver releases, you'll see that multi-GPU performance is generally crap right after a game is released, unless it's really major A studio stuff. It takes ATI/NV a while to profile and tweak the settings to get multi-GPU really moving. It's mostly abstracted from the end user, but the results are undeniable.
Neither ATI nor NV has any sort of equivilent profiling under Linux so far. There's a global setting and you can do some gross per-app tweaking, but it's user-intensive and the results are nowhere near what you get under Windows.
Multi-GPU is just not a good sell for any gaming under Linux, and likely will not be for quite some time, if ever.
If you look at the FOSS ATI stuffs, they don't have *any* multi-GPU support at the present time, and that's unlikely to change. The closed-source ATI and NV stuff may eventually implement it, but it's unlikely. By then any currently shipping GPUs will be irrelevant.
I had one of the dual GPU single slot GeForce 7950GX2s for quite some time. I got a rather ridiculous speedup by upgrading to a single 8800GT, simply because ~99% of the time under Linux, only one of my GPUs was doing ANYTHING at all.
Re:This is a huge amount of work
on
Linux 2.6.27 Out
·
· Score: 5, Insightful
As far as I see, the real change is that what was the 2.4 and what was the 2.5 trees are now kept very close together. Active work (was 2.5) is done on the XX.YY.ZZ-preNUM kernels, it's all polished/troubleshot/reviewed in the XX.YY.ZZ-rcNUM kernels, and then it gets released. What was once 'stable tree' (2.4) work is now done on the XX.YY.ZZ.1.2.3 releases, and the developers move to XX.YY.ZZ+1-preNUM.
It seems to work quite well, and now you no longer have to meddle with dark arts and unsupported known-broken dev kernels to get recent hardware working. Win win all around IMO.
No more backporting/sideporting/up/down/leftporting to get current hardware code into current kernels, just all the dev community working on one codebase. Makes progress a lot more straightforward and apparently better/cleaner/less buggy.
Your 7600 did not use the affected solder/soldering method.
This defect affects primarily G84/G86 cards (mainly marketed as GeForce 8600). The G92-based 8800GT and 8800GTS 512 are not *supposed* to be affected, and the G80 based 8800GTX and 8800GTS 320/640 are believed unaffected as well.
Blu-Ray *should* have at least a fallback standard AC3 track for primary audio, but some don't, even now in the early days. If prior formats are any example, these sort of soft limits get ignored more and more often as the format ages.
So to recap; Blu-Ray *should* have AC3 or a DTS core of the primary English audio. Players *should* be able to output legacy DTS. SPDIF *should* always work.
In practice that is not the case.
That's not a failing of the DRM, though, so I'm prepared to drop it and let the rest of the comment stand.
Simply put, DVD CSS did not restrict the methods of use for your average person. If they had a store-bought DVD player and put a store bought DVD in it, IT PLAYED. End of line.
Put a store-bought BD in your store bought BD player and it bitches about your digital-but-not-HDCP-enough TV and refuses to play. It sees your SPDIF connection to your stereo and pitches a fit. It sees you doing ANYTHING but the Sony-approved Viewing Ritual and it just stops cold. It notices that the disc is using a newer encryption than the player and it tosses a shitfit, demanding that you get on the intertubes and burn a CDR with newer firmware. Average Joe shits a brick and returns his hardware when his MOVIE PLAYER THING tells him to get on the Intertubes. It's not flying.
End users notice that shit, and they're saying no.
Actually, the stormtroopers in the later movies are no longer Jango clones, the Republic lost the templates and ability to make new Jango clones not too long after old purple armor decided his head should pursue a career as a solo artist.
The stormtroopers by the time of Ep4 and on should all be either draftees or extremely geriatric clones. They were engineered to age faster to get them ready to fight in 2 years, so by the time of Ep4 they're supposed to be roughly 140 years old in people years.
Anyways, Star Wars is just about done. There's only so much more Lucas can do to it before nobody really cares and we all just wistfully shake our heads.
I'm less worried about the patent troll than the fact that the Patent Office allowed this crap to get through. I think it is time for some people to get summarily executed in public.
Bingo. I have a desktop running the Nvidia graphics drivers, it has Wine, Skype, the whole works.
My laptop on the other hand, is utterly pure from an ideological POV. Both are exactly what I want.
If I could do everything I wanted on both machines with solely OSS, I'd do it. Since I need closed stuff to make my desktop run the way I want it, that's what I use.
Of course, some day those RadeonHD guys will get RV770 working and I'll be one step closer.
So you're expecting the Martians to tag all the cameras and then tip over the probe soonish? The probe doesn't STOP when the crew goes home, by your own link the few people coming in are just supervising while the probe works on pre-scheduled work. Also, the dude you linked who was leaving sounds like an intern. He did his years, he saw a lot, learned some stuff, and he's ready to move on. Not everyone is as worked up over Phoenix as you seem to be.
I'm not seeing the strange.
Also, while we no longer build them like we used to, the Viking landers and orbiters grossly outperformed their expected MTBF. Viking 1 Lander went over SIX YEARS on the surface of Mars, taking pictures and so on, until some tool on Earth told it to point the main antenna elsewhere, making it hard to get back in touch.
Go over that again... SIX FREAKING YEARS. What was the expected duration? Quite a lot less. It's not unreasonable for us to expect Phoenix to possibly beat it's expiration date as well.
Slashdot Mirror
Yeah, I'll just add a DC to each of the 400 students scattered to Hell and gone all over the state. When I say geographically separated, I don't mean we have a stretch between buildings, I mean we have counties between each student and the next.
I know the suggestions are a healthy mix of 'how I'd do it' and 'UR DOIN IT RONG', but I'm really one of those cases where the MS Way simply will not work, no matter how much or little I'd like it to.
Yeah, cause Active Directory scales great over the internet, and EVERYONE has a 100Mb connection or better at their place of business.
We're physically discontiguous and your solution, while what I would do (and have done) in single site or robust WAN environments, simply does not work with the tools I have at hand and the geographical barriers I have to hurdle.
So yeah, you pass the MCSE exam but fail the Real Life test. Not everything can be solved by dropping WSUS onto an underutilized server and defining a new policy object.
By that logic NT4 and IE5.01 should be bulletproof. Since they are not, we can see that your argument's logic is flawed.
Often patches *create* issues and bugs as well as fixing them. This is the little detail which upsets your great oxcart.
Your computer got the fix yesterday, applied it this AM at 3:01AM, and then shut down again (I assume the last bit).
The problem is that lots of PCs don't automatically wake up as they're supposed to, and lots of users see updates as a Bad Thing, and actively work against them.
By the way, your OS would have pinged at you to reboot periodically yesterday if you had been using it.
Probably because it wasn't, and it wasn't for a VERY long time. It's only when the EU got serious about pushing for an IE-less Windows that MS suddenly started integrating the crap out of IE/Windows.
As recently as Windows 2000, you could have a fully functional machine with IE fully removed. MS would swear up and down that it wasn't possible, but folks all over did it every day.
With XP and onwards, MS used IE instead of the older Explorer cousin to render local folders and files. This was a gargantuan mistake in many opinions, mine included. It exposed myriad security holes in IE, most of which got patched, which is a net-good effect, but it also exposed a TON more attackable surface to the local filesystem.
I work for a school district, cyber-schooling. Ours may not be a scientifically valid cross-section either, but I'd say 6/10 or more machines either have WUAU turned off (the more advanced kids) or they simply hit the 'go away' button and never reboot to apply updates.
If you have pending updates, suspend/resume at night, and never manually reboot, WUAU will NOT apply further updates till the pending ones go on. I've had machines 6 months and more out of date (coming in today with XP SP2) on a regular basis.
I think one of the key things here is that Windows seems to require a reboot for EVERY LITTLE PATCH, which is a problem with the way they've hyper-integrated the kernel, the IE engine, and the shell. If things weren't tied together so tightly, a lot less reboots would be needed, and I'd imagine fewer people would be clicking 'later, go away' on WUAU notifications.
Hell, *I* am guilty. My work laptop applied the IE7 rush fix this AM and I told Vista to stuff it for 4 hours. When it pops up after lunch I'll tell it to stuff it for 4 again. I'm not using IE at all (never unless I have to), so I know I'm not running in a compromised state, but I'm sure the great majority of the 'later' clickers both do not know what they are postponing and further WOULD NOT CARE.
I've got a 360, and I've scratched discs with it. You do not need to tip it a great amount, 10-15 degrees would do it, maybe less with a little bad luck.
I installed three foam pads in the top of the DVD drive at a total cost of about .60$. My 360 no longer scratches discs, no matter how sharply tipped.
Microsoft having not done something similar is negligent. They had a noted defect and simply chose not to address it.
The part that I find hilarious is that even with all that precaching, most people who I've showed it to STILL find XP 'snappier' than Vista!
So if it's not making the OS more responsive, then Vista is precaching incorrectly.
If (more likely) it IS precaching correctly, then OMFG, what would it run like WITHOUT it??
As someone who routinely runs all three OSes being discussed, and who has a great number of acquaintances running primarily just one, I will freely agree that most OSX users do not run games, and the few that do tend to run very low-end casual games.
However, the situation is much the same among the few Linux-only users I know. Most 'gamers' run at least two of the troika, usually Lin+Win or OSX+Win, and anything that won't run cleanly and easily under Wine/Crossover/Cedega/WTFever gets run in Windows natively.
I'm not an authority, but it certainly looks like the nay-sayers from 1999 were right. Windows can kill any serious Wine-based momentum, only native ports are beyond their influence.
IBM/Lenovo's passwords aren't set in the CMOS, they are stored in a single purpose non-volatile flash. They've been a serious security device ever since IBM started doing it that way, back around 2000-2001 or so.
Old wives' tale actually. Please do pedant responsibly.
Yes, it'll probably be as secure as the Lenovo BIOS supervisor passwords.
(Hint: Supervisor password? Get a paperclip. The data pin goes to ground, boot laptop. Enter bios. Remove paperclip, set [new] supervisor password. It overwrites the old one. Which chip to mess with and which pins are which I leave to you and Google. Shouldn't take long.)
You have it backwards. The newest Apple HD crap will ONLY play on the newest hardware, which has HDCP and DPCP. Without the HARDWARE copy prevention, you get NO VIDEO PLAYBACK.
Person writing TFA has NFI.
HDCP which is now being included is a prerequisite for full-resolution Bluray. IT DOES NOT IN ANY WAY FUCK WITH YOUR FILES.
HDCP is NOT DRM. HDCP is a technology used by DRM. It's meant to secure the data path from GPU to cables to monitor to pixels.
THIS TECH IS ALREADY ON ALL NEW GRAPHICS CARDS AND ALL NEW MONITORS, Apple is LATE in implementing it if anything.
Replying to the intent and not the awkward wording:
Neither.
Multi-GPU on Linux works, but doesn't have the profiling and per-app settings that make it really work. If you look back over Windows driver releases, you'll see that multi-GPU performance is generally crap right after a game is released, unless it's really major A studio stuff. It takes ATI/NV a while to profile and tweak the settings to get multi-GPU really moving. It's mostly abstracted from the end user, but the results are undeniable.
Neither ATI nor NV has any sort of equivilent profiling under Linux so far. There's a global setting and you can do some gross per-app tweaking, but it's user-intensive and the results are nowhere near what you get under Windows.
Multi-GPU is just not a good sell for any gaming under Linux, and likely will not be for quite some time, if ever.
If you look at the FOSS ATI stuffs, they don't have *any* multi-GPU support at the present time, and that's unlikely to change. The closed-source ATI and NV stuff may eventually implement it, but it's unlikely. By then any currently shipping GPUs will be irrelevant.
I had one of the dual GPU single slot GeForce 7950GX2s for quite some time. I got a rather ridiculous speedup by upgrading to a single 8800GT, simply because ~99% of the time under Linux, only one of my GPUs was doing ANYTHING at all.
As far as I see, the real change is that what was the 2.4 and what was the 2.5 trees are now kept very close together. Active work (was 2.5) is done on the XX.YY.ZZ-preNUM kernels, it's all polished/troubleshot/reviewed in the XX.YY.ZZ-rcNUM kernels, and then it gets released. What was once 'stable tree' (2.4) work is now done on the XX.YY.ZZ.1 .2 .3 releases, and the developers move to XX.YY.ZZ+1-preNUM.
It seems to work quite well, and now you no longer have to meddle with dark arts and unsupported known-broken dev kernels to get recent hardware working. Win win all around IMO.
No more backporting/sideporting/up/down/leftporting to get current hardware code into current kernels, just all the dev community working on one codebase. Makes progress a lot more straightforward and apparently better/cleaner/less buggy.
Your 7600 did not use the affected solder/soldering method.
This defect affects primarily G84/G86 cards (mainly marketed as GeForce 8600). The G92-based 8800GT and 8800GTS 512 are not *supposed* to be affected, and the G80 based 8800GTX and 8800GTS 320/640 are believed unaffected as well.
Random Google result:
http://www.arcsoft.com/forum/forum_posts.asp?TID=921&PID=3914
Blu-Ray *should* have at least a fallback standard AC3 track for primary audio, but some don't, even now in the early days. If prior formats are any example, these sort of soft limits get ignored more and more often as the format ages.
So to recap; Blu-Ray *should* have AC3 or a DTS core of the primary English audio. Players *should* be able to output legacy DTS. SPDIF *should* always work.
In practice that is not the case.
That's not a failing of the DRM, though, so I'm prepared to drop it and let the rest of the comment stand.
Simply put, DVD CSS did not restrict the methods of use for your average person. If they had a store-bought DVD player and put a store bought DVD in it, IT PLAYED. End of line.
Put a store-bought BD in your store bought BD player and it bitches about your digital-but-not-HDCP-enough TV and refuses to play. It sees your SPDIF connection to your stereo and pitches a fit. It sees you doing ANYTHING but the Sony-approved Viewing Ritual and it just stops cold. It notices that the disc is using a newer encryption than the player and it tosses a shitfit, demanding that you get on the intertubes and burn a CDR with newer firmware. Average Joe shits a brick and returns his hardware when his MOVIE PLAYER THING tells him to get on the Intertubes. It's not flying.
End users notice that shit, and they're saying no.
Actually, the stormtroopers in the later movies are no longer Jango clones, the Republic lost the templates and ability to make new Jango clones not too long after old purple armor decided his head should pursue a career as a solo artist. The stormtroopers by the time of Ep4 and on should all be either draftees or extremely geriatric clones. They were engineered to age faster to get them ready to fight in 2 years, so by the time of Ep4 they're supposed to be roughly 140 years old in people years. Anyways, Star Wars is just about done. There's only so much more Lucas can do to it before nobody really cares and we all just wistfully shake our heads.
I'm less worried about the patent troll than the fact that the Patent Office allowed this crap to get through. I think it is time for some people to get summarily executed in public.
Fixed that for ya. You're welcome.
Bingo. I have a desktop running the Nvidia graphics drivers, it has Wine, Skype, the whole works.
My laptop on the other hand, is utterly pure from an ideological POV. Both are exactly what I want.
If I could do everything I wanted on both machines with solely OSS, I'd do it. Since I need closed stuff to make my desktop run the way I want it, that's what I use.
Of course, some day those RadeonHD guys will get RV770 working and I'll be one step closer.
So you're expecting the Martians to tag all the cameras and then tip over the probe soonish? The probe doesn't STOP when the crew goes home, by your own link the few people coming in are just supervising while the probe works on pre-scheduled work. Also, the dude you linked who was leaving sounds like an intern. He did his years, he saw a lot, learned some stuff, and he's ready to move on. Not everyone is as worked up over Phoenix as you seem to be.
I'm not seeing the strange.
Also, while we no longer build them like we used to, the Viking landers and orbiters grossly outperformed their expected MTBF. Viking 1 Lander went over SIX YEARS on the surface of Mars, taking pictures and so on, until some tool on Earth told it to point the main antenna elsewhere, making it hard to get back in touch.
Go over that again... SIX FREAKING YEARS. What was the expected duration? Quite a lot less. It's not unreasonable for us to expect Phoenix to possibly beat it's expiration date as well.
Liar.
http://www.softpedia.com/get/Windows-Widgets/Widget-Miscellaneous/Homeland-Security-Widget.shtml
You're only about a year behind.
Besides, it's not the threat level widget we should fear, it's the automatically granted remote logins and kernel-based keyloggers.