From: David Masover <jedi@ninja.dynup.net>
To: reiserfs-list@namesys.com
Subject: more about links (was Re: A bold idea (Re: Carrying Attributes too Far))
Date: Tue, 09 Dec 2003 20:12:22 -0600 [thread overview]
Message-ID: <3FD68106.7050800@ninja.dynup.net> (raw)
In-Reply-To: <1070956991.3579.12.camel@schlappix.schnulli.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Heinz-Josef Claes wrote:
>Am Mo, 2003-12-08 um 21.54 schrieb Boyd Waters:
>
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Heinz-Josef Claes wrote:
>>
>>| I think hard linking directories is a very good idea. The should be a
>>| count for the number of hard links and it should be handled like with
>>| normal files. I directly have an application with would have a great
>>| benefit of this kind of hard linked directories, but up to now they are
>>| not available in linux :-(
>>
>>I use
>>
>>mount -o bind path/to/subdirectory path/to/mountpoint
>>
>>as a sort-of "hard-link" directories...
>>
>>
>>
>Yes, that would look a little bit like a hard link. But I want to use it
>as a possiblity for my backup tool (see below). It makes a backup to
>another hard disk and hard links to files with a contents which is
>already in the backup. If a hole directory had not changed, I could make
>a link to the previous one and that's all. Now I have to mkdir the
>directories and hard link every single file. I could use much less space
>if there were an op
>
If a symlink really won't work for you, have the whole directory be a
hardlink farm. Trust me, it's cleaner that way.
My backup system involves using rsync to do that -- first I do a 'cp
- -al' from the old generation dir to the new one. Then I rsync over my
current files. Only the files that have changed are updated.
If that still isn't enough, use symlinks. Some things which used to be
hardlinks on my distro have been changed to symlinks, and I like the change.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBP9aBCgisZLIF6uqOAQK0YA/6AxzwZ33y1n+NVY/5WbJhFz30tcQDLcy4
l/5d8BQi75JGaGphuhb40+wh9omNQ+WBDYnTpL93XC2JeegmTbO5MYRqhTLyvfmD
oPkSNN9F3O1FdLDAIKJbJKu5zuQMulifzuqw1/Ru9j9Tck8JkRmlmCws/OFKoTTB
lN0IU9PiobBbOGrGpisfHARxy5rzVLXVpO3zUFLV8nrIdym2AVUi0sg4QAvfgaAT
FOLFDADdySPGFUyHoUYZ2dYNh9X+XiEw2fGJIvL1PzjfO+C9vWFpi5CW9goH3WKf
FInlVTkhijJPVi/lhRG2MnMcih64IH0xgTlm8jUBlgwnxc1/rncjBwISJNu+v7Si
y0yOa+CWcCajoiYrLrTzUI7ltDiynhZWhJClGGXIdqdpD606taU5N9t7nZk6TkTT
2fnXEnTSUaOp+vjNT2HsZ287ZITmCeMfD4O3okqbmTEM+Tg6fzxRgF45p3h2mKxn
44lLEBJY22rvVsOkZseP/Ar82fknyaHBIQy9BH2ZMwptPBbD8Nb40PH3FciZMdta
5D+emORumurMe8vnYNesl7NKQUZ/kKeEBZ87Pg2MQHKJbPRG+HzrIBtkhsXGa30n
UqnX8vvZGrDRZvJJKh98u6ljRVrhPVgz7hzpDpZsU1U2Kx0VfmLaHF1/VHNcKKjp
8Vu0oMwEwVQ=
=S65a
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-12-10 2:12 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-04 5:58 Carrying Attributes too Far lrc1
2003-10-04 18:17 ` Alexander G. M. Smith
2003-10-04 20:10 ` Hubert Chan
2003-12-03 19:18 ` Hans Reiser
2003-12-05 0:30 ` lrc1
2003-12-05 3:58 ` A bold idea (Re: Carrying Attributes too Far) David Masover
2003-12-05 9:44 ` Heinz-Josef Claes
2003-12-05 14:00 ` David Masover
2003-12-05 16:37 ` Hubert Chan
2003-12-06 1:38 ` David Masover
2003-12-06 4:01 ` Hubert Chan
2003-12-06 17:40 ` David Masover
2003-12-06 22:41 ` lrc1
2003-12-07 1:18 ` carrying links too far? (was Re: A bold idea (Re: Carrying Attributes too Far)) David Masover
2003-12-07 2:26 ` Hubert Chan
2003-12-07 9:08 ` The danger of bad external links lrc1
2003-12-07 18:15 ` Hubert Chan
2003-12-07 13:18 ` carrying links too far? (was Re: A bold idea (Re: Carrying Attributes too Far)) lrc1
2003-12-07 16:17 ` David Masover
2003-12-07 18:25 ` Hubert Chan
2003-12-07 2:11 ` A bold idea (Re: Carrying Attributes too Far) Hubert Chan
2003-12-08 20:54 ` Boyd Waters
2003-12-09 8:03 ` Heinz-Josef Claes
2003-12-10 2:12 ` David Masover [this message]
2003-12-11 11:35 ` more about links (was Re: A bold idea (Re: Carrying Attributes too Far)) Heinz-Josef Claes
2003-12-05 13:16 ` More on Hard Links (was " Alexander G. M. Smith
2003-12-05 14:07 ` David Masover
2003-12-05 14:17 ` Nikita Danilov
2003-12-05 15:58 ` Hans Reiser
2003-12-05 16:18 ` Nikita Danilov
2003-12-06 1:50 ` Garbage collection for files (was Re: More on Hard Links (was A bold idea (Re: Carrying Attributes too Far))) David Masover
2003-12-07 3:27 ` Hans Reiser
2003-12-06 10:06 ` More on Hard Links (was A bold idea (Re: Carrying Attributes too Far)) Stewart Smith
2003-12-05 22:38 ` Alexander G. M. Smith
2003-12-06 1:54 ` David Masover
2003-12-06 15:31 ` Alexander G. M. Smith
2003-12-07 1:08 ` David Masover
2003-12-07 2:42 ` Alexander G. M. Smith
2003-12-09 5:21 ` More on Hard Links Narcoleptic Electron
2003-12-09 18:48 ` Hubert Chan
2003-12-09 19:52 ` Narcoleptic Electron
2003-12-09 21:31 ` Hubert Chan
2003-12-09 23:47 ` Narcoleptic Electron
2003-12-10 0:13 ` Narcoleptic Electron
2003-12-10 3:05 ` Hubert Chan
2004-01-22 21:15 ` Narcoleptic Electron
2003-12-10 2:53 ` Hubert Chan
2003-12-10 3:22 ` Religion and Hard Links (was Re: More on Hard Links) David Masover
2003-12-10 20:49 ` More on Hard Links Matt Stegman
2003-12-16 1:27 ` Hubert Chan
2003-12-10 2:44 ` David Masover
2003-12-05 5:27 ` Carrying Attributes too Far Hubert Chan
2003-12-05 12:38 ` Hans Reiser
2003-12-06 23:33 ` lrc1
2003-12-07 2:48 ` Hubert Chan
2003-12-07 17:08 ` Hans Reiser
[not found] ` <3FD0023D.5030500@ninja.dynup.net>
2003-12-07 6:37 ` Saved Re: A bold idea (Re: Carrying Attributes too Far) lrc1
2003-12-07 6:39 ` lrc1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FD68106.7050800@ninja.dynup.net \
--to=jedi@ninja.dynup.net \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.