On Wed, Dec 08, 2010 at 11:31:42AM +0100, Petter Reinholdtsen wrote: > Dec 8 10:07:06 in-target: mount: /dev/sdb1 already mounted or /media/cdrom0 > busy > Dec 8 10:07:06 in-target: mount: according to mtab, /dev/sdb1 is already > mounted on /media/cdrom0 > Dec 8 10:07:06 in-target: error: LTSP client installation ended abnormally > Dec 8 10:07:06 ltsp-client-builder: ERROR: ltsp-build-client failed to run > Dec 8 10:07:06 main-menu[494]: WARNING **: Configuring 'ltsp-client-builder' > failed with error code 1 > Dec 8 10:07:06 main-menu[494]: WARNING **: Menu item 'ltsp-client-builder' > failed. > I guess this is because the LTSP code expect the ISO to be mounted as > /dev/cdrom, while it is mounted as /dev/sdb1 instead.
all 099-mount-cdrom does is: mount /media/cdrom so if the USB stick is not configured to be mounted as /media/cdrom, then it's not going to work. my guess is oded is probably right about it being the same bug (#540990) as the multiple cdrom drive issue, maybe showing up as cdrom1 or some other device altogether. i've never been able to navigate the relevent debconf databases that we could actually query the right information during install time, so it's pretty much guesswork, and will break as soon as something *slightly* unusual is happening. it wouldn't bee too difficult to configure it to fall back to attempting to mount additional paths if the first failed, but then you need to coordinate that with the mirrors used as well. live well, vagrant -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
