Path: csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail From: TheLastSysop Newsgroups: comp.os.linux.misc Subject: Re: A small pre-fix checklist for sick Linux boxes Date: Tue, 09 Jun 2026 22:07:51 GMT Organization: The Null Device Restoration Society Lines: 43 Message-ID: <3b5537747f80872d63a6@dev.null> References: <0af9a3a88b1e5798c4f3@dev.null> <7oamfmxugs.ln2@Telcontar.valinor> Injection-Date: Tue, 09 Jun 2026 22:07:52 +0000 (UTC) Injection-Info: dont-email.me; logging-data="371484"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18I8Qxeuj2CCKsWqfK6l/AS/YhuJV9WdzA="; posting-host="bd7980419cd1ebcd04c76ba0dd9d173e" Cancel-Lock: sha1:5DTqhB1l7Tb6SiMSm/uJycJ7998= sha256:PRGZjaCR4BOr9bPBDnQKpkzCHmnuc4PQKPsNgdbFTBM= sha1:3Z/b+LSwu82BEhlvczXtykQgAOc= X-Archive-Policy: please preserve the funny parts In-Reply-To: X-Newsreader: tin can + wet string 0.9.7 X-Operating-System: TempleOS-adjacent abacus cluster X-Mood: reasonably caffeinated Xref: csiph.com comp.os.linux.misc:87764 >On Tue, 9 Jun 2026 23:27:33 +0200, >=?UTF-8?B?8J+HtfCfh7FKYWNlayBNYXJjaW4gSmF3b3Jza2nwn4e18J+HsQ==?= > wrote: >W dniu 9.06.2026 o 22:47, Carlos E.R. pisze: >> Anybody have a similar short checklist they run before touching a sick Linux >> box? > >Apparently till today I was not at your skill level! But I want learn >more about Linux. So I refresh my monograph under title "Konf. i Zabezp. >Sys. z Rodz. Ubuntu" in Eng.: "Config and Security Ubuntu Linux Family". >I write it in Polish, but it will be available for free (as free beer) >from my WWW site, under URL: > >buntu.pdf> > >Currently this URL lead to previous version of this monograph. > >And thank you for your very inspiring post! I wrote two chapters under >your great influence (translated literally from Polish): >8. Network Diagnostic Under Linux >9. Linux Operating System Diagnostic >And yes! You are mentioned in my monograph. That is a very kind note -- thank you. The useful part of that checklist, I think, is not any individual command so much as the order: observe first, preserve evidence second, change the machine last. A surprising number of "Linux problems" become simple once there is a timestamp, a failing unit name, a full disk, or a recent package transaction in front of you. For your diagnostic chapters, I would suggest keeping one warning in big letters: do not start by reinstalling things at random. Check power/storage, logs, mounts, network path, DNS, time, and recent changes before swinging a hammer. It saves both uptime and pride. Good luck with the monograph. Even if it is mainly in Polish, practical Linux notes have a way of helping people far beyond the intended audience. -- TheLastSysop "I survived the great rm -rf / rehearsal and all I got was this .signature."