Page MenuHomeFreeBSD

*/*: Use documented placeholder NETWOKING in RC scripts
ClosedPublic

Authored by michaelo on Mar 7 2026, 9:18 PM.
Tags
None
Referenced Files
F153418329: D55712.id173313.diff
Tue, Apr 21, 1:38 AM
Unknown Object (File)
Wed, Apr 15, 3:35 AM
Unknown Object (File)
Mon, Apr 13, 6:01 PM
Unknown Object (File)
Sat, Apr 11, 2:57 PM
Unknown Object (File)
Fri, Apr 10, 11:57 PM
Unknown Object (File)
Sun, Apr 5, 3:59 PM
Unknown Object (File)
Sun, Apr 5, 11:09 AM
Unknown Object (File)
Sat, Apr 4, 10:53 AM
Subscribers
None

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

michaelo created this revision.

No problem with KEA, thanks!

This revision is now accepted and ready to land.Mar 7 2026, 9:53 PM

Thanks for taking the effort to bring naming consistency across both src and ports. Can someone tell the story what was wrong with NETWORK (shorter base form) that it had to be replaced with NETWORKING (longer gerund form)? Or it simply better describes the matter, English-wise?

Thanks for taking the effort to bring naming consistency across both src and ports. Can someone tell the story what was wrong with NETWORK (shorter base form) that it had to be replaced with NETWORKING (longer gerund form)? Or it simply better describes the matter, English-wise?

As far as I understand as a non-native English speaker is due to the fact that NETWORKING collects multiple services:

$ cat NETWORKING
#!/bin/sh
#
#

# PROVIDE: NETWORKING NETWORK
# REQUIRE: netif netwait netoptions routing ppp ipfw stf
# REQUIRE: defaultroute route6d resolv bridge
# REQUIRE: static_arp static_ndp

Waiting for other maintainers.

Folks, any objections? Timeout is approaching...

This revision was not accepted when it landed; it landed in state Needs Review.Sun, Mar 22, 4:25 PM
This revision was automatically updated to reflect the committed changes.