Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

Re: exiting a chroot environment

by LazerRed (Pilgrim)
on Jul 08, 2003 at 00:21 UTC ( #272160=note: print w/replies, xml ) Need Help??

in reply to exiting a chroot environment

From the Solaris 8 Man:

Maintenance Commands chroot(1M) NAME chroot - change root directory for a command SYNOPSIS /usr/sbin/chroot newroot command DESCRIPTION The chroot utility causes command to be executed relative to newroot. The meaning of any initial slashes (|) in the path names is changed to newroot for command and any of its child processes. Upon execution, the initial working directory is newroot. Notice that redirecting the output of command to a file, chroot newroot command >x will create the file x relative to the original root of command, not the new one. The new root path name is always relative to the current root. Even if a chroot is currently in effect, the newroot argument is relative to the current root of the running pro- cess. This command can be run only by the super-user. RETURN VALUES The exit status of chroot is the return value of command. EXAMPLES Example 1: Using the chroot utility. The chroot utility provides an easy way to extract tar files (see tar(1)) written with absolute filenames to a different location: example# cp /usr/sbin/static/tar /tmp example# dd if=/dev/nrst0 | chroot /tmp tar xvf - Note that tar is statically linked, so it is not necessary to copy any shared libraries to the newroot filesystem. ATTRIBUTES See attributes(5) for descriptions of the following attri- butes: SunOS 5.8 Last change: 20 Mar 1998 1 Maintenance Commands chroot(1M) ____________________________________________________________ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | |_____________________________|_____________________________| | Availability | SUNWcsu | |_____________________________|_____________________________| SEE ALSO cd(1), tar(1), chroot(2), ttyname(3C), attributes(5) NOTES Exercise extreme caution when referencing device files in the new root file system. References by routines such as ttyname(3C) to stdin, stdout, and stderr will find that the device associated with the file descriptor is unknown after chroot is run.

My thoughts, maybe you just need to run a single command from within your chroot'd environment? I pasted the man because of the example with the tar command, and it's absolute filenames. Heed the warnings at the end though :)

Good Luck

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://272160]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (3)
As of 2017-03-29 23:55 GMT
Find Nodes?
    Voting Booth?
    Should Pluto Get Its Planethood Back?

    Results (353 votes). Check out past polls.