Package: unionfs Severity: important Hello,
The unionfs doesn't seem to work like other filesystems
in a "chroot" environment. Below is the collection of steps
that demonstrates this "misbehaviour".
I did take the strace output of the su command but could not
notice any differences in Step 2 and Step 3 until the "clone"
function call.
Regards,
Kapil.
****start of experiment****
Step 1:
Setup a minimal Debian image. For example
I did the following.
1. dd if=/dev/zero bs=10M count=30 of=image
2. losetup /dev/loop0 image
3. mke2fs /dev/loop0
4. mount /dev/loop0 /mnt
5. debootstrap --variant=buildd /mnt etch
Step 2:
Use it without unionfs.
1. chroot /mnt
2. su bin
Works fine!
Step 3:
Use it with unionfs.
1. WRITE=$(mktemp -d /tmp/XXXX)
2. MOUNT=$(mktemp -d /tmp/XXXX)
3. mount -t unionfs -o dirs=${WRITE}=rw:/mnt=ro none ${MOUNT}
4. chroot ${MOUNT}
4. su bin
Exits with error message 'No shell'
****end of experiment****
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8)
signature.asc
Description: Digital signature
