linux-kernel - Re: Hardlink Pitfalls (was: Patches for REALLY TINY 386 kernels)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0707171341420.10600@anakin>
Date:	Tue, 17 Jul 2007 13:43:43 +0200 (CEST)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Al Boldi <a1426z@...ab.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Hardlink Pitfalls (was: Patches for REALLY TINY 386 kernels)

On Mon, 16 Jul 2007, Al Boldi wrote:
> Satyam Sharma wrote:
> > Or just "cp -al" to create multiple trees at (almost) no disk cost
> > that won't interfere with each other in any way, and makes the
> > development process / generating patchsets trifle easier as well ...
> 
> That would be correct if hardlinks would actually do a CoW on modify, instead 
> of misleading the user into thinking he is modifying an independent file.
> 
> Moral of the story:  try to avoid hardlinks as much as possible!

Or use a different user account.

I used to have `all' Linux kernel source trees hardlinked where possible, as
special user `src'. So I could create a `cp -rl' copy under my own account and
get an error when trying to modify a file.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/