Seb,
On Tuesday 29 May 2007 10:05, Seb wrote:
> On Tue, 29 May 2007 09:50:46 -0500,
> C M Reinehr <[EMAIL PROTECTED]> wrote:
>
> [...]
>
> > Add the '-v' option to your schroot command and review the diagnostic
> > output. This will give you a better idea of what's going on. If you
> > can't figure out what's happening, send us a copy of your command line
> > including the diagnostic output along with a copy of your
> > /etc/schroot/schroot.conf file.
>
> Thank you and Hamish for your feedback. In fact, this is happening at
> system boot up, not when I schroot into my chroot (I guess this is the
> Hamish too). I only have a single chroot, and this is my
> /etc/schroot/schroot.conf:
Ok, I understand where you are now. I had the same thing happen to me.
I
didn't take the time to figure out exactly what was wrong but I figured out
how to make it go away. Maybe someone else more experienced or knowledgeable
with schroot can jump in to help.
When schroot setups up a chroot environment it builds a chroot
in /var/lib/schroot. Under the directory mount it creates a new directory
using a concatenation of the chroot name and a unique identifier. (I haven't
taken the time to figure out the means.) That's the alphanumeric code that
you're seeing.) Schroot also creats a file of the same name under the
directory session.
When things work correctly, all of this is removed after you exit the
chroot,
but for some reason (with type=plain I believe) things are not getting
shutdown & removed correctly. Here, I first noticed it when I ran a `mount`
command to see what was mounted and noticed all of these old schroot sessions
were still mounted. What's more, they would not `umount` because of some
active process. (Can't remember the name now.) I finally was able to clean
things up by switching into single-user/maintenance mode and removing all of
the mount & session entries. In the process, I CLOBBERED MY CHROOT DIRECTORY!
Anyway, when I rebuilt the chroot I switched to type=directory and
everything
has been working just fine.
I know this is incomplete but I have to leave in just a few minutes
(and
don't know a whole lot more, anyway!) but I hope it points you in the right
direction. Here's a copy of my schroot.conf file:
[etch-i386]
type=directory
description=Debian etch (stable) 32-bit
priority=1
users=cmr
groups=cmr
aliases=default
run-setup-scripts=true
run-exec-scripts=true
personality=linux_32bit
location=/var/chroot/etch-i386
Cheers!
cmr
> ---<---------------cut here---------------start-------------->---
> [sid-32]
> description=Debian sid (unstable) 32-bit
> location=/var/chroot/sid-ia32
> priority=3
> groups=users
> root-groups=root
> aliases=unstable,ia32,default
> run-setup-scripts=true
> run-exec-scripts=true
> personality=linux32
> ---<---------------cut here---------------end---------------->---
>
> I nonetheless tried logging into my chroot with 'schroot -v' but did not
> find any errors or hints. This is what my /etc/fstab looks like, if
> that's helpful:
>
> ---<---------------cut here---------------start-------------->---
> # /etc/fstab: static file system information.
> #
> # <file system> <mount point> <type> <options>
> <dump> <pass> proc /proc
> proc defaults 0
> 0 /dev/hda1 / ext3
> defaults,errors=remount-ro 0 1 /dev/hda6
> /home ext3 defaults
> 0 2 /dev/hda5 none swap
> sw 0 0 /dev/hdc
> /media/cdrom0 auto user,noauto
> 0 0 /dev/sde1 /media/sde1 auto
> user,noauto 0 0 /dev/hdb1
> /home/myuser/Backup-Drive ext3 defaults,user
> 0 2 192.168.0.101:/home /home/myuser/other nfs
> rw,intr,user 0 0
>
> # Chroot mounts
> /home /var/chroot/sid-ia32/home none bind
> 0 0 /tmp
> /var/chroot/sid-ia32/tmp none bind
> 0 0 proc /var/chroot/sid-ia32/proc proc
> defaults 0 0 # /dev
> /var/chroot/sid-ia32/dev none bind
> 0 0 # /media/cdrom /var/chroot/sid-ia32/media/cdrom
> none bind 0 0
> ---<---------------cut here---------------end---------------->---
>
>
>
> Cheers,
>
> --
> Seb
--
Debian 'Etch' - Registered Linux User #241964
--------
"More laws, less justice." -- Marcus Tullius Ciceroca, 42 BC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
