Microsoft, by witholding the source, would be violating the copyright held by the people that wrote the OOM killer. They could then be sued by the copyright holders, and forced to seek settlement or ordered to pay damages - just like IBM could sue them if they lifted code out of AIX. It is very unlikely that a court would force them to license Windows under the GPL as a result.
Windowcleaners, builders and undersea welders risk life and limb on a daily basis (and not just three weeks out of their entire career) and nobody blathers on pompously about their "effort and sacrifice" when they simply do their job.
Huh? Tune into something like the NatGeo channel; documentaries highlighting these professions and the risks are a dime a dozen.
I don't think the Australian Computer Society has any formal status. It's certainly not required by law, or any employer I've ever seen, to be accredited by them.
VirtualLock on Win32 and mlock on *nix already provide this functionality.
(Actually, both those functions will "lock memory" in the sense that accessing that memory will never cause a page fault, but that doesn't necessarily mean that the data won't be written out to disk preemptively. The Linux man page for mlock strongly implies that the data won't ever be paged out, but it could well be on Win32 and other *nix).
the summary makes me think he made a mountain from a molehill.
I think the emphasis is more on the historical significance, given the rarity of the tapes and the fact that the only digitised copy floating about has been patched.
I mean, MSI does have some really cool features, but dependency tracking for DLLs is not one of them.
Take a look at C:\Windows\WinSxS on an XP SP2 or later system. MSI won't magically download stuff on demand, and I don't think it does "this version _or better_ handling", but it will save you from having ten different copies of the VC++8.0 runtime on your machine, and I think will allow commonly redistributed libraries to have a common copy receive a security update via Windows Update.
if you develop nicely enough you can make the app in a mixed dev environment and just do final testing and deployment onto windows ce.
If you care about your user interface, you should get the application up and running on a real device ASAP and always use it as your guide. Emulators are very handy for when you're doing a rapid compile-run-code cycle during the early stage of developing a particular feature, and debugging.
Part of the point of using Visual Studio is testing your software and your deployment on the emulator beforehand so that you don't end up bricking an actual device and having to do a hard reset.
If you can fix it with a hard reset it's not a brick.
I don't believe such machines would be remotely vulnerably to a direct assault, but a weak host key would make logins to that machine vulnerable to a MITM attack.
It also lacked wireless..
on
iMac Turns 10
·
· Score: -1, Troll
While it's a royal pain, you can call Microsoft to activate and they will let you do so. The whole ten minute process really makes me want a work experience kid, though.
"100 Mbit/second" ethernet operates at 100*10^6 bits/sec, not 100*2^20 bits/sec. If every hard drive manufacturer under the sun is going to get hit up for adhering to their common convention (whether you agree with it or not, it's the same for every hard drive), why not Realtek, Intel, 3com and Cisco?
I don't understand how you could prove that it truly was an accident.
If it was suicide, you may be able to find some evidence of this, if he left a note, plans, etc behind in his accounts.
If it truly was an accident, you'd find no such thing. However, it would also be possible for this to be a suicide, and he simply didn't commit any of his plans to electronic media.
Slashdot Mirror
This is not the case.
Microsoft, by witholding the source, would be violating the copyright held by the people that wrote the OOM killer. They could then be sued by the copyright holders, and forced to seek settlement or ordered to pay damages - just like IBM could sue them if they lifted code out of AIX. It is very unlikely that a court would force them to license Windows under the GPL as a result.
I suspect their state can throw them in jail, but their vote stands.
Yo dawg I heard you like magnifying, so we put a gravitational lens in your gravitational lens.
Huh? Tune into something like the NatGeo channel; documentaries highlighting these professions and the risks are a dime a dozen.
Can't find it on Apple's site, but I'm pretty sure 10.3.x is unsupported and receives no security updates.
I read his book. Recommended.
I don't think the Australian Computer Society has any formal status. It's certainly not required by law, or any employer I've ever seen, to be accredited by them.
VirtualLock on Win32 and mlock on *nix already provide this functionality.
(Actually, both those functions will "lock memory" in the sense that accessing that memory will never cause a page fault, but that doesn't necessarily mean that the data won't be written out to disk preemptively. The Linux man page for mlock strongly implies that the data won't ever be paged out, but it could well be on Win32 and other *nix).
Perl is still a good fit for Extraction and Reporting.
In which case, from the BBC's perspective, surely H.264 is unencumbered?
You mean like Cobol on Cogs? :)
Optimization would be having seven reverse gears in your car to get optimal gas mileage in reverse.
Can't argue with Italian craftsmanship!
I think the emphasis is more on the historical significance, given the rarity of the tapes and the fact that the only digitised copy floating about has been patched.
Next up is patent-speak: a plurality of virion classifications..
Take a look at C:\Windows\WinSxS on an XP SP2 or later system. MSI won't magically download stuff on demand, and I don't think it does "this version _or better_ handling", but it will save you from having ten different copies of the VC++8.0 runtime on your machine, and I think will allow commonly redistributed libraries to have a common copy receive a security update via Windows Update.
Be careful not to take this point too generally.. some virora (such as Hep A) can survive for months outside of the human body.
My understanding is that this is a major factor in miserable performance when starting and stopping virtual machines.
What's the point? If you want OS X, run OS X.
If you care about your user interface, you should get the application up and running on a real device ASAP and always use it as your guide. Emulators are very handy for when you're doing a rapid compile-run-code cycle during the early stage of developing a particular feature, and debugging.
If you can fix it with a hard reset it's not a brick.
I don't believe such machines would be remotely vulnerably to a direct assault, but a weak host key would make logins to that machine vulnerable to a MITM attack.
.. and had less space than a Nomad.
While it's a royal pain, you can call Microsoft to activate and they will let you do so. The whole ten minute process really makes me want a work experience kid, though.
"100 Mbit/second" ethernet operates at 100*10^6 bits/sec, not 100*2^20 bits/sec. If every hard drive manufacturer under the sun is going to get hit up for adhering to their common convention (whether you agree with it or not, it's the same for every hard drive), why not Realtek, Intel, 3com and Cisco?
I don't understand how you could prove that it truly was an accident.
If it was suicide, you may be able to find some evidence of this, if he left a note, plans, etc behind in his accounts.
If it truly was an accident, you'd find no such thing. However, it would also be possible for this to be a suicide, and he simply didn't commit any of his plans to electronic media.