-
Bug
-
Resolution: Done
-
Minor
-
RH134 - RHEL9.0-en-1-20220525
-
1
-
en-US (English)
URL: https://rol.redhat.com/rol/app/courses/rh134-9.0/pages/ch01s05
Reporter RHNID: carias@redhat.com
Section: 5 - Match Text in Command Output with Regular Expressions
Language: en-US (English)||||||||
Workaround: Either change the word semicolon for colon, or find another file that contains a second special character to grep out.
Description: The following sentence talks about a semicolon, but in the brackets there is a colon.
"To look at a file without being distracted by comment lines, use the grep command -v option. In the following example, the regular expression matches all lines that begin with a hash character (#) or the semicolon (:) character. Either of these two characters at the beginning of a line indicates a comment that is omitted from the output."
Despite that, the ethertypes example is confusing, as there is no single semicolon, and the only lines that contains colon are already commented with '#'.