Date: Thu, 21 Dec 2017 15:42:22 +0000 From: Arthur Chance <freebsd@qeng-ho.org> To: Manish Jain <bourne.identity@hotmail.com>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: How to fix : Cannot extract through symlink Message-ID: <9879912b-5e7a-b0a0-4794-636e2ff3ca56@qeng-ho.org> In-Reply-To: <VI1PR02MB12009190A3338F191796057EF60D0@VI1PR02MB1200.eurprd02.prod.outlook.com> References: <VI1PR02MB12009190A3338F191796057EF60D0@VI1PR02MB1200.eurprd02.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21/12/2017 14:37, Manish Jain wrote: > Hi, > > 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 ? Looking at the manual for link(2), hard linking directories is explicitly forbidden by the kernel. Many moons ago under SunOS I tried hard linking directories just to see what happened. Believe me, it's not a place you want to be, especially not if the link went up the file hierarchy. -- An amusing coincidence: log2(58) = 5.858 (to 0.0003% accuracy).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9879912b-5e7a-b0a0-4794-636e2ff3ca56>