Is SMF responsible for the conversion of 'internal' services
supplied by inetd to external services?

If there is no longer any such thing as an 'internal' service
for inetd, then why can I register an inetd service
(using inetconv) successfully?
The man page still documents 'internal' as referring to a
service that inetd provides itself - is this technically true
for any service, now?

Previously it was possible to individually control whether
or not services such as echo and friends were enabled for
IPv4 or IPv6.  This control seems to have vanished?
Or have I not looked hard enough?

Darren


Reply via email to