Unfortunately, sometimes (often) there is no man page for what you are looking for. So if you get a page not found, that's usually the case. You can usually find associated pages all the way at the bottom. That helps when what you are looking for isn't a command, but a reference. I don't remember exactly where it is, but man pages are stored in a directory. Probably /etc or /usr. You can always dump that list into fzf or use grep to search to see if there is a page for what you are looking for. It's not a perfect system by any means, but it's a good one to have in your toolbelt.
wuphysics87
I can appreciate that. Appologies if you know this already, but just don't like them. Here are some tips.
It helps a lot to get title/subtitle/flag highlighting. By default man pages are hard to use simply because of how dense they are. It's much easier to skim when you can separate the parts you are looking for up front from the text.
Don't forget '/', 'n', and 'N'. First way to use man pages more effectively is to search them easily. And you can search via regex. Often I'm looking for more info on a particular flag. So I'll press '/' followed by '^ *-g'. For a g flag.
Take notes on the side. It saves you time later. Your future self will thank you. And you learn a lot by skimming them.
Man pages can be intimidating/confusing, but, imho, it's worth training that skill. Even if you are slower up front, it's totally worth it.
Yea that's a good point. I guess I'm living in fairy tale land considering meeting mandatory minimum and deductible 🤣 A boy can dream
tldr is the first of 4 ways I rtfm. Then -h, man, and then the arch wiki
Shop around if you don't like your GP. Tell them your situation and ask them for a referal to every specialist under the sun. Get tested and innoculated for absolutely everything they suggest.
Some people also use downvotes as way to say they dislike something. Unlikely, but some people might be down voting to indicate they don't like the insurance industry.
I have two. One moving some 'friends'. One moving myself.
The first was when I was in graduate school. About five of us agreed to move a couple and their kid across town. One was another graduate student. His wife was the front office admin. We figured it was nbd. One of us had a truck and they got uhaul. Little did we know 'moving' meant 'packing'. What should have been an afternoon turned into three days. Largely because of how particular she was about how things were packed. We would have said no, but she was in charge of important documents like travel reimbursements so we didn't want to risk it.
The second was moving to a new job. The truck was late, the place was filthy, and I had to sleep on the wooden floors. Those floors were so disgusting I decided to clean them. I vacuumed. I mopped. Nothing would get them clean, so I got a power washer. I learned that day that power washers can set off smoke detectors. The entire building was evacuated. Afterwards, I had to meet with the dean about it. She chewed me out and asked why I hadn't called facilities to have it clean. I told her if it wasn't cleaned before I moved in why should I expect it to be cleaned now. I have a feeling my contract not being renewed had something to do with that.
If you can forgo a gui, it shouldn't be hard to write a bash script to do this
Yes that's partly the idea. It doesn't tip the scale. The idea with lowering the voting age as possible it does come out in the wash, but the benefit is that kids are civically engaged. The hope being that engagement carries over as they get older
Aside from practical reasons like being able to read and write, I think the age to vote should be as low as possible.
People are concerned that parents will coerce their kids, but that would happen across the board. It would come out in the wash.
The most important thing is that folks are civically engaged as young as possible. They are invested in the outcome and exercise their rights early.
I would say a good starting point would be third grade. Right when you begin learning social studies.
Do something that will make them laugh and enjoy themselves.
I gave a seminar once that ended with a demonstration of the terminal, ssh, and nginx. I had everyone go to the url where I was hosting a hello world. I killed the server over ssh and told them to refresh the page. Nothing there. I swapped the page, turned it back on, and told them to refresh the page again. I Rick Rolled them. They all laughed. It may not have been the most informative talk, I didn't really 'teach' them anything, but I got some good questions afterwards.
Be creative and make it fun and they will come to you.
That is a very unpleasant analogy