On Tue, 24 Mar 2009, John H. Robinson, IV wrote:
> I'm curious as to why no one is looking at the index node numbers
> themselves.
Because the second field of "ls -l" is "hardlink count" and is enough
alone to conclude:
> 7342643 -rwxr-xr-x 2 root root 101992 Apr 4 2008 ls
Jerome Warnier wrote:
> Peter Samuelson wrote:
> > [Jerome Warnier]
> >
> >> I don't know however how dpkg treats hardlinks. Does it "break" the
> >> hardlink before replacing a file or does it replace the file whatever
> >> its real nature is?
> >>
> >
> > You know, given the time it takes
On Tue, Mar 24, 2009 at 03:11:17PM +0100, Jerome Warnier
wrote:
> Mike Hommey wrote:
> > On Tue, Mar 24, 2009 at 02:34:09PM +0100, Jerome Warnier
> > wrote:
> >
> >> Giacomo A. Catenazzi wrote:
> >>
> >>> Jerome Warnier wrote:
> >>>
> Raphael Hertzog wrote:
>
>
Jerome Warnier (Di 24 Mär 2009 14:58:35 CET):
>
> The question here is: which one is the hardlink to the other? :-P
You can't distinguish hardlinks from each other - in the sense of
original and link...
They are just different directory entries referring to the same file system
object.
Bes
Mike Hommey wrote:
> On Tue, Mar 24, 2009 at 02:34:09PM +0100, Jerome Warnier
> wrote:
>
>> Giacomo A. Catenazzi wrote:
>>
>>> Jerome Warnier wrote:
>>>
Raphael Hertzog wrote:
> On Tue, 24 Mar 2009, Jerome Warnier wrote:
>
>
>> For fi
Steve McIntyre wrote:
> In article <49c8dcdb.90...@beeznest.net> you write:
>
>> Before the upgrade, the file is a hardlink (because I hardlinked it
>> manually), then it tries to upgrade the file/hardlink. Does it "break"
>> the hardlink* before upgrading the file or does it overwrite the
>> fi
On Tue, Mar 24, 2009 at 02:34:09PM +0100, Jerome Warnier
wrote:
> Giacomo A. Catenazzi wrote:
> > Jerome Warnier wrote:
> >> Raphael Hertzog wrote:
> >>> On Tue, 24 Mar 2009, Jerome Warnier wrote:
> >>>
> For files from packages, though, deduplication might be a good
> idea, as
>
In article <49c8dcdb.90...@beeznest.net> you write:
>Before the upgrade, the file is a hardlink (because I hardlinked it
>manually), then it tries to upgrade the file/hardlink. Does it "break"
>the hardlink* before upgrading the file or does it overwrite the
>file/hardlink and all of its "siblings"
Giacomo A. Catenazzi wrote:
> Jerome Warnier wrote:
>> Raphael Hertzog wrote:
>>> On Tue, 24 Mar 2009, Jerome Warnier wrote:
>>>
For files from packages, though, deduplication might be a good
idea, as
dpkg is supposedly the only one to ever modify the files (under
/usr for
>>>
Peter Samuelson wrote:
> [Jerome Warnier]
>
>> I don't know however how dpkg treats hardlinks. Does it "break" the
>> hardlink before replacing a file or does it replace the file whatever
>> its real nature is?
>>
>
> You know, given the time it takes to type a 20-line email, including
> fi
[Jerome Warnier]
> I don't know however how dpkg treats hardlinks. Does it "break" the
> hardlink before replacing a file or does it replace the file whatever
> its real nature is?
You know, given the time it takes to type a 20-line email, including
finding the appropriate Wikipedia article to li
On 2009-03-24, Mike Hommey wrote:
> On Tue, Mar 24, 2009 at 02:09:25PM +0100, Raphael Hertzog
> wrote:
>> On Tue, 24 Mar 2009, Jerome Warnier wrote:
>> > For files from packages, though, deduplication might be a good idea, as
>> > dpkg is supposedly the only one to ever modify the files (under /
Jerome Warnier wrote:
Raphael Hertzog wrote:
On Tue, 24 Mar 2009, Jerome Warnier wrote:
For files from packages, though, deduplication might be a good idea, as
dpkg is supposedly the only one to ever modify the files (under /usr for
example).
I don't know however how dpkg treats hardlinks. D
On Tue, Mar 24, 2009 at 02:09:25PM +0100, Raphael Hertzog
wrote:
> On Tue, 24 Mar 2009, Jerome Warnier wrote:
> > For files from packages, though, deduplication might be a good idea, as
> > dpkg is supposedly the only one to ever modify the files (under /usr for
> > example).
> > I don't know how
Raphael Hertzog wrote:
> On Tue, 24 Mar 2009, Jerome Warnier wrote:
>
>> For files from packages, though, deduplication might be a good idea, as
>> dpkg is supposedly the only one to ever modify the files (under /usr for
>> example).
>> I don't know however how dpkg treats hardlinks. Does it "br
On Tue, 24 Mar 2009, Jerome Warnier wrote:
> For files from packages, though, deduplication might be a good idea, as
> dpkg is supposedly the only one to ever modify the files (under /usr for
> example).
> I don't know however how dpkg treats hardlinks. Does it "break" the
> hardlink before replaci
Hi guys,
I'm currently thinking about deduplication[1] on my Debian systems.
As you probably know, the whole thing about deduplication is that
replacing files with content with hardlink to other file(s) with the
exact same content is sometimes a good idea, at least to regain
(uselessly used) disk
17 matches
Mail list logo
