Skip to content

Conversation

spirillen
Copy link

As there was a lot of usage of spyware, I have removed these are replaced them with proper RFC references to example.net.

As there was a lot of usage of spyware, I have removed these are replaced them with proper RFC references to example.net.
README.md Outdated
# Exponent operator
echo "10^2" | bc
#100
$ 100
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be # instead of $

Copy link
Author

@spirillen spirillen Aug 29, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By adding a hashtag you would generate a H1 header and not be demonstrating the shell output of the command. And to stick to more common layout for the rest of the document $ should be the right character here

echo "10^2" | bc
$ 100 # returned value from the echo command

README.md Outdated
echo "scale=2;2/3" | bc
#.66

$ .66
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be # instead of $

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above, it is following your style for returned values. where you uses the # as the shell promt indication, usual this would be the $ sign. Should I replace them all for you to the more used $ or would you keep using the #?

Replaced command line indicators from `$` to `#`
##### Send a ping with a limited TTL to 10 (TTL: Time-To-Live, which is the maximum number of hops that a packet can travel across the Internet before it gets discarded.)
```bash
ping 8.8.8.8 -t 10
ping 192.0.2.1 -t 10
Copy link

@dibs dibs Sep 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this packet would travel across the internet but it would with 8.8.8.8

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

by using the RFC:5737 TEST-NET-1 network address 192.0.2.1 you are not promoting any trackers/spyware or any other malicious address. By mention any particular DNS recursor, would only end up in a religious war or mistrust on the idea for this cheat sheet. This is why I changed the bad resolver to a "fictive" address for neutrality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants