Well while the above works fine and dandy, if you have scan setup by default but actually you don't want to use any home or conf what do you do? Well why not also add the following patch so you can do home|myconf=no|none!

Change the home section to
___________________________
[Aa][Uu][Tt][Oo]|[Ss][Cc][Aa][Nn]|[Ff][Ii][Nn][Dd])
MYHOMEDIR="$(findfile knoppix.img)"
MYHOMEDEVICE="${MYHOMEDIR##/mnt/}"
MYHOMEDEVICE="/dev/${MYHOMEDEVICE%%/*}"
MYHOMEMOUNTPOINT="/mnt/${MYHOMEDEVICE##/dev/}"
;;
[Nn][Oo]|[Nn][Oo][Nn][Ee])
echo "${GREEN}Home switched off.${NORMAL}"
;;
*)
echo "${CRE}${RED}Invalid ${CYAN}home=${RED} option '$HOMEDIR' specified (must
start with /dev/ or /mnt/ or 'scan').${NORMAL}"
echo "${CRE}${RED}Option ignored.${NORMAL}"
;;
esac
fi
___________________________

and change the conf section to
___________________________
[Aa][Uu][Tt][Oo]|[Ss][Cc][Aa][Nn]|[Ff][Ii][Nn][Dd])
MYCONFDIR="$(findfile knoppix.sh)"
if [-n "$MYCONFDIR" ]; then
MYCONFDEVICE="${MYCONFDIR##/mnt/}"
MYCONFDEVICE="/dev/${MYCONFDEVICE%%/*}"
MYCONFMOUNTPOINT="/mnt/${MYCONFDEVICE##/dev/}"
MYCONFDIR="${MYCONFMOUNTPOINT}"
else
FOUND_CONFIG="none"
fi
;;
[Nn][Oo]|[Nn][Oo][Nn][Ee])
echo "${GREEN}Configdir turned off.${NORMAL}"
FOUND_CONFIG="off"
;;
*)
echo "${CRE}${RED}Invalid configdir '$MYCONFDIR' specified (must start with /de
v/ or /mnt/ or 'scan').${NORMAL}"
echo "${CRE}${RED}Option ignored.${NORMAL}"
FOUND_CONFIG="invalid"
;;
esac
___________________________

I've also come across what seems to be a problem concerning timezones. I was trying to figure out why my remaster had the time an hour early, even if I was in the right timezone! I think it's because the system clock is set ignorant of the timezone because hwclock is called in knoppix-autoconfig when TZ has not been exported. Now ordering gets tricky so I'm not 100% certain of how this should best be addressed. I think the answer is to export TZ after the tz cheatcode has been picked up (and localtime set) and then run hwclock there, that way it will see the correct TZ (or the best it's going to) when it sets the system clock. I assume there would also be no problem removing the first running of hwclock Sorry I'm posting these before I've tested them (when I can get back to it, tonight or perhaps earlier), but with 3.4 so imminent I wanted to mention them as soon as I came up with/across them.