"Philip Warrick" <[EMAIL PROTECTED]> writes: > My /etc/apt/sources.list in the chroot looks like this: > > deb ftp://ftp.debian.org/debian/ testing main > deb-src ftp://ftp.debian.org/debian/ testing main > # deb http://security.debian.org/ testing/updates main > > as created by apt-setup (I said no the the security option, not knowing if I > wanted this).
Aeh, sorry, that was for a 32bit chroot, right? Disregard previous mail, I just got up. You use testing here but the /var/chroot/sid-ia32/ below? > These files do exist in the chroot: /etc/hosts, /etc/passwd, /etc/group (not > /etc/groups), /etc/shadow, > /proc (as described in the AMD-64 How-to). I had done nothing with /etc/mtab > and its entries were: > > proc /proc proc rw 0 0 > > whereas my chroot /etc/mtab was simply > > /dev/sda7 / ext3 rw,errors=remount-ro 0 0 > proc /proc proc rw 0 0 > devpts /dev/pts devpts rw,gid=5,mode=620 0 0 > proc /var/chroot/sid-ia32/proc proc rw 0 0 > /dev/sda1 /mnt/winC ntfs ro,noexec,nosuid,nodev,umask=0222 0 0 > /dev/sda5 /mnt/winD ntfs ro,noexec,nosuid,nodev,umask=0222 0 0 > /home /var/chroot/sid-ia32/home none rw,bind 0 0 > /tmp /var/chroot/sid-ia32/tmp none rw,bind 0 0 > //lmsrd01/DataDrive /mnt/lmsrd01 smbfs rw 0 0 > /dev/sda6 /mnt/winE vfat rw,noexec,nosuid,gid=100,umask=000 0 0 That will confuse e.g. df. Nor realy harmfull but gives confusing output. > Following ?good? advice elsewhere > (http://hacktavista.com/howto/chroot_slackware.html) I did the following for > the mtab file: > rm -f /etc/mtab > ln -s /proc/mounts /etc/mtab > > the contents of /proc/mounts in the chroot are: > > rootfs / rootfs rw 0 0 > /dev2/root2 / ext3 rw 0 0 > proc /proc proc rw,nodiratime 0 0 > devpts /dev/pts devpts rw 0 0 > proc /var/chroot/sid-ia32/proc proc rw,nodiratime 0 0 > /dev/sda1 /mnt/winC ntfs > ro,noatime,nodiratime,nosuid,nodev,noexec,uid=0,gid=0,umask=0222,nls=cp437,errors=continue,mft_zone_multiplier=1 > 0 0 > /dev/sda5 /mnt/winD ntfs > ro,noatime,nodiratime,nosuid,nodev,noexec,uid=0,gid=0,umask=0222,nls=cp437,errors=continue,mft_zone_multiplier=1 > 0 0 > /dev2/root2 /var/chroot/sid-ia32/home ext3 rw 0 0 > /dev2/root2 /var/chroot/sid-ia32/tmp ext3 rw 0 0 > //lmsrd01/DataDrive /mnt/lmsrd01 smbfs > rw,nodiratime,nosuid,nodev,file_mode=0744,dir_mode=0755 0 0 > /dev/sda6 /mnt/winE vfat > rw,nodiratime,nosuid,noexec,gid=100,fmask=0000,dmask=0000 0 0 Ugh, when did the chroot stop stripping /proc/mounts paths? I just noticed that it is the same here. > After all that I still get the same errors. apt is definitely able to > connect (apt-get update downloaded some packages successfully). > > Any ideas? I'm out. > Thanks, > > Phil MfG Goswin
