Doing a reverse DNS lookup by typing out the IP address in reverse, plus adding .in-addr.arpa to the end is tedious, but fortunately dig has the -x option which makes that process much simpler as one can just feed it a normal IP address.
* psql: Improve page
- Removed * , this was causing problems with rendering. The node client was
gobbling up the entire word !
- Changed 'query' to 'command' as it can be a postgres db command too.
- Used the -f flag for running multiple commands as its a better and scalable
option.
* Addressing comments
* Replacing against with on
- Mentioning the default user
* rm: various tweaks for clarity; add -v
changed some descriptions and tokens to make the meaning of each command clearer, and facilitate memorization of the flags
added the -v (verbose) option
* use a more intuitive pattern for the -i option
The version I have uses `-d` for the depth option, not `-depth`. Here's the version string as shown by `man du`:
```
BSD June 2, 2004 BSD
```
In addition to this fix, this commit changes the tokens to clarify that they are paths, and changes "directory" to "folder", which is shorter and more accessible.
* Applying the snake_case convention throughout the repo
- Also removing the file extension where not needed
- Adding {{ }} on a few old pages
* Addressing concerns
- Added {{ }} where they were missed out
- Removed spaces inside {{ }}
- Reverting "file" to "filename" to make it clearer
* Fixing the comments on nc page
Numbered field references have been used in the first two examples,
so it's quite reasonable to take the opportunity to introduce a new (and quite useful!) concept.
In addition, this commit makes a few tweaks to the example descriptions, to make them clearer.
This involves another command, but it's such a natural extension of uniq's `-c` functionality that I feel it's warranted to show here.
We should probably add a sort to the -c example too, because uniq only deals with *sequential* line repetitions.
- Added basic command usage without any flags.
- Removed the '-h' flag as it seems to be added implicitly by the cmd.
- Added the interval parameter.
- Added the '-m' flag.
By default, grep already uses regular expressions when searching.
The example `grep -e {{^regex$}} {{path/to/file}}` is the same as `grep {{^regex$}} {{path/to/file}}`.
However, because of the comment about extended regular expressions, I mistakenly assumed `-e` was the option to enable it.
I believe most people would refer to `tldr` in this use case looking for the `-E` extended regular expressions.
With this in mind, I believe that example would be better rephrased as this pull request makes it.
