Hot answers tagged

4

A symbolic link is just a reference to the actual file. There is no synchronization or something like that. If you look at the ls output for a symbuolic link you generally see something like: ls -l /bin/bzcmp lrwxrwxrwx 1 root root 6 jul 9 2014 /bin/bzcmp -> bzdiff As you can see the file /bin/bzcmp is just 6 bytes in size which happens to be ...


2

Symlinks aren't copies of files, they're essentially pointers which point at the same file. That means for example, that you can't do anything about permissions, if you can't access the original file then no matter what you do with the symlink, you can't get around that. Also, they are always 'in sync' because they always point directly to the same file.


2

You can use bind mount to simulate hard linking directories sudo mount --bind /some/existing_real_contents /else/dummy_but_existing_directory sudo umount /else/dummy_but_existing_directory


2

If the software root is using can be configured to do "evil" stuff (or to display information in some unexpected way so that the root user does "evil" stuff out of not-knowing or false knowledge) by the config file, then that is a viable attack. In general, you weaken security, if access rights to edit ~/<configfile> can be more easily gained for that ...


1

If all you're looking for is a single conditional test for a single command, you don't need an if statement—just use a list. According to LESS=+/Lists man bash: A list is a sequence of one or more pipelines separated by one of the operators ;, &, &&, or ||, and optionally terminated by one of ;, &, or <newline>. ... An ...


1

cron intentionally runs with a limited environment (including a restricted path, it does not have the same path as your standard shell). You either need to run a script (including the full path to the script) which then sets a path variable internally, or you need to set the path in the crontab line itself. One example of that is, 12 0 * * * (export ...


1

You need to delete your local libgmp completely: rm /usr/local/lib/libgmp.so* There's no need to run ldconfig afterwards. ldconfig makes sure the appropriate symlinks are present; libgmp.so.10 is a symlink to the latest library with that soname (run ls -l /usr/local/lib/libgmp.so* before deleting the files to see what I mean). Previously you deleted that ...



Only top voted, non community-wiki answers of a minimum length are eligible