Page MenuHomeFreeBSD

*/*: Use documented placeholder NETWOKING in RC scripts
Needs ReviewPublic

Authored by michaelo on Sat, Mar 7, 9:18 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Mar 18, 11:43 AM
Unknown Object (File)
Wed, Mar 18, 3:52 AM
Unknown Object (File)
Wed, Mar 18, 3:51 AM
Unknown Object (File)
Wed, Mar 18, 3:51 AM
Unknown Object (File)
Tue, Mar 17, 7:46 AM
Unknown Object (File)
Mon, Mar 16, 10:41 PM
Unknown Object (File)
Mon, Mar 16, 4:23 PM
Unknown Object (File)
Mon, Mar 16, 4:18 PM
Subscribers
None

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 71383
Build 68266: arc lint + arc unit

Event Timeline

michaelo created this revision.

No problem with KEA, thanks!

This revision is now accepted and ready to land.Sat, Mar 7, 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.