On Jan 27, 2008 2:10 PM, Steve Langasek <[EMAIL PROTECTED]> wrote: > mount.cifs doesn't honor smb.conf, yes. It only resolves hostnames using > gethostbyname(), and only supports overriding this resolution using an ip= > mount option. Presumably this worked for you before only because you were > using mount.smbfs rather than mount.cifs.
I've been using mount.smbfs, which apparently was recently forcibly switched to mount.cifs, regardless of how it's specified in /etc/fstab. > As for all hostnames being resolved incorrectly by Verizon's DNS servers, > that's not our problem to fix. They're the ILEC where I live and I refuse > to do any business with them because of their incompetence and their > reprehensible political lobbying; if you choose to deal with an Internet > provider who spits on Internet standards, you'll have to find your own way > to overcome the resulting problems. I can certainly appreciate that this is an error on Verizon's end (which they have no intentions of correcting), but why force a switch on users when the new version doesn't respect what the old version did? mount.smbfs worked fine, and I could prevent it from talking to the wider network. As it is, I now have to hard-code an IP address that isn't stable (because of DHCP), when SMB has a perfectly good naming scheme. -- Michael A. Marsh http://www.umiacs.umd.edu/~mmarsh http://mamarsh.blogspot.com http://36pints.blogspot.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
