On Sun, May 27, 2012 at 05:37:49PM +0300, Georgi Naplatanov wrote: > > There is my configuration of schroot - > http://os.oles.biz/openjdk/schroot-etc-2012-05-27.tar.gz > > I don't know what anything more to try so any suggestions are welcome.
If it's related to /run/lock, it might be a case of the /run/lock directory being unavailable. On a base unstable system, I have: % ls -ld /run /run/lock /var/run /var/lock drwxr-xr-x 28 root root 980 May 27 15:39 /run drwxrwxrwt 4 root root 80 May 27 14:11 /run/lock lrwxrwxrwx 1 root root 9 May 13 2011 /var/lock -> /run/lock lrwxrwxrwx 1 root root 4 May 13 2011 /var/run -> /run In a chroot, I have: $ ls -ld /run /run/lock /var/run /var/lock lrwxrwxrwx 1 root root 8 May 17 2011 /run -> /var/run/ lrwxrwxrwx 1 root root 9 May 17 2011 /run/lock -> /var/lock/ drwxrwxrwt 2 root root 4096 Jan 19 14:11 /var/lock/ drwxr-xr-x 5 root root 4096 May 14 18:06 /var/run/ This is due to the special handling of chroots in the initscripts maintainer scripts for /run migration. For either case, you should have valid paths. Note if you upgrade a chroot, you'll have the second set of paths; if you do a fresh debootstrap, you should get the first. If the logic is somehow wrong on kFreeBSD, it might result in broken paths. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120527144723.gp22...@codelibre.net
