|
On Friday 29 August 2008, macintoshzoom wrote: > > For your particular case, I suggest you trust your distribution to do > > the sensible thing, and use the package manager to remove unneeded > > packages. > > Yes I trust my OpenBSD, but not blindly. > I am building an OpenBSD-KDE distro. > And I want to know why it's storing those GB files hard-linked to > different subfolders (in such way that I can't know via standard KDE > tools what is the real space left free on my box, that this is YES a > matter of issue for me. Well if all you are really worried about is the amount of free disk space then Konqueror/Dolphin and tools such KDiskFree will give you an accurate assessment. You can also use the "du" command at the command line to determine amount of space used by the current directory tree, or "df" to determine free space on a partition. I don't work on OpenBSD but I would imagine that the reason they use hard-linking is because it's basically a "free" copy. Because of this they can arrange the data in different hierarchies all at the same time without using any extra disk space. And unlink symlinks they are all a "real" file so you don't have to worry about accidentally breaking things by deleting the wrong file and all of a sudden 3 other symlinks end up broken. But yes, this does mean that it is harder to free up disk space just by unlinking a file since you have to ensure that it is the last pointer to the inode. Also keep in mind like someone else pointed out that processes can have inodes open even if no files point to the inode anymore. In that case the inode would not go away (and free up that space) until all the processes using that inodes were killed. Regards, - Michael Pyne |
Attachment:
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<