TorrentFreak reports:
After doing without an element needed for safe harbor protection, 4chan has just introduced an official DMCA policy. The decision comes in the wake of the celebrity photo leak known as The Fappening and 4chan users' connections to it. In the meantime, the leaked image library has clocked a million torrent downloads.
While most US-based user-generated content websites should not entertain operating without safe harbor, the way 4chan is set up provides a unique scenario in respect of infringing content being posted by its users.
“Threads expire and are pruned by 4chan’s software at a relatively high rate. Since most boards are limited to eleven or sixteen pages, content is usually available for only a few hours or days before it is removed,” the site’s FAQ explains.
(Score: 2) by stderr on Thursday September 04 2014, @04:41PM
The shell redirects stdout before the commands are started. You would end up with a file called "/dev/{}".
alias sudo="echo make it yourself #" #
(Score: 2) by DECbot on Thursday September 04 2014, @05:51PM
I see, quite the conundrum. The solution I can think of is absurd:
find /dev/ -name 'sd*' -print0 | xargs -n1 -0 -I {} echo "/dev/zero > /dev/{}" | xargs -n1 -0 cat
I'm not even sure it would work. If this was c/c++/bashscript, you would do a for each, but I'm looking for a nice bash one-liner.
cats~$ sudo chown -R us /home/base
(Score: 2) by stderr on Friday September 05 2014, @12:33AM
The first xargs doesn't output any '\0', so I don't know why you would add a -0 to the second xargs. Not sure why you would use cat in the second xargs either.
You could replace the complete second xargs with a sh -s (or maybe sudo -s if that's your thing).
I would probably use a -maxdepth on the find to avoid writing to e.g. /dev/foo/bar/baz/sdqux. Or more likely just use something like ls -1 /dev/sd*. The devices don't have weird names (and if they do, sucks to be you) so no need for stuff like -print0 and -0 at all. The /dev/ is already part of the {}, so remove that. If I were on a system where you would need sudo, I might use sudo tee {} > /dev/null instead of > {}, to have as little as possible running as root. I might even use tee on systems where sudo ain't needed.
All in all, I would probably use something like:
ls -1 /dev/sd* | xargs -i echo "tee {} < /dev/zero > /dev/null" | sh -s
Or simply use good, old dd:
ls -1 /dev/sd* | xargs -i dd if=/dev/zero of={}
alias sudo="echo make it yourself #" #
(Score: 2) by stderr on Friday September 05 2014, @12:44AM
Writing to /dev/sda and /dev/sdb probably doesn't have to wait on each other, so
( ls -1 /dev/sd* | xargs -i echo "dd if=/dev/zero of={} &" ; echo wait ) | sh -s
could also be used, if you want a little speed-up.
The wait part is of course only needed if you (like me in this case) would prefer NOT to get the prompt back before ALL the writing is done.
alias sudo="echo make it yourself #" #
(Score: 2) by DECbot on Friday September 05 2014, @03:23AM
Thanks for the reply. My bashfu has gone to mush as I only get to touch windows, java, and MS access if I'm lucky enough to code that month. dd makes a lot more sense than cat. That is the obvious choice. Not sure where I would ever use it. Perhaps as a cron job that keeps getting delayed by some warrant cannery. Or maybe employment insurance at some fictional Linux/Unix/Mac shop where I dream of working.
cats~$ sudo chown -R us /home/base