Re: ghostscript fails on pdf generation

[Wols Lists]

On 12/02/17 19:59, David Wright wrote:
> In the case cited from June, the OP was using an odd system (eg it
> used # as a *user* prompt) whose tar couldn't create symlinks when
> it unpacked an archive (permissions messages); they had to be
> created manually.

I don't know when it started happening - maybe a year ago? - but I
suddenly found I couldn't symlink files. And I couldn't find anything
about it on the net, but as far as I have been able to make out ...

You need "rw" permissions on somebody else's files if you want to create
a hard link.

It seems daft to me that you need "w" permissions, and I haven't
experimented deeply with it, but if I have access to a file, why
shouldn't I be able to create a link to it?

I don't know how tar unpacking works particularly, but if it unpacks a
file, gives away ownership, and then tries to link to it, that could be
why that problem happened.

Cheers,
Wol