Hi Bob, I'm grateful for your reply. Since I posted to Debian-users, I've had a reply to my second post on the TrueCrypt forum. That reply suggests that the error message is generated by a TrueCrypt assumption that the volume being mounted is formatted as FAT or NTFS, which mine isn't. Hopefully that means I can safely ignore the error message, although this goes against my instincts!
Nonetheless, I'll answer your points/questions below, in case this proves fruitful. 2008/10/15 Bob McGowan <[EMAIL PROTECTED]> > As noted on the Ubuntu forums page you reference, the TrueCrypt page > requires an account and login to view the details. That's why I copied my post from the TrueCrypt forum to the Ubuntu forum, but not to worry. > I'm taking a blind shot (shot in the dark, whatever;) with this. > > Does the 'uid=1000' follow the '-o' option? Nope. My other posts at http://ubuntuforums.org/showthread.php?t=946994 will give you a better idea of what the error message looks like and the context in which it appears. > And, if it does, but there are other options used with it, is it a comma > separated list? No, I'm afraid not. > The pertinent part of the 'mount' man page is: > > -o Options are specified with a -o flag followed by a comma > separated string of options. Some of these options are only > useful when they appear in the /etc/fstab file. Interesting. Given that I didn't actually use the 'mount' command, I'm not sure this is relevant to me, but perhaps TrueCrypt is calling it. I haven't looked at TrueCrypt's source code to check this. > And many of the options are filesystem specific, so a final question: > Does the FS being mounted support the option? The 'uid=...' is listed > under specific filesystem types, implying some don't support the > concept. I was using the TrueCrypt command to mount an ext3 volume, which in fact doesn't seem to have 'uid=' listed as an option in the 'mount' man page. All best, Sam
