Hi,
I had a program which I compile with cmake. This program was on an NTFS
partition with permissions: defaults. This meant all files were owned
by root with 777 permissions. This worked fine but it was not secure
and created problems with the postrm/posinst scripts.
Recently I tried
Hi,
Desktop files and icons do not need any execute permissions. They are only data
files. The executable that the desktop file points to must be executable,
though. To mount the NTFS partition as a user, use either pmount or your
desktop mount utility.
OTOH, you make your life unusual hard
El 19/03/2017 a las 15:13, Gonzalo Garramuño escribió:
Hi,
I had a program which I compile with cmake. This program was on an
NTFS partition with permissions: defaults. This meant all files were
owned by root with 777 permissions. This worked fine but it was not
secure and created
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, nightly has been updated
discards 5f196337f169ebb86d98ed233e8ed75efad1dc16 (commit)
discards
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, nightly-master has been updated
via baba0a435a9f715c3f3e399b8284f25e558a5bad (commit)
from
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
discards b7d2d374017f940a7f66611d027ff2175c2c91a5 (commit)
discards
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via a5931b61e9dc8d8c6324f50837ef16aa1683ba0a (commit)
from
