By copying files on the same parition, it only requires a change in the file table entry. Which is just a few bytes, the file itself stays where it is on the drive. By copying to a different partition, the full file needs to be read and written in its entireity to another location.
This setting appears to be disabled by default on Vista. (ie atime is not set). Which makes sense with the amount of thumbnail viewing that goes on in that OS.
You are ignoring reading from a cached file, that then requires a seek on the HD in order to write. If you read in 100 small files scattered about your HD that have been cached, I think you would notice a fair difference if the kernel does or doesn't have to seek to each file to write its atime.
All the "problems" of MS Windows which really are the fault of third party apps are starting to show signs in other OS's too. Hopefully this will start to shut those fanboys up who think that an OS is broken just because someone wrote a buggy application to run on it.
What if the 'other blogs' they 'pick up' on, are in turn using AideRSS to determine what to blog. The whole blogging thing really does seem like one giant feedback loop with only a few people generating actual useful content.
Especially if such article also has a "Digg it" link attached to it, and written with the sole intention of trying to get linked to by Digg for ad revenue. A Top x article with a "Digg it" link is a proven formula which works on the uneducated masses of Digg, but don't post it here.
Well you could take a look at the number of downloads of the most popular distros (eg ubuntu) from their primary download sites, and thn extrapolate from there. Its true that only a fraction of people running Linux will download that particular distro from that particular source; but as long as that fraction is relatively constant, you can still measure growth.
eg, you can extrapolate that Linux adoption has doubled if ubuntu downloads have doubled, even if you don't have the full figures.
Whos at fault? Your company. They are not using WSUS (http://technet.microsoft.com/en-us/wsus/default.a spx) or something similar. The technology is there, don't blame MS.
I would guess the bug affects some Ring0 OS type of service/instruction (such as switching in and out of protected mode, paging, faults etc) which MacOS doesn't use. Hence the patch is part of the OS. I speculate that its a workaround in the OS rather than a patch to the actual CPU.
I havent seen that much personally, but Ive been reduced to blocking people on IM who insist on using 'da' (the) and 'dat' (that). With 'wat' it's at least somewhat of an abbrv, it has most of the correct letters. But, 'da' and 'dat' is just plain wrong, and in my head I feel like I'm talking to some ghetto trash.
Exactly... they wouldn't bend over backwards to change their algorithm when someone elses product doesn't rank 1st for a search, especially if it was just new. Only when it's their own do they think 'something needs to change'.
If they just gave it a few months people would link to it, it would get older etc and its ranking would boost over time. That is the stock response they would give to anyone else that complained. I don't know why they think their algorithm has to list their product as first overnight just because its theirs.
But perhaps thats because the good earphones make crap sounds, sound good? You could argue that with the apple earphones, you need the higher bitrate to get a decent sound out of them.
Google are actaully making steps to correct this as of June 1st. It will make a pretty big impact on the web for those pages make up a pretty sizeable chunk of the internet.
This appears to be limited to content scanning, and isn't really a vulnerability in itself. Relying on content scanning to prevent an exploit to reach an exploitable system is a pretty bad idea, much better to fix the system than the extra layer of defense on the outside.
Content scanning is mostly useful against filtering known exploits, and is hardly meant to be your primary defense. Being able to bypass this scanning won't buy you much. If the content scanner is aware of an exploit it scans for, chances are so are the systems being targeted and are patched to protect against it.
Well I suspect it will be programmable. Imagine when holding ctrl and seeing the 'S' become 'Save', the 'V' become 'Paste' etc.
Also, within vi/vim, depending on whether you are in command or input mode, the 'hjkl' keys could be arrow keys (as well as appropriate symbols etc for the other keys).
Of course.. all this assumes you actually look at your keyboard while using it. Strange that the das keyboard has not markings on its keys at all, and is proud of it. There is some logic to it.. I suspect having displays on your keys will actually slow you down quite a bit.
Well then it is the 'device key' (or at least a key encrypted by that key) that is common between every DVD, even if the key is encrpyted multiple times by different device keys on a DVD.
Note that I said "the "processing key" which is in part used to derive the real key"
ie. "in part", so it is combined with the title key or whatever, it is part of the chain - even if its not the shared secret itself. But the point is there is still something common between all DVDs (device keys), even if its multiple things, and some of those things could be removed in future DVDs (ie device keys revoked). And the processing key that is being discussed is certainly not a symmetric key that is used to unlock all HD-DVD content - but its not possible to require a different key for every DVD without some 'shared secret' and still have players capable of playing them.
Something needs to be common between every DVD, otherwise you couldn't make players that can play every DVD.
The keys are actually different for each DVD, but they are derived from a common secret, and hashed and mixed about etc. The system is actually quite clever, and not a single symmetric key by any means. But no matter how you slice it, there will always need to be a common shared secret which is used to derive the means to unlock the media. That shared secret isn't the key itself, but the "processing key" which is in part used to derive the real key for each disc (to put it in very simple terms).
Thats all well and good except when you realise you can get your encoding done in half the time by using two threads. This then chokes both cores. You are then stuck with an unresponsive UI again.
So why not just use one core thats twice as fast, but without the hassle of writing multi-thread code?
Have you ever waited in line to buy a hamburger? Shouldn't you have used that time to save those people from malnutrition? In fact, what are you doing buying a burger, shouldnt that money have gone towards savining those people from malnutrition?
What are you doing posting on slashdot? Shouldnt you be out saving those people from malnutrition?
The WMF 'exploit' was actually 'by design' and supposed to execute code, it was a feature. Originally used to handle cases where an abort or something is required when rendering and the WMF file itself could contain a callback consisting of code to handle it. (I forget the exact details, but its something like that).
A buffer overflow is something completely different.
I just don't understand why an internet browser would be attempting to download and parse an.ANI file automatically without prompting the user.
The first thing I thought of when I read this article is the famous 'ctrl-alt-del' keyboard.
Originally a dig at MS and their OS and needing to restart it etc I guess.
Because those 'stupid' enough to go out and buy those stocks give the spammers incentive to continue. Spamming people like you and I who don't buy the crap.
Slashdot Mirror
By copying files on the same parition, it only requires a change in the file table entry. Which is just a few bytes, the file itself stays where it is on the drive. By copying to a different partition, the full file needs to be read and written in its entireity to another location.
This setting appears to be disabled by default on Vista. (ie atime is not set). Which makes sense with the amount of thumbnail viewing that goes on in that OS.
You are ignoring reading from a cached file, that then requires a seek on the HD in order to write. If you read in 100 small files scattered about your HD that have been cached, I think you would notice a fair difference if the kernel does or doesn't have to seek to each file to write its atime.
All the "problems" of MS Windows which really are the fault of third party apps are starting to show signs in other OS's too. Hopefully this will start to shut those fanboys up who think that an OS is broken just because someone wrote a buggy application to run on it.
What if the 'other blogs' they 'pick up' on, are in turn using AideRSS to determine what to blog. The whole blogging thing really does seem like one giant feedback loop with only a few people generating actual useful content.
Especially if such article also has a "Digg it" link attached to it, and written with the sole intention of trying to get linked to by Digg for ad revenue. A Top x article with a "Digg it" link is a proven formula which works on the uneducated masses of Digg, but don't post it here.
"Top 10" style article written in 5 minutes, check.
"Digg it" link at the bottom of the article, check.
Welcome to the new age of "publishing".
Well you could take a look at the number of downloads of the most popular distros (eg ubuntu) from their primary download sites, and thn extrapolate from there. Its true that only a fraction of people running Linux will download that particular distro from that particular source; but as long as that fraction is relatively constant, you can still measure growth.
eg, you can extrapolate that Linux adoption has doubled if ubuntu downloads have doubled, even if you don't have the full figures.
Whos at fault? Your company. They are not using WSUS (http://technet.microsoft.com/en-us/wsus/default.a spx) or something similar. The technology is there, don't blame MS.
Not the sharpest tool in the box.
I would guess the bug affects some Ring0 OS type of service/instruction (such as switching in and out of protected mode, paging, faults etc) which MacOS doesn't use. Hence the patch is part of the OS. I speculate that its a workaround in the OS rather than a patch to the actual CPU.
I havent seen that much personally, but Ive been reduced to blocking people on IM who insist on using 'da' (the) and 'dat' (that). With 'wat' it's at least somewhat of an abbrv, it has most of the correct letters. But, 'da' and 'dat' is just plain wrong, and in my head I feel like I'm talking to some ghetto trash.
This should be a poll... "mashup" would get my vote. Its a lame attempt to seem 'cool' but in reality makes my skin crawl reading it.
Exactly... they wouldn't bend over backwards to change their algorithm when someone elses product doesn't rank 1st for a search, especially if it was just new. Only when it's their own do they think 'something needs to change'.
If they just gave it a few months people would link to it, it would get older etc and its ranking would boost over time. That is the stock response they would give to anyone else that complained. I don't know why they think their algorithm has to list their product as first overnight just because its theirs.
But perhaps thats because the good earphones make crap sounds, sound good? You could argue that with the apple earphones, you need the higher bitrate to get a decent sound out of them.
Google are actaully making steps to correct this as of June 1st.
It will make a pretty big impact on the web for those pages make up a pretty sizeable chunk of the internet.
No-one else seems intersted in this story however: http://slashdot.org/firehose.pl?op=view&id=178417
This appears to be limited to content scanning, and isn't really a vulnerability in itself. Relying on content scanning to prevent an exploit to reach an exploitable system is a pretty bad idea, much better to fix the system than the extra layer of defense on the outside.
Content scanning is mostly useful against filtering known exploits, and is hardly meant to be your primary defense. Being able to bypass this scanning won't buy you much. If the content scanner is aware of an exploit it scans for, chances are so are the systems being targeted and are patched to protect against it.
Well I suspect it will be programmable. Imagine when holding ctrl and seeing the 'S' become 'Save', the 'V' become 'Paste' etc.
Also, within vi/vim, depending on whether you are in command or input mode, the 'hjkl' keys could be arrow keys (as well as appropriate symbols etc for the other keys).
Of course.. all this assumes you actually look at your keyboard while using it. Strange that the das keyboard has not markings on its keys at all, and is proud of it. There is some logic to it.. I suspect having displays on your keys will actually slow you down quite a bit.
Well then it is the 'device key' (or at least a key encrypted by that key) that is common between every DVD, even if the key is encrpyted multiple times by different device keys on a DVD.
Note that I said "the "processing key" which is in part used to derive the real key"
ie. "in part", so it is combined with the title key or whatever, it is part of the chain - even if its not the shared secret itself. But the point is there is still something common between all DVDs (device keys), even if its multiple things, and some of those things could be removed in future DVDs (ie device keys revoked). And the processing key that is being discussed is certainly not a symmetric key that is used to unlock all HD-DVD content - but its not possible to require a different key for every DVD without some 'shared secret' and still have players capable of playing them.
Something needs to be common between every DVD, otherwise you couldn't make players that can play every DVD.
The keys are actually different for each DVD, but they are derived from a common secret, and hashed and mixed about etc. The system is actually quite clever, and not a single symmetric key by any means. But no matter how you slice it, there will always need to be a common shared secret which is used to derive the means to unlock the media. That shared secret isn't the key itself, but the "processing key" which is in part used to derive the real key for each disc (to put it in very simple terms).
Thats all well and good except when you realise you can get your encoding done in half the time by using two threads. This then chokes both cores. You are then stuck with an unresponsive UI again.
So why not just use one core thats twice as fast, but without the hassle of writing multi-thread code?
Have you ever waited in line to buy a hamburger? Shouldn't you have used that time to save those people from malnutrition? In fact, what are you doing buying a burger, shouldnt that money have gone towards savining those people from malnutrition?
What are you doing posting on slashdot? Shouldnt you be out saving those people from malnutrition?
Think of the children!
Give me a fucking break. Mod parent down.
The WMF 'exploit' was actually 'by design' and supposed to execute code, it was a feature. Originally used to handle cases where an abort or something is required when rendering and the WMF file itself could contain a callback consisting of code to handle it. (I forget the exact details, but its something like that).
.ANI file automatically without prompting the user.
A buffer overflow is something completely different.
I just don't understand why an internet browser would be attempting to download and parse an
The first thing I thought of when I read this article is the famous 'ctrl-alt-del' keyboard. Originally a dig at MS and their OS and needing to restart it etc I guess.
So I'm assuming you never go for a swim? Never go in an airplane? I mean, what if your son was in a car crash.. you wouldn't be able to find out!
Because those 'stupid' enough to go out and buy those stocks give the spammers incentive to continue. Spamming people like you and I who don't buy the crap.