You know, as much as I don’t love AI, a small model sitting in the terminal of noob installations might be a useful thing.

update graphics driver

:hey, that’s not a command, but if you’re looking to do that, you should … (step by step process)

That’s actually a good idea, just a tiny local model just to help you learn how to work in a terminal. I would have loved that when I first made the jump, the RTFM crowd almost made me give up.

I’ve been avoiding RTFM for 30 years. command --help at best. Whoever writes the manual pages and I just don’t see eye to eye on documentation.

command - description

20 examples of common usage

exhaustive list of options with a short paragraph each and acceptable usage.

that’s what I want.

It seems either they want to write you a 50 page novel mentioning random options or just give you 250 options with loose references of what’s not allowed with what.

I’ve been throwing a lot of my shell scripts into llm and asking for best practice updates, it’s shocking how much cool shit it out there that i’ve never even considered.

today’s gem:

script -q ~/command.log

do a bunch of crap

exit

script get’s written

put that together with SSH.

Now you log ssh sessions on all servers to one file. You can go back and farm that for history.

script that out so that on exit it expunges export, sql and vault type passwords/keys.