Date: Thu, 21 Dec 2017 21:33:22 +0100 From: Tijl Coosemans <tijl@coosemans.org> To: Manish Jain <bourne.identity@hotmail.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: How to fix : Cannot extract through symlink Message-ID: <20171221213322.0f17ad3d@kalimero.tijl.coosemans.org> In-Reply-To: <20171221195958.010ce64f@kalimero.tijl.coosemans.org> References: <VI1PR02MB12009190A3338F191796057EF60D0@VI1PR02MB1200.eurprd02.prod.outlook.com> <20171221195958.010ce64f@kalimero.tijl.coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 21 Dec 2017 19:59:58 +0100 Tijl Coosemans <tijl@FreeBSD.org> wrote: > On Thu, 21 Dec 2017 14:37:43 +0000 Manish Jain <bourne.identity@hotmail.com> wrote: >> Whenever I try to install any rpm under my Linuxulator (linux_base-c7), >> I get the error: cannot extract through <sym> >> >> <sym> can be bin / sbin / lib / lib64, which are symbolic links to >> usr/<sym> (under the path /compat/linux/) >> >> Each time I am faced with this problem, I have to delete <sym> and copy >> the actual directory in its place. But this is far less than ideal. >> >> 1) Is there some way I can avoid the above mess ? >> 2) If not, there was a time under Unix when hard-linking a directory was >> possible. Is there some hack by which I could hard-link directories >> under FreeBSD ? > > Try extracting with tar -P, but please read the tar manual because -P > does other things like preserving absolute paths. Instead of using -P perhaps it's better to extract into a temporary directory and move bin, sbin, lib, and lib64 to usr there. Then copy everything to /compat/linux. That's essentially what we do in the ports tree.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171221213322.0f17ad3d>