Re: [opensuse] "Cut" performance in kde vs "mv" in shell
rvJJax wrote:
(maybe i make a miscommunication in my first email. so let's make this clear.)
Sam Clemens wrote:
rvJJax wrote:
Konqueror have their own protocol/function (what they call it ?) for browsing directory. i.e: file:///, smb://, fish:// etc.
i have two file X and Y, X is 4 GB and Y is 3 GB, and i want to move it to another directory in the same machine and the same partition.
so i used konqueror. selecting this two files, and then pressing "CTRL-X", and then click the directory where i want to paste, and press "CTRL-V".
and then pop up window come, displaying progress bar, saying it take more than 3 minutes or more.
That's because konqueror is, for each file, reading, byte for byte, each file, and CREATING a new file in the new location, and then deleting the old files Very inefficient, and... wasteful. The Konqueror developers SHOULD have written the code to fork off one or more mv commands, because mv is optimized (unix philosophy...a command does ONE thing, and does it VERY WELL), whereas Konqueror's "reinvention of the wheel" has produced a somewhat round-ish polygon instead of the efficient, circular object which is desired.
i just realized that "Cut" and "Paste", when the "source" and "destination" is in the same machine and partition, is like doing download from another machine.
and then, i try it back in shell using Konsole, by using "mv" command, is just take a second.
Because, as explained before, all the mv command does is link the files into the new directory, and then unlink them from their original directory. This is a VERY simple operation -- only a couple of records changed in two directories, and disk write consists of only a few blocks
When i go to shell and do,
# mv x y ../dir
is just like a second, maybe less (where x is 4GB and y is 3GB)
from my perspective view this is a bug. but maybe other's have different view.
Why would that be a bug that mv works so quickly? is not mv is issue here, it is kde "Cut 'n Paste" one. all mv does is unlink a file and then re-link the file. So to mv two files doesn't take anywhere near a second, unless the new directory is on a different filesystem (partition).
i know that.
Then what are you talking about?
Seriously -- the Microsoft way of moving a file by performing a copy, even from one directory to another directory on the same partition is a bug...there's no reason to perform all of that I/O.
that is what happen in my kde / konqueror. since i am usually updated my kde in the latest version in repos, i think this problem is only occur in my kde box. that's way i asking other if they have the same problem like above.
????
question 1: so what do you think ? bug or not ? question 2: if this is a bug where should i report, bugzilla.novell.com first or going directly to bugs.kde.org ?
Here's some better questions: What illicit drugs are you taking? What amounts of those drugs are you using?
i take coffea arabica one cup every morning. is it dangerous ?
Apparently for you. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, May 20, 2008 at 9:35 PM, Washington Irving <washton.irving@gmail.com> wrote:
Because, as explained before, all the mv command does is link the files into the new directory, and then unlink them from their original directory.
This is a VERY simple operation -- only a couple of records changed in two directories, and disk write consists of only a few blocks
The Kong developers took the easy way out. Their method works across partitions, drives, networks connections (ftp etc). mv in a shell only works on file systems. And it doesn't do the link + un-link across partitions, but you knew that. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Mittwoch, 21. Mai 2008 08:53:15 schrieb John Andersen:
The Kong developers took the easy way out. Their method works across partitions, drives, networks connections (ftp etc).
mv in a shell only works on file systems. And it doesn't do the link + un-link across partitions, but you knew that.
Well I think it should be possible to determind which methode out of severals would be the right one if the adress is known by konqueror. So why not fill a feature request? Greetings Michael
John Andersen wrote:
mv in a shell only works on file systems. And it doesn't do the link + un-link across partitions, but you knew that.
That's not true. mv is happy to move cross-filesystem. Not on all OS to be sure but it does on Suse. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dave Howorth wrote:
John Andersen wrote:
mv in a shell only works on file systems. And it doesn't do the link + un-link across partitions, but you knew that.
That's not true. mv is happy to move cross-filesystem. Not on all OS to be sure but it does on Suse.
The directory entry for a file is the "link" or hard link which can only exist on the same partition as the file. If the file is moved to another partition, it has to be copied and then the original deleted. If the move is on the same partition, then you simply have to copy & delete the directory entry. Don't get confused with symbolic links, which can work with different partitions. -- Use OpenOffice.org <http://www.openoffice.org> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 21 May 2008 10:13, James Knott wrote:
Dave Howorth wrote:
John Andersen wrote:
mv in a shell only works on file systems. And it doesn't do the link + un-link across partitions, but you knew that.
That's not true. mv is happy to move cross-filesystem. Not on all OS to be sure but it does on Suse.
The directory entry for a file is the "link" or hard link which can only exist on the same partition as the file. If the file is moved to another partition, it has to be copied and then the original deleted. If the move is on the same partition, then you simply have to copy & delete the directory entry. Don't get confused with symbolic links, which can work with different partitions.
You're both right, of course. Everything James says about links, (both hard and symbolic) are true. It's also the case that mv will act like copy (followed by the removal of the original) when the destination directory is on a different file system than the source file(s). Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, May 21, 2008 at 8:07 AM, Dave Howorth <dhoworth@mrc-lmb.cam.ac.uk> wrote:
John Andersen wrote:
mv in a shell only works on file systems. And it doesn't do the link + un-link across partitions, but you knew that.
That's not true. mv is happy to move cross-filesystem. Not on all OS to be sure but it does on Suse.
Cheers, Dave --
I didn't say it would not move "cross-filesystems". I said it wouldn't move across raw networks (It requires a mounted filesystem). You can't mv to/from an ftp site (for exmple). And the speed trick (link-unlink) only works within a single partition. (Which is a great time saver, and the only situation where mv is faster, and should have been done by Kong. Had Kong simply handed off a drag and drop from mounted file systems to mv it would have been much faster. But apparently doing that simple test (is source and desitination it on a mounted filesystem) was something the kong developers simply did not do. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote:
On Wed, May 21, 2008 at 8:07 AM, Dave Howorth <dhoworth@mrc-lmb.cam.ac.uk> wrote:
John Andersen wrote:
mv in a shell only works on file systems. And it doesn't do the link + un-link across partitions, but you knew that. That's not true. mv is happy to move cross-filesystem. Not on all OS to be sure but it does on Suse.
Cheers, Dave --
I didn't say it would not move "cross-filesystems".
I said it wouldn't move across raw networks (It requires a mounted filesystem). You can't mv to/from an ftp site (for exmple).
Huh? I'm confused. Actually, in the context of this thread, this is the first you've mentioned anything about raw networks or ftp sites.
And the speed trick (link-unlink) only works within a single partition. (Which is a great time saver, and the only situation where mv is faster, and should have been done by Kong. Had Kong simply handed off a drag and drop from mounted file systems to mv it would have been much faster. But apparently doing that simple test (is source and desitination it on a mounted filesystem) was something the kong developers simply did not do.
All to save a few lines of code :-/ Or laziness. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, May 21, 2008 at 12:54 PM, Washington Irving <washton.irving@gmail.com> wrote:
John Andersen wrote:
On Wed, May 21, 2008 at 8:07 AM, Dave Howorth <dhoworth@mrc-lmb.cam.ac.uk> wrote:
John Andersen wrote:
mv in a shell only works on file systems.
See the above.
Huh? I'm confused.
Actually, in the context of this thread, this is the first you've mentioned anything about raw networks or ftp sites.
I specifically mentioned ftp upthread. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dave Howorth wrote:
John Andersen wrote:
mv in a shell only works on file systems. And it doesn't do the link + un-link across partitions, but you knew that.
That's not true. mv is happy to move cross-filesystem. Not on all OS to be sure but it does on Suse.
It does so on ANY *nix platform. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote:
On Tue, May 20, 2008 at 9:35 PM, Washington Irving <washton.irving@gmail.com> wrote:
Because, as explained before, all the mv command does is link the files into the new directory, and then unlink them from their original directory.
This is a VERY simple operation -- only a couple of records changed in two directories, and disk write consists of only a few blocks
The Kong developers took the easy way out. Their method works across partitions, drives, networks connections (ftp etc).
mv in a shell only works on file systems. And it doesn't do the link + un-link across partitions, but you knew that.
Since when? If the destination location is on another partition, mv does a copy and remove. If you don't believe me, try it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, May 21, 2008 at 12:50 PM, Washington Irving <washton.irving@gmail.com> wrote:
John Andersen wrote:
On Tue, May 20, 2008 at 9:35 PM, Washington Irving <washton.irving@gmail.com> wrote:
Because, as explained before, all the mv command does is link the files into the new directory, and then unlink them from their original directory.
This is a VERY simple operation -- only a couple of records changed in two directories, and disk write consists of only a few blocks
The Kong developers took the easy way out. Their method works across partitions, drives, networks connections (ftp etc).
mv in a shell only works on file systems. And it doesn't do the link + un-link across partitions, but you knew that.
Since when?
If the destination location is on another partition, mv does a copy and remove.
If you don't believe me, try it. --
How can you quote me and STILL get it wrong?? I said: "it doesn't do the link + un-link across partitions," -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Dave Howorth -
James Knott -
John Andersen -
M. Skiba -
Randall R Schulz -
Washington Irving