Re: File has hard-links. Detach before saving?
On Fri, 27 Oct 2006 07:18:18 +0200 Oswald Buddenhagen [EMAIL PROTECTED] wrote: now this dialog's default is Yes. But, for example, default Fedora installation has /etc/resolv.conf and /etc/sysconfig/networking/profiles/default/resolv.conf hardlinked. In this case I don't want to detach. So I propose default to be No. i'm strictly opposed. it would make working with cloned source trees harder. and i'm pretty sure that my use case is sort of more common than yours. :-P Why? Do you think there are more programmers using mc than system administrators? :) fwiw, i think the setup you described is totally braindead. it's just a matter of time until some other editor detaches the file. one of the files should be a symlink to the other one. Because of that I proposed to make default No, not Yes, because you may accidentally press Enter on Yes. Or should it be configurable? Any other opinions? Regards, Nerijus ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: File has hard-links. Detach before saving?
Any other opinions? I think the main question is what the main purpose of hardlinks is. Is it to (1) save disk space for files that actually happen to be the same at this very moment, but live separate lives? Or is it to be (2) a way to have one file accessible by more names, so that they live the same life? I think the general right answer is (2), and having two large source trees and diffing them is an exception. When doing so, you do not explicitely want hard links, this is just an easy way for saving 50% disk space and making diff run faster. For the case of diff this approach is not the best possible in theory, but we don't have better in practice. The running time could be drastically decreased if diff had an option to assume to files are the same if their size and modification time is the same. For the disk usage part, IMHO the operating system kernels and file systems should support an option to copy a whole file using copy-on-write techniques (similar to the one used in memory management when forking a process) so that it's completely transparent to the applications and the file is only physically copied when someone modifies it. So my vote goes for not detaching hard links by default. -- Egmont ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
File has hard-links. Detach before saving?
Hello, now this dialog's default is Yes. But, for example, default Fedora installation has /etc/resolv.conf and /etc/sysconfig/networking/profiles/default/resolv.conf hardlinked. In this case I don't want to detach. So I propose default to be No. Regards, Nerijus ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: File has hard-links. Detach before saving?
On Fri, Oct 27, 2006 at 05:12:00AM +0300, Nerijus Baliunas wrote: now this dialog's default is Yes. But, for example, default Fedora installation has /etc/resolv.conf and /etc/sysconfig/networking/profiles/default/resolv.conf hardlinked. In this case I don't want to detach. So I propose default to be No. i'm strictly opposed. it would make working with cloned source trees harder. and i'm pretty sure that my use case is sort of more common than yours. :-P fwiw, i think the setup you described is totally braindead. it's just a matter of time until some other editor detaches the file. one of the files should be a symlink to the other one. -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
