Page MenuHomeFreeBSD

Cover using symbolic names for interfaces in VLAN article of handbook.
ClosedPublic

Authored by sevan on May 26 2018, 6:49 PM.
Tags
None
Referenced Files
F81682547: D15586.id43552.diff
Fri, Apr 19, 9:19 PM
F81649813: D15586.id43551.diff
Fri, Apr 19, 11:22 AM
F81622149: D15586.id.diff
Fri, Apr 19, 3:14 AM
Unknown Object (File)
Thu, Apr 18, 3:44 PM
Unknown Object (File)
Tue, Apr 16, 12:37 PM
Unknown Object (File)
Fri, Apr 12, 12:54 AM
Unknown Object (File)
Sat, Mar 30, 12:09 AM
Unknown Object (File)
Mar 1 2024, 10:32 AM
Subscribers
None

Details

Summary

Bug 228231
Brian Haug haug.bsd6114 AT yahoo

Diff Detail

Repository
rD FreeBSD doc repository - subversion
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 17141
Build 16995: arc lint + arc unit

Event Timeline

A few corrections and sentence rephrasing.

en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml
5274

This line needs to be connected to the sentence above (after the sentence stop) and reflowed properly.

5276

Same here.

5281

Don't use "I" in the handbook. Make it third-person, like this:

For example, interfaces for video and audio can be named to associate ...

5292

This needs to be wrapped in <replaceable>s as the address is not static.

5298

s/interfaces/interface/

This sentence could be a bit shorter to simply say: For an interface named <literal>video</literal> use the following:

5303

s/confguration/configuration/

I'd write the sentence as follows: To apply the changes at boot time, add ...

This revision was not accepted when it landed; it landed in state Needs Review.Jun 10 2018, 6:31 PM
This revision was automatically updated to reflect the committed changes.