| 1 |
Ah, and a minor note. |
| 2 |
|
| 3 |
On Thu, 18 Oct 2012 02:15:43 -0700 |
| 4 |
Brian Harring <ferringb@×××××.com> wrote: |
| 5 |
|
| 6 |
> /usr/libexec/python/wrapper upon invocation, takes a look at argv[0]; |
| 7 |
> sees how it was invoked basically. This will be the /usr/bin/whatever |
| 8 |
> pathway. It reads the symlink, in the process getting the allowed |
| 9 |
> versions and preferred order of the versions. |
| 10 |
> |
| 11 |
> Few notes; vast majority of filesystems will store the symlink target |
| 12 |
> into the core inode if at all possible- in doing so, this avoids |
| 13 |
> wasting an inode and is only limited by the length of the target. |
| 14 |
> That length is capped by PATH_MAX- which can range from 256 to 4k (or |
| 15 |
> higher). |
| 16 |
|
| 17 |
It is capped by SYMLINK_MAX, I believe. |
| 18 |
|
| 19 |
-- |
| 20 |
Best regards, |
| 21 |
Michał Górny |
Archives