This is a valid point. Personally, though, I buy nice shirts for $5 from goodwill (seems I usually end up with Ralph Lauren, though I never look for any brand in particular). It's cheap because the stores can't sell last season's shirts, and they'd rather take a tax write off giving them to Goodwill than pay to ship them back to the factory.
Actually, a lot of designer labels will destroy their product rather than have homeless people walking around in their gear. This turns up in the news as a "shocking disgrace" story every few years and then people promptly stop caring again.
Those shirts you buy are more than likely unwanted Christmas gifts or something that was bought and never worn rather than remaindered goods.
Unless you have overwritten the area on the physical disk that contained the data, multiple times, the data can still be recovered.
A simple dd command with one run of 0's will permanently delete the data on a disk. Once upon a time it may have been possible to read the data after a single write but it is no longer possible. This challenge has been standing for quite some time and even though this is not proof of my assertion I am certain the multiple passes of writes thing is complete garbage.
good thing I explicitly disable autorun for every Windows computed I've ever configured for someone.
I hope you didn't just use tweakUI or similar to disable it. Conflicker gets past that level of "disabling" autorun and installs anyway when windows parses the autorun files.
. just means the current directory when specifying a path, the reason you need to provide it when executing something in the current directory is because most sane people don't put . in their $PATH as it is a fairly big security risk.
In other words the following commands are equivalent:
If filtering like this begins to become common then I would imagine we would see systems similar to the large botnets start to emerge for torrent trackers, using fast flux and the likes to keep domains and IP addresses moving.
Slashdot Mirror
This is a valid point. Personally, though, I buy nice shirts for $5 from goodwill (seems I usually end up with Ralph Lauren, though I never look for any brand in particular). It's cheap because the stores can't sell last season's shirts, and they'd rather take a tax write off giving them to Goodwill than pay to ship them back to the factory.
Actually, a lot of designer labels will destroy their product rather than have homeless people walking around in their gear. This turns up in the news as a "shocking disgrace" story every few years and then people promptly stop caring again.
Those shirts you buy are more than likely unwanted Christmas gifts or something that was bought and never worn rather than remaindered goods.
Unless you have overwritten the area on the physical disk that contained the data, multiple times, the data can still be recovered.
A simple dd command with one run of 0's will permanently delete the data on a disk. Once upon a time it may have been possible to read the data after a single write but it is no longer possible. This challenge has been standing for quite some time and even though this is not proof of my assertion I am certain the multiple passes of writes thing is complete garbage.
good thing I explicitly disable autorun for every Windows computed I've ever configured for someone.
I hope you didn't just use tweakUI or similar to disable it. Conflicker gets past that level of "disabling" autorun and installs anyway when windows parses the autorun files.
FYI, All Australian DVD players are region free or can be easily made region free.
. just means the current directory when specifying a path, the reason you need to provide it when executing something in the current directory is because most sane people don't put . in their $PATH as it is a fairly big security risk.
In other words the following commands are equivalent:
cp ./somefile.mp3 ./../../somedirectorythathappenstobe2levelsup/
cp somefile.mp3 ../../somedirectorythathappenstobe2levelsup/
note that ./cp would be different to cp since cp is probably in /bin/cp
VB.NET is equally as powerful as C#. You're comment shows your ignorance
YOUR comment shows YOUR ignorance.
If filtering like this begins to become common then I would imagine we would see systems similar to the large botnets start to emerge for torrent trackers, using fast flux and the likes to keep domains and IP addresses moving.