[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Konqueror to inform about hard links?
From: "Michael Howell" <mhowell123 () gmail ! com>
Date: 2008-08-29 13:19:27
Message-ID: a2927be10808290619wa3461edkd5b23a5f0665bd15 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Fri, Aug 29, 2008 at 2:23 AM, macintoshzoom <macintoshzoom@lavabit.com>wrote:
> To make konqueror regularly or by demand "scan the whole filesystem" is
> possible? Is that a hard task?
The easiest and probably best way is to somehow have strigi index the inode
number. The other way would involve a kded module or an entirely new daemon.
Showing a different icon for files with more than one inode, and using
strigi to look up the other names, would make sense.
Yes I trust my OpenBSD, but not blindly.
Makes perfect sense, particularly since OpenBSD is a really
security-oriented BSD distribution.
> 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.
Do you know why they aren't using soft links? They'd be easier to manage,
for sure. It's also easier to archive a system with soft links as opposed to
hard links (e.g. cp -R and tar -c give you multiple copies of the same
file).
--
Michael Howell
mhowell123@gmail.com
[Attachment #5 (text/html)]
<div dir="ltr">On Fri, Aug 29, 2008 at 2:23 AM, macintoshzoom <span dir="ltr"><<a \
href="mailto:macintoshzoom@lavabit.com">macintoshzoom@lavabit.com</a>></span> \
wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" \
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; \
padding-left: 1ex;">
To make konqueror regularly or by demand "scan the whole filesystem" is<br>
possible? Is that a hard task?</blockquote><div>The easiest and probably best way is \
to somehow have strigi index the inode number. The other way would involve a kded \
module or an entirely new daemon. Showing a different icon for files with more than \
one inode, and using strigi to look up the other names, would make sense.<br> \
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Yes I trust my OpenBSD, but not \
blindly.</blockquote><div>Makes perfect sense, particularly since OpenBSD is a really \
security-oriented BSD distribution. <br></div><div> </div><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;">
I am building an OpenBSD-KDE distro.<br>
And I want to know why it's storing those GB files hard-linked to<br>
different subfolders (in such way that I can't know via standard KDE<br>
tools what is the real space left free on my box, that this is YES a<br>
matter of issue for me.</blockquote><div>Do you know why they aren't using soft \
links? They'd be easier to manage, for sure. It's also easier to archive a \
system with soft links as opposed to hard links (e.g. cp -R and tar -c give you \
multiple copies of the same file).<br> </div></div> <br><br><br \
clear="all"><br>-- <br>Michael Howell<br><a \
href="mailto:mhowell123@gmail.com">mhowell123@gmail.com</a><br> </div>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic