commandlinefu.com is the place to record those command-line gems that you return to again and again.
Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/
You can sign-in using OpenID credentials, or register a traditional username and password.
First-time OpenID users will be automatically assigned a username which can be changed after signing in.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
In my job I often have to deal with moving 100,000 files or more. A mv won't do it because there are too many. This will move everything in the current directory to the target path.
There is 1 alternative - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
That will be _very_ slow. I suggest you:
find -maxdepth 1 | xargs mv --target=destdirfind -maxdepth 1matches '.' ... so you'll get
mv: cannot move `.' to `/home/rpolli/.local/.': Device or resource busy
find -maxdepth 1 -mindepth 1 | xargs mv --target=destdir
Or use:
find /dir/with/largefiles -type f -name "*.gz" -exec mv {} /targetdir \;
wtf. Why not
mv * <target_path>It does exactly what it is supposed to do.
Ok sorry for my last message. I didn't read the description carefully ("A mv won't do it because there are too many.")
However mv only works perfectly well with 200 000 files under debian and cygwin.
Which system are you using ? Is the problem related to the size of the file ?
It sounds strange to my that gnu mv would actually need a patch.
After a bit of investigation:
gnu mv can handle the max size of a signed int.
However the number of arguments that can be given to a command is limited by ARG_MAX:
http://www.in-ulm.de/~mascheck/various/argmax/
There's no such limitation since linux 2.6.23