Mladen Turk wrote:
> Rainer Jung wrote:
>> OK, I forgot, that I actually had a user and group named asf (I
>> thought tar would ignore their non-existance).
>>
>> All in all I would suggest root:bin to.
>
> I used root:users instead.
> Think the users group exists on all *nixes.
So does bin. use
All in all I would suggest root:bin to.
I used root:users instead.
Think the users group exists on all *nixes.
Hmm, it doesn't after all :(
Switching to suggested root/bin
Regards,
Mladen.
-
To unsubscribe, e-mail: [EMAIL
Rainer Jung wrote:
OK, I forgot, that I actually had a user and group named asf (I thought
tar would ignore their non-existance).
All in all I would suggest root:bin to.
I used root:users instead.
Think the users group exists on all *nixes.
Regards,
Mladen.
OK, I forgot, that I actually had a user and group named asf (I thought
tar would ignore their non-existance).
But I agree with William, that we should instead use a general purpose
user and group exactly because of the reasons given by him.
If a non-root user extracts the tarball, his owners
Mladen Turk wrote:
> Rainer Jung wrote:
>> Hi Mladen,
>>
>> did you delete setting owner and group by accident from the release
>> script?
>>
>
> No, I did it by purpose. I don't have user or group named asf, so the tar
> fails. What would be a purpose of it anyhow, and how would you ensure
> that
Rainer Jung wrote:
Hi Mladen,
did you delete setting owner and group by accident from the release script?
No, I did it by purpose. I don't have user or group named asf, so the tar
fails. What would be a purpose of it anyhow, and how would you ensure
that the same user will exist on the users
Hi Mladen,
did you delete setting owner and group by accident from the release script?
[EMAIL PROTECTED] schrieb:
>
> # Pack and sign
> -tar cvf ${JK_DIST}.tar --owner="${JK_OWNER}" --group="${JK_GROUP}" ${JK_DIST}
> -gzip ${JK_DIST}.tar
> +tar cfz ${JK_DIST}.tar.gz ${JK_DIST}
> perl ${JK_DIS
