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] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 19 Jun 2007 18:21:46 -0400
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	david@...g.hm
Cc:	Chris Snook <csnook@...hat.com>,
	Jack Stone <jack@...keye.stone.uk.eu.org>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	akpm@...ux-foundation.org, viro@...iv.linux.org.uk, hpa@...or.com,
	alan <alan@...eserver.org>
Subject: Re: Versioning file system

On Tue, Jun 19, 2007 at 03:07:40PM -0700, david@...g.hm wrote:
> since anything starting with . is considered a 'hidden' file per *nix 
> tradition it's ignored by many programs and optionally ignored by most 
> others (and anything that doesn't ignore . files when presending files to 
> the user has many other problems on modern desktop systems anyway ;-)
> 
> the only trouble I ever had with the .snapshot approach is when tar or 
> find would decend down into the .snapshot when I didn't really intend for 
> it to do so.

That is why a readdir shouldn't even include .snapshot.  Only explicitly
asking to open .snapshot should give it to you.  That way tar can't
accidentally include it unless you specifically asked it to go into
.snapshot and archive the contents.

So by hidden it means completely hidden, not just left out by the shell
and the unix conventions.

Of course backup tools have to know about this, but then again backup
tools have to know about all sorts of low level filesystem stuff that
normal tools don't.

--
Len Sorensen
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ