chroot() and dlopen()
phil-news-nospam_at_ipal.net
Date: 04/29/04
- Previous message: cbfk23: "Re: Help: raising x-window on top of a display through HPUX shell command?"
- Next in thread: Måns Rullgård: "Re: chroot() and dlopen()"
- Reply: Måns Rullgård: "Re: chroot() and dlopen()"
- Reply: David Schwartz: "Re: chroot() and dlopen()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 29 Apr 2004 09:25:51 GMT
Should dlopen() be able to work when chroot() into another directory,
even if the library being loaded only has references to symbols that
are already loaded in the process. I'm wondering if the references
to specific libraries within the library being loaded are made using
the given filesystem paths, which will no longer be valid under the
chroot directory.
The executable will be dynamically linked with libc and other libraries
that will be needed when it starts. Then calls chroot(), then later
calls dlopen(). The library being dlopen'd is in the chroot directory,
and is being referenced in a way it can be found.
-- ----------------------------------------------------------------------------- | Phil Howard KA9WGN | http://linuxhomepage.com/ http://ham.org/ | | (first name) at ipal.net | http://phil.ipal.org/ http://ka9wgn.ham.org/ | -----------------------------------------------------------------------------
- Previous message: cbfk23: "Re: Help: raising x-window on top of a display through HPUX shell command?"
- Next in thread: Måns Rullgård: "Re: chroot() and dlopen()"
- Reply: Måns Rullgård: "Re: chroot() and dlopen()"
- Reply: David Schwartz: "Re: chroot() and dlopen()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|