Hi Bill,

Ok... I installed the latest pump... and put the knoppix-halt script back to the default actions...
and got errors on reboot.

So instead of loops and whatnot... down around line 170 I killed pump with it's own kill daemon option
after the last network command I could see. Comments in the file seem to indicate a 'bring network down'
procedure was envisioned but not implemented formally. So just try this out with some nfs stuff.


# Unmount network filesystems first before shutting down network
NFSBUSY=""
NETMOUNTS="$(gawk '{if($1~/:/){print $2}}' /proc/mounts 2>/dev/null)"
if [ -n "$NETMOUNTS" ]; then
echo "${BLUE}Unmounting network filesystems.${NORMAL}"
# Preload programs we need later, in case we lose the network too early
swapoff --help >/dev/null 2>&1
losetup --help >/dev/null 2>&1
mount --help >/dev/null 2>&1
umount --help >/dev/null 2>&1
gawk --help >/dev/null 2>&1
tac --help >/dev/null 2>&1
# Umount NFS (if not busy)
umount -t nfs,nfs4,smbfs -alv 2>/dev/null
fi
# see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=261803 for why this is needed here.
# When knoppix-persistent home feature is used... pump prevents their umount from succeeding.
# unless killed explicitly.
pump -k

# Umount devpts early (otherwise UNIONFS may stay busy)
umount -t devpts -a 2>/dev/null

# UNIONFS umount
if [ "$(ls -l1d /lib | gawk '{print $NF}')" = "/UNIONFS/lib" ]
then

cheers

If it works for you... then I'll post this as a bug to fix on the debian-knoppix list with link to this topic.