On 7 Jun 2000, Henning P. Schmiedehausen wrote:
> 5.2 did work. This basically sucks sometimes with Linux/free software.
Just wondering if I was the only one who noticed the irony of this
statement coming from TANSTAAFL Consulting? ;-)
> A change with no apparent reason.
No apparant reason? The new behavior makes more sense and is more
consistent with the way other NIS/file configuration issues are
handled. And if it's more consistent with Sun, too, so much the
better.
> You won't see this from SUN/HP/IBM/SGI (maybe they will drop the
> whole product line but not just make such a subtle, not well
> documented, not well visible change).
HP did drop a whole product line on us, after we went through an
HP-UX upgrade that was more painful than bumping up Red Hat versions
has been. Fortunately our department finished a Linux port last year,
and won't be buying anything more from HP.
> Upgrading from one OS release (5.2) to another (6.2) and suddently
> your auto-mounts which worked for ages stop working.
I consider it a hazard of an upgrade, frankly. With Red Hat, you
already have some non-trivial work to do in an upgrade, merging
configuration changes left around in .rpmsave files with changes in
various packages' default config files. Fixing places where backwards
compatibility has been broken too (a "yp:auto_nfs" -> "yp auto_nfs"
syntax fix caught me) is annoying, but not too much extra work.
> No, I didn't find it in the release notes.
This is a more serious oversight, certainly.
---
Roy Stogner
