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
Unknown Object (File)
Tue, May 13, 12:42 PM
Unknown Object (File)
Mon, May 12, 8:56 PM
Unknown Object (File)
Sun, May 11, 4:40 PM
Unknown Object (File)
Sat, May 10, 4:32 PM
Unknown Object (File)
Wed, Apr 23, 10:55 PM
Unknown Object (File)
Apr 17 2025, 2:01 PM
Unknown Object (File)
Apr 15 2025, 10:06 AM
Unknown Object (File)
Mar 4 2025, 6:37 PM
Subscribers
None

Details

Summary

Bug 228231
Brian Haug haug.bsd6114 AT yahoo

Diff Detail

Repository
rD FreeBSD doc repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

A few corrections and sentence rephrasing.

en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml
5274 ↗(On Diff #43043)

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

5276 ↗(On Diff #43043)

Same here.

5281 ↗(On Diff #43043)

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 ↗(On Diff #43043)

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

5298 ↗(On Diff #43043)

s/interfaces/interface/

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

5303 ↗(On Diff #43043)

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.