Hi! Thursday, 11 October, 2001 Christopher Faylor [EMAIL PROTECTED] wrote:
CF> I actually don't like either method. binmode has two uses -- devices and CF> unknown disk files that are opened via redirection. CF> /cygdrive settings are for files accessed through the /cygdrive prefix. it may look like a play with words but /cygdrive is just a thing created by "internal kernel automounter". but //server/share is, imho, just the same thing! CF> Neither seems like the correct solution to me. CF> If this was UNIX, we wouldn't have to worry about this (and not just CF> because UNIX doesn't worry about binmode/textmode foolishness). In CF> UNIX, you'd mount the directory. or UNIX automounter would do that for you. what we're talking about is, basically, a feature for "automounter configuration". CF> That is always what I've suggested for people who have this problem. CF> How about an extension to the mount table such that you could do something CF> like: CF> mount -s -b --settings //server CF> or, even: CF> mount -s -b --settings //* we can allow separate automounter settings in different parts of namespace, but do we really need it? the problem is that "network neighborhood" is much more volatile comparing to local drive mappings. it's possible to maintain the settings for the latter, but sometimes quite hard to maintain the settings for the former. 'mount -s -b --settings //*' will solve the problem fine, but i still can't see the need to have two different set of settings for "local automounted paths" and "remote automounted paths". If someone really needs this, it'd surely possible to implement. CF> I think it might be simpler to just change remote shares to use CF> "automode". this wouldn't work in all cases. Egor. mailto:[EMAIL PROTECTED] ICQ 5165414 FidoNet 2:5020/496.19
