Good advice. Thanks!
On 9/2/24 09:38, Åke Nordin wrote:
> On 2024-08-31 15:55, Peter N. M. Hansteen wrote:
>
>> After offering https://marc.info/?l=openbsd-misc&m=172503305621176&w=2,
>> I remembered writing that slightly longer piece, which offers some explanation
>> of how things work in addition to copy-pasteable material.
>>
>> There is room for both approaches.
> There is one piece of advice in Peters
> https://nxdomain.no/~peter/youve_installed_it_now_what_packages.html
> that is virtually invaluable: use the "script" command to get a log
> of all commands you enter and their output.
>
> https://man.openbsd.org/script
>
> I'll add one piece of advice: keep a log book, a diary of what problems
> you face and how you intend to solve them. Then, if something doesn't
> work the way you intended, your script files and the log book tells you
> where to start digging. As a bonus, when you eventually replace the
> machine, you will know a lot better what you need to do to get the new
> one in the working order you prefer.
>
> Even if you're a seasoned Unix admin and work with OpenBSD systems all
> day, you will forget details about individual systems. Keeping a log
> book is how you still can stay on top of your game. It also improves
> learning.
>
No comments:
Post a Comment