On Tue, 05 Sep 2006 09:08:02 -0500, Owen Heisler <[EMAIL PROTECTED]> wrote:
[...] > I'm not sure about that. I just wanted to make as few changes as > possible to my system (/var/chroot/* & /etc/fstab). Same here! > I use schroot to run stuff in the chroot. Just "schroot -p <command>", > unless you have multiple chroots, then add the -c option. It works > nicely. I wasn't aware of schroot, but followed suggestions to use dchroot; I'll see what the advantages are with schroot. > It doesn't look like you mentioned whether you are using Sarge. If so, > the schroot package is unavailable. Then you would want to use dchroot. > But dchroot has a problem with changes in the login package (in the > chroot); if you get an error, that's probably what the problem is. You > can get around this by running the command indirectly, through a script > in the chroot ("dchroot -d <script-in-chroot>"). But that isn't really > a "comfortable" way to use your chroot! When I was running Sarge, I > just installed Sarge in the chroot, told aptitude to hold the login > package to that version, then upgraded the chroot to Etch. Or maybe > schroot is available from backports. Hopefully you're using Etch, so > this isn't a problem. Yes, I'm using Etch, and haven't seen any problems getting into the chroot so far (I've only installed the chroot up to now). Thanks, -- Seb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]