The Fungi <fu...@yuggoth.org> writes: > I think this is part of the misunderstanding. If these systems are nodes > on an AX.25 network, what's being renamed (and potentially broken) is > the userspace binary which connects the machine to the network. Think of > it as if you're suggesting a rename of /usr/sbin/sshd to > /usr/sbin/secureshelld. Sure it's usually only started from packaged > scripts and managed configuration files, but when it's also your only > way into some remote systems that has a much greater potential to render > them indefinitely inaccessible.
Yes, this is something I'd not realized before and am now realizing. Also, the point that starting the service from inetd isn't the only way that it's started, and it may be embedded in custom scripts and the like, was new information for me. Contrary to how it may have sounded from my previous messages, it really isn't that I want to discount the effect on the ham radio community, and I completely agree with other posters that having Debian serve the needs of the ham radio community is important for a wide variety of reasons. Raphael's approach of creating a compatibility symlink in postinst during upgrades but not for new installs sounds better to me the more I think about it, since that addresses the major concern of breaking someone's system during an upgrade. It's not ideal in terms of making the conflict go away, but it does address the problem going forward, if not on currently-running systems. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87r4v0negs....@windlord.stanford.edu
