dist-upgrade of chroot

[Bill Moseley]

This is on Edubuntu Gutsy.

I wanted to enable vnc[1], but my chroot only had a cdrom for
sources.list.  So I copied the sources.list file from the server to
the chroot, and then ran a dist-upgrade.

Then I got a few errors:

    Can not write log, openpty() failed (/dev/pts not mounted?)

In addition to chroot /opt/ltsp/i386 do I need to mount /dev/pts in
general?  Same with /proc?

Also, a new kernel came with the update.


Preparing to replace linux-image-2.6.22-14-386 2.6.22-14.46 (using .../linux-image-2.6.22-14-386_2.6.22-14.47_i386.deb) ...
Done.
Unpacking replacement linux-image-2.6.22-14-386 ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/ltsp-update-kernels
Cannot open ``/boot/nbi.img-2.6.22-14-386'':File exists
run-parts: /etc/kernel/postrm.d/ltsp-update-kernels exited with return code 1
Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/linux-image-2.6.22-14-386.postrm line 320.
dpkg: warning - old post-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
[...]

So, what needs to be resolve there?

Wouldn't ltsp-updte-kernels need to be run after installing a new
kernel in the chroot from *outside* the chroot?


[1] Btw, shouldn ltsp-update-image be run after modifying the chroot
on https://wiki.edubuntu.org/InstallX11VncOnLtspClients ?


-- 
Bill Moseley
moseley at hank.org