[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Res: Konqueror to inform about hard links?
From: "Michael Howell" <mhowell123 () gmail ! com>
Date: 2008-08-29 0:57:29
Message-ID: a2927be10808281757h70ce1ffeve9931fe1680ff7b0 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Thu, Aug 28, 2008 at 4:43 PM, Matthew Woehlke <
mw_triad@users.sourceforge.net> wrote:
> I didn't say anything about cross-filesystem... but bind mounts can put
> one hunk of an FS in one place, and another somewhere else (and I don't
> know of any reason a hardlink couldn't span this since it's still the
> same physical FS). Similar with NFS mounts, the 'same filesystem' would
> apply, I assume, the the server, which need not export the entire FS.
Wait. I did't understand you correctly. 'mount --bind' allows you to place
on chunk of a file system somewhere else. As a result, /home/ftp and
/home/someone/ftp (as a use case is to allow ways out of chroot jails) may
be the same physical directories. In that way, yes 'mount --bind' is similar
to hard linking. NFS, of course, can be used to allow a file system to be
accessible to two computers. However, 'mount --bind' and NFS are all on top
the the physical file system, in the VFS. Hard links exist in the physical
file system, so for example, hard links don't work on some file systems
(i.e. Windows ones), similar to symbolic links which are also part of the
file systems. Also, 'mount --bind' and NFS can easily be traced (just run
'mount' and you'll see both of them).
And yes, it should be possible to hard link between files on multiple 'mount
--bind' links, as long as they are both on the same physical file system.
However, I just tried it and it didn't work.
--
Michael Howell
mhowell123@gmail.com
[Attachment #5 (text/html)]
<div dir="ltr">On Thu, Aug 28, 2008 at 4:43 PM, Matthew Woehlke <span \
dir="ltr"><<a href="mailto:mw_triad@users.sourceforge.net">mw_triad@users.sourceforge.net</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;"> I didn't say anything about cross-filesystem... but bind \
mounts can put<br> one hunk of an FS in one place, and another somewhere else (and I \
don't<br> know of any reason a hardlink couldn't span this since it's \
still the<br> same physical FS). Similar with NFS mounts, the 'same \
filesystem' would<br> apply, I assume, the the server, which need not export the \
entire FS.</blockquote><div>Wait. I did't understand you correctly. 'mount \
--bind' allows you to place on chunk of a file system somewhere else. As a \
result, /home/ftp and /home/someone/ftp (as a use case is to allow ways out of chroot \
jails) may be the same physical directories. In that way, yes 'mount --bind' \
is similar to hard linking. NFS, of course, can be used to allow a file system to be \
accessible to two computers. However, 'mount --bind' and NFS are all on top \
the the physical file system, in the VFS. Hard links exist in the physical file \
system, so for example, hard links don't work on some file systems (i.e. Windows \
ones), similar to symbolic links which are also part of the file systems. Also, \
'mount --bind' and NFS can easily be traced (just run 'mount' and \
you'll see both of them).<br> <br></div></div>And yes, it should be possible to \
hard link between files on multiple 'mount --bind' links, as long as they are \
both on the same physical file system. However, I just tried it and it didn't \
work.<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