Date: Wed, 02 Jul 2008 10:51:57 +0400 From: Vladimir Grebenschikov <vova@fbsd.ru> To: Tim Kientzle <kientzle@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: cpio -dumpl damages the files? Message-ID: <1214981517.2513.11.camel@localhost> In-Reply-To: <486AF561.70201@freebsd.org> References: <20080626110521.GA68764@wep4017.physik.uni-wuerzburg.de> <1214815958.3581.67.camel@localhost> <486901FB.5080308@freebsd.org> <1214842042.8768.12.camel@localhost> <4869C4C4.1050806@freebsd.org> <1214900266.1947.13.camel@localhost> <486A53AD.9090904@freebsd.org> <1214930730.1898.3.camel@localhost> <486AF561.70201@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2008-07-01 at 20:26 -0700, Tim Kientzle wrote: > Vladimir Grebenschikov wrote: > > On Tue, 2008-07-01 at 08:56 -0700, Tim Kientzle wrote: > > > >>Try adding the following to the above condition: > >> > >> && archive_entry_filetype(entry) != AE_IFLNK > > > > I guess it will work. I just wander about other AE_IF* that may not pass > > link(2). > > Perhaps cpio -dumpl should only try to hardlink regular files? I think, one need to check original cpio behaviour and do exactly as was done here. Probably some software expect, for example, same inode number after cpio -dump on, say, copied devices or like. IMHO, It is more compatibility issue. > That would be an easy change. > > Tim -- Vladimir B. Grebenschikov vova@fbsd.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1214981517.2513.11.camel>