Comment 18 for bug 251923

Revision history for this message
Steve Langasek (vorlon) wrote :

> So this explains why I need above command to work, no matter how
> strange and pointless it may look.

Well, the straightforward workaround for this should be:
 - create a shell script named 'mount' that maps 'mountvers=2' to 'nfsvers=2' and calls /bin/mount
 - put this shell script in /usr/local/bin
 - make sure /usr/local/bin is in the path before /bin
 - call /opt/tta_tem/bin/tem startcdm

If that doesn't work, you can use 'dpkg-divert' to permanently move /bin/mount aside in a way that will be respected on upgrades, and install your script directly as /bin/mount.

> My assertion is that this option should not have been touched, damn it!!

That's as may be, but we didn't touch it. You'd have to take up the question of not touching it with linux-nfs upstream.

> This boneheaded changing of options because "nobody should be using
> this" is making Debian and Ubuntu *impossible* to use in a professional
> environment.

This is not due to any Debian or Ubuntu changes; it's due to an upstream change, probably one that was meant to fix something else and only incidentally broke mount version 2 support. And it probably went unnoticed because the only thing affected was a version of the protocol that's been *obsolete* for a decade.

I agree that it's a bug to have the option stop working. I also think it's a bug that the software you're using is setting that option. Neither of these bugs are going to be a high priority for the Ubuntu team, because the number of users affected by problems with NFSv2 support is very, very small.

> One day the option is there ... you upgrade a few packages
> and ... *POOOOFFF!* ... option is gone all of a sudden and your
> Enterprise Remote Access solution partially stops to work.

> Nice one. Seriously. :-(

If by "upgrade a few packages" you mean "upgrade to the next version of the release, which is not guaranteed to be feature-compatible with the previous version", sure.

The way I see it, you have several options to get this bug fixed.
 - Talk to upstream.
 - Work out how to fix it yourself.
 - Contract someone to fix the bug. There are a number of companies that provide paid support for Linux distributions, including for Debian and Ubuntu. For information about Canonical's paid support options, see <http://www.ubuntu.com/support>.

But escalating the bug via the community bug tracker is not likely to lead to a fix in the foreseeable future, because this is going to be a deep bug and there are a lot of other bugs that need fixing.