-1

I shared another query a while ago. @StephenKitt shared and I quote

there's no reason for it to recommend networking tools (considering recommendations as defined in Debian Policy), and removing the recommendation is safe because default installations still end up with ifupdown installed. Cleaning such dependencies up will simplify possible future switches to other default tools. -Stephen Kitt

Now while I can understand that, what is needed to know are possible replacements. For instance it has removed three services which are essential to me. I do understand that they will be installed as default but still -

  • services: removed ssh (22/udp).

  • services: removed http (80/udp), https (443/udp).

from /usr/share/doc/netbase

While we do hope that web server providers will make https a default offering either with tying up with multiple certificate providers at low-cost or something, as of now it's upto the site creator to do the way s/he wants to set up. Don't see that changing soon.

Similarly I don't know anything better than ssh ?

[$] ssh -v localhost

OpenSSH_7.3p1 Debian-5, OpenSSL 1.0.2j  26 Sep 2016

I am ok with the changes being proposed, just need to know what changes (if any) are going to become defaults so I can work that out.

  • This reads more like a rant. Would you be able to clarify the post? – Rui F Ribeiro Jan 9 '17 at 11:40
  • It is not a rant. It is trying to understand what changes could be coming which make the above services obsolete. Usually removal of services signal what the devs. are thinking about, so trying to get more insight on whatever proposed changes might be. – shirish Jan 9 '17 at 11:43
  • 1
    @AlexP the services weren't removed as dependencies (if only comments could be downvoted...), they were removed from /etc/services. – Stephen Kitt Jan 9 '17 at 12:28
2

The removals are only removals of service definitions from /etc/services. The definitions were removed because they were obsolete or unused:

etc. (read the git log for details of all the changes).

This only affects short-hand service definitions, and even then only unused service definitions, nothing else. It doesn't affect dependencies, the availability of services (which are provided by other packages anyway), your ability to provide services, etc.

  • thanx, that cleared lot of confusion in my mind. – shirish Jan 9 '17 at 12:41

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.