Howdy, I rewrote mount's option parsing to use getopt and this bug seems to have disappeared. I also tested the interaction with loop devices, and it appears that the standard mount is perfectly happy to mount block devices via them, so I don't think we should behave differently. Matt