Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

An excruciatingly detailed guide to SSH (but only the things I find useful)

grahamhelton.com

Post reply on HN
Print view View original

11–20 of 120 posts

Re: An excruciatingly detailed guide to SSH (but only the things I find useful)

#11

Post by deepspace »

sevenseventen wrote: post #3

Great article that collected a lot of info that I usually wind up looking for separately. But I have to ask: do people really find color schemes like this easier to read? I'm squinting at it throughout.

> I'm squinting at it throughout

Same here. I have anecdotally noted that many people, like myself, who were around in the days of actual green screen terminals and later green monochrome monitors are far less likely to prefer dark mode than younger people.

For me, the advent of color screens that made black-on-white text possible was a huge improvement in terms of readability and eye strain reduction, and I cannot imagine going back to the old ways.

Re: An excruciatingly detailed guide to SSH (but only the things I find useful)

#12

Post by lynx23 »

zamadatix wrote: post #4
tedunangst wrote: post #2

Another member of the intergovernmental agency domain squatters club.

For those wondering what this is referring to it's the use of ".int" for the TLD of the examples. ".test" and ".example" are the only really good reserved TLDs for this (".local" isn't quite what people think it is).

I am not sure what you are hinting at with your side comment about .local, but I came here to say that I pretty much love .local. Switched all my home machines to the systemd-resolved stub with enabled mDNS. Feels so much nicer then maintaining your own DNS or hosts files... Yes, there is some initial lookup delay, but thats totally fine for private use methinks.

Re: An excruciatingly detailed guide to SSH (but only the things I find useful)

#13

Post by knome »

lynx23 wrote: post #12
zamadatix wrote: post #4

Earlier quoted context omitted.

For those wondering what this is referring to it's the use of ".int" for the TLD of the examples. ".test" and ".example" are the only really good reserved TLDs for this (".local" isn't quite what people think it is).

I am not sure what you are hinting at with your side comment about .local, but I came here to say that I pretty much love .local. Switched all my home machines to the systemd-resolved stub with enabled mDNS. Feels so much nicer then maintaining your own DNS or hosts files... Yes, there is some initial lookup delay, but thats totally fine for private use methinks.

>I am not sure what you are hinting at with your side comment about .local

They are probably referring to its special status and special handling.

https://en.wikipedia.org/wiki/.local

>The Internet Engineering Task Force (IETF) reserves the use of the domain name label .local as a special-use domain name for hostnames in local area networks that can be resolved via the Multicast DNS name resolution protocol.[2] Any DNS query for a name ending with the label local must be sent to the mDNS IPv4 link-local multicast address 224.0.0.251, or its IPv6 equivalent ff02::fb. A domain name ending in .local may be resolved concurrently via other mechanisms, for example, unicast DNS

Re: An excruciatingly detailed guide to SSH (but only the things I find useful)

#14

Post by emptyfile »

sevenseventen wrote: post #3

Great article that collected a lot of info that I usually wind up looking for separately. But I have to ask: do people really find color schemes like this easier to read? I'm squinting at it throughout.

[dead]

Re: An excruciatingly detailed guide to SSH (but only the things I find useful)

#15

Post by SL61 »

deepspace wrote: post #11
sevenseventen wrote: post #3

Great article that collected a lot of info that I usually wind up looking for separately. But I have to ask: do people really find color schemes like this easier to read? I'm squinting at it throughout.

> I'm squinting at it throughout Same here. I have anecdotally noted that many people, like myself, who were around in the days of actual green screen terminals and later green monochrome monitors are far less likely to prefer dark mode than younger people. For me, the advent of color screens that made black-on-white text possible was a huge improvement in terms of readability and eye strain reduction, and I cannot i…

As a younger person who strongly prefers black text on white backgrounds, I talked to some of my friends who use dark mode and discovered that they almost exclusively use their screens in dark rooms. Scrolling through their phone in bed with the lights off, for example. And younger PC gamers typically leave their room light off when they're on their computer.

The constant "light mode hurts my eyes!" never made sense to me until I tried using my computer in a completely dark room. So I think the trend over the past decade isn't really dark mode itself, it's more people using screens in dark rooms.

Re: An excruciatingly detailed guide to SSH (but only the things I find useful)

#16

Post by salawat »

deepspace wrote: post #11
sevenseventen wrote: post #3

Great article that collected a lot of info that I usually wind up looking for separately. But I have to ask: do people really find color schemes like this easier to read? I'm squinting at it throughout.

> I'm squinting at it throughout Same here. I have anecdotally noted that many people, like myself, who were around in the days of actual green screen terminals and later green monochrome monitors are far less likely to prefer dark mode than younger people. For me, the advent of color screens that made black-on-white text possible was a huge improvement in terms of readability and eye strain reduction, and I cannot i…

Was around in the tail end of the glory days of monochrome green/amber terminal. Still love me some dark mode. I'll admit though I've never understood light gray on black when other options stand out better.

Re: An excruciatingly detailed guide to SSH (but only the things I find useful)

#17

Post by progbits »

zamadatix wrote: post #9

For forwarding I almost never do -f. It can be a footgun in making it hard to tell which forwards are still open or operational. -t is a cool trick, didn't know about that one. An important note that's easy to overlook in the ~ escape command list is you can nest the escape when in nested sessions (i.e. if you're not using -J for whatever reason). Cool list, it definitely lines up with what I've found useful and had…

-t is great, I use

$ ssh -t my-dev-vps 'tmux new-session -A -s main'

So each time I run it I'm right back where I left off.

Re: An excruciatingly detailed guide to SSH (but only the things I find useful)

#18

Post by digging »

tiffanyh wrote: post #10
zamadatix wrote: post #4

Earlier quoted context omitted.

For those wondering what this is referring to it's the use of ".int" for the TLD of the examples. ".test" and ".example" are the only really good reserved TLDs for this (".local" isn't quite what people think it is).

Example.com People should just use example.com, it’s reserved and the most obvious to the end user that it’s for example purposes. https://en.wikipedia.org/wiki/Example.com

Doesn't work if you need to refer to more than one domain.

.example is also reserved for this exact purpose.

Re: An excruciatingly detailed guide to SSH (but only the things I find useful)

#20

Post by layer8 »

digging wrote: post #18
tiffanyh wrote: post #10

Earlier quoted context omitted.

Example.com People should just use example.com, it’s reserved and the most obvious to the end user that it’s for example purposes. https://en.wikipedia.org/wiki/Example.com

Doesn't work if you need to refer to more than one domain. .example is also reserved for this exact purpose.

It does work when you use subdomains. And there’s also example.org and example.net.
Post reply on HN