> > well until the su in a chroot issue is solved a chroot will > never be a proper > > test bed. > > Running an sshd or telnetd inside the chroot and using that to log > into the chroot doesn't work?
It's just one extra thing to compile. I had on my list to try build up one or the other but the task stalled after an initial problem. ssh requires a fair bit of other stuff. Our current scheme is a little complex, to run inside the SI we can do one of two things: * build it inside the si build, which there's some sentiment about not doing since it's not contributing to the spec * build it LSB-conforming using the application battery framework, which can be tricky for some programs (I anticipate sshd will be a challenge...) Right now I'm just running "login" in the same terminal where I've started the chroot, is that sufficient? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with subject of "unsubscribe". Trouble? Email [EMAIL PROTECTED]
