Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Strange behaviour of zsh-3.1.5 on IRIX 6.2
- X-seq: zsh-users 1915
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: Roland Jesse <jesse@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>, zsh-users@xxxxxxxxxxxxxxx
- Subject: Re: Strange behaviour of zsh-3.1.5 on IRIX 6.2
- Date: Sun, 1 Nov 1998 10:13:57 -0800
- In-reply-to: <13884.8743.733953.358182@knecht>
- References: <19981031003916.B29500@xxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.05.9810301553210.6235-100000@xxxxxxxxxxxxxxxxxxx> <13884.8743.733953.358182@knecht>
On Nov 1, 9:56am, Roland Jesse wrote:
} Subject: Re: Strange behaviour of zsh-3.1.5 on IRIX 6.2
}
} After the build the shell works just fine on this particular
} machine. But on another O2 machine I simply get: "13116:-zsh: rld:
} Fatal Error: attempted access to unresolvable symbol in -zsh:
} cap_get_proc."
"cap_get_proc" is part of the POSIX "capability sets" system, for extended
protection/access rules. Apparently this is installed on the system where
you built zsh, but is not on the system where you're getting that failure.
The file access part of capability sets is isolated to the "cap" module,
but the runtime tests for process privileges (setuid/setgid) are built in
to the main binary in the privasserted() function in Src/utils.c.
The only effect that a failure of privasserted() would have as far as I
can tell is to alter (or fail to alter) the display of the prompt, or to
incorrectly report that a directory was inaccessible in [[ -x dir ]]. So
it would probably be reasonable to either put that in a module as well,
or simply provide a configure option to turn it off.
} BTW: As I wrote before: zsh-3.0.5 build the same way as above was
} running just fine.
3.0.5 doesn't know about capability sets.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author