|
|
|
|
|
by otakucode
4126 days ago
|
|
Yes, that is precisely what I mean. I should have been clearer. Ideally if a copy operation involved busy devices that would be the only time they would queue, but I would settle for a background processing queue that prevented long-running operations from running concurrently. I've never seen anything smart enough to base 'concurrent or not' off of what device a piece of the filesystem is on though, so I'll give that a pass. I'd also really like a file manager that had a little daemon (or interacted with an rsync daemon or such already running) on boxes over the network so when I say 'copy from network share A to share B' the data never has to transit my desktop but goes directly from A to B. I think about file manager a lot. I have a long wishlist... |
|