Re: [osol-discuss] some command can't be used in chroot,

On Thu, Aug 7, 2008 at 8:07 AM, wan_jm <[EMAIL PROTECTED]> wrote: > thanks. resolved. > > another question: can i use chroot to add driver in the virtual system. Yes you can but what is the point ? Chroot does not run a separate kernel. It is just a filesystem jail within the running OS. Re

Re: [osol-discuss] some command can't be used in chroot,

thanks. resolved. another question: can i use chroot to add driver in the virtual system. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org

Re: [osol-discuss] some command can't be used in chroot, what is the reason.

Seems like this line is being a problem: > open("/proc/self/auxv", O_RDONLY) Err#2 ENOENT Do you have procfs mounted under chroot environment? Milan Cermak wan_jm wrote: > when using chroot, I found that sort, and add_drv can't be used in chroot. > > bash-3.00# chroot /secroot /usr

[osol-discuss] some command can't be used in chroot, what is the reason.

when using chroot, I found that sort, and add_drv can't be used in chroot. bash-3.00# chroot /secroot /usr/sbin/add_drv /usr/sbin/add_drv: getexecname() failed bash-3.00# chroot /secroot /usr/bin/sort /usr/bin/sort: getexecname() failed following is the turss message. what is the reason. could