The Following User Says Thank You to jedi For This Useful Post: | ||
![]() |
2011-08-03
, 14:14
|
Posts: 87 |
Thanked: 46 times |
Joined on Nov 2010
@ lisbon, portugal
|
#22
|
![]() |
2011-08-03
, 14:16
|
Posts: 122 |
Thanked: 2 times |
Joined on Jul 2010
@ Latvia, Ireland
|
#23
|
orCode:find . -name "*.jpg" -print | xargs cp -R {} /media/mmc1 \;
Or somthingCode:find . -name "*.jpg" -print | xargs -I{} cp "{}" /media/mmc1
lol, I dunno.
![]() |
2011-08-03
, 14:18
|
Posts: 122 |
Thanked: 2 times |
Joined on Jul 2010
@ Latvia, Ireland
|
#24
|
What do you mean it didn't help?
There is a more or less simple way to do this, half the work has been done for you. Just fiddle the above till it works.Code:find . -name "*.jpg" -print0 | xargs -0 -I {} cp {} /media/mmc1
Read up about find, xargs, cp, what all the flags do etc.
Must try harder FFS!
![]() |
2011-08-03
, 14:25
|
Posts: 122 |
Thanked: 2 times |
Joined on Jul 2010
@ Latvia, Ireland
|
#25
|
Seems from what vi_ and jedi have said, you've posted about this already. That is _not_ good behaviour. If you don't get the help you want from the question you ask, re-phrase it. If you've been waiting a while, by all means bump the thread. The nature of the problem will determine the urgency e.g. device still in reboot loop after taking the battery out and putting back in, as well as expecting a call about a new job - ok, repost in an hour. But don't start a new thread just because you didn't get a reply. The only caviat might be that there are occasions where you will post at the end of an old/dead thread and get a lacklustre response, in these cases starting a new thread might be more appropriate because you can ask the question more precisely to your needs. Whatever you do: Use TMO with care: it's fragile.
Not sure it's wise to reward this sort of thing but publishing your findings will probably help others ... lets see what can be done:
What version of busy box are you running?
What are you trying to execute with 'exec'?
![]() |
2011-08-03
, 14:33
|
Posts: 268 |
Thanked: 1,053 times |
Joined on May 2010
@ The Netherlands
|
#26
|
Busybox doesn't work with -exec when you type in x-term so what I must do to get -exec working.. please help guys.. Can't get command done
The Following User Says Thank You to iDont For This Useful Post: | ||
![]() |
2011-08-03
, 14:48
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#27
|
find /home/user/ -name "*.jpg" -print | while read this; do cp $this /media/mmc1/; done
The Following User Says Thank You to vi_ For This Useful Post: | ||
![]() |
2011-08-03
, 16:48
|
Posts: 122 |
Thanked: 2 times |
Joined on Jul 2010
@ Latvia, Ireland
|
#28
|
![]() |
2011-08-03
, 17:46
|
|
Posts: 1,411 |
Thanked: 1,330 times |
Joined on Jan 2010
@ Tatooine
|
#29
|
When i try moving files jpg to my MicroSD true x-term it moves couple of them but not all of them.. And space left for microSD is 1.5 gb I have 2 gb MicroSD..
Why does x-term says for all other image jpg files : - No space left on device!!
wtf?? :O help please guys
![]() |
2011-08-03
, 18:02
|
Posts: 1,258 |
Thanked: 672 times |
Joined on Mar 2009
|
#30
|
The Following 3 Users Say Thank You to shadowjk For This Useful Post: | ||
You mean the find command provided by busybox does not support the -exec parameter. This has already been explained and more than one work-around already provided.
May the source be with you.