<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kituwa Blog</title><link>https://it.kituwa.com/blogs/blog/</link><atom:link href="https://it.kituwa.com/blogs/blog/index.xml" rel="self" type="application/rss+xml"/><description>Kituwa Blog</description><generator>HugoBlox Kit (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Thu, 19 Nov 2026 20:19:57 +0000</lastBuildDate><item><title>NGINX2Root: Remote Code Execution vulnerabilities in nginx</title><link>https://it.kituwa.com/blogs/blog/nginx2root-remote-code-execution-vulnerabilities-in-nginx/</link><pubDate>Thu, 19 Nov 2026 20:19:57 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/nginx2root-remote-code-execution-vulnerabilities-in-nginx/</guid><description>&lt;p class="news-article__lede"&gt;# NGINX2Root: Remote Code Execution vulnerabilities in nginx Xint is reporting that it has discovered a collection of five critical vulnerabilities in the NGINX web server. The worst flaw, it says, would allow an unauthenticated attacker to execute commands on an affected nginx server with HTTP/2 enabled. The company also reports a local-privilege escalation (LPE) kernel vulnerability, which was introduced in the 4.15 kernel, in the Stream Control Transmission Protocol (SCTP) subsystem. If chained with the NGINX vulnerability, it would allow an attacker to gain root privileges on the host. A kernel patch for this is not yet available. We also obtained a root shell on the host in a setup where nginx was running in a Docker container. On many Linux distributions, the SCTP module is installed by default and the kernel loads it automatically the first time a program opens an SCTP socket. Whether SCTP is reachable on a given host still depends on the kernel, the available modules, and the container&amp;#x27;s restrictions. Where it is reachable, the attacker can take over the host kernel. Since all containers on the host share that kernel, this gives the attacker control of the host and every co&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Key components named in the report: nginx.&lt;/li&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;pre&gt;&lt;code&gt; &amp;lt;h2&amp;gt;Why it matters&amp;lt;/h2&amp;gt;
&amp;lt;p&amp;gt;Linux runs a large share of the internet&amp;amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&amp;lt;/p&amp;gt;
&amp;lt;h2&amp;gt;What to do&amp;lt;/h2&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Check the official advisory for the affected versions and fixed versions.&amp;lt;/li&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://lwn.net/Articles/1108362" target="_blank" rel="noopener noreferrer"&gt;LWN.net&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>Debian's APT Removing Some Features Due To Advancements In AI Security Discoveries</title><link>https://it.kituwa.com/blogs/blog/debian-s-apt-removing-some-features-due-to-advancements-in-ai-security/</link><pubDate>Thu, 19 Nov 2026 17:18:59 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/debian-s-apt-removing-some-features-due-to-advancements-in-ai-security/</guid><description>&lt;p class="news-article__lede"&gt;# Debian&amp;#x27;s APT Removing Some Features Due To Advancements In AI Security Discoveries Written by Michael Larabel in Debian on 19 November 2026 at 09:15 AM EST. ... Stemming from the recent Debian APT man-in-the-middle attack from a vulnerability in APT&amp;#x27;s downloading code and ongoing advancements in AI/LLMs around security research, APT is now resorting to disabling and removing some older, complex features that may make the program more vulnerable to finding exploits moving forward. Debian developer Julian Andres Klode announced that next week he will be removing support for various features in APT that are now declared end-of-life. The features planned for the near-immediate removal include support for repositories with detached Release.gpg signatures, repositories with only weak hashes like MD5 or SHA1, and repositories without hashes / Release file. Also being considered for removal are insecure repositories with the &amp;quot;allow-insecure&amp;quot; or &amp;quot;allow-downgrade-to-insecure&amp;quot; options, fallbacks to a different file if one route fails, and other non-essential features. Some features could be restored later if they are deemed &amp;quot;safe&amp;quot;: &amp;quot;As we gain a better understanding of the control flow we m&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Key components named in the report: Debian.&lt;/li&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software”&lt;/p&gt;&lt;footer&gt;— Phoronix&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;Phoronix Premium allows ad-free access to the site, multi-page articles on a single page, and other features while supporting this site&amp;#x27;s continued operations.&lt;/p&gt;&lt;p&gt;The mission at Phoronix since 2004 has centered around enriching the Linux hardware experience. In addition to supporting our site through advertisements, you can help by subscribing to Phoronix Premium. You can also contribute to Phoronix through tips/donations via PayPal or Stripe.&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Linux runs a large share of the internet&amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://phoronix.com/news/Debian-APT-Removing-Features" target="_blank" rel="noopener noreferrer"&gt;Phoronix&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>Linux 6.18.64 [LWN.net]</title><link>https://it.kituwa.com/blogs/blog/linux-6-18-64-lwn-net/</link><pubDate>Thu, 19 Nov 2026 02:15:44 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/linux-6-18-64-lwn-net/</guid><description>&lt;p class="news-article__lede"&gt;LWN .net News from the source · Content · Weekly Edition · Archives · Search · Kernel · Security · Events calendar · Unread comments · LWN FAQ · Write for us · | | Log in / Subscribe / Register · I&amp;#x27;m announcing the release of the 6.18.64 kernel. All users of the 6.18 kernel series ...&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;pre&gt;&lt;code&gt; &amp;lt;h2&amp;gt;Why it matters&amp;lt;/h2&amp;gt;
&amp;lt;p&amp;gt;Linux runs a large share of the internet&amp;amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&amp;lt;/p&amp;gt;
&amp;lt;h2&amp;gt;What to do&amp;lt;/h2&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Check the official advisory for the affected versions and fixed versions.&amp;lt;/li&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://lwn.net/Articles/1108144" target="_blank" rel="noopener noreferrer"&gt;LWN.net&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>AlmaLinux 10.3 Released With ModSecurity Restored, Various Updates</title><link>https://it.kituwa.com/blogs/blog/almalinux-10-3-released-with-modsecurity-restored-various-updates/</link><pubDate>Tue, 17 Nov 2026 11:18:05 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/almalinux-10-3-released-with-modsecurity-restored-various-updates/</guid><description>&lt;p class="news-article__lede"&gt;# AlmaLinux 10.3 Released With ModSecurity Restored, Various Updates Written by Michael Larabel in Operating Systems on 16 November 2026 at 05:35 PM EST. ... Following the recent Red Hat Enterprise Linux 10.3 release, AlmaLinux 10.3 is now available in production along with AlmaLinux 9.9. ... There are also a wide variety of security updates. On the security side, AlmaLinux 10.3 restores the ModSecurity web application firewall and OWASP Core Rule Set (CRS) after they were removed back in AlmaLinux 10.0.&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software”&lt;/p&gt;&lt;footer&gt;— Phoronix&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;Phoronix Premium allows ad-free access to the site, multi-page articles on a single page, and other features while supporting this site&amp;#x27;s continued operations.&lt;/p&gt;&lt;p&gt;The mission at Phoronix since 2004 has centered around enriching the Linux hardware experience. In addition to supporting our site through advertisements, you can help by subscribing to Phoronix Premium. You can also contribute to Phoronix through tips/donations via PayPal or Stripe.&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Kernel and distribution changes set the support window, driver support, and security posture for everything built on top. Knowing what landed now helps you plan upgrades, test drivers, and avoid surprises when the change reaches your distribution&amp;#x27;s stable branch.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Read the release notes for changes that affect your hardware or workflow.&lt;/li&gt;
&lt;li&gt;Test the new kernel or distribution on a spare machine before a production upgrade.&lt;/li&gt;
&lt;li&gt;Keep the previous kernel or a rollback path available until the new one is proven.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://phoronix.com/news/AlmaLinux-10.3-Released" target="_blank" rel="noopener noreferrer"&gt;Phoronix&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>Gitea 28.4 Patches Multiple Security Vulnerabilities</title><link>https://it.kituwa.com/blogs/blog/gitea-28-4-patches-multiple-security-vulnerabilities/</link><pubDate>Tue, 17 Nov 2026 08:15:53 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/gitea-28-4-patches-multiple-security-vulnerabilities/</guid><description>&lt;p class="news-article__lede"&gt;Gitea 28.4 addresses security vulnerabilities involving remote code execution, password hash exposure, authentication, and repository permissions.&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Tracked as CVE-2026-125423, CVE-2026-123006.&lt;/li&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“Gitea, the self-hosted Git service and software development platform, has released version 28.4, the fourth maintenance update in the 28.x series. Given the severity of the security fixes, the developers strongly recommend that all users upgrade as soon as possible.”&lt;/p&gt;&lt;footer&gt;— Linuxiac&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;One of the most serious vulnerabilities, tracked as CVE-2026-125423, affects repository initialization. Under certain conditions, a user allowed to create repositories could exploit a race condition to overwrite a Git hook on the server and execute commands with the privileges of the Gitea system account.&lt;/p&gt;&lt;p&gt;Another significant issue, CVE-2026-123006, involves the repository search endpoint. Since Gitea 28.0, its responses could include internal user information, allowing authenticated users to retrieve repository owners’ password hashes, salts, and email addresses. The endpoint now limits returned data to the necessary commit status information.&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Linux runs a large share of the internet&amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://linuxiac.com/gitea-28-4-patches-multiple-security-vulnerabilities" target="_blank" rel="noopener noreferrer"&gt;Linuxiac&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>Asahi Linux Moves from MIT to GPL Licensing, Expands M3 Support</title><link>https://it.kituwa.com/blogs/blog/asahi-linux-moves-from-mit-to-gpl-licensing-expands-m3-support/</link><pubDate>Tue, 17 Nov 2026 05:18:59 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/asahi-linux-moves-from-mit-to-gpl-licensing-expands-m3-support/</guid><description>&lt;p class="news-article__lede"&gt;# Asahi Linux Moves from MIT to GPL Licensing, Expands M3 Support Asahi Linux moves toward GPL licensing amid concerns over commercial code reuse and removes installation restrictions for M3 Macs. Asahi Linux, the project to get Linux running on Apple Silicon Macs, has announced a significant change to its licensing approach. In its most recent progress report, they say they are moving from the permissive MIT license to GPL v2 or later. This licensing decision comes after what the project describes as several attempts by third parties to take over their work, with the intention of replacing the project and then commercializing Linux on Apple Silicon. According to Asahi Linux, various third parties have attempted to do this. In the most extreme cases, the team stated that code which was still in development was simply copied directly from the contributors’ personal repos and re-published without any attribution. In other cases, they’ve reportedly used large language models to rewrite the code and, in that way, mask the source. Asahi Linux initially went with the MIT license in order to encourage collaboration with other open source operating systems (including the BSD projects). The&lt;/p&gt;
&lt;pre&gt;&lt;code&gt; &amp;lt;h2&amp;gt;What happened&amp;lt;/h2&amp;gt;
&amp;lt;blockquote&amp;gt;&amp;lt;p&amp;gt;“Asahi Linux, the project to get Linux running on Apple Silicon Macs, has announced a significant change to its licensing approach. In its most recent progress report, they say they are moving from the permissive MIT license to GPL v2 or later.”&amp;lt;/p&amp;gt;&amp;lt;footer&amp;gt;— Linuxiac&amp;lt;/footer&amp;gt;&amp;lt;/blockquote&amp;gt;
&amp;lt;p&amp;gt;The licensing decision comes after what the project describes as several attempts by third parties to take over their work, with the intention of replacing the project and then commercializing Linux on Apple Silicon. According to Asahi Linux, various third parties have attempted to do this.&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;In the most extreme cases, the team stated that code which was still in development was simply copied directly from the contributors’ personal repos and re-published without any attribution. In other cases, they’ve reportedly used large language models to rewrite the code and, in that way, mask the source.&amp;lt;/p&amp;gt;
&amp;lt;h2&amp;gt;Why it matters&amp;lt;/h2&amp;gt;
&amp;lt;p&amp;gt;Linux runs a large share of the internet&amp;amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&amp;lt;/p&amp;gt;
&amp;lt;h2&amp;gt;What to do&amp;lt;/h2&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Check the official advisory for the affected versions and fixed versions.&amp;lt;/li&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://linuxiac.com/asahi-linux-moves-from-mit-to-gpl-licensing-expands-m3-support" target="_blank" rel="noopener noreferrer"&gt;Linuxiac&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>Rocky Linux 10.3 Released with More Post-Quantum Cryptography Improvements</title><link>https://it.kituwa.com/blogs/blog/rocky-linux-10-3-released-with-more-post-quantum-cryptography-improvements/</link><pubDate>Tue, 17 Nov 2026 02:17:13 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/rocky-linux-10-3-released-with-more-post-quantum-cryptography-improvements/</guid><description>&lt;p class="news-article__lede"&gt;# Rocky Linux 10.3 Released with More Post-Quantum Cryptography Improvements This release is based on the Red Hat Enterprise Linux 10.3 operating system and it’s powered by Linux kernel 6.12 LTS. Rocky Linux 10.3 has been released as a free alternative to Red Hat Enterprise Linux 10.3 with more post-quantum cryptography improvements, new kernel features, updated components, and other changes. Coming five and a half months after Rocky Linux 10.2, the Rocky Linux 10.3 release brings more post-quantum cryptography improvements, including support for ML-KEM-768 and ML-KEM-1024 post-quantum key exchange in IKEv2 with libreswan 5.4. The post-quantum cryptography improvements continue with support for the mlkem768nistp256-sha256 and mlkem1024nistp384-sha384 hybrid key exchange algorithms, now preferred, in SSH’s FIPS mode, and full post-quantum cryptography support in rust-sequoia-sqv, based on the final OpenPGP RFC 9980. Rocky Linux 10.3 also updates the audit packages to support TLS 1.3 with post-quantum cryptography and PSK authentication for remote logging, while OpenSC received support for PKCS #11 version 3.2 and post-quantum cryptography features, and the Go programming language ge&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Key components named in the report: Linux kernel.&lt;/li&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;pre&gt;&lt;code&gt; &amp;lt;h2&amp;gt;Why it matters&amp;lt;/h2&amp;gt;
&amp;lt;p&amp;gt;Linux runs a large share of the internet&amp;amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&amp;lt;/p&amp;gt;
&amp;lt;h2&amp;gt;What to do&amp;lt;/h2&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Review SSH exposure first: restrict access and watch authentication logs.&amp;lt;/li&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://9to5linux.com/rocky-linux-10-3-released-with-more-post-quantum-cryptography-improvements" target="_blank" rel="noopener noreferrer"&gt;9to5Linux&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>NoisyTCP bug gives Linux servers a remote crash problem 11 years in the making</title><link>https://it.kituwa.com/blogs/blog/noisytcp-bug-gives-linux-servers-a-remote-crash-problem-11-years-in-the-making/</link><pubDate>Mon, 16 Nov 2026 23:15:47 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/noisytcp-bug-gives-linux-servers-a-remote-crash-problem-11-years-in-the-making/</guid><description>&lt;p class="news-article__lede"&gt;# NoisyTCP bug gives Linux servers a remote crash problem 11 years in the making Flaw can take down an entire host, even when the vulnerable service is running inside a container The researcher who sounded the alarm over Dirty Frag earlier this year has uncovered another Linux kernel flaw, and this one lets attackers crash entire servers remotely without so much as a password. The vulnerability, tracked as CVE-2026-99288 and dubbed NoisyTCP, was discovered by security researcher Hyunwoo Kim, who says it affects almost all Linux distributions. The flaw dates back to October 2015 and went unnoticed until this year, when Kim found and patched it. Attackers don&amp;#x27;t need to log in or get their hands on any credentials to cause trouble. They can simply knock the server over, although there&amp;#x27;s no evidence yet that the flaw can be used to steal data or hijack a machine. REG AD The bug is buried in Linux&amp;#x27;s TCP networking code. Two parts of the kernel can trip over each other while processing incoming traffic, leaving one trying to use memory that&amp;#x27;s already been freed. When that happens, Linux can panic and take the whole machine down with it. REG AD Kim says there&amp;#x27;s no need for any special ser&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Tracked as CVE-2026-99288.&lt;/li&gt;&lt;li&gt;Key components named in the report: Linux kernel, nginx, ARM.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“Flaw can take down an entire host, even when the vulnerable service is running inside a container”&lt;/p&gt;&lt;footer&gt;— The Register&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;The researcher who sounded the alarm over Dirty Frag earlier this year has uncovered another Linux kernel flaw, and this one lets attackers crash entire servers remotely without so much as a password.&lt;/p&gt;&lt;p&gt;The vulnerability, tracked as CVE-2026-99288 and dubbed NoisyTCP, was discovered by security researcher Hyunwoo Kim, who says it affects almost all Linux distributions. The flaw dates back to October 2015 and went unnoticed until this year, when Kim found and patched it.&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Linux runs a large share of the internet&amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Review SSH exposure first: restrict access and watch authentication logs.&lt;/li&gt;
&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://theregister.com/security/2026/11/16/noisytcp-bug-gives-linux-servers-a-remote-crash-problem-11-years-in-the-making/5310144" target="_blank" rel="noopener noreferrer"&gt;The Register&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>im a lil penuin who check major linux outlets hourly and brings you important updates from the world beyond facebook!…</title><link>https://it.kituwa.com/blogs/blog/facebook-20261116-im-a-lil-penuin-who-check-major-linux-outlets-hourly-539584/</link><pubDate>Mon, 16 Nov 2026 20:42:06 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/facebook-20261116-im-a-lil-penuin-who-check-major-linux-outlets-hourly-539584/</guid><description>&lt;p&gt;im a lil penuin who check major linux outlets hourly and brings you important updates from the world beyond facebook! Follow to really stay in the know on everything linux.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.facebook.com/122105052855539584/posts/122109149079539584" target="_blank" rel="noopener noreferrer"&gt;View this post on Facebook&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Ubuntu kernel security update: USN-9035-1</title><link>https://it.kituwa.com/blogs/blog/ubuntu-alert-usn-9035-1-kernel-ubuntu-alert-usn-9035-1-kernel/</link><pubDate>Mon, 16 Nov 2026 20:16:31 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/ubuntu-alert-usn-9035-1-kernel-ubuntu-alert-usn-9035-1-kernel/</guid><description>&lt;p class="news-article__lede"&gt;Canonical published USN-9035-1 for several Linux kernel vulnerabilities. Check the affected Ubuntu release, apply the tested update after a backup, and keep a rollback path.&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Tracked as CVE-2017-9986, CVE-2022-49114, CVE-2023-52784.&lt;/li&gt;&lt;li&gt;Key components named in the report: Linux kernel, Ubuntu.&lt;/li&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;pre&gt;&lt;code&gt; &amp;lt;h2&amp;gt;Why it matters&amp;lt;/h2&amp;gt;
&amp;lt;p&amp;gt;Linux runs a large share of the internet&amp;amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&amp;lt;/p&amp;gt;
&amp;lt;h2&amp;gt;What to do&amp;lt;/h2&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Check the official advisory for the affected versions and fixed versions.&amp;lt;/li&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://lwn.net/Articles/1106493" target="_blank" rel="noopener noreferrer"&gt;LWN.net&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>Microsoft's Azure Linux gets 470-plus security fixes in one almighty patching session</title><link>https://it.kituwa.com/blogs/blog/microsoft-s-azure-linux-gets-470-plus-security-fixes-in-one-almighty-patching/</link><pubDate>Sun, 15 Nov 2026 11:19:12 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/microsoft-s-azure-linux-gets-470-plus-security-fixes-in-one-almighty-patching/</guid><description>&lt;p class="news-article__lede"&gt;Over the weekend, Microsoft rolled ... from the Linux kernel to open source packages and container software. The changelog runs to hundreds of entries, so anyone planning to read the whole thing might want to put the kettle on. Microsoft&amp;#x27;s release notes contain more than 470 CVE references, although some vulnerabilities appear multiple times because they affect different packages. So that&amp;#x27;s not necessarily 470 separate security holes, but ...&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Key components named in the report: Linux kernel.&lt;/li&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“A mountain of CVEs, a certificate cleanup, and yet more work for Microsoft&amp;#x27;s patching teams”&lt;/p&gt;&lt;footer&gt;— The Register&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;Microsoft has unleashed a whopper of an update for Azure Linux, packing more than 470 CVE fixes into a single release as the software industry&amp;#x27;s ever-growing pile of vulnerabilities shows little sign of shrinking.&lt;/p&gt;&lt;p&gt;Over the weekend, Microsoft rolled out Azure Linux 3.0.2022 with fixes covering everything from the Linux kernel to open source packages and container software. The changelog runs to hundreds of entries, so anyone planning to read the whole thing might want to put the kettle on.&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Linux runs a large share of the internet&amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://theregister.com/security/2026/11/09/microsofts-azure-linux-gets-470-plus-security-fixes-in-one-almighty-patching-session/5308434" target="_blank" rel="noopener noreferrer"&gt;The Register&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>OpenAI Codex Helps Uncover &amp; Fix A Nearly 20 Year Old Radeon Linux Driver Bug</title><link>https://it.kituwa.com/blogs/blog/openai-codex-helps-uncover-fix-a-nearly-20-year-old-radeon-linux-driver-bug/</link><pubDate>Sun, 15 Nov 2026 08:18:34 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/openai-codex-helps-uncover-fix-a-nearly-20-year-old-radeon-linux-driver-bug/</guid><description>&lt;p class="news-article__lede"&gt;Sent out today was the latest batch of AMD kernel graphics/compute driver patches destined for the Linux 7.5 merge window opening up at year&amp;#x27;s end/ Besides a lot of fixes and continued work around new IP enablement for upcoming GPUs, there is even a fix for old ATI/AMD Radeon R600 era hardware after help from OpenAI&amp;#x27;s Codex.&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Key components named in the report: AMD.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software”&lt;/p&gt;&lt;footer&gt;— Phoronix&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;Phoronix Premium allows ad-free access to the site, multi-page articles on a single page, and other features while supporting this site&amp;#x27;s continued operations.&lt;/p&gt;&lt;p&gt;The mission at Phoronix since 2004 has centered around enriching the Linux hardware experience. In addition to supporting our site through advertisements, you can help by subscribing to Phoronix Premium. You can also contribute to Phoronix through tips/donations via PayPal or Stripe.&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Linux runs a large share of the internet&amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://phoronix.com/news/Codex-R600-UVD-FIx-Linux-7.5" target="_blank" rel="noopener noreferrer"&gt;Phoronix&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>NVIDIA NvRoot &amp; ForgePtr Vulnerabilities Published For Linux Driver, 25 More Coming</title><link>https://it.kituwa.com/blogs/blog/nvidia-nvroot-forgeptr-vulnerabilities-published-for-linux-driver-25-more-coming/</link><pubDate>Sun, 15 Nov 2026 05:19:01 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/nvidia-nvroot-forgeptr-vulnerabilities-published-for-linux-driver-25-more-coming/</guid><description>&lt;p class="news-article__lede"&gt;# NVIDIA NvRoot &amp;amp; ForgePtr Vulnerabilities Published For Linux Driver, 25 More Coming Written by Michael Larabel in NVIDIA on 12 November 2026 at 09:17 AM EST. ... In addition to Jensen Huang resigning, coincidentally the embargo just expired on the first two of 25 more NVIDIA graphics driver security vulnerabilities coming. ForgePtr and NvRoot are particularly volatile for those renting GPU slices in the cloud. Stealthium made public today ForgePtr (CVE-2026-47501) and NvRoot (CVE-2026-47591). With ForgePtr, an unprivileged process in a GPU container can go root on the host. With NvRoot, the GPU can rewrite files the OS has marked as read-only from any tenant on the node. These vulnerabilities have existed in the NVIDIA open kernel modules for the past four years and rated as CVE 7.8 &amp;quot;high&amp;quot; vulnerabilities. NvRoot is fixed by the NVIDIA 610.57.04 / 595.91.07 / 580.178.04 drivers while ForgePtr is fixed in 615.71.09. In a message to Phoronix, Stealthium says they have 25 more security disclosures to come that affect the NVIDIA AI runtime stack. Blog posts provide more details on NvRoot and ForgePtr.&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Tracked as CVE-2026-47501, CVE-2026-47591.&lt;/li&gt;&lt;li&gt;Key components named in the report: NVIDIA.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software”&lt;/p&gt;&lt;footer&gt;— Phoronix&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;Phoronix Premium allows ad-free access to the site, multi-page articles on a single page, and other features while supporting this site&amp;#x27;s continued operations.&lt;/p&gt;&lt;p&gt;The mission at Phoronix since 2004 has centered around enriching the Linux hardware experience. In addition to supporting our site through advertisements, you can help by subscribing to Phoronix Premium. You can also contribute to Phoronix through tips/donations via PayPal or Stripe.&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Linux runs a large share of the internet&amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://phoronix.com/news/NVIDIA-NvRoot-ForgePtr" target="_blank" rel="noopener noreferrer"&gt;Phoronix&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>Ubuntu Pro users get early access to AI-written security fixes</title><link>https://it.kituwa.com/blogs/blog/ubuntu-pro-users-get-early-access-to-ai-written-security-fixes/</link><pubDate>Sun, 15 Nov 2026 02:16:41 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/ubuntu-pro-users-get-early-access-to-ai-written-security-fixes/</guid><description>&lt;p class="news-article__lede"&gt;Canonical is giving Ubuntu Pro users early access to AI-generated patches for known security flaws, available through a new opt-in archive called Edge. To&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Key components named in the report: Ubuntu.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“Canonical is giving Ubuntu Pro users early access to AI-generated patches for known security flaws, available through a new opt-in archive called Edge.”&lt;/p&gt;&lt;footer&gt;— OMG! Ubuntu&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;To get fixes out faster to customers and users, the company has built a multi-agent system called Surge to backport fixes for vulnerabilities in software packages.&lt;/p&gt;&lt;p&gt;The machine-generated patches land in the Edge archive. This is opt-in and not enabled by default. Ubuntu Pro Users who want fixes before they receive full testing or ‘qualification’, will need to manually enable the Edge archive on supported systems.&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Linux runs a large share of the internet&amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://omgubuntu.co.uk/2026/11/ubuntu-pro-ai-security-archive" target="_blank" rel="noopener noreferrer"&gt;OMG! Ubuntu&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>Cloudflare Open Sources Kitesurf: Their Web Browser For AI Agents</title><link>https://it.kituwa.com/blogs/blog/cloudflare-open-sources-kitesurf-their-web-browser-for-ai-agents/</link><pubDate>Sat, 14 Nov 2026 17:20:03 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/cloudflare-open-sources-kitesurf-their-web-browser-for-ai-agents/</guid><description>&lt;p class="news-article__lede"&gt;Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt; &amp;lt;h2&amp;gt;What happened&amp;lt;/h2&amp;gt;
&amp;lt;blockquote&amp;gt;&amp;lt;p&amp;gt;“Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software”&amp;lt;/p&amp;gt;&amp;lt;footer&amp;gt;— Phoronix&amp;lt;/footer&amp;gt;&amp;lt;/blockquote&amp;gt;
&amp;lt;p&amp;gt;Phoronix Premium allows ad-free access to the site, multi-page articles on a single page, and other features while supporting this site&amp;amp;#x27;s continued operations.&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;The mission at Phoronix since 2004 has centered around enriching the Linux hardware experience. In addition to supporting our site through advertisements, you can help by subscribing to Phoronix Premium. You can also contribute to Phoronix through tips/donations via PayPal or Stripe.&amp;lt;/p&amp;gt;
&amp;lt;h2&amp;gt;Why it matters&amp;lt;/h2&amp;gt;
&amp;lt;p&amp;gt;Linux runs a large share of the internet&amp;amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&amp;lt;/p&amp;gt;
&amp;lt;h2&amp;gt;What to do&amp;lt;/h2&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Check the official advisory for the affected versions and fixed versions.&amp;lt;/li&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://phoronix.com/news/Cloudflare-Kitesurf-Open-Source" target="_blank" rel="noopener noreferrer"&gt;Phoronix&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>Intel Begins Linux Kernel Enablement For Coral Rapids &amp; Razor Lake</title><link>https://it.kituwa.com/blogs/blog/intel-begins-linux-kernel-enablement-for-coral-rapids-razor-lake/</link><pubDate>Sat, 14 Nov 2026 14:20:01 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/intel-begins-linux-kernel-enablement-for-coral-rapids-razor-lake/</guid><description>&lt;p class="news-article__lede"&gt;Razor Lake is the successor to the upcoming Nova Lake processors. These Intel CPUs coming out in 2028 should be quite interesting and great seeing the open-source/Linux support now getting underway. On the same day as posting the GCC patches, Tony Luck at Intel posted the first kernel patch ...&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Key components named in the report: Linux kernel.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software”&lt;/p&gt;&lt;footer&gt;— Phoronix&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;Phoronix Premium allows ad-free access to the site, multi-page articles on a single page, and other features while supporting this site&amp;#x27;s continued operations.&lt;/p&gt;&lt;p&gt;The mission at Phoronix since 2004 has centered around enriching the Linux hardware experience. In addition to supporting our site through advertisements, you can help by subscribing to Phoronix Premium. You can also contribute to Phoronix through tips/donations via PayPal or Stripe.&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Linux runs a large share of the internet&amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://phoronix.com/news/Linux-Coral-Rapids-Razor-Lake" target="_blank" rel="noopener noreferrer"&gt;Phoronix&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>NVIDIA Highlights Their Open-Source vGPU Upstreaming Work Built Atop Nova</title><link>https://it.kituwa.com/blogs/blog/nvidia-highlights-their-open-source-vgpu-upstreaming-work-built-atop-nova/</link><pubDate>Fri, 13 Nov 2026 23:17:39 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/nvidia-highlights-their-open-source-vgpu-upstreaming-work-built-atop-nova/</guid><description>&lt;p class="news-article__lede"&gt;NVIDIA 620.70.06 Linux Driver Released With Wayland Fixes &amp;amp; Performance Work · CUDA Oxide 0.3 Vastly Improves Rust Support For NVIDIA CUDA Programming · NVIDIA&amp;#x27;s Nova Driver Continues Leading The Way For Linux Rust GPU Drivers · About The Author · Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience.&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Key components named in the report: Wayland, NVIDIA.&lt;/li&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software”&lt;/p&gt;&lt;footer&gt;— Phoronix&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;Phoronix Premium allows ad-free access to the site, multi-page articles on a single page, and other features while supporting this site&amp;#x27;s continued operations.&lt;/p&gt;&lt;p&gt;The mission at Phoronix since 2004 has centered around enriching the Linux hardware experience. In addition to supporting our site through advertisements, you can help by subscribing to Phoronix Premium. You can also contribute to Phoronix through tips/donations via PayPal or Stripe.&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Linux runs a large share of the internet&amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://phoronix.com/news/NVIDIA-Upstream-vGPU-Nova" target="_blank" rel="noopener noreferrer"&gt;Phoronix&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>ATI/AMD R300 To R500 GPUs See New 2026 OpenGL Linux Driver Optimizations</title><link>https://it.kituwa.com/blogs/blog/ati-amd-r300-to-r500-gpus-see-new-2026-opengl-linux-driver-optimizations/</link><pubDate>Fri, 13 Nov 2026 20:18:54 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/ati-amd-r300-to-r500-gpus-see-new-2026-opengl-linux-driver-optimizations/</guid><description>&lt;p class="news-article__lede"&gt;Over 24 years old, the ATI (AMD) Radeon R300 graphics processors are still seeing improvements in the open-source Linux driver space. Merged to Mesa 27.0-devel this week were a number of shader compiler optimizations for the R300g driver that benefits not only the original R300 series graphics ...&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Key components named in the report: Mesa, AMD.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software”&lt;/p&gt;&lt;footer&gt;— Phoronix&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;Phoronix Premium allows ad-free access to the site, multi-page articles on a single page, and other features while supporting this site&amp;#x27;s continued operations.&lt;/p&gt;&lt;p&gt;The mission at Phoronix since 2004 has centered around enriching the Linux hardware experience. In addition to supporting our site through advertisements, you can help by subscribing to Phoronix Premium. You can also contribute to Phoronix through tips/donations via PayPal or Stripe.&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Linux runs a large share of the internet&amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://phoronix.com/news/AMD-R300g-Better-Shaders-2026" target="_blank" rel="noopener noreferrer"&gt;Phoronix&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>Libreboot 26.11 Open-Source BIOS/UEFI Firmware Brings Various Improvements</title><link>https://it.kituwa.com/blogs/blog/libreboot-26-11-open-source-bios-uefi-firmware-brings-various-improvements/</link><pubDate>Fri, 13 Nov 2026 14:18:44 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/libreboot-26-11-open-source-bios-uefi-firmware-brings-various-improvements/</guid><description>&lt;p class="news-article__lede"&gt;On top of that, this release disables experimental EDK2 support on ASUS Fam15h boards, replaces p7zip with 7zip and zlib with zlib-ng, merges BIOS- and UEFI-based Coreboot targets into single targets, marks ASUS KFSN4-DRE as untested, and adds support for EDK2 payloads on Dell OptiPlex 780 variants.&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;pre&gt;&lt;code&gt; &amp;lt;h2&amp;gt;Why it matters&amp;lt;/h2&amp;gt;
&amp;lt;p&amp;gt;Linux runs a large share of the internet&amp;amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&amp;lt;/p&amp;gt;
&amp;lt;h2&amp;gt;What to do&amp;lt;/h2&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Check the official advisory for the affected versions and fixed versions.&amp;lt;/li&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://9to5linux.com/libreboot-26-11-open-source-bios-uefi-firmware-brings-various-improvements" target="_blank" rel="noopener noreferrer"&gt;9to5Linux&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>LibreOffice 26.8.3 Open-Source Office Suite Released with More Than 40 Bug Fixes</title><link>https://it.kituwa.com/blogs/blog/libreoffice-26-8-3-open-source-office-suite-released-with-more-than-40-bug/</link><pubDate>Thu, 12 Nov 2026 20:19:46 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/libreoffice-26-8-3-open-source-office-suite-released-with-more-than-40-bug/</guid><description>&lt;p class="news-article__lede"&gt;This release also fixes a Navigator loop caused by a group shape in a footer, which consumed CPU continuously since LibreOffice 26.8, has also been resolved.&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;pre&gt;&lt;code&gt; &amp;lt;h2&amp;gt;Why it matters&amp;lt;/h2&amp;gt;
&amp;lt;p&amp;gt;Linux runs a large share of the internet&amp;amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&amp;lt;/p&amp;gt;
&amp;lt;h2&amp;gt;What to do&amp;lt;/h2&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Check the official advisory for the affected versions and fixed versions.&amp;lt;/li&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://9to5linux.com/libreoffice-26-8-3-open-source-office-suite-released-with-more-than-40-bug-fixes" target="_blank" rel="noopener noreferrer"&gt;9to5Linux&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>RHEL 10.3 Released with Linux Kernel 6.12, GCC 16, and Sealed Images</title><link>https://it.kituwa.com/blogs/blog/rhel-10-3-released-with-linux-kernel-6-12-gcc-16-and-sealed-images/</link><pubDate>Thu, 12 Nov 2026 17:18:48 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/rhel-10-3-released-with-linux-kernel-6-12-gcc-16-and-sealed-images/</guid><description>&lt;p class="news-article__lede"&gt;# RHEL 10.3 Released with Linux Kernel 6.12, GCC 16, and Sealed Images Red Hat Enterprise Linux 10.3 ships with Linux kernel 6.12, GCC 16, sealed OS images, MCP-based diagnostics, and updated developer tools. Red Hat has announced Red Hat Enterprise Linux 10.3, the latest update to its enterprise-focused Linux distro, alongside RHEL 9.9. Under the hood, RHEL 10.3 ships with Linux kernel 6.12, including Red Hat’s patches and backported improvements. Kernel changes include stronger Integrity Measurement Architecture enforcement, preventing modified executables on previously excluded filesystems from bypassing integrity checks. Kernel Samepage Merging gains an option to deduplicate only zero-filled memory pages, reducing scanning overhead in virtualization environments. Plus, the Real-Time Linux Analysis framework now supports executing custom eBPF programs. Another main addition is the general availability of sealed images for RHEL image mode. These provide cryptographic integrity verification across the boot process, from firmware and bootloader to the kernel and root filesystem. Combined with a read-only root filesystem, this lets systems reject unauthorized modifications rather th&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Key components named in the report: Linux kernel.&lt;/li&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“Red Hat has announced Red Hat Enterprise Linux 10.3, the latest update to its enterprise-focused Linux distro, alongside RHEL 9.9.”&lt;/p&gt;&lt;footer&gt;— Linuxiac&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;Under the hood, RHEL 10.3 ships with Linux kernel 6.12, including Red Hat’s patches and backported improvements. Kernel changes include stronger Integrity Measurement Architecture enforcement, preventing modified executables on previously excluded filesystems from bypassing integrity checks.&lt;/p&gt;&lt;p&gt;Kernel Samepage Merging gains an option to deduplicate only zero-filled memory pages, reducing scanning overhead in virtualization environments. Plus, the Real-Time Linux Analysis framework now supports executing custom eBPF programs.&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Linux runs a large share of the internet&amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Review SSH exposure first: restrict access and watch authentication logs.&lt;/li&gt;
&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://linuxiac.com/rhel-10-3-released-with-linux-kernel-6-12-gcc-16-and-sealed-images" target="_blank" rel="noopener noreferrer"&gt;Linuxiac&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>XOrg Server 21.1.26 and Xwayland 24.1.15 Are Out to Patch More Security Issues</title><link>https://it.kituwa.com/blogs/blog/xorg-server-21-1-26-and-xwayland-24-1-15-are-out-to-patch/</link><pubDate>Thu, 12 Nov 2026 14:17:05 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/xorg-server-21-1-26-and-xwayland-24-1-15-are-out-to-patch/</guid><description>&lt;p class="news-article__lede"&gt;# XOrg Server 21.1.26 and Xwayland 24.1.15 Are Out to Patch More Security Issues Users are urged to update their systems to the XOrg Server 21.1.26 and Xwayland 24.1.15 releases as soon as possible. The XOrg Server 21.1.26 and Xwayland 24.1.15 display implementations have been released today, November 10th, 2026, patching multiple security vulnerabilities that could lead to crashes and corrupt memory. The fixes include CVE-2026-109091, a vulnerability that could allow a malicious monitor or crafted EDID to supply extra descriptors that overrun those arrays and clobber adjacent MonRec fields (Modes, Last, DDC), causing an out-of-bounds write that can crash the server or corrupt memory. Also fixed is CVE-2026-109092, a shared-memory bounds overflow in XvShmPutImage, where a negative size value combined with a crafted offset can wrap an addition and bypass bounds checking, passing an invalid source pointer to PutImage and potentially enabling an out-of-bounds read or write in the server. Moreover, these updates fix CVE-2026-109093, a stack out-of-bounds write in XTestFakeInput, where valuator fields were copied into a fixed-size stack array before checking whether the range actually f&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Tracked as CVE-2026-109091, CVE-2026-109092, CVE-2026-109093.&lt;/li&gt;&lt;li&gt;Key components named in the report: Wayland.&lt;/li&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;pre&gt;&lt;code&gt; &amp;lt;h2&amp;gt;Why it matters&amp;lt;/h2&amp;gt;
&amp;lt;p&amp;gt;Linux runs a large share of the internet&amp;amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&amp;lt;/p&amp;gt;
&amp;lt;h2&amp;gt;What to do&amp;lt;/h2&amp;gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Check the official advisory for the affected versions and fixed versions.&amp;lt;/li&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://9to5linux.com/xorg-server-21-1-26-and-xwayland-24-1-15-are-out-to-patch-more-security-issues" target="_blank" rel="noopener noreferrer"&gt;9to5Linux&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>Podman 6.2 Released with Security Fixes, Kubernetes Improvements</title><link>https://it.kituwa.com/blogs/blog/podman-6-2-released-with-security-fixes-kubernetes-improvements/</link><pubDate>Wed, 11 Nov 2026 20:16:50 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/podman-6-2-released-with-security-fixes-kubernetes-improvements/</guid><description>&lt;p class="news-article__lede"&gt;Podman 6.2 fixes three security vulnerabilities, expands Kubernetes YAML support, improves Quadlet configuration, and adds native systemd support for WSL.&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Tracked as CVE-2026-121885, CVE-2026-111361, CVE-2026-123876.&lt;/li&gt;&lt;li&gt;Key components named in the report: systemd.&lt;/li&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“The open-source, daemonless container management tool Podman has released version 6.2, with expanded Kubernetes support, new Quadlet configuration options, native systemd support for WSL machines, and security fixes.”&lt;/p&gt;&lt;footer&gt;— Linuxiac&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;The release addresses CVE-2026-121885, which could allow untrusted container image labels to manipulate Podman’s auto-update mechanism to restart unintended systemd units. It also fixes CVE-2026-111361, a vulnerability involving potential bypasses of image digest and signature validation, and CVE-2026-123876, which could allow malicious containers to bypass a socket restriction in the default seccomp profile.&lt;/p&gt;&lt;p&gt;Kubernetes integration receives several improvements. The podman kube play command now supports a --validate option to control how unrecognized YAML fields are handled, while --label allows users to assign labels to containers, pods, volumes, and secrets created from Kubernetes manifests.&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Linux runs a large share of the internet&amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://linuxiac.com/podman-6-2-released-with-security-fixes-kubernetes-improvements" target="_blank" rel="noopener noreferrer"&gt;Linuxiac&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>Linux News right in your Facebook feed</title><link>https://it.kituwa.com/blogs/blog/facebook-20261111-linux-news-right-in-your-facebook-feed-539584/</link><pubDate>Wed, 11 Nov 2026 20:05:20 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/facebook-20261111-linux-news-right-in-your-facebook-feed-539584/</guid><description>&lt;p&gt;Linux News right in your Facebook feed&lt;/p&gt;
&lt;p&gt;&lt;img src="https://it.kituwa.com/blogs/facebook/facebook-20261111-linux-news-right-in-your-facebook-feed-539584.jpg" alt="Linux News right in your Facebook feed" loading="lazy"&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.facebook.com/122105052855539584/posts/122105039631539584" target="_blank" rel="noopener noreferrer"&gt;View this post on Facebook&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Kituwa update — November 11, 2026</title><link>https://it.kituwa.com/blogs/blog/facebook-20261111-kituwa-update-november-11-2026-539584/</link><pubDate>Wed, 11 Nov 2026 20:03:22 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/facebook-20261111-kituwa-update-november-11-2026-539584/</guid><description>&lt;p&gt;Kituwa shared an update on Facebook.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://it.kituwa.com/blogs/facebook/facebook-20261111-kituwa-update-november-11-2026-539584.jpg" alt="Kituwa update — November 11, 2026" loading="lazy"&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.facebook.com/122105052855539584/posts/122105038053539584?substory_index=1537669008168989" target="_blank" rel="noopener noreferrer"&gt;View this post on Facebook&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Vulnerability that lets hackers SSH into Linux devices is under active exploitation</title><link>https://it.kituwa.com/blogs/blog/vulnerability-that-lets-hackers-ssh-into-linux-devices-is-under-active/</link><pubDate>Wed, 11 Nov 2026 18:46:41 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/vulnerability-that-lets-hackers-ssh-into-linux-devices-is-under-active/</guid><description>&lt;p class="news-article__lede"&gt;Hackers are actively exploiting a recently discovered critical vulnerability that allows them to log in to privileged accounts on many Linux systems, multiple researchers are reporting.&lt;/p&gt;
&lt;ul class="news-article__facts"&gt;&lt;li&gt;Key components named in the report: OpenSSH, musl.&lt;/li&gt;&lt;li&gt;The source reports exploitation in the wild, not just a theoretical flaw.&lt;/li&gt;&lt;li&gt;This is a release or availability story, so upgrade timing and rollback matter.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;What happened&lt;/h2&gt;
&lt;blockquote&gt;&lt;p&gt;“The vulnerability, tracked under the name *sshole, arises from the interaction between OpenSSH and a code library known as musl. Linux systems that use both of these packages and meet certain other requirements can be hacked to give unauthenticated access to high-privilege accounts in a matter of seconds. *sshole became publicly known last Thursday and quickly stoked concerns it could lead to widespread compromise of”&lt;/p&gt;&lt;footer&gt;— Ars Technica&lt;/footer&gt;&lt;/blockquote&gt;
&lt;p&gt;Security firm Greynoise said Monday that honeypots it maintains in Southeast Asia have come under attack by a group it’s tracking as GT10. The group conducted “mature intrusions” into the systems, which Greynoise uses to detect attempted or successful attacks in real time. Greynoise subsequently gained access to a GT10 server that revealed potential other victims and some of the tools used in the campaign. A backdoor&lt;/p&gt;
&lt;h2&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;Linux runs a large share of the internet&amp;#x27;s servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.&lt;/p&gt;
&lt;h2&gt;What to do&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Review SSH exposure first: restrict access and watch authentication logs.&lt;/li&gt;
&lt;li&gt;Check the official advisory for the affected versions and fixed versions.&lt;/li&gt;
&lt;li&gt;Apply the vendor update after a normal backup and a short test where possible.&lt;/li&gt;
&lt;li&gt;If a patch is not available yet, use the mitigations in the advisory and reduce exposure.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;Read the original&lt;/h2&gt;
&lt;p&gt;The full report, including versions, affected systems and any vendor statement, is at &lt;a href="https://arstechnica.com/security/2026/11/vulnerability-that-lets-hackers-ssh-into-linux-devices-is-under-active-exploitation" target="_blank" rel="noopener noreferrer"&gt;Ars Technica&lt;/a&gt;. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.&lt;/p&gt;</description></item><item><title>SSD or RAM: which upgrade helps?</title><link>https://it.kituwa.com/blogs/blog/ssd-or-ram-which-upgrade-helps/</link><pubDate>Wed, 11 Nov 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/ssd-or-ram-which-upgrade-helps/</guid><description>&lt;p&gt;Three situations, three different next steps.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;SSD or RAM: which upgrade helps?&lt;/li&gt;
&lt;li&gt;Start with the symptom.&lt;/li&gt;
&lt;li&gt;Mechanical HDD — Investigate an SSD&lt;/li&gt;
&lt;li&gt;SSD + memory pressure — Investigate RAM&lt;/li&gt;
&lt;li&gt;SSD + enough RAM — Diagnose further&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Still booting from a mechanical hard drive? Investigate an SSD first. Startup, app launches, and file searches usually feel the difference most.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Already on an SSD but stuttering with many tabs or apps? Investigate RAM. Check memory pressure under your real workload, not a single idle screenshot.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Already on an SSD with enough memory? Diagnose further before buying: thermals, CPU load, failing hardware, background jobs, or software.&lt;/p&gt;
&lt;h3 id="prove-the-restore"&gt;Prove the restore&lt;/h3&gt;
&lt;p&gt;Before any purchase, check upgradeability. Some laptops have soldered RAM, one slot, or no free M.2/SATA bay. Confirm the exact model, warranty, and part compatibility. And keep the no-purchase option: free up storage, review startup apps, update, and test a restore.&lt;/p&gt;
&lt;h3 id="step-5-what-to-check"&gt;Step 5: what to check&lt;/h3&gt;
&lt;p&gt;Share non-sensitive specs if you want a direction. I cannot promise individual replies.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which situation sounds like yours?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Start with the symptom.&lt;/li&gt;
&lt;li&gt;☐ Mechanical HDD — Investigate an SSD&lt;/li&gt;
&lt;li&gt;☐ SSD + memory pressure — Investigate RAM&lt;/li&gt;
&lt;li&gt;☐ SSD + enough RAM — Diagnose further&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Three situations, three different next steps.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.crucial.com/upgrades"&gt;Crucial — compatible memory and SSD upgrades&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/free.1.html"&gt;man free — memory pressure signals&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.kernel.org/gpu/drm-mm.html"&gt;Linux kernel — DRM memory management&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/slow-computer-diagnose-before-buying"&gt;Slow computer: diagnose before buying&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/linux-mint-vs-ubuntu-desktop"&gt;Linux Mint vs Ubuntu Desktop&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-home-folder-backup-you-can-verify"&gt;A home folder backup you can verify&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Slow computer: diagnose before buying</title><link>https://it.kituwa.com/blogs/blog/slow-computer-diagnose-before-buying/</link><pubDate>Tue, 10 Nov 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/slow-computer-diagnose-before-buying/</guid><description>&lt;p&gt;When a computer feels slow, do not buy parts yet. Follow the symptom first.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Diagnose before you buy&lt;/li&gt;
&lt;li&gt;Check the cause first.&lt;/li&gt;
&lt;li&gt;Startup apps — What launches at login&lt;/li&gt;
&lt;li&gt;CPU load — One process pinned?&lt;/li&gt;
&lt;li&gt;Memory pressure — Available memory&lt;/li&gt;
&lt;li&gt;Storage space — Room to work&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-top"&gt;Check &lt;code&gt;top&lt;/code&gt;&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Startup apps: does the delay happen at login? Check what launches automatically.&lt;/li&gt;
&lt;li&gt;CPU load: is one process pinned? On Linux, &lt;code&gt;top&lt;/code&gt; or &lt;code&gt;uptime&lt;/code&gt; gives a first look.&lt;/li&gt;
&lt;li&gt;Memory pressure: does it stutter with many tabs or apps? Check available memory with &lt;code&gt;free -h&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Storage capacity: is the system drive nearly full? Check &lt;code&gt;df -h&lt;/code&gt;, and leave working headroom.&lt;/li&gt;
&lt;li&gt;Temperatures: does it slow down after a few minutes? Dust, airflow, and thermal throttling matter.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="check-systemd-analyze-blame"&gt;Check &lt;code&gt;systemd-analyze blame&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Linux examples: &lt;code&gt;systemd-analyze blame&lt;/code&gt; for boot time, &lt;code&gt;top&lt;/code&gt; for CPU, &lt;code&gt;free -h&lt;/code&gt; for memory, &lt;code&gt;df -h&lt;/code&gt; for space, and &lt;code&gt;sensors&lt;/code&gt; from lm-sensors for temperatures. Other systems have equivalents. The sequence is OS-neutral; the tools are not.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Avoid registry cleaners, “one-click speedup” tools, and claims of instant results. Change one thing at a time and rerun the same task.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;When does it slow down: startup, browsing, gaming, or everything?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Diagnose before you buy&lt;/li&gt;
&lt;li&gt;☐ Check the cause first.&lt;/li&gt;
&lt;li&gt;☐ Startup apps — What launches at login&lt;/li&gt;
&lt;li&gt;☐ CPU load — One process pinned?&lt;/li&gt;
&lt;li&gt;☐ Memory pressure — Available memory&lt;/li&gt;
&lt;li&gt;☐ Storage space — Room to work&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;When a computer feels slow, do not buy parts yet.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/systemd-analyze.1.html"&gt;man systemd-analyze&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/top.1.html"&gt;man top&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/free.1.html"&gt;man free&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/df.1.html"&gt;man df&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/lm-sensors/lm-sensors"&gt;lm-sensors project&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/ram-is-not-storage"&gt;RAM is not storage&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/ssd-or-ram-which-upgrade-helps"&gt;SSD or RAM: which upgrade helps?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/linux-mint-vs-ubuntu-desktop"&gt;Linux Mint vs Ubuntu Desktop&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>RAM is not storage</title><link>https://it.kituwa.com/blogs/blog/ram-is-not-storage/</link><pubDate>Mon, 09 Nov 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/ram-is-not-storage/</guid><description>&lt;p&gt;RAM is the workbench. Storage is the cupboard. VRAM is the graphics card's own workbench.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;RAM is not storage&lt;/li&gt;
&lt;li&gt;Three kinds of memory. Three different jobs.&lt;/li&gt;
&lt;li&gt;RAM — active work&lt;/li&gt;
&lt;li&gt;SSD — stored files&lt;/li&gt;
&lt;li&gt;VRAM — graphics memory&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;System RAM holds the programs and files your computer is using right now. It is fast, and it loses its contents when power goes off. When active work does not fit, the system leans on swap or starts closing things.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;SSD capacity is persistent storage: files stay put when the machine is off. A larger SSD gives you room for photos, projects, and updates. It does not automatically make a memory-starved computer faster.&lt;/p&gt;
&lt;h3 id="test-the-model-on-your-task"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;VRAM is memory on the graphics card. Games, video work, and local AI models can be limited by how much fits there. A card with more VRAM can hold larger models or textures, but the CPU, system RAM, and software still matter.&lt;/p&gt;
&lt;h3 id="check-free-h"&gt;Check &lt;code&gt;free -h&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;So “more storage” and “more memory” solve different problems. Check before buying: on Linux, run &lt;code&gt;free -h&lt;/code&gt; and read the available column; on Windows, open Task Manager's Performance tab; on macOS, use Activity Monitor's Memory tab.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which part of your machine is actually running out first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/li&gt;
&lt;li&gt;Never testing a restore of a real file.&lt;/li&gt;
&lt;li&gt;Keeping the only copy on the same device or in the same location.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Three kinds of memory. Three different jobs.&lt;/li&gt;
&lt;li&gt;☐ RAM — active work&lt;/li&gt;
&lt;li&gt;☐ SSD — stored files&lt;/li&gt;
&lt;li&gt;☐ VRAM — graphics memory&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;RAM is the workbench.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.kernel.org/mm/physical_memory.html"&gt;Linux kernel — physical memory&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.kernel.org/gpu/drm-mm.html"&gt;Linux kernel — DRM memory management (VRAM)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/free.1.html"&gt;man free — available memory&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-would-you-rescue-first"&gt;What would you rescue first?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/slow-computer-diagnose-before-buying"&gt;Slow computer: diagnose before buying&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/ssd-or-ram-which-upgrade-helps"&gt;SSD or RAM: which upgrade helps?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Find What Is Filling Your Linux Disk: df, Inodes, and du</title><link>https://it.kituwa.com/blogs/blog/find-what-is-filling-your-linux-disk/</link><pubDate>Sun, 08 Nov 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/find-what-is-filling-your-linux-disk/</guid><description>&lt;p&gt;A full Linux disk is not one problem. It can be a filesystem with no free bytes, a filesystem with no free inodes, a single directory that grew too large, or a mount you did not realize was separate. The first job is to identify which one you have. Deleting files before that is guessing.&lt;/p&gt;
&lt;p&gt;This guide uses three read-only tools: &lt;code&gt;df -h&lt;/code&gt;, &lt;code&gt;df -i&lt;/code&gt;, and &lt;code&gt;du&lt;/code&gt;. It does not include deletion commands. Once you know what is full and why, you can make a deliberate decision about what is safe to remove, move, or archive.&lt;/p&gt;
&lt;h2 id="the-three-questions"&gt;The three questions&lt;/h2&gt;
&lt;p&gt;Ask these in order:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Which filesystem is full?&lt;/strong&gt; &lt;code&gt;df -h&lt;/code&gt; shows capacity and mount points.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Is it out of bytes or out of inodes?&lt;/strong&gt; &lt;code&gt;df -i&lt;/code&gt; shows inode use.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Which directory is responsible?&lt;/strong&gt; &lt;code&gt;du&lt;/code&gt; measures directory usage.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The answers can differ. A filesystem can have gigabytes free and still refuse a new file because it has no free inodes. A root filesystem can be full while &lt;code&gt;/home&lt;/code&gt; has plenty of space because they are separate mounts. A directory can look large in a file manager but contain mostly sparse or hard-linked files.&lt;/p&gt;
&lt;h2 id="1-check-capacity-and-mounts-with-df-h"&gt;1. Check capacity and mounts with df -h&lt;/h2&gt;
&lt;p&gt;Run:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-bash"&gt;df -h
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The columns are filesystem, size, used, available, use percentage, and mount point. The mount point matters as much as the percentage. A full &lt;code&gt;/&lt;/code&gt; is not the same as a full USB drive mounted at &lt;code&gt;/media/you/USB&lt;/code&gt;, and a separate &lt;code&gt;/home&lt;/code&gt; partition has its own capacity.&lt;/p&gt;
&lt;p&gt;Look for:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;Use%&lt;/code&gt; at or near 100% on the filesystem that matters.&lt;/li&gt;
&lt;li&gt;A small &lt;code&gt;Avail&lt;/code&gt; value even if the percentage looks moderate.&lt;/li&gt;
&lt;li&gt;The mount point of the directory you are actually writing to.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you want to check one path specifically:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-bash"&gt;df -h /path/to/directory
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;code&gt;df&lt;/code&gt; reports the filesystem that contains that path. It does not tell you which file inside the directory is large.&lt;/p&gt;
&lt;p&gt;A note on reserved space: some filesystems reserve blocks for root or system use. &lt;code&gt;df&lt;/code&gt; may show less available space than the raw size suggests. That is normal, but it is another reason not to interpret the percentage without the available column.&lt;/p&gt;
&lt;h2 id="2-check-inode-use-with-df-i"&gt;2. Check inode use with df -i&lt;/h2&gt;
&lt;p&gt;Run:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-bash"&gt;df -i
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The columns are filesystem, inodes, used inodes, free inodes, inode use percentage, and mount point.&lt;/p&gt;
&lt;p&gt;An inode is a filesystem object that stores metadata about a file or directory. A filesystem creates a fixed number of inodes when it is made. Many small files can exhaust the inode table while plenty of bytes remain. This is common with mail queues, session files, caches made of tiny files, container layers, and old backup trees.&lt;/p&gt;
&lt;p&gt;If &lt;code&gt;df -i&lt;/code&gt; shows 100% inode use on the filesystem you are writing to, creating a new file can fail even though &lt;code&gt;df -h&lt;/code&gt; shows free space. The fix is not “buy a bigger disk” by default; it is to find the directory producing the tiny files and decide what belongs there.&lt;/p&gt;
&lt;p&gt;Inode counts and limits vary by filesystem and by how it was created. Do not assume every filesystem behaves the same way.&lt;/p&gt;
&lt;h2 id="3-measure-directories-with-du"&gt;3. Measure directories with du&lt;/h2&gt;
&lt;p&gt;&lt;code&gt;du&lt;/code&gt; reports disk usage by directory. Start inside a directory you own, not at &lt;code&gt;/&lt;/code&gt;. A shallow first pass is easier to read:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-bash"&gt;du -h --max-depth=1 ~ | sort -h
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;code&gt;--max-depth=1&lt;/code&gt; limits the output to the directory and its immediate children. &lt;code&gt;-h&lt;/code&gt; makes sizes human-readable. &lt;code&gt;sort -h&lt;/code&gt; orders the results by size.&lt;/p&gt;
&lt;p&gt;To keep the scan on one filesystem, add &lt;code&gt;-x&lt;/code&gt;:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-bash"&gt;du -x -h --max-depth=1 /path/to/directory | sort -h
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;code&gt;-x&lt;/code&gt; tells &lt;code&gt;du&lt;/code&gt; not to cross into other mounted filesystems. That is useful when &lt;code&gt;/home&lt;/code&gt; or a network mount is separate from &lt;code&gt;/&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;If you need more detail, increase the depth one level at a time:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-bash"&gt;du -x -h --max-depth=2 /path/to/directory | sort -h
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Do not start with a full recursive scan of &lt;code&gt;/&lt;/code&gt; on a busy machine unless you understand the time and I/O cost. Start narrow and expand.&lt;/p&gt;
&lt;h2 id="permission-errors-are-information"&gt;Permission errors are information&lt;/h2&gt;
&lt;p&gt;&lt;code&gt;du&lt;/code&gt; may print “Permission denied” for directories your user cannot read. That is normal. It does not mean the command is broken, and it does not mean you should immediately run the same command with &lt;code&gt;sudo&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;First, check the directory’s ownership and permissions:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-bash"&gt;ls -ld /path/to/directory
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Then decide:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If the directory belongs to your user, you should be able to read it.&lt;/li&gt;
&lt;li&gt;If it belongs to another service or user, &lt;code&gt;sudo&lt;/code&gt; may let you measure it, but you still need to understand what it is before changing anything.&lt;/li&gt;
&lt;li&gt;If it is a system directory, read-only measurement is usually enough; do not delete files just because they are large.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Running &lt;code&gt;sudo du&lt;/code&gt; can hide the real ownership question. Use it only when you need the measurement and you understand the directory.&lt;/p&gt;
&lt;h2 id="a-safe-investigation-sequence"&gt;A safe investigation sequence&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Run &lt;code&gt;df -h&lt;/code&gt; and note the full mount point.&lt;/li&gt;
&lt;li&gt;Run &lt;code&gt;df -i&lt;/code&gt; on the same filesystem and note whether inodes are the limit.&lt;/li&gt;
&lt;li&gt;Pick a directory you own on that filesystem.&lt;/li&gt;
&lt;li&gt;Run &lt;code&gt;du -h --max-depth=1&lt;/code&gt; on it, then go one level deeper where the largest usage appears.&lt;/li&gt;
&lt;li&gt;Write down the path, the size, and what created it.&lt;/li&gt;
&lt;li&gt;Decide whether to move, archive, or remove data — and only then use a deletion command you understand.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If the full filesystem is &lt;code&gt;/&lt;/code&gt;, start with likely data directories such as &lt;code&gt;/var/log&lt;/code&gt;, &lt;code&gt;/var/cache&lt;/code&gt;, container storage, or application data. If it is &lt;code&gt;/home&lt;/code&gt;, start with your own home directory. Do not delete from &lt;code&gt;/var&lt;/code&gt; or &lt;code&gt;/usr&lt;/code&gt; just because the names look familiar.&lt;/p&gt;
&lt;h2 id="what-this-guide-deliberately-does-not-do"&gt;What this guide deliberately does not do&lt;/h2&gt;
&lt;p&gt;It does not tell you to run &lt;code&gt;rm -rf&lt;/code&gt;, clear caches, vacuum journals, or delete old kernels. Those actions have prerequisites and consequences. They also may not address the actual cause. Measure first; change second.&lt;/p&gt;
&lt;p&gt;It also does not claim that a full disk is always caused by user files. Logs, package caches, containers, snapshots, and deleted-but-open files can all consume space. The three commands above tell you where to look; they do not replace judgment.&lt;/p&gt;
&lt;h2 id="quick-reference"&gt;Quick reference&lt;/h2&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Question&lt;/th&gt;
&lt;th&gt;Command&lt;/th&gt;
&lt;th&gt;What to read&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Which filesystem is full?&lt;/td&gt;
&lt;td&gt;&lt;code&gt;df -h&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Mount point, Avail, Use%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Are inodes exhausted?&lt;/td&gt;
&lt;td&gt;&lt;code&gt;df -i&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;IUse%, IFree&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Which directory is large?&lt;/td&gt;
&lt;td&gt;&lt;code&gt;du -h --max-depth=1 ~ \| sort -h&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Largest immediate children&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Stay on one filesystem&lt;/td&gt;
&lt;td&gt;&lt;code&gt;du -x -h --max-depth=1 /path \| sort -h&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;No crossing into other mounts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Why permission denied?&lt;/td&gt;
&lt;td&gt;&lt;code&gt;ls -ld /path&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Owner, group, mode&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;p&gt;All links checked 2026-11-05.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;df(1)&lt;/code&gt; — filesystem space and inode reporting: &lt;a href="https://man7.org/linux/man-pages/man1/df.1.html"&gt;https://man7.org/linux/man-pages/man1/df.1.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;du(1)&lt;/code&gt; — directory usage: &lt;a href="https://man7.org/linux/man-pages/man1/du.1.html"&gt;https://man7.org/linux/man-pages/man1/du.1.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;GNU Coreutils — &lt;code&gt;df&lt;/code&gt; invocation: &lt;a href="https://www.gnu.org/software/coreutils/manual/html_node/df-invocation.html"&gt;https://www.gnu.org/software/coreutils/manual/html_node/df-invocation.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;GNU Coreutils — &lt;code&gt;du&lt;/code&gt; invocation: &lt;a href="https://www.gnu.org/software/coreutils/manual/html_node/du-invocation.html"&gt;https://www.gnu.org/software/coreutils/manual/html_node/du-invocation.html&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help-interpreting-the-output"&gt;Need help interpreting the output?&lt;/h2&gt;
&lt;p&gt;If the numbers do not add up, or you are unsure which directory is safe to touch, Kituwa can help you read the evidence before anything is deleted. Start with the three read-only commands above; they are the cheapest diagnostic you can run.&lt;/p&gt;</description></item><item><title>What would you rescue first?</title><link>https://it.kituwa.com/blogs/blog/what-would-you-rescue-first/</link><pubDate>Sun, 08 Nov 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/what-would-you-rescue-first/</guid><description>&lt;p&gt;Four things are waiting on a decision. An old laptop that still works. A folder of family photos. A slow office PC. A shared drive everyone treats as a dumping ground.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;What would you rescue first?&lt;/li&gt;
&lt;li&gt;One practical next step for each.&lt;/li&gt;
&lt;li&gt;Old laptop — Lightweight Linux?&lt;/li&gt;
&lt;li&gt;Family photos — Verified backup&lt;/li&gt;
&lt;li&gt;Slow PC — Diagnose first&lt;/li&gt;
&lt;li&gt;Shared drive — Owners + backup&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;The laptop might become a lightweight Linux machine, a backup target, or a spare browser. The photos need at least one verified copy on a separate device, and a restore test. The office PC needs diagnosis before replacement: startup load, memory pressure, disk health, temperatures. The shared drive needs owners, folders, and a backup, not just more space.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;None of these is a guaranteed miracle. Each is a practical next step.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;If you could rescue one first, which would you choose — and what problem do you want solved?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ One practical next step for each.&lt;/li&gt;
&lt;li&gt;☐ Old laptop — Lightweight Linux?&lt;/li&gt;
&lt;li&gt;☐ Family photos — Verified backup&lt;/li&gt;
&lt;li&gt;☐ Slow PC — Diagnose first&lt;/li&gt;
&lt;li&gt;☐ Shared drive — Owners + backup&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Four things are waiting on a decision.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu backup and restore guidance&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/five-read-only-linux-health-checks"&gt;Five read-only Linux health checks&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/ram-is-not-storage"&gt;RAM is not storage&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/slow-computer-diagnose-before-buying"&gt;Slow computer: diagnose before buying&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Five read-only Linux health checks</title><link>https://it.kituwa.com/blogs/blog/five-read-only-linux-health-checks/</link><pubDate>Sat, 07 Nov 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/five-read-only-linux-health-checks/</guid><description>&lt;p&gt;A slow or strange Linux machine does not need random deletion. Start with five read-only checks and write down what you see.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Five read-only health checks&lt;/li&gt;
&lt;li&gt;Look first. Change nothing.&lt;/li&gt;
&lt;li&gt;uptime — Run time and load averages&lt;/li&gt;
&lt;li&gt;free -h — Memory and swap; read available&lt;/li&gt;
&lt;li&gt;df -h — Free space per filesystem&lt;/li&gt;
&lt;li&gt;lsblk — Disks, partitions, mounts&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-uptime"&gt;Check &lt;code&gt;uptime&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;uptime&lt;/code&gt; shows how long the system has been running and the 1, 5, and 15-minute load averages. High load on a low-core machine deserves a look, but context matters.&lt;/p&gt;
&lt;h3 id="check-free-h"&gt;Check &lt;code&gt;free -h&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;free -h&lt;/code&gt; shows memory and swap. Read the &lt;code&gt;available&lt;/code&gt; column, not just &lt;code&gt;free&lt;/code&gt;; Linux uses spare memory for caching.&lt;/p&gt;
&lt;h3 id="check-df-h"&gt;Check &lt;code&gt;df -h&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;df -h&lt;/code&gt; shows free space per mounted filesystem. A full root partition can break updates and logs.&lt;/p&gt;
&lt;h3 id="check-lsblk"&gt;Check &lt;code&gt;lsblk&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;lsblk&lt;/code&gt; shows disks, partitions, and mount points. Use it to confirm which device you are looking at before touching anything.&lt;/p&gt;
&lt;h3 id="check-systemctl-failed"&gt;Check &lt;code&gt;systemctl --failed&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;systemctl --failed&lt;/code&gt; lists systemd units in a failed state. A failed unit is a clue, not an instruction to reset or delete it. Read the service log next with &lt;code&gt;journalctl -u &amp;lt;unit&amp;gt;&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;These assume a Linux system with systemd and standard util-linux/coreutils tools. Output varies with hardware, workload, and configuration. A warning means “diagnose”, not “clean everything”.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which result is hardest for you to interpret?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Five read-only health checks&lt;/li&gt;
&lt;li&gt;☐ Look first. Change nothing.&lt;/li&gt;
&lt;li&gt;☐ uptime — Run time and load averages&lt;/li&gt;
&lt;li&gt;☐ free -h — Memory and swap; read available&lt;/li&gt;
&lt;li&gt;☐ df -h — Free space per filesystem&lt;/li&gt;
&lt;li&gt;☐ lsblk — Disks, partitions, mounts&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A slow or strange Linux machine does not need random deletion.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/free.1.html"&gt;man free — available memory column&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/df.1.html"&gt;man df — filesystem space&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man8/lsblk.8.html"&gt;man lsblk — block devices&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/uptime.1.html"&gt;man uptime — load averages&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.freedesktop.org/software/systemd/man/latest/systemctl.html"&gt;systemctl — --failed&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/try-linux-without-replacing-windows"&gt;Linux without replacing Windows&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-would-you-rescue-first"&gt;What would you rescue first?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/ram-is-not-storage"&gt;RAM is not storage&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Try Linux Without Replacing Windows: A Safe Live USB Walkthrough</title><link>https://it.kituwa.com/blogs/blog/try-linux-without-replacing-windows/</link><pubDate>Thu, 05 Nov 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/try-linux-without-replacing-windows/</guid><description>&lt;p&gt;You do not have to erase Windows to find out whether Linux works on your computer. Linux Mint can start from a USB stick in a &lt;strong&gt;live session&lt;/strong&gt;: a temporary desktop that runs without installing anything on the internal drive. That gives you a low-risk way to test Wi-Fi, audio, suspend, the touchpad, and the apps you actually use.&lt;/p&gt;
&lt;p&gt;This walkthrough covers the full path: back up, download from the official source, verify the image, write a spare USB, boot it, test the hardware, and decide whether to install. It also explains the difference between a live session, a persistent USB, and a normal installation, because those are not the same thing.&lt;/p&gt;
&lt;p&gt;The short version: &lt;strong&gt;test first, install later, and never skip the backup&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id="what-a-live-session-is-and-what-it-is-not"&gt;What a live session is — and what it is not&lt;/h2&gt;
&lt;p&gt;A live session is the operating system running from the USB stick instead of the internal disk. Linux Mint's official installation guide describes it as similar to a normal session, with three important differences:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;It is slower, because it is loaded from a USB stick or DVD instead of an SSD or hard drive.&lt;/li&gt;
&lt;li&gt;Changes you make are &lt;strong&gt;not permanent&lt;/strong&gt; by default. They are not written to the USB stick, and they do not affect the installed system.&lt;/li&gt;
&lt;li&gt;Some applications behave differently or do not work at all in the live session. The guide specifically names Timeshift, Flatpak, Update Manager, and the Welcome Screen as examples.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That makes a live session a good hardware test and a poor place to do real work. Do not judge final performance from it, and do not expect files or settings to survive a reboot unless you have deliberately set up persistence.&lt;/p&gt;
&lt;p&gt;Persistence is a separate configuration. Linux Mint's official installation guide does not document a standard persistence workflow, and a persistent live USB is still not the same as a normal installation. If you want a permanent system, install Linux Mint to a disk. If you only want to test, use the default live session.&lt;/p&gt;
&lt;h2 id="what-you-need"&gt;What you need&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The computer you want to test.&lt;/li&gt;
&lt;li&gt;A spare USB flash drive. It will be completely erased. Use a drive larger than the ISO with room to spare; 8 GB is a common practical minimum, but check the current ISO size on the official download page.&lt;/li&gt;
&lt;li&gt;A reliable backup of anything you cannot lose.&lt;/li&gt;
&lt;li&gt;Access to the firmware boot menu or boot order settings.&lt;/li&gt;
&lt;li&gt;Linux Mint's official download and verification pages.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You do not need to repartition anything, disable Windows features, or open the computer case for a live-session test.&lt;/p&gt;
&lt;h2 id="1-back-up-before-you-touch-anything"&gt;1. Back up before you touch anything&lt;/h2&gt;
&lt;p&gt;The live session itself should not write to your internal drive. Installation is a different story: it can erase or resize partitions, and a mistake at the disk-selection screen can destroy data. Back up first.&lt;/p&gt;
&lt;p&gt;A backup is not just a copy sitting in the same folder. Ubuntu's official backup guidance recommends keeping copies on a separate device, deciding what to back up, how often, where the copies live, and how to restore them. At minimum:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Copy important files to an external drive or another trusted location.&lt;/li&gt;
&lt;li&gt;Check that the copy contains the files you expect.&lt;/li&gt;
&lt;li&gt;Restore one expendable file into a new folder and open it.&lt;/li&gt;
&lt;li&gt;Keep the backup drive disconnected while you install.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If you use a cloud account for browser data, make sure it has synced before you start. If you use a password manager, confirm you can sign in on another device.&lt;/p&gt;
&lt;h2 id="2-download-the-right-linux-mint-edition"&gt;2. Download the right Linux Mint edition&lt;/h2&gt;
&lt;p&gt;Download only from the official Linux Mint site:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Download page: &lt;a href="https://linuxmint.com/download.php"&gt;https://linuxmint.com/download.php&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Mirrors: &lt;a href="https://linuxmint.com/mirrors.php"&gt;https://linuxmint.com/mirrors.php&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Linux Mint publishes several editions. Cinnamon is the flagship desktop; MATE and Xfce are alternatives. Choose the edition that matches your hardware and preference, not a random mirror link from a search result. At the time of writing, Linux Mint 22.3 "Zena" is the current LTS line, supported until April 2029, but you should check the official download page for the current release and support window before downloading.&lt;/p&gt;
&lt;p&gt;Save the ISO and the two checksum/signature files that the mirror provides:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;sha256sum.txt&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;sha256sum.txt.gpg&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Do not copy the text out of a web page. Download the files themselves so the signature check is meaningful.&lt;/p&gt;
&lt;h2 id="3-verify-the-iso-before-you-write-it"&gt;3. Verify the ISO before you write it&lt;/h2&gt;
&lt;p&gt;Verification has two parts. The &lt;strong&gt;integrity check&lt;/strong&gt; confirms the download is complete and matches the file on the mirror. The &lt;strong&gt;authenticity check&lt;/strong&gt; confirms the checksum file was signed by Linux Mint. Both are documented on the official verification page: &lt;a href="https://linuxmint.com/verify.php"&gt;https://linuxmint.com/verify.php&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id="integrity-check"&gt;Integrity check&lt;/h3&gt;
&lt;p&gt;From a terminal in the folder containing the ISO and &lt;code&gt;sha256sum.txt&lt;/code&gt;:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-bash"&gt;sha256sum -b linuxmint-*.iso
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Compare the output with the matching line in &lt;code&gt;sha256sum.txt&lt;/code&gt;. If the values differ, download the ISO again. Do not "fix" the checksum file to match the download.&lt;/p&gt;
&lt;h3 id="authenticity-check"&gt;Authenticity check&lt;/h3&gt;
&lt;p&gt;Import the Linux Mint signing key and verify the signature. The exact commands and fingerprint are published in the official installation guide:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-bash"&gt;gpg --keyserver keyserver.ubuntu.com --recv-key &amp;quot;27DE B156 44C6 B3CF 3BD7 D291 300F 846B A25B AE09&amp;quot;
gpg --verify sha256sum.txt.gpg sha256sum.txt
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;A good signature tells you the checksum file came from Linux Mint. GPG may warn that the key is not marked as trusted locally; the official guide says this is expected. What matters is that the signature is good and the fingerprint matches the published value.&lt;/p&gt;
&lt;p&gt;If you are already running Linux Mint, the guide also documents the built-in &lt;code&gt;mint-iso-verify&lt;/code&gt; tool and the right-click &lt;strong&gt;Verify&lt;/strong&gt; action.&lt;/p&gt;
&lt;h2 id="4-write-the-iso-to-a-spare-usb-drive"&gt;4. Write the ISO to a spare USB drive&lt;/h2&gt;
&lt;p&gt;This step &lt;strong&gt;erases the entire USB drive&lt;/strong&gt;. Confirm the drive letter or device name before you start, and unplug any other removable drives you do not want to touch.&lt;/p&gt;
&lt;p&gt;Linux Mint's official guide documents two supported paths:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;In Linux Mint:&lt;/strong&gt; right-click the ISO and choose &lt;strong&gt;Make Bootable USB Stick&lt;/strong&gt;, or open &lt;strong&gt;Menu → Accessories → USB Image Writer&lt;/strong&gt;, select the USB device, and click &lt;strong&gt;Write&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;In Windows, macOS, or another Linux distribution:&lt;/strong&gt; download and install &lt;a href="https://etcher.balena.io/"&gt;Etcher&lt;/a&gt;, select the ISO, select the USB drive, and click &lt;strong&gt;Flash&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Etcher and USB Image Writer are the beginner-safe options. If you use &lt;code&gt;dd&lt;/code&gt;, you are responsible for identifying the correct whole device. A partition number is the wrong target. This command is destructive:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-bash"&gt;lsblk
sudo dd if=linuxmint-*.iso of=/dev/sdX bs=4M status=progress oflag=sync
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Replace &lt;code&gt;/dev/sdX&lt;/code&gt; with the whole USB device, not &lt;code&gt;/dev/sdX1&lt;/code&gt;. If you cannot explain why that difference matters, use Etcher or USB Image Writer instead.&lt;/p&gt;
&lt;h2 id="5-boot-from-the-usb"&gt;5. Boot from the USB&lt;/h2&gt;
&lt;p&gt;Insert the USB, restart the computer, and open the firmware boot menu. The exact key depends on the machine; Linux Mint's guide lists common options: &lt;strong&gt;Escape, F1, F2, F8, F10, F11, F12, or Delete&lt;/strong&gt;. The key is usually shown briefly during startup.&lt;/p&gt;
&lt;p&gt;On a Mac, hold &lt;strong&gt;Alt&lt;/strong&gt; or &lt;strong&gt;Option&lt;/strong&gt; after the boot sound. The Linux Mint ISO can boot in EFI or BIOS mode; the menu you see depends on the mode.&lt;/p&gt;
&lt;p&gt;If the USB does not appear:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Recheck the boot order in the firmware settings.&lt;/li&gt;
&lt;li&gt;Try another USB port, preferably a direct port rather than a hub.&lt;/li&gt;
&lt;li&gt;Confirm the ISO was written as a disk image, not copied as a file.&lt;/li&gt;
&lt;li&gt;Check the manufacturer's documentation for Secure Boot and firmware-specific boot options.&lt;/li&gt;
&lt;li&gt;If Secure Boot is part of the problem, change one setting at a time and understand the security trade-off before disabling anything permanently.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="6-test-the-hardware-you-actually-use"&gt;6. Test the hardware you actually use&lt;/h2&gt;
&lt;p&gt;Once the live desktop loads, test the things that would make or break the switch for you. The live session is temporary, so this is the right time to be nosy.&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Check&lt;/th&gt;
&lt;th&gt;What to do&lt;/th&gt;
&lt;th&gt;Why it matters&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Wi-Fi&lt;/td&gt;
&lt;td&gt;Connect to your normal network, load a page, disconnect and reconnect&lt;/td&gt;
&lt;td&gt;Some wireless chips need drivers or firmware&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Audio&lt;/td&gt;
&lt;td&gt;Play a local file and a browser video; test speakers and headphones&lt;/td&gt;
&lt;td&gt;Audio routing and codecs vary&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Suspend&lt;/td&gt;
&lt;td&gt;Suspend, wait, wake, and repeat once&lt;/td&gt;
&lt;td&gt;Laptops can fail to resume cleanly&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Touchpad&lt;/td&gt;
&lt;td&gt;Tap, two-finger scroll, right-click, and disable tap-to-click if needed&lt;/td&gt;
&lt;td&gt;Gesture support depends on the desktop and driver&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Webcam and microphone&lt;/td&gt;
&lt;td&gt;Open a video-call test page or a local app&lt;/td&gt;
&lt;td&gt;Privacy and meeting hardware should work before you commit&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Printer or scanner&lt;/td&gt;
&lt;td&gt;Add the device and print a test page if you use one&lt;/td&gt;
&lt;td&gt;Drivers and network discovery are common friction points&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Essential apps&lt;/td&gt;
&lt;td&gt;Open the browser, office suite, chat app, or development tools you need&lt;/td&gt;
&lt;td&gt;The live session is a compatibility test, not a benchmark&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Storage and sleep&lt;/td&gt;
&lt;td&gt;Check that the drive and any external devices are detected&lt;/td&gt;
&lt;td&gt;Confirms basic hardware support&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;Do not install a driver or run a random script from a forum during the live test unless you understand what it changes. A live session is for observation first.&lt;/p&gt;
&lt;h2 id="7-live-session-vs-installed-system-vs-persistence"&gt;7. Live session vs installed system vs persistence&lt;/h2&gt;
&lt;p&gt;These three things are often confused:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Live session:&lt;/strong&gt; runs from the USB, is slower, and discards changes by default. Good for testing hardware and the desktop.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Persistent live USB:&lt;/strong&gt; a separately configured live system that saves some changes between boots. It is still not a normal installation, and it has limitations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Installed system:&lt;/strong&gt; writes the operating system to an internal or external disk. Changes persist, performance is normal, and the bootloader is configured. This is the real migration step.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If your goal is to use Linux every day, test in the live session and then install. If your goal is only to rescue files or check hardware, the live session may be enough.&lt;/p&gt;
&lt;h2 id="8-decide-what-to-do-next"&gt;8. Decide what to do next&lt;/h2&gt;
&lt;p&gt;If the live session works well, read the official installation guide before you install:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Installation guide: &lt;a href="https://linuxmint-installation-guide.readthedocs.io/en/latest/install.html"&gt;https://linuxmint-installation-guide.readthedocs.io/en/latest/install.html&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The guide covers the live session, the installer, disk selection, and the restart. Two rules matter more than any version number:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Back up first.&lt;/strong&gt; The installer can erase or resize disks.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Read the disk-selection screen.&lt;/strong&gt; If you do not understand an option, stop and ask. "Erase disk" is not the same as "install alongside."&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If the live session does not work, do not force an installation. Note the exact failure, check the official release notes and hardware documentation, and test another edition or a newer kernel only if you understand the trade-off. A failed live test is useful information, not a failure on your part.&lt;/p&gt;
&lt;h2 id="troubleshooting-quick-reference"&gt;Troubleshooting quick reference&lt;/h2&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Symptom&lt;/th&gt;
&lt;th&gt;First checks&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;USB not listed in boot menu&lt;/td&gt;
&lt;td&gt;Boot order, direct USB port, image written as a disk image, firmware documentation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Checksum mismatch&lt;/td&gt;
&lt;td&gt;Re-download the ISO and the checksum files from an official mirror&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GPG warning about trust&lt;/td&gt;
&lt;td&gt;Confirm the signature is good and the fingerprint matches the official value; local trust is a separate setting&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Wi-Fi missing&lt;/td&gt;
&lt;td&gt;Check whether the adapter is detected, try a direct connection, review the release notes for your hardware&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No sound&lt;/td&gt;
&lt;td&gt;Check output device selection, test headphones, confirm the live session sees the card&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Suspend does not resume&lt;/td&gt;
&lt;td&gt;Note the hardware model; do not install until you understand whether the issue is fixable&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Installer cannot see a disk&lt;/td&gt;
&lt;td&gt;Check firmware storage mode (RAID/Intel RST), backup first, and read the official guide before changing settings&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="pre-install-checklist"&gt;Pre-install checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Important files copied to a separate device.&lt;/li&gt;
&lt;li&gt;☐ One file restored and opened from the backup.&lt;/li&gt;
&lt;li&gt;☐ ISO downloaded from the official site.&lt;/li&gt;
&lt;li&gt;☐ SHA-256 checksum matches.&lt;/li&gt;
&lt;li&gt;☐ GPG signature is good and the fingerprint matches.&lt;/li&gt;
&lt;li&gt;☐ USB written with Etcher, USB Image Writer, or a verified &lt;code&gt;dd&lt;/code&gt; command.&lt;/li&gt;
&lt;li&gt;☐ Live session boots.&lt;/li&gt;
&lt;li&gt;☐ Wi-Fi, audio, suspend, touchpad, and essential apps tested.&lt;/li&gt;
&lt;li&gt;☐ Installation guide read before touching the disk.&lt;/li&gt;
&lt;li&gt;☐ Backup drive disconnected during installation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;p&gt;All links checked 2026-11-05.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Linux Mint — Download: &lt;a href="https://linuxmint.com/download.php"&gt;https://linuxmint.com/download.php&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Linux Mint — Verify your ISO image: &lt;a href="https://linuxmint.com/verify.php"&gt;https://linuxmint.com/verify.php&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Linux Mint Installation Guide — Verify your ISO: &lt;a href="https://linuxmint-installation-guide.readthedocs.io/en/latest/verify.html"&gt;https://linuxmint-installation-guide.readthedocs.io/en/latest/verify.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Linux Mint Installation Guide — Create the bootable media: &lt;a href="https://linuxmint-installation-guide.readthedocs.io/en/latest/burn.html"&gt;https://linuxmint-installation-guide.readthedocs.io/en/latest/burn.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Linux Mint Installation Guide — Boot Linux Mint: &lt;a href="https://linuxmint-installation-guide.readthedocs.io/en/latest/boot.html"&gt;https://linuxmint-installation-guide.readthedocs.io/en/latest/boot.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Linux Mint Installation Guide — Install Linux Mint: &lt;a href="https://linuxmint-installation-guide.readthedocs.io/en/latest/install.html"&gt;https://linuxmint-installation-guide.readthedocs.io/en/latest/install.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Linux Mint — Supported releases: &lt;a href="https://linuxmint.com/download_all.php"&gt;https://linuxmint.com/download_all.php&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Linux Mint — Mirrors: &lt;a href="https://linuxmint.com/mirrors.php"&gt;https://linuxmint.com/mirrors.php&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Etcher: &lt;a href="https://etcher.balena.io/"&gt;https://etcher.balena.io/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Ubuntu — Backups and restore planning: &lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;https://ubuntu.com/server/docs/how-to/backups&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-a-second-opinion-before-switching"&gt;Need a second opinion before switching?&lt;/h2&gt;
&lt;p&gt;If you want help checking the hardware, planning the backup, or deciding between a live test and a full install, Kituwa can review the machine and the plan with you. Start with the free live-session test above; it is the cheapest diagnostic you can run.&lt;/p&gt;</description></item><item><title>Immich vs Google Photos vs Apple Photos</title><link>https://it.kituwa.com/blogs/blog/immich-vs-google-photos-vs-apple-photos/</link><pubDate>Sat, 03 Oct 2026 21:17:05 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/immich-vs-google-photos-vs-apple-photos/</guid><description>&lt;p&gt;So I've been slowly de-googling my life, and the biggest piece was Google Photos. That thing was basically a ticking time bomb of "pay us or lose your storage," plus who knows what they're doing with all your family pics behind the scenes.&lt;/p&gt;
&lt;p&gt;Solution: I set up my own version using a free open-source tool called Immich. It's basically Google Photos, except it lives on my own server instead of Google's. Auto backup from my phone, timeline, albums, face recognition, search — all of it, just running on hardware I own.&lt;/p&gt;
&lt;p&gt;I got almost 17000 images downloaded from Google takeout and organized into Immich!&lt;/p&gt;
&lt;p&gt;Setup wise: it runs in Docker on a Linux box, you connect the Immich app on your phone to your own server instead of Google's, and it backs up in the background exactly like you're used to. I've got mine reachable from anywhere using Tailscale so it's not just stuck at home on my wifi. There's also a migration tool if you want to pull your whole existing Google Photos library over instead of starting fresh.&lt;/p&gt;
&lt;p&gt;Not gonna lie, getting all the pieces (Linux, Docker, networking) talking to each other correctly is the part that trips people up.&lt;/p&gt;
&lt;p&gt;If you want off Google Photos but don't want to fight with a terminal for a weekend, we'll install and configure Immich (or whatever self-hosted setup you're after) for you. Just message us.&lt;/p&gt;</description></item><item><title>Homarr: One Dashboard for My Self-Hosted Stack</title><link>https://it.kituwa.com/blogs/blog/homarr-dashboard-self-hosted-stack/</link><pubDate>Sat, 03 Oct 2026 21:07:29 +0000</pubDate><guid>https://it.kituwa.com/blogs/blog/homarr-dashboard-self-hosted-stack/</guid><description>&lt;p&gt;Homarr is one of the most useful containers in my stack. It’s a free, open-source dashboard that puts my self-hosted services on one page.&lt;/p&gt;
&lt;p&gt;The screenshot shows my own instance: Immich, Nextcloud, Seafile, Joplin, Mattermost, Matrix/Element, Vikunja, OpenProject, Invoice Ninja, Akaunting, n8n, and Uptime Kuma, among others. The green dots are status indicators, so I can see what’s responding without digging through bookmarks and port numbers.&lt;/p&gt;
&lt;h2&gt;Quick setup with Docker Compose&lt;/h2&gt;
&lt;p&gt;Create a &lt;code&gt;docker-compose.yml&lt;/code&gt; file with this example:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;services:
homarr:
image: ghcr.io/homarr-labs/homarr:latest
container_name: homarr
restart: unless-stopped
ports:
- "7575:7575"
volumes:
- ./homarr/appdata:/appdata
# Optional: add the Docker socket only for Docker integration.
# - /var/run/docker.sock:/var/run/docker.sock
environment:
- SECRET_ENCRYPTION_KEY=${SECRET_ENCRYPTION_KEY}&lt;/code&gt;&lt;/pre&gt;
&lt;ol&gt;
&lt;li&gt;Run &lt;code&gt;openssl rand -hex 32&lt;/code&gt; to generate a key, then put it in a &lt;code&gt;.env&lt;/code&gt; file next to the Compose file as &lt;code&gt;SECRET_ENCRYPTION_KEY=your-generated-key&lt;/code&gt;. Keep that key and your &lt;code&gt;appdata&lt;/code&gt; directory backed up.&lt;/li&gt;
&lt;li&gt;Run &lt;code&gt;docker compose up -d&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Open &lt;code&gt;http://YOUR_HOST_IP:7575&lt;/code&gt; and complete the initial account setup.&lt;/li&gt;
&lt;li&gt;Add a tile for each service with its URL and icon. Configure status checks and the widgets you want, such as weather, calendar, or Docker information.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If you enable Docker discovery or management, uncomment the Docker socket mount. That grants the dashboard significant control over the Docker host, so only enable it when you need the integration and secure access to the dashboard.&lt;/p&gt;
&lt;p&gt;Check &lt;a href="https://homarr.dev/docs/getting-started/installation/docker/"&gt;Homarr’s current Docker installation guide&lt;/a&gt; before deploying, since the project’s setup can change.&lt;/p&gt;
&lt;p&gt;You can build a dashboard like this yourself on an old PC or mini PC. If you’d rather have the server, services, and dashboard set up for you, &lt;a href="https://it.kituwa.com/blogs/pages/contact"&gt;contact Kituwa IT&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;What’s on your dashboard? Do you prefer another option over Homarr?&lt;/p&gt;</description></item><item><title>Your next 30 days: keep learning</title><link>https://it.kituwa.com/blogs/blog/your-next-30-days-keep-learning/</link><pubDate>Fri, 13 Feb 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/your-next-30-days-keep-learning/</guid><description>&lt;p&gt;Pick one topic for the next 30 days, not ten.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Your next 30 days: keep learning&lt;/li&gt;
&lt;li&gt;One topic, one small project.&lt;/li&gt;
&lt;li&gt;Pick one topic — Not ten&lt;/li&gt;
&lt;li&gt;Small project — Done is defined&lt;/li&gt;
&lt;li&gt;Official docs — Spare device or VM&lt;/li&gt;
&lt;li&gt;Share the result — Teach to test&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Choose a small project: test a Linux live session, verify a backup restore, document your network, or replace one subscription with a self-hosted tool. Define what “done” looks like, schedule one hour a week, and write down what you learn.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Use official documentation and test on a spare device or VM. Keep a rollback path. Share one useful result with someone else; teaching is a check on understanding.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What is your one topic for next month?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ One topic, one small project.&lt;/li&gt;
&lt;li&gt;☐ Pick one topic — Not ten&lt;/li&gt;
&lt;li&gt;☐ Small project — Done is defined&lt;/li&gt;
&lt;li&gt;☐ Official docs — Spare device or VM&lt;/li&gt;
&lt;li&gt;☐ Share the result — Teach to test&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Pick one topic for the next 30 days, not ten.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://linuxmint-installation-guide.readthedocs.io/en/latest/"&gt;Linux Mint installation guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/tutorials"&gt;Ubuntu tutorials&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-simple-change-log"&gt;A simple change log&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>A simple change log</title><link>https://it.kituwa.com/blogs/blog/a-simple-change-log/</link><pubDate>Thu, 12 Feb 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/a-simple-change-log/</guid><description>&lt;p&gt;Write down changes while you remember them.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A simple change log&lt;/li&gt;
&lt;li&gt;Date, change, reason, rollback.&lt;/li&gt;
&lt;li&gt;1 Date&lt;/li&gt;
&lt;li&gt;2 What changed&lt;/li&gt;
&lt;li&gt;3 Why&lt;/li&gt;
&lt;li&gt;4 Rollback&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;A simple change log entry: date, what changed, why, who did it, and how to roll back. Include the affected system and a link to the ticket or note. Do not paste secrets or full configuration files.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;This is not bureaucracy; it is how you answer “what changed?” during an incident. It also helps the next person understand why a setting exists.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Keep the log where the team can find it, and review it before a migration.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What was the last change you made without a note?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Date, change, reason, rollback.&lt;/li&gt;
&lt;li&gt;☐ 1 Date&lt;/li&gt;
&lt;li&gt;☐ 2 What changed&lt;/li&gt;
&lt;li&gt;☐ 3 Why&lt;/li&gt;
&lt;li&gt;☐ 4 Rollback&lt;/li&gt;
&lt;li&gt;☐ 5 Owner&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Write down changes while you remember them.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://git-scm.com/book/en/v2"&gt;Pro Git — Git basics&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/pubs/sp/800/61/r3/final"&gt;NIST SP 800-61 — incident handling&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/choosing-a-domain-and-email-setup"&gt;Choosing a domain and email setup&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-next-30-days-keep-learning"&gt;Your next 30 days: keep learning&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Choosing a domain and email setup</title><link>https://it.kituwa.com/blogs/blog/choosing-a-domain-and-email-setup/</link><pubDate>Wed, 11 Feb 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/choosing-a-domain-and-email-setup/</guid><description>&lt;p&gt;A domain and email setup is infrastructure. Choose it deliberately.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Choosing a domain and email setup&lt;/li&gt;
&lt;li&gt;Registrar, MX, SPF, DKIM, DMARC.&lt;/li&gt;
&lt;li&gt;Registrar — Lock + recovery&lt;/li&gt;
&lt;li&gt;DNS — Nameservers + TTL&lt;/li&gt;
&lt;li&gt;MX — Mail delivery&lt;/li&gt;
&lt;li&gt;SPF — Allowed senders&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="make-recovery-practical"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;Register the domain with a registrar you can recover access to. Use a registrar lock, strong account security, and a recovery path. For email, decide who hosts the mailbox, then configure DNS: MX records for delivery, SPF to list allowed senders, DKIM to sign messages, and DMARC to publish policy and reporting.&lt;/p&gt;
&lt;h3 id="make-recovery-practical_1"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;Test sending and receiving from more than one provider. Check that password reset and account recovery work. Keep DNS changes documented, and lower TTLs before a migration.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Do not run mail on a whim without understanding deliverability and abuse handling.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Keep the registrar account separate from the mailbox account. Use a long-lived recovery path, not a phone number you might lose. Document the DNS change and its rollback. Check the records with a DNS lookup after the change. Wait for TTL before deleting old records. Which record would you check first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Registrar, MX, SPF, DKIM, DMARC.&lt;/li&gt;
&lt;li&gt;☐ Registrar — Lock + recovery&lt;/li&gt;
&lt;li&gt;☐ DNS — Nameservers + TTL&lt;/li&gt;
&lt;li&gt;☐ MX — Mail delivery&lt;/li&gt;
&lt;li&gt;☐ SPF — Allowed senders&lt;/li&gt;
&lt;li&gt;☐ DKIM — Signed mail&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A domain and email setup is infrastructure.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc7208"&gt;RFC 7208 — SPF&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc7489"&gt;RFC 7489 — DMARC&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-home-lab-power-plan"&gt;A home-lab power plan&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-simple-change-log"&gt;A simple change log&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-next-30-days-keep-learning"&gt;Your next 30 days: keep learning&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>A home-lab power plan</title><link>https://it.kituwa.com/blogs/blog/a-home-lab-power-plan/</link><pubDate>Tue, 10 Feb 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/a-home-lab-power-plan/</guid><description>&lt;p&gt;Power is part of the system, not an accessory.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A home-lab power plan&lt;/li&gt;
&lt;li&gt;UPS, clean shutdown, tested battery.&lt;/li&gt;
&lt;li&gt;1 UPS&lt;/li&gt;
&lt;li&gt;2 Clean shutdown&lt;/li&gt;
&lt;li&gt;3 Surge + airflow&lt;/li&gt;
&lt;li&gt;4 Battery age&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;A UPS can ride out a short outage and give the server time to shut down cleanly. It only helps if the server knows how to listen to it and if the battery is healthy. Test the shutdown path; do not assume the beep means everything is covered.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Use surge protection, avoid daisy-chaining power strips, and keep ventilation clear. Check battery age and replace it on the vendor's schedule. Document which devices are on the UPS and how long they can run.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;For a laptop server, the battery can act as a small UPS, but a swollen battery is a stop-now issue.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Label the UPS outlets so the next person knows what is protected. A graceful shutdown is better than a sudden power cut. Test a short outage on a non-critical day. Replace the battery before it fails. When did you last test a clean shutdown?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ UPS, clean shutdown, tested battery.&lt;/li&gt;
&lt;li&gt;☐ 1 UPS&lt;/li&gt;
&lt;li&gt;☐ 2 Clean shutdown&lt;/li&gt;
&lt;li&gt;☐ 3 Surge + airflow&lt;/li&gt;
&lt;li&gt;☐ 4 Battery age&lt;/li&gt;
&lt;li&gt;☐ 5 Documented load&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Power is part of the system, not an accessory.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://networkupstools.org/documentation.html"&gt;Network UPS Tools&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs"&gt;Ubuntu Server documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/storage-planning-for-photos-and-video"&gt;Storage planning for photos and video&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/choosing-a-domain-and-email-setup"&gt;Choosing a domain and email setup&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-simple-change-log"&gt;A simple change log&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Storage planning for photos and video</title><link>https://it.kituwa.com/blogs/blog/storage-planning-for-photos-and-video/</link><pubDate>Mon, 09 Feb 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/storage-planning-for-photos-and-video/</guid><description>&lt;p&gt;Photo and video storage grows in one direction: up.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Storage planning for photos and video&lt;/li&gt;
&lt;li&gt;Originals, working files, backups.&lt;/li&gt;
&lt;li&gt;1 Originals&lt;/li&gt;
&lt;li&gt;2 Working files&lt;/li&gt;
&lt;li&gt;3 Growth estimate&lt;/li&gt;
&lt;li&gt;4 Backups&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Plan for originals, working files, and backups separately. A phone photo may be a few megabytes; a video project can be tens of gigabytes. Keep the originals, and know which edits or exports you can recreate.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Estimate growth from your actual library, not a generic number. Leave headroom for imports and temporary files. Use a filesystem and backup tool you understand. Test a restore of one photo and one video project.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;If you use a self-hosted library, back up the database as well as the files. Do not delete the source library until the new one is verified.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Keep a small free-space buffer; full volumes cause strange failures. Name the folders that hold originals. Use checksums or a verified copy tool for large archives. Review the plan when you buy a new camera or phone. Write down the growth number. What is your current growth rate?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/li&gt;
&lt;li&gt;Never testing a restore of a real file.&lt;/li&gt;
&lt;li&gt;Keeping the only copy on the same device or in the same location.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Originals, working files, backups.&lt;/li&gt;
&lt;li&gt;☐ 1 Originals&lt;/li&gt;
&lt;li&gt;☐ 2 Working files&lt;/li&gt;
&lt;li&gt;☐ 3 Growth estimate&lt;/li&gt;
&lt;li&gt;☐ 4 Backups&lt;/li&gt;
&lt;li&gt;☐ 5 Restore test&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Photo and video storage grows in one direction: up.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://immich.app/docs/overview/introduction"&gt;Immich documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-calm-incident-response-for-a-small-team"&gt;A calm incident response for a small team&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-home-lab-power-plan"&gt;A home-lab power plan&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/choosing-a-domain-and-email-setup"&gt;Choosing a domain and email setup&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>A calm incident response for a small team</title><link>https://it.kituwa.com/blogs/blog/a-calm-incident-response-for-a-small-team/</link><pubDate>Sun, 08 Feb 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/a-calm-incident-response-for-a-small-team/</guid><description>&lt;p&gt;When something breaks, calm beats heroics.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A calm incident response for a small team&lt;/li&gt;
&lt;li&gt;Stop, preserve, communicate, restore, review.&lt;/li&gt;
&lt;li&gt;1 Stop + scope — What changed?&lt;/li&gt;
&lt;li&gt;2 Preserve — Logs + time&lt;/li&gt;
&lt;li&gt;3 Communicate — Owner + update&lt;/li&gt;
&lt;li&gt;4 Restore + review — Verify + prevent&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="prove-the-restore"&gt;Prove the restore&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Stop and scope: what is affected, who is impacted, and what changed?&lt;/li&gt;
&lt;li&gt;Preserve evidence: note the time, error, recent changes, and relevant logs. Do not wipe or rebuild before you understand.&lt;/li&gt;
&lt;li&gt;Communicate: one owner, one channel, a short status, and the next update time.&lt;/li&gt;
&lt;li&gt;Restore: use the documented recovery path, one step at a time, and verify.&lt;/li&gt;
&lt;li&gt;Review: write down the cause, the fix, and one prevention step.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Do not share credentials or private data in the incident channel. Do not promise a fix time you cannot support.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Name a backup for the incident owner. Keep a timeline; memory is unreliable under stress. After the review, assign one prevention action and a date. Do not let the incident channel become a blame session. Practice the communication step before a real outage. Write the template down. What is your first communication template?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Stop, preserve, communicate, restore, review.&lt;/li&gt;
&lt;li&gt;☐ 1 Stop + scope — What changed?&lt;/li&gt;
&lt;li&gt;☐ 2 Preserve — Logs + time&lt;/li&gt;
&lt;li&gt;☐ 3 Communicate — Owner + update&lt;/li&gt;
&lt;li&gt;☐ 4 Restore + review — Verify + prevent&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;When something breaks, calm beats heroics.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/pubs/sp/800/61/r3/final"&gt;NIST SP 800-61 — incident handling&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/when-to-replace-instead-of-repair"&gt;When to replace instead of repair&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/storage-planning-for-photos-and-video"&gt;Storage planning for photos and video&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-home-lab-power-plan"&gt;A home-lab power plan&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>When to replace instead of repair</title><link>https://it.kituwa.com/blogs/blog/when-to-replace-instead-of-repair/</link><pubDate>Sat, 07 Feb 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/when-to-replace-instead-of-repair/</guid><description>&lt;p&gt;Repair or replace? Start with evidence.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;When to replace instead of repair&lt;/li&gt;
&lt;li&gt;Evidence before the purchase.&lt;/li&gt;
&lt;li&gt;Repair&lt;/li&gt;
&lt;li&gt;Replace&lt;/li&gt;
&lt;li&gt;Age — Young + supported — Old + unsupported&lt;/li&gt;
&lt;li&gt;Failure — One known part — Repeated faults&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Check the age, failure history, parts availability, power use, and whether the device still receives security updates. A failing drive, swollen battery, or intermittent power fault changes the calculation. A slow machine with a healthy drive may just need more memory or an SSD.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Estimate the cost of downtime and migration, not just the part. Can you move the data? Are the apps available? Will the old peripherals work?&lt;/p&gt;
&lt;h3 id="prove-the-restore"&gt;Prove the restore&lt;/h3&gt;
&lt;p&gt;A repair that restores reliability is often the better choice; a repair that buys six months before the same failure may not be. Do not invent a lifespan for every device; measure its condition and support status.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Check whether the device is still supported by the vendor and the OS. A spare part you cannot buy is not a repair plan. Write down the migration steps before the old device fails. What evidence would change your decision?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Evidence before the purchase.&lt;/li&gt;
&lt;li&gt;☐ Repair&lt;/li&gt;
&lt;li&gt;☐ Replace&lt;/li&gt;
&lt;li&gt;☐ Age — Young + supported — Old + unsupported&lt;/li&gt;
&lt;li&gt;☐ Failure — One known part — Repeated faults&lt;/li&gt;
&lt;li&gt;☐ Parts — Available — Scarce&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Repair or replace?&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.smartmontools.org/"&gt;smartmontools&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/certified"&gt;Ubuntu certified hardware&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-small-business-password-policy"&gt;A small-business password policy&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-calm-incident-response-for-a-small-team"&gt;A calm incident response for a small team&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/storage-planning-for-photos-and-video"&gt;Storage planning for photos and video&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>A small-business password policy</title><link>https://it.kituwa.com/blogs/blog/a-small-business-password-policy/</link><pubDate>Fri, 06 Feb 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/a-small-business-password-policy/</guid><description>&lt;p&gt;A password policy should make the safe path practical.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A small-business password policy&lt;/li&gt;
&lt;li&gt;Practical rules, named owners.&lt;/li&gt;
&lt;li&gt;1 Manager&lt;/li&gt;
&lt;li&gt;2 Unique passwords&lt;/li&gt;
&lt;li&gt;3 MFA&lt;/li&gt;
&lt;li&gt;4 Recovery codes&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="make-recovery-practical"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;Use a password manager, unique passwords per account, long passphrases where a human must remember one, and MFA on important accounts. Do not force arbitrary periodic rotation; rotate on suspicion or exposure. Do not share accounts; use delegated access with names attached.&lt;/p&gt;
&lt;h3 id="make-recovery-practical_1"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;Store recovery codes offline and test one recovery path. Protect the password manager with a strong master password and MFA. Remove access promptly when someone leaves.&lt;/p&gt;
&lt;h3 id="make-recovery-practical_2"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;Write the policy in one page: who approves access, how MFA is enrolled, where recovery codes live, and who reviews accounts quarterly.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Length beats complexity; a long passphrase is easier than a short puzzle. Do not reuse the master password anywhere else. Store the policy where onboarding can find it. Review access after role changes, not only departures. Test one recovery path before you need it. Which rule would be hardest to follow today?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Reusing credentials or recovery material across accounts.&lt;/li&gt;
&lt;li&gt;Storing recovery codes only on the device they protect.&lt;/li&gt;
&lt;li&gt;Skipping MFA or independent verification because it is inconvenient.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Practical rules, named owners.&lt;/li&gt;
&lt;li&gt;☐ 1 Manager&lt;/li&gt;
&lt;li&gt;☐ 2 Unique passwords&lt;/li&gt;
&lt;li&gt;☐ 3 MFA&lt;/li&gt;
&lt;li&gt;☐ 4 Recovery codes&lt;/li&gt;
&lt;li&gt;☐ 5 Access review&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A password policy should make the safe path practical.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Reusing credentials or recovery material across accounts.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://pages.nist.gov/800-63-4/"&gt;NIST SP 800-63B — digital identity&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.nist.gov/itl/ai-risk-management-framework"&gt;NIST — AI risk management&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-to-document-before-you-ask-for-help"&gt;What to document before you ask for help&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/when-to-replace-instead-of-repair"&gt;When to replace instead of repair&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-calm-incident-response-for-a-small-team"&gt;A calm incident response for a small team&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>What to document before you ask for help</title><link>https://it.kituwa.com/blogs/blog/what-to-document-before-you-ask-for-help/</link><pubDate>Thu, 05 Feb 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/what-to-document-before-you-ask-for-help/</guid><description>&lt;p&gt;When you ask for help, context saves time.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;What to document before you ask for help&lt;/li&gt;
&lt;li&gt;Context, evidence, redaction.&lt;/li&gt;
&lt;li&gt;1 Model + OS&lt;/li&gt;
&lt;li&gt;2 Exact error&lt;/li&gt;
&lt;li&gt;3 Recent changes&lt;/li&gt;
&lt;li&gt;4 Steps tried&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="test-the-model-on-your-task"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;Write down: the device model and operating system version; the exact error text or a screenshot; what changed recently; what you already tried; and whether the problem is reproducible. Redact names, tokens, email addresses, and anything private before sharing logs.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;A useful message sounds like: “Linux Mint 22.3 on a ThinkPad T480. Wi-Fi disconnects after suspend. Started after the last update. Tried a reboot and reconnecting; still reproducible. Log excerpt attached with the MAC address removed.”&lt;/p&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;That is far better than “Wi-Fi broken, help.” It also helps you think.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Use the same template for every request; it becomes faster with practice. If logs are large, include a time window and the relevant lines, not the whole file. Say what you need: an explanation, a command review, or a second pair of eyes. A good question is part of the fix. What detail do you usually forget?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Context, evidence, redaction.&lt;/li&gt;
&lt;li&gt;☐ 1 Model + OS&lt;/li&gt;
&lt;li&gt;☐ 2 Exact error&lt;/li&gt;
&lt;li&gt;☐ 3 Recent changes&lt;/li&gt;
&lt;li&gt;☐ 4 Steps tried&lt;/li&gt;
&lt;li&gt;☐ 5 Redact secrets&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;When you ask for help, context saves time.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs"&gt;Ubuntu Server documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/journalctl.1.html"&gt;man journalctl&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-monthly-review-that-actually-helps"&gt;A monthly review that actually helps&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-small-business-password-policy"&gt;A small-business password policy&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/when-to-replace-instead-of-repair"&gt;When to replace instead of repair&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>A monthly review that actually helps</title><link>https://it.kituwa.com/blogs/blog/a-monthly-review-that-actually-helps/</link><pubDate>Wed, 04 Feb 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/a-monthly-review-that-actually-helps/</guid><description>&lt;p&gt;A monthly review should change one thing, not produce a report nobody reads.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A monthly review that actually helps&lt;/li&gt;
&lt;li&gt;One check, one change, one owner.&lt;/li&gt;
&lt;li&gt;1 Backup restore&lt;/li&gt;
&lt;li&gt;2 Updates&lt;/li&gt;
&lt;li&gt;3 Storage&lt;/li&gt;
&lt;li&gt;4 Recovery&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Check five areas: backup restore, updates, storage headroom, account recovery, and incidents. For each, write one line: what you checked, what you found, and what you will change.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Example: “Restored one file from backup; it opened. Storage at 78%; schedule archive review. One failed update; read the release note. Recovery codes still offline.”&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Pick one improvement for next month and give it an owner and a date. If nothing needs changing, say so and stop. A review that always finds ten action items is not a review; it is a backlog.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Keep the review short: a 15-minute check is more likely to happen than a quarterly audit. Store the notes with the backup documentation. If a check fails, fix the process, not just the symptom. Review the last three months for repeat issues. What is the one thing you would change this month?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ One check, one change, one owner.&lt;/li&gt;
&lt;li&gt;☐ 1 Backup restore&lt;/li&gt;
&lt;li&gt;☐ 2 Updates&lt;/li&gt;
&lt;li&gt;☐ 3 Storage&lt;/li&gt;
&lt;li&gt;☐ 4 Recovery&lt;/li&gt;
&lt;li&gt;☐ 5 One improvement&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A monthly review should change one thing, not produce a report nobody reads.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://linuxmint-user-guide.readthedocs.io/en/latest/mintupdate.html"&gt;Linux Mint User Guide — Update Manager&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-month-end-tech-check"&gt;Your month-end tech check&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-to-document-before-you-ask-for-help"&gt;What to document before you ask for help&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-small-business-password-policy"&gt;A small-business password policy&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Your month-end tech check</title><link>https://it.kituwa.com/blogs/blog/your-month-end-tech-check/</link><pubDate>Tue, 03 Feb 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/your-month-end-tech-check/</guid><description>&lt;p&gt;A month-end tech check in five items:&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Your month-end tech check&lt;/li&gt;
&lt;li&gt;Five checks, one documented change.&lt;/li&gt;
&lt;li&gt;1 Restore test&lt;/li&gt;
&lt;li&gt;2 Updates&lt;/li&gt;
&lt;li&gt;3 Account recovery&lt;/li&gt;
&lt;li&gt;4 Storage headroom&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Restore test: recover one expendable file from backup.&lt;/li&gt;
&lt;li&gt;Updates: apply supported updates and reboot if required.&lt;/li&gt;
&lt;li&gt;Account recovery: confirm recovery codes and a second factor.&lt;/li&gt;
&lt;li&gt;Storage headroom: check free space and inode use.&lt;/li&gt;
&lt;li&gt;One documented improvement: write down what you changed and why.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;This is not a full audit; it is a habit that catches drift. If something fails, fix the process before the next month.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What topic should next month’s tutorials cover?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Five checks, one documented change.&lt;/li&gt;
&lt;li&gt;☐ 1 Restore test&lt;/li&gt;
&lt;li&gt;☐ 2 Updates&lt;/li&gt;
&lt;li&gt;☐ 3 Account recovery&lt;/li&gt;
&lt;li&gt;☐ 4 Storage headroom&lt;/li&gt;
&lt;li&gt;☐ 5 One improvement&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A month-end tech check in five items:&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://linuxmint-user-guide.readthedocs.io/en/latest/mintupdate.html"&gt;Linux Mint User Guide — Update Manager&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/build-a-rescue-usb-with-a-purpose"&gt;Build a rescue USB with a purpose&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-monthly-review-that-actually-helps"&gt;A monthly review that actually helps&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-to-document-before-you-ask-for-help"&gt;What to document before you ask for help&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Build a rescue USB with a purpose</title><link>https://it.kituwa.com/blogs/blog/build-a-rescue-usb-with-a-purpose/</link><pubDate>Mon, 02 Feb 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/build-a-rescue-usb-with-a-purpose/</guid><description>&lt;p&gt;Build a rescue USB with a purpose, not a pile of tools.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Build a rescue USB with a purpose&lt;/li&gt;
&lt;li&gt;Diagnostics, recovery, backup.&lt;/li&gt;
&lt;li&gt;Diagnostics — Inspect, don't change&lt;/li&gt;
&lt;li&gt;File recovery — Read-only first&lt;/li&gt;
&lt;li&gt;Backup — Copy out&lt;/li&gt;
&lt;li&gt;Verify — Checksum + source&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Pick tools for three jobs: diagnostics, file recovery, and backups. Verify each download and its source. Label the drive and note the version. Test that it boots on the hardware you might need to rescue.&lt;/p&gt;
&lt;h3 id="find-the-real-limit"&gt;Find the real limit&lt;/h3&gt;
&lt;p&gt;Separate diagnostics from destructive repair. A live system can inspect disks, memory, and logs without changing them. Partition editing and disk wiping are different tasks; do not include them in a beginner rescue kit without a specific plan.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;A rescue kit should be boring, labeled, and tested. Do not download tools from unknown mirrors. Keep a copy of the recovery notes offline. Test the USB on the target machine. Replace it when versions age. Write the date. A rescue kit is not a backup; it is a way to reach a machine and its data. Keep the rescue USB with your backup drive and recovery notes. Include a note with the boot key and test date. Test one file recovery and one backup restore. Keep a second copy of the documentation. Test it before an emergency, not during one.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What would your rescue USB need to do?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Diagnostics, recovery, backup.&lt;/li&gt;
&lt;li&gt;☐ Diagnostics — Inspect, don't change&lt;/li&gt;
&lt;li&gt;☐ File recovery — Read-only first&lt;/li&gt;
&lt;li&gt;☐ Backup — Copy out&lt;/li&gt;
&lt;li&gt;☐ Verify — Checksum + source&lt;/li&gt;
&lt;li&gt;☐ Label — Version + purpose&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Build a rescue USB with a purpose, not a pile of tools.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/tutorials/try-ubuntu-before-you-install"&gt;Ubuntu — try before installing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://clonezilla.org/"&gt;Clonezilla&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/linux-in-ram-the-useful-version"&gt;Linux in RAM: the useful version&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-month-end-tech-check"&gt;Your month-end tech check&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-monthly-review-that-actually-helps"&gt;A monthly review that actually helps&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Linux in RAM: the useful version</title><link>https://it.kituwa.com/blogs/blog/linux-in-ram-the-useful-version/</link><pubDate>Sun, 01 Feb 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/linux-in-ram-the-useful-version/</guid><description>&lt;p&gt;Linux in RAM is a useful tool, not magic.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Linux in RAM: the useful version&lt;/li&gt;
&lt;li&gt;Boot, load, work, discard.&lt;/li&gt;
&lt;li&gt;1 Boot — Live media&lt;/li&gt;
&lt;li&gt;2 Load to RAM — Distro-specific&lt;/li&gt;
&lt;li&gt;3 Work — Temporary session&lt;/li&gt;
&lt;li&gt;4 Save or discard — Persistence choice&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-toram"&gt;Check &lt;code&gt;toram&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;A live boot starts a system from removable media. Some distributions can copy the live image into RAM (&lt;code&gt;toram&lt;/code&gt;-style options), which may let the media be removed after boot and can make some operations faster. Behavior depends on the distribution and the boot options.&lt;/p&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;Persistence is a separate choice. A plain live session discards changes on shutdown; a persistent setup saves some changes but is not a normal installation. RAM boot alone does not guarantee anonymity or leave no traces: the network, storage, logs, and your own actions still matter.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;A live session is slower than an installed system; RAM boot can be faster but still depends on hardware. Check the distribution's documentation for the exact option and memory requirement. Test on a spare machine. Measure it. Do not assume zero wear or instant speed.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What would you use a RAM boot for?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Boot, load, work, discard.&lt;/li&gt;
&lt;li&gt;☐ 1 Boot — Live media&lt;/li&gt;
&lt;li&gt;☐ 2 Load to RAM — Distro-specific&lt;/li&gt;
&lt;li&gt;☐ 3 Work — Temporary session&lt;/li&gt;
&lt;li&gt;☐ 4 Save or discard — Persistence choice&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Linux in RAM is a useful tool, not magic.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://linuxmint-installation-guide.readthedocs.io/en/latest/install.html"&gt;Linux Mint installation guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/tutorials/try-ubuntu-before-you-install"&gt;Ubuntu — try before installing&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-would-make-you-switch-operating-systems"&gt;What would make you switch operating systems?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/build-a-rescue-usb-with-a-purpose"&gt;Build a rescue USB with a purpose&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-month-end-tech-check"&gt;Your month-end tech check&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>What would make you switch operating systems?</title><link>https://it.kituwa.com/blogs/blog/what-would-make-you-switch-operating-systems/</link><pubDate>Sat, 31 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/what-would-make-you-switch-operating-systems/</guid><description>&lt;p&gt;What would make you switch operating systems?&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;What would make you switch operating systems?&lt;/li&gt;
&lt;li&gt;Name the unmet need.&lt;/li&gt;
&lt;li&gt;Reliability — Does it work?&lt;/li&gt;
&lt;li&gt;Privacy — What data leaves?&lt;/li&gt;
&lt;li&gt;Compatibility — Apps + hardware&lt;/li&gt;
&lt;li&gt;Control — What can you change?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Consider five things: reliability, privacy, compatibility, control, and support. A switch is justified by a concrete unmet need, not by a slogan. Staying with your current OS is a valid choice if it works.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Name the need: a specific app, a privacy requirement, a hardware problem, a support constraint, or a cost. Then test the smallest change that addresses it.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Write the need down and test the smallest change that addresses it. A switch is a tool, not an identity. Do not switch just because a platform is fashionable. Measure the migration cost. Which of the five matters most to you?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Name the unmet need.&lt;/li&gt;
&lt;li&gt;☐ Reliability — Does it work?&lt;/li&gt;
&lt;li&gt;☐ Privacy — What data leaves?&lt;/li&gt;
&lt;li&gt;☐ Compatibility — Apps + hardware&lt;/li&gt;
&lt;li&gt;☐ Control — What can you change?&lt;/li&gt;
&lt;li&gt;☐ Support — Who helps?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;What would make you switch operating systems?&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://linuxmint.com/"&gt;Linux Mint&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/desktop"&gt;Ubuntu Desktop&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/before-you-switch-your-main-computer"&gt;Before you switch your main computer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/linux-in-ram-the-useful-version"&gt;Linux in RAM: the useful version&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/build-a-rescue-usb-with-a-purpose"&gt;Build a rescue USB with a purpose&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Before you switch your main computer</title><link>https://it.kituwa.com/blogs/blog/before-you-switch-your-main-computer/</link><pubDate>Fri, 30 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/before-you-switch-your-main-computer/</guid><description>&lt;p&gt;Before you switch your main computer, make a packing list.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Before you switch your main computer&lt;/li&gt;
&lt;li&gt;A packing list, not a leap.&lt;/li&gt;
&lt;li&gt;Files — Backup + restore&lt;/li&gt;
&lt;li&gt;Apps — Feature check&lt;/li&gt;
&lt;li&gt;Browser — Bookmarks + passwords&lt;/li&gt;
&lt;li&gt;Peripherals — Printer, dock, camera&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Files: back up everything you cannot recreate, and test a restore. Essential apps: list the app, the feature you need, and a Linux alternative or workaround. Browser data: bookmarks, passwords, extensions, and sync. Peripherals: printer, scanner, camera, dock, and any vendor software. Recovery media: a live USB and a way back to the old system. A tested backup: separate device, recent copy, known restore steps.&lt;/p&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;Write down the app/feature pairs; a familiar name is not enough. Check the printer/scanner vendor support. Check licenses and account recovery before you move. Test on spare hardware or a live session before replacing a working setup. Test a full workday on the new setup. Keep the old drive or a full image until the new system has survived a week of real work. Document the network and login details you need. Ask for help before the deadline. Test a full workday. Then decide. Do not rush.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Ask for help before the deadline. Document the rollback. Which item would you check first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ A packing list, not a leap.&lt;/li&gt;
&lt;li&gt;☐ Files — Backup + restore&lt;/li&gt;
&lt;li&gt;☐ Apps — Feature check&lt;/li&gt;
&lt;li&gt;☐ Browser — Bookmarks + passwords&lt;/li&gt;
&lt;li&gt;☐ Peripherals — Printer, dock, camera&lt;/li&gt;
&lt;li&gt;☐ Recovery — Live USB + way back&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Before you switch your main computer, make a packing list.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://linuxmint-installation-guide.readthedocs.io/en/latest/install.html"&gt;Linux Mint installation guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/gaming-on-linux-check-your-games-first"&gt;Gaming on Linux: check your games first&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-would-make-you-switch-operating-systems"&gt;What would make you switch operating systems?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/linux-in-ram-the-useful-version"&gt;Linux in RAM: the useful version&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Gaming on Linux: check your games first</title><link>https://it.kituwa.com/blogs/blog/gaming-on-linux-check-your-games-first/</link><pubDate>Thu, 29 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/gaming-on-linux-check-your-games-first/</guid><description>&lt;p&gt;Gaming on Linux starts with a game list, not a distro debate.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Gaming on Linux: check your games first&lt;/li&gt;
&lt;li&gt;A game list before a distro debate.&lt;/li&gt;
&lt;li&gt;1 Game list&lt;/li&gt;
&lt;li&gt;2 Native or Proton&lt;/li&gt;
&lt;li&gt;3 Anti-cheat&lt;/li&gt;
&lt;li&gt;4 Launcher + GPU&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Check each title you actually play: does it have a native Linux build, a Proton compatibility rating, or a known anti-cheat limitation? Check the launcher, the GPU driver, and whether multiplayer works. A single-player game can be fine while a competitive title is blocked.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Use current primary sources where possible: the game's store page, the publisher's support page, ProtonDB reports, and anti-cheat tracking sites. Treat community reports as evidence, not guarantees.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Check the game's store page and the publisher's support notes for the current status. A community report can change after an update. Test the launcher and controller before committing. Compatibility can change after a game or anti-cheat update; recheck before you commit. Test one game before moving your main setup. Keep your existing console or dual-boot as a reasonable option if your favorite title does not work. Record what works and keep a fallback. Do not assume every game in a series behaves the same. Test one title first. Keep a fallback. Document what worked.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;One title at a time. Which game would you test first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ A game list before a distro debate.&lt;/li&gt;
&lt;li&gt;☐ 1 Game list&lt;/li&gt;
&lt;li&gt;☐ 2 Native or Proton&lt;/li&gt;
&lt;li&gt;☐ 3 Anti-cheat&lt;/li&gt;
&lt;li&gt;☐ 4 Launcher + GPU&lt;/li&gt;
&lt;li&gt;☐ 5 Multiplayer&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Gaming on Linux starts with a game list, not a distro debate.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.protondb.com/"&gt;ProtonDB&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://areweanticheatyet.com/"&gt;Are We Anti-Cheat Yet?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ValveSoftware/Proton"&gt;ValveSoftware Proton&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/hardware-wallet-or-software-wallet"&gt;Hardware wallet or software wallet?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/before-you-switch-your-main-computer"&gt;Before you switch your main computer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-would-make-you-switch-operating-systems"&gt;What would make you switch operating systems?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Hardware wallet or software wallet?</title><link>https://it.kituwa.com/blogs/blog/hardware-wallet-or-software-wallet/</link><pubDate>Wed, 28 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/hardware-wallet-or-software-wallet/</guid><description>&lt;p&gt;Hardware and software wallets store keys differently.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This is general security education, not investment advice.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Hardware wallet or software wallet?&lt;/li&gt;
&lt;li&gt;Key storage, convenience, verification.&lt;/li&gt;
&lt;li&gt;Hardware wallet&lt;/li&gt;
&lt;li&gt;Software wallet&lt;/li&gt;
&lt;li&gt;Keys — Dedicated device — General device&lt;/li&gt;
&lt;li&gt;Convenience — More steps — Easier&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;A hardware wallet keeps keys on a dedicated device and asks you to confirm transactions. It can reduce exposure to a compromised computer, but it cannot make a bad transaction safe. You still verify the address, amount, and network.&lt;/p&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;A software wallet is convenient and often free, but the key is on a general-purpose device. Malware, phishing, and backups matter more.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Recovery: both depend on a recovery phrase or backup. Store it offline and never share it. Convenience and verification are trade-offs, not a brand ranking.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which security concept needs a future explainer?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Reusing credentials or recovery material across accounts.&lt;/li&gt;
&lt;li&gt;Storing recovery codes only on the device they protect.&lt;/li&gt;
&lt;li&gt;Skipping MFA or independent verification because it is inconvenient.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Key storage, convenience, verification.&lt;/li&gt;
&lt;li&gt;☐ Hardware wallet&lt;/li&gt;
&lt;li&gt;☐ Software wallet&lt;/li&gt;
&lt;li&gt;☐ Keys — Dedicated device — General device&lt;/li&gt;
&lt;li&gt;☐ Convenience — More steps — Easier&lt;/li&gt;
&lt;li&gt;☐ Verification — Confirm on device — Confirm on screen&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Hardware and software wallets store keys differently.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Reusing credentials or recovery material across accounts.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ethereum.org/en/wallets/"&gt;Ethereum.org — wallets&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ethereum.org/en/security/"&gt;Ethereum.org — security&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/recognize-a-wallet-approval-trap"&gt;Recognize a wallet approval trap&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/gaming-on-linux-check-your-games-first"&gt;Gaming on Linux: check your games first&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/before-you-switch-your-main-computer"&gt;Before you switch your main computer&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Recognize a wallet approval trap</title><link>https://it.kituwa.com/blogs/blog/recognize-a-wallet-approval-trap/</link><pubDate>Tue, 27 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/recognize-a-wallet-approval-trap/</guid><description>&lt;p&gt;Connecting a wallet, signing a message, approving token access, and sending a transaction are different actions with different risks.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This is general security education, not investment advice.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Recognize a wallet approval trap&lt;/li&gt;
&lt;li&gt;Connect, sign, approve, send.&lt;/li&gt;
&lt;li&gt;1 Connect — Share address&lt;/li&gt;
&lt;li&gt;2 Sign message — Read the text&lt;/li&gt;
&lt;li&gt;3 Approve access — Spender + amount&lt;/li&gt;
&lt;li&gt;4 Send — Value + fees&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Connecting usually shares an address and may request permissions. Signing a message can prove ownership or authorize an action, depending on what the message says. Approving token access can let a contract spend a token; the amount and spender matter. Sending a transaction moves value or changes state and costs network fees.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Read the request before you approve it. Check the site, the spender, the amount, and whether the action is unlimited. Use a small test setup, never real funds you cannot afford to lose. No live links here.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;A transaction can be irreversible; a signature can authorize more than you expect. Use a separate test wallet for new sites. Read the full request. Revoke approvals you no longer need, and use a separate wallet for experiments. Bookmark official sites; do not trust search ads. If a prompt is confusing, close it. Slow down. If you are unsure what a signature authorizes, stop.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which action would you review most carefully?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Reusing credentials or recovery material across accounts.&lt;/li&gt;
&lt;li&gt;Storing recovery codes only on the device they protect.&lt;/li&gt;
&lt;li&gt;Skipping MFA or independent verification because it is inconvenient.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Connect, sign, approve, send.&lt;/li&gt;
&lt;li&gt;☐ 1 Connect — Share address&lt;/li&gt;
&lt;li&gt;☐ 2 Sign message — Read the text&lt;/li&gt;
&lt;li&gt;☐ 3 Approve access — Spender + amount&lt;/li&gt;
&lt;li&gt;☐ 4 Send — Value + fees&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Connecting a wallet, signing a message, approving token access, and sending a transaction are different actions with different risks.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Reusing credentials or recovery material across accounts.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ethereum.org/en/security/"&gt;Ethereum.org — security&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ethereum.org/en/wallets/"&gt;Ethereum.org — wallets&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/seed-phrases-and-account-passwords-differ"&gt;Seed phrases and account passwords differ&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/hardware-wallet-or-software-wallet"&gt;Hardware wallet or software wallet?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/gaming-on-linux-check-your-games-first"&gt;Gaming on Linux: check your games first&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Seed phrases and account passwords differ</title><link>https://it.kituwa.com/blogs/blog/seed-phrases-and-account-passwords-differ/</link><pubDate>Mon, 26 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/seed-phrases-and-account-passwords-differ/</guid><description>&lt;p&gt;A wallet recovery phrase, an exchange password, a device PIN, and a two-factor code are different credentials with different jobs.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This is general security education, not investment advice.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Seed phrases and account passwords differ&lt;/li&gt;
&lt;li&gt;Four credentials, four recovery paths.&lt;/li&gt;
&lt;li&gt;Recovery phrase — Never share&lt;/li&gt;
&lt;li&gt;Exchange login — Account credential&lt;/li&gt;
&lt;li&gt;Device PIN — Local unlock&lt;/li&gt;
&lt;li&gt;2FA code — Second factor&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="prove-the-restore"&gt;Prove the restore&lt;/h3&gt;
&lt;p&gt;A wallet recovery phrase can restore a wallet; anyone who has it may control the wallet. Never share it, including with supposed support staff. An exchange login is an account credential protected by the exchange's security controls. A device PIN unlocks a local device. A one-time code is a second factor, not a recovery phrase.&lt;/p&gt;
&lt;h3 id="make-recovery-practical"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;Losing a device is different from losing an account. Know which recovery path applies before you need it. Test recovery with an empty wallet or a small test setup, never with funds you cannot afford to lose.&lt;/p&gt;
&lt;h3 id="make-recovery-practical_1"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;A recovery phrase is not a password you can reset; losing it can mean losing access. Store recovery material offline; do not keep it only in a cloud note. A hardware wallet does not make every transaction safe; you still verify what you sign.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which credential would you check first in an emergency?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Reusing credentials or recovery material across accounts.&lt;/li&gt;
&lt;li&gt;Storing recovery codes only on the device they protect.&lt;/li&gt;
&lt;li&gt;Skipping MFA or independent verification because it is inconvenient.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Four credentials, four recovery paths.&lt;/li&gt;
&lt;li&gt;☐ Recovery phrase — Never share&lt;/li&gt;
&lt;li&gt;☐ Exchange login — Account credential&lt;/li&gt;
&lt;li&gt;☐ Device PIN — Local unlock&lt;/li&gt;
&lt;li&gt;☐ 2FA code — Second factor&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A wallet recovery phrase, an exchange password, a device PIN, and a two-factor code are different credentials with different jobs.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Reusing credentials or recovery material across accounts.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ethereum.org/en/security/"&gt;Ethereum.org — security&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ethereum.org/en/wallets/"&gt;Ethereum.org — wallets&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/could-your-business-recover-without-you"&gt;Could your business recover without you?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/recognize-a-wallet-approval-trap"&gt;Recognize a wallet approval trap&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/hardware-wallet-or-software-wallet"&gt;Hardware wallet or software wallet?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Could your business recover without you?</title><link>https://it.kituwa.com/blogs/blog/could-your-business-recover-without-you/</link><pubDate>Sun, 25 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/could-your-business-recover-without-you/</guid><description>&lt;p&gt;Could your business recover without you?&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Could your business recover without you?&lt;/li&gt;
&lt;li&gt;Write it down, delegate it, test it.&lt;/li&gt;
&lt;li&gt;1 Accounts&lt;/li&gt;
&lt;li&gt;2 Delegated access&lt;/li&gt;
&lt;li&gt;3 Backup owner&lt;/li&gt;
&lt;li&gt;4 Renewals&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Imagine you are away for a week. Can someone else find the accounts, renew the domains, restore the backups, and contact the right people?&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Write down: documented accounts, delegated access, backup ownership, renewal tracking, and emergency contacts. Do not share passwords in a document; use a password manager with a recovery plan.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Test one process with a trusted person. If they cannot follow it without calling you, it depends on your memory.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which process would fail first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Write it down, delegate it, test it.&lt;/li&gt;
&lt;li&gt;☐ 1 Accounts&lt;/li&gt;
&lt;li&gt;☐ 2 Delegated access&lt;/li&gt;
&lt;li&gt;☐ 3 Backup owner&lt;/li&gt;
&lt;li&gt;☐ 4 Renewals&lt;/li&gt;
&lt;li&gt;☐ 5 Contacts&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Could your business recover without you?&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/pubs/sp/800/34/r1/upd1/final"&gt;NIST SP 800-34 — contingency planning&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/review-browser-extension-permissions"&gt;Review browser extension permissions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/seed-phrases-and-account-passwords-differ"&gt;Seed phrases and account passwords differ&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/recognize-a-wallet-approval-trap"&gt;Recognize a wallet approval trap&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Review browser extension permissions</title><link>https://it.kituwa.com/blogs/blog/review-browser-extension-permissions/</link><pubDate>Sat, 24 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/review-browser-extension-permissions/</guid><description>&lt;p&gt;Browser extensions are small programs with permissions. Review them like software, not wallpaper.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Review browser extension permissions&lt;/li&gt;
&lt;li&gt;Publisher, permissions, need.&lt;/li&gt;
&lt;li&gt;Installed — What is running?&lt;/li&gt;
&lt;li&gt;Permissions — Read + change&lt;/li&gt;
&lt;li&gt;Still needed? — Update + remove&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Check installed extensions, who publishes each one, what it can read or change, when it was last updated, and whether you still need it. A permission to “read and change all your data on all websites” is broad; a permission limited to one site is narrower.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Use browser-neutral steps unless you have verified the current interface: open the extensions page, inspect details/permissions, and remove what you do not use. Check the publisher and the store listing, but do not assume store approval guarantees safety.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path_1"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Remove extensions you do not recognize. Check whether the extension can read page content or only click. Prefer fewer extensions. After an update, recheck permissions; they can change. If an extension is abandoned, replace it or remove it. Review after browser updates. Use the browser's extension manager. Use the browser's extension manager.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which extension would you remove today?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Publisher, permissions, need.&lt;/li&gt;
&lt;li&gt;☐ Installed — What is running?&lt;/li&gt;
&lt;li&gt;☐ Permissions — Read + change&lt;/li&gt;
&lt;li&gt;☐ Still needed? — Update + remove&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Browser extensions are small programs with permissions.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://support.google.com/chrome_webstore/answer/2664769"&gt;Chrome Web Store — permissions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://support.mozilla.org/en-US/kb/permissions-addons"&gt;Firefox — extension permissions&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/scam-messages-verify-through-another-route"&gt;Scam messages: verify through another route&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/could-your-business-recover-without-you"&gt;Could your business recover without you?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/seed-phrases-and-account-passwords-differ"&gt;Seed phrases and account passwords differ&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Scam messages: verify through another route</title><link>https://it.kituwa.com/blogs/blog/scam-messages-verify-through-another-route/</link><pubDate>Fri, 23 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/scam-messages-verify-through-another-route/</guid><description>&lt;p&gt;Urgency is a tactic. Pause before you act.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Scam messages: verify through another route&lt;/li&gt;
&lt;li&gt;Pause, then verify independently.&lt;/li&gt;
&lt;li&gt;Urgent payment — Verify by phone&lt;/li&gt;
&lt;li&gt;Login link — Type the address&lt;/li&gt;
&lt;li&gt;Remote support — Never cold-call install&lt;/li&gt;
&lt;li&gt;Account alert — Official channel&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Red flags: an urgent payment request, an unexpected login link, a remote-support request, or a fake account alert. The message may look perfect; appearance and spelling alone do not prove it is safe or fraudulent.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Verify through another route. Find the organization's official phone number or website independently, then contact them. Do not reply to the message, do not use the link, and do not install remote-access software because someone called you.&lt;/p&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;If you already acted, disconnect, change the relevant passwords from a known device, contact the provider through an official channel, and report the message. Report the message to the provider and, where appropriate, to IC3. Do not share codes or remote access with a caller. Use a known device and a known network. Write down what happened. Tell the people who share the account. Keep the evidence.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which request would you verify first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Reusing credentials or recovery material across accounts.&lt;/li&gt;
&lt;li&gt;Storing recovery codes only on the device they protect.&lt;/li&gt;
&lt;li&gt;Skipping MFA or independent verification because it is inconvenient.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Pause, then verify independently.&lt;/li&gt;
&lt;li&gt;☐ Urgent payment — Verify by phone&lt;/li&gt;
&lt;li&gt;☐ Login link — Type the address&lt;/li&gt;
&lt;li&gt;☐ Remote support — Never cold-call install&lt;/li&gt;
&lt;li&gt;☐ Account alert — Official channel&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Urgency is a tactic.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Reusing credentials or recovery material across accounts.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.ic3.gov/"&gt;FBI IC3&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.nist.gov/itl/ai-risk-management-framework"&gt;NIST — AI risk management&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/where-does-your-team-lose-information"&gt;Where does your team lose information?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/review-browser-extension-permissions"&gt;Review browser extension permissions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/could-your-business-recover-without-you"&gt;Could your business recover without you?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Where does your team lose information?</title><link>https://it.kituwa.com/blogs/blog/where-does-your-team-lose-information/</link><pubDate>Thu, 22 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/where-does-your-team-lose-information/</guid><description>&lt;p&gt;Four common information traps:&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Where does your team lose information?&lt;/li&gt;
&lt;li&gt;One process fix for each.&lt;/li&gt;
&lt;li&gt;Buried decisions — Record + link&lt;/li&gt;
&lt;li&gt;Duplicate docs — One current file&lt;/li&gt;
&lt;li&gt;Inbox approvals — Visible status&lt;/li&gt;
&lt;li&gt;Ownerless tasks — Name + date&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Decisions buried in chat. Fix: record the decision and link it from the task.
Duplicate documents. Fix: one current file with an owner and a link.
Approvals in a private inbox. Fix: a shared approval step with a visible status.
Tasks without an owner. Fix: one named owner and a due date.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;None of these requires a new app. They require a place, a link, and a habit. Pick one trap and change one step this week.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which single change would make work easier right now?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ One process fix for each.&lt;/li&gt;
&lt;li&gt;☐ Buried decisions — Record + link&lt;/li&gt;
&lt;li&gt;☐ Duplicate docs — One current file&lt;/li&gt;
&lt;li&gt;☐ Inbox approvals — Visible status&lt;/li&gt;
&lt;li&gt;☐ Ownerless tasks — Name + date&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Four common information traps:&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.mattermost.com/"&gt;Mattermost documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.nextcloud.com/server/latest/admin_manual/"&gt;Nextcloud admin manual&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-shared-team-workspace-blueprint"&gt;A shared team workspace blueprint&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/scam-messages-verify-through-another-route"&gt;Scam messages: verify through another route&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/review-browser-extension-permissions"&gt;Review browser extension permissions&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>A shared team workspace blueprint</title><link>https://it.kituwa.com/blogs/blog/a-shared-team-workspace-blueprint/</link><pubDate>Wed, 21 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/a-shared-team-workspace-blueprint/</guid><description>&lt;p&gt;A small team needs four work areas, not ten apps.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A shared team workspace blueprint&lt;/li&gt;
&lt;li&gt;Small stack, clear ownership.&lt;/li&gt;
&lt;li&gt;Files — Current documents&lt;/li&gt;
&lt;li&gt;Tasks — Owner + status&lt;/li&gt;
&lt;li&gt;Chat — Quick coordination&lt;/li&gt;
&lt;li&gt;Docs — How we work&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Files: where the current document lives. Tasks: what is being done and by whom. Chat: quick coordination, not the system of record. Documentation: how the team works, decisions, and onboarding.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Add an access strip: who can read, write, invite, and remove? Name an owner for each area. Onboarding should add a person to the right groups and give them the documentation. Offboarding should remove access, transfer ownership, and archive what matters.&lt;/p&gt;
&lt;h3 id="prove-the-restore"&gt;Prove the restore&lt;/h3&gt;
&lt;p&gt;Write down the current file, the task owner, and the decision log. Back up the areas that hold irreplaceable data. Keep the stack small; every extra service adds updates, accounts, and failure modes. A small stack with clear links beats a large stack with no map. Name the person who can remove access. Document the onboarding path. Review access quarterly. Test one restore.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which area is currently a mess?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Small stack, clear ownership.&lt;/li&gt;
&lt;li&gt;☐ Files — Current documents&lt;/li&gt;
&lt;li&gt;☐ Tasks — Owner + status&lt;/li&gt;
&lt;li&gt;☐ Chat — Quick coordination&lt;/li&gt;
&lt;li&gt;☐ Docs — How we work&lt;/li&gt;
&lt;li&gt;☐ Access — Read/write/invite&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A small team needs four work areas, not ten apps.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.mattermost.com/"&gt;Mattermost documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.nextcloud.com/server/latest/admin_manual/"&gt;Nextcloud admin manual&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/jitsi-mattermost-and-matrix"&gt;Jitsi, Mattermost, and Matrix&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/where-does-your-team-lose-information"&gt;Where does your team lose information?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/scam-messages-verify-through-another-route"&gt;Scam messages: verify through another route&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Jitsi, Mattermost, and Matrix</title><link>https://it.kituwa.com/blogs/blog/jitsi-mattermost-and-matrix/</link><pubDate>Tue, 20 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/jitsi-mattermost-and-matrix/</guid><description>&lt;p&gt;Three collaboration tools, three different centers of gravity.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Jitsi, Mattermost, and Matrix&lt;/li&gt;
&lt;li&gt;Meetings, team chat, federation.&lt;/li&gt;
&lt;li&gt;Jitsi — Meetings + screen share&lt;/li&gt;
&lt;li&gt;Mattermost — Channels + threads&lt;/li&gt;
&lt;li&gt;Matrix — Federated messaging&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Jitsi is built around meetings: rooms, audio/video, screen sharing, and a browser-first experience. Deployment and security configuration depend on how you host it.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Mattermost is team collaboration: channels, threads, files, and integrations for an organization. It is closer to a shared workspace than a meeting tool.&lt;/p&gt;
&lt;h3 id="check-the-assumptions_1"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Matrix is a federated messaging protocol with clients such as Element. Federation lets different homeservers talk; it is not the same thing as end-to-end encryption. Encryption depends on the room, client, and configuration.&lt;/p&gt;
&lt;h3 id="check-the-assumptions_2"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Jitsi can be self-hosted; Mattermost and Matrix also require ongoing maintenance. Compare intended use, deployment burden, and security model. Check encryption mode and client support before assuming privacy. Document who administers each service. Test with a small group. Test with a small group. Do not assume “federated” means “encrypted,” or that a self-hosted tool is secure by default.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which job are you solving: meetings, team chat, or federated messaging?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Meetings, team chat, federation.&lt;/li&gt;
&lt;li&gt;☐ Jitsi — Meetings + screen share&lt;/li&gt;
&lt;li&gt;☐ Mattermost — Channels + threads&lt;/li&gt;
&lt;li&gt;☐ Matrix — Federated messaging&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Three collaboration tools, three different centers of gravity.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://jitsi.github.io/handbook/"&gt;Jitsi handbook&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.mattermost.com/"&gt;Mattermost documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://matrix.org/docs/"&gt;Matrix documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/would-you-automate-this-or-simplify-it"&gt;Would you automate this or simplify it?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-shared-team-workspace-blueprint"&gt;A shared team workspace blueprint&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/where-does-your-team-lose-information"&gt;Where does your team lose information?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Would you automate this or simplify it?</title><link>https://it.kituwa.com/blogs/blog/would-you-automate-this-or-simplify-it/</link><pubDate>Mon, 19 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/would-you-automate-this-or-simplify-it/</guid><description>&lt;p&gt;Automation is not always the answer.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Would you automate this or simplify it?&lt;/li&gt;
&lt;li&gt;Automation is not the goal.&lt;/li&gt;
&lt;li&gt;Automate — Stable + repetitive&lt;/li&gt;
&lt;li&gt;Simplify — Remove steps&lt;/li&gt;
&lt;li&gt;Review — Judgment needed&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;One fictional process needs automation: a repetitive, rule-based handoff that happens often and has clear exceptions.
One needs simplification: three approvals and two duplicate forms for a low-risk request. Remove steps before adding code.
One needs human judgment: a decision with incomplete information, high consequence, or a relationship at stake.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Ask: is the process stable, measurable, and worth maintaining? Who owns the automation when it breaks? Could a simpler policy remove the need entirely?&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Would you automate, simplify, or review your process?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Automation is not the goal.&lt;/li&gt;
&lt;li&gt;☐ Automate — Stable + repetitive&lt;/li&gt;
&lt;li&gt;☐ Simplify — Remove steps&lt;/li&gt;
&lt;li&gt;☐ Review — Judgment needed&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Automation is not always the answer.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.n8n.io/"&gt;n8n documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/build-an-error-notification-that-helps"&gt;Build an error notification that helps&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/jitsi-mattermost-and-matrix"&gt;Jitsi, Mattermost, and Matrix&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-shared-team-workspace-blueprint"&gt;A shared team workspace blueprint&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Build an error notification that helps</title><link>https://it.kituwa.com/blogs/blog/build-an-error-notification-that-helps/</link><pubDate>Sun, 18 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/build-an-error-notification-that-helps/</guid><description>&lt;p&gt;A useful automation alert answers five questions: what failed, when, where, how bad, and what to do next.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Build an error notification that helps&lt;/li&gt;
&lt;li&gt;Context without secrets.&lt;/li&gt;
&lt;li&gt;Workflow — Name + run ID&lt;/li&gt;
&lt;li&gt;Time — When it failed&lt;/li&gt;
&lt;li&gt;Failed step — Where it stopped&lt;/li&gt;
&lt;li&gt;Safe error — No secrets&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Include the workflow name, timestamp, failed step, a safe error summary, a run identifier, and a next action. Remove secrets, tokens, and personal payload contents. “Something failed” is not actionable.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Fictional example: “Lead intake · 2026-11-29 14:02 · step: create task · error: destination returned 503 · run: lead-7f3a · next: retry once, then check the task API.” That tells the owner where to look without exposing the lead’s private data.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Include the environment (prod/test) and a correlation ID. Route the alert to a channel someone actually reads. Link to the runbook, not just the log. Test the alert with a harmless failure. Keep the message short. Use a stable alert template. Name the owner. Set a severity. Test the notification path before you rely on it.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Would this alert help you fix the problem?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Context without secrets.&lt;/li&gt;
&lt;li&gt;☐ Workflow — Name + run ID&lt;/li&gt;
&lt;li&gt;☐ Time — When it failed&lt;/li&gt;
&lt;li&gt;☐ Failed step — Where it stopped&lt;/li&gt;
&lt;li&gt;☐ Safe error — No secrets&lt;/li&gt;
&lt;li&gt;☐ Next action — What to try&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A useful automation alert answers five questions: what failed, when, where, how bad, and what to do next.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.n8n.io/"&gt;n8n documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://prometheus.io/docs/practices/alerting/"&gt;Prometheus — alerting practices&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/retries-can-create-duplicates"&gt;Retries can create duplicates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/would-you-automate-this-or-simplify-it"&gt;Would you automate this or simplify it?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/jitsi-mattermost-and-matrix"&gt;Jitsi, Mattermost, and Matrix&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Retries can create duplicates</title><link>https://it.kituwa.com/blogs/blog/retries-can-create-duplicates/</link><pubDate>Sat, 17 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/retries-can-create-duplicates/</guid><description>&lt;p&gt;A timeout does not mean the request failed. It means you did not receive a response in time. The remote system may have completed the work anyway.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Retries can create duplicates&lt;/li&gt;
&lt;li&gt;Timeouts are not proof of failure.&lt;/li&gt;
&lt;li&gt;1 Request — Send once&lt;/li&gt;
&lt;li&gt;2 Timeout — No response&lt;/li&gt;
&lt;li&gt;3 Check state — Did it succeed?&lt;/li&gt;
&lt;li&gt;4 Idempotency — Safe to retry&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="verify-the-key-path"&gt;Verify the key path&lt;/h3&gt;
&lt;p&gt;If you retry blindly, you can create two tickets, two charges, or two emails. The fix is an identifier that makes the operation safe to repeat: a unique request ID, an idempotency key, or a uniqueness constraint at the destination.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Fictional example: your workflow sends a ticket request, times out, and retries. Without a shared request ID, the ticket system creates a second ticket. With the ID, the second request is recognized and returns the first result.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;The destination should enforce uniqueness, not just the sender. Log the request ID with the result. There is no universal retry rule. Decide which operations are safe to repeat, which need a check-before-retry, and which should stop and ask a human.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which of your automations retries without checking?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Timeouts are not proof of failure.&lt;/li&gt;
&lt;li&gt;☐ 1 Request — Send once&lt;/li&gt;
&lt;li&gt;☐ 2 Timeout — No response&lt;/li&gt;
&lt;li&gt;☐ 3 Check state — Did it succeed?&lt;/li&gt;
&lt;li&gt;☐ 4 Idempotency — Safe to retry&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A timeout does not mean the request failed.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.stripe.com/api/idempotent_requests"&gt;Stripe — idempotent requests&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.n8n.io/"&gt;n8n documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-repetitive-task-costs-you-attention"&gt;What repetitive task costs you attention?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/build-an-error-notification-that-helps"&gt;Build an error notification that helps&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/would-you-automate-this-or-simplify-it"&gt;Would you automate this or simplify it?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>What repetitive task costs you attention?</title><link>https://it.kituwa.com/blogs/blog/what-repetitive-task-costs-you-attention/</link><pubDate>Fri, 16 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/what-repetitive-task-costs-you-attention/</guid><description>&lt;p&gt;Four repetitive loops that quietly eat attention:&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;What repetitive task costs you attention?&lt;/li&gt;
&lt;li&gt;Measure it before automating.&lt;/li&gt;
&lt;li&gt;Copy forms — Repeated entry&lt;/li&gt;
&lt;li&gt;Rename scans — Manual naming&lt;/li&gt;
&lt;li&gt;Weekly report — Three sources&lt;/li&gt;
&lt;li&gt;Health checks — Many dashboards&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Copying form submissions into a spreadsheet.
Renaming scans so they can be found later.
Compiling the same weekly report from three sources.
Checking service health one dashboard at a time.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;A good automation candidate has a measurable task, stable inputs, clear exception rules, and an owner. “It annoys me” is a start; “it happens 20 times a week and takes four minutes each” is a business case.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;When you describe it, include the trigger, the current steps, and the result you want — not just an app name.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which loop would you remove first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Measure it before automating.&lt;/li&gt;
&lt;li&gt;☐ Copy forms — Repeated entry&lt;/li&gt;
&lt;li&gt;☐ Rename scans — Manual naming&lt;/li&gt;
&lt;li&gt;☐ Weekly report — Three sources&lt;/li&gt;
&lt;li&gt;☐ Health checks — Many dashboards&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Four repetitive loops that quietly eat attention:&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.n8n.io/"&gt;n8n documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/design-an-automation-before-building-it"&gt;Design an automation before building it&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/retries-can-create-duplicates"&gt;Retries can create duplicates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/build-an-error-notification-that-helps"&gt;Build an error notification that helps&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Design an automation before building it</title><link>https://it.kituwa.com/blogs/blog/design-an-automation-before-building-it/</link><pubDate>Thu, 15 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/design-an-automation-before-building-it/</guid><description>&lt;p&gt;Before you build an automation, write the worksheet.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Design an automation before building it&lt;/li&gt;
&lt;li&gt;Seven answers before the first node.&lt;/li&gt;
&lt;li&gt;Trigger — What starts it?&lt;/li&gt;
&lt;li&gt;Inputs — Required fields&lt;/li&gt;
&lt;li&gt;Validation — What is invalid?&lt;/li&gt;
&lt;li&gt;Destination — Where does it go?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Trigger: what starts the workflow?
Input fields: what data arrives, and which fields are required?
Validation: what makes an input invalid?
Destination: where does the result go?
Duplicate protection: what stops the same request from creating two records?
Retries: what happens after a failure, and how many attempts?
Owner: who fixes it when it breaks?&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Fictional example: an internal lead-intake form. Validate the email and required fields, create one task, check a unique request ID, and notify the owner after a failed retry. No unsolicited outreach.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Write the expected output for one sample input; it exposes gaps before you build. Decide what happens to invalid submissions. Keep a manual fallback. A clear worksheet is cheaper than debugging a mystery workflow. If you want help turning the worksheet into a build, Kituwa can scope it with you.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which field would you validate first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Seven answers before the first node.&lt;/li&gt;
&lt;li&gt;☐ Trigger — What starts it?&lt;/li&gt;
&lt;li&gt;☐ Inputs — Required fields&lt;/li&gt;
&lt;li&gt;☐ Validation — What is invalid?&lt;/li&gt;
&lt;li&gt;☐ Destination — Where does it go?&lt;/li&gt;
&lt;li&gt;☐ Duplicates — Unique request ID&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Before you build an automation, write the worksheet.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.n8n.io/"&gt;n8n documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.stripe.com/api/idempotent_requests"&gt;Stripe — idempotent requests&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/n8n-what-workflow-automation-means"&gt;n8n: what workflow automation means&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-repetitive-task-costs-you-attention"&gt;What repetitive task costs you attention?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/retries-can-create-duplicates"&gt;Retries can create duplicates&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>n8n: what workflow automation means</title><link>https://it.kituwa.com/blogs/blog/n8n-what-workflow-automation-means/</link><pubDate>Wed, 14 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/n8n-what-workflow-automation-means/</guid><description>&lt;p&gt;An automation is a small pipeline: trigger, action, condition, error path.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;n8n: what workflow automation means&lt;/li&gt;
&lt;li&gt;Trigger, action, condition, error.&lt;/li&gt;
&lt;li&gt;1 Trigger — Form or schedule&lt;/li&gt;
&lt;li&gt;2 Action — Create or notify&lt;/li&gt;
&lt;li&gt;3 Condition — Branch by rule&lt;/li&gt;
&lt;li&gt;4 Error path — Retry or alert&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Trigger: what starts it? A form submission, schedule, webhook, or new file.
Action: what happens? Create a task, send a message, update a record.
Condition: when should it branch? Only for a certain category or amount.
Error path: what happens when a step fails? Retry, notify, or stop.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;A fictional inquiry form: trigger on submission; validate required fields; create an internal task; if the email domain is internal, route to a different queue; on failure, notify the owner with a run ID.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;n8n is a workflow tool; licensing depends on the edition and use. Do not call every self-hostable product open source without checking its license. A retry is not free; it can duplicate an action. Keep the first workflow small enough to read in one screen. Test the failure path before the happy path. Document the owner.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which step would you automate first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Trigger, action, condition, error.&lt;/li&gt;
&lt;li&gt;☐ 1 Trigger — Form or schedule&lt;/li&gt;
&lt;li&gt;☐ 2 Action — Create or notify&lt;/li&gt;
&lt;li&gt;☐ 3 Condition — Branch by rule&lt;/li&gt;
&lt;li&gt;☐ 4 Error path — Retry or alert&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;An automation is a small pipeline: trigger, action, condition, error path.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.n8n.io/"&gt;n8n documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.n8n.io/sustainable-use-license/"&gt;n8n Sustainable Use License&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/where-should-ai-need-your-approval"&gt;Where should AI need your approval?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/design-an-automation-before-building-it"&gt;Design an automation before building it&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-repetitive-task-costs-you-attention"&gt;What repetitive task costs you attention?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Where should AI need your approval?</title><link>https://it.kituwa.com/blogs/blog/where-should-ai-need-your-approval/</link><pubDate>Tue, 13 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/where-should-ai-need-your-approval/</guid><description>&lt;p&gt;Use consequence and reversibility to decide.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Where should AI need your approval?&lt;/li&gt;
&lt;li&gt;Consequence and reversibility.&lt;/li&gt;
&lt;li&gt;Draft — Review, easy discard&lt;/li&gt;
&lt;li&gt;Document edit — Version + diff&lt;/li&gt;
&lt;li&gt;Customer email — Approve before send&lt;/li&gt;
&lt;li&gt;Purchase / server — Explicit approval + rollback&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Draft creation: low consequence, easy to discard; a review is still wise.
Document edits: moderate; keep a version and review changes.
Customer emails: high; approve before send.
Purchases: high; require explicit approval and a limit.
Server changes: high; require approval, a rollback, and a change window.&lt;/p&gt;
&lt;h3 id="test-the-model-on-your-task"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;The more consequential and irreversible the action, the stronger the gate. “The AI did it” is not an incident response.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which action would you never let run unattended?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Consequence and reversibility.&lt;/li&gt;
&lt;li&gt;☐ Draft — Review, easy discard&lt;/li&gt;
&lt;li&gt;☐ Document edit — Version + diff&lt;/li&gt;
&lt;li&gt;☐ Customer email — Approve before send&lt;/li&gt;
&lt;li&gt;☐ Purchase / server — Explicit approval + rollback&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Use consequence and reversibility to decide.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.nist.gov/itl/ai-risk-management-framework"&gt;NIST AI Risk Management Framework&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://support.claude.com/en/articles/12512198-how-to-create-custom-skills"&gt;Claude — custom skills&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/turn-a-checklist-into-a-reusable-ai-workflow"&gt;Turn a checklist into a reusable AI workflow&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/n8n-what-workflow-automation-means"&gt;n8n: what workflow automation means&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/design-an-automation-before-building-it"&gt;Design an automation before building it&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Turn a checklist into a reusable AI workflow</title><link>https://it.kituwa.com/blogs/blog/turn-a-checklist-into-a-reusable-ai-workflow/</link><pubDate>Mon, 12 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/turn-a-checklist-into-a-reusable-ai-workflow/</guid><description>&lt;p&gt;Take a task you already do: editing a blog draft.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Turn a checklist into a reusable AI workflow&lt;/li&gt;
&lt;li&gt;Inputs, rules, checks, approval.&lt;/li&gt;
&lt;li&gt;1 Inputs — Draft + sources&lt;/li&gt;
&lt;li&gt;2 Style rules — Voice + format&lt;/li&gt;
&lt;li&gt;3 Factual checks — Sources + flags&lt;/li&gt;
&lt;li&gt;4 Human approval — Before publish&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Define inputs: draft, audience, style guide, and source links.
Define style rules: voice, length, headings, forbidden claims.
Define factual checks: every claim needs a source; flag unverified numbers.
Define output structure: edited draft, change list, and open questions.
Add a human approval point before publishing.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Save the instructions as a reusable workflow. The example is a proposed workflow, not a tested skill package. Access to tools depends on the product and permissions.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Name the owner of the workflow and the approval step. The value is consistency: same inputs, same checks, same review. Start with one task and one owner; expand only after the workflow survives a real week. Keep the source material and the output in separate folders so you can compare. Review the workflow quarterly. A workflow is documentation you can run.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which checklist do you repeat every week?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Inputs, rules, checks, approval.&lt;/li&gt;
&lt;li&gt;☐ 1 Inputs — Draft + sources&lt;/li&gt;
&lt;li&gt;☐ 2 Style rules — Voice + format&lt;/li&gt;
&lt;li&gt;☐ 3 Factual checks — Sources + flags&lt;/li&gt;
&lt;li&gt;☐ 4 Human approval — Before publish&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Take a task you already do: editing a blog draft.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://support.claude.com/en/articles/12512198-how-to-create-custom-skills"&gt;Claude — custom skills&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/overview"&gt;Anthropic prompt engineering overview&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/ai-skills-are-not-magic-slash-commands"&gt;AI skills are not magic slash commands&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/where-should-ai-need-your-approval"&gt;Where should AI need your approval?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/n8n-what-workflow-automation-means"&gt;n8n: what workflow automation means&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>AI skills are not magic slash commands</title><link>https://it.kituwa.com/blogs/blog/ai-skills-are-not-magic-slash-commands/</link><pubDate>Sun, 11 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/ai-skills-are-not-magic-slash-commands/</guid><description>&lt;p&gt;A reusable instruction set is not the same as a built-in feature.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;AI skills are not magic slash commands&lt;/li&gt;
&lt;li&gt;Instructions, tools, permissions.&lt;/li&gt;
&lt;li&gt;Instructions — Text you use&lt;/li&gt;
&lt;li&gt;Custom skill — Product-specific package&lt;/li&gt;
&lt;li&gt;Permissions — Tools + access&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="test-the-model-on-your-task"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;Instructions: text you paste or save to guide a model. They work only where you use them.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Custom skills: packaged instructions and resources that a specific product loads in a specific way. The name, installation method, and availability depend on the product.&lt;/p&gt;
&lt;h3 id="test-the-model-on-your-task_1"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;Installed integrations/tools: connections that let a model call another service. They need permissions and a configured environment.&lt;/p&gt;
&lt;h3 id="check-the-assumptions_1"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Do not assume a slash command from a screenshot is available to everyone. Verify the product, the package, and the installation steps. Do not claim “tried and tested” unless you actually tested it. Start with a plain instruction; add a skill or tool only when it solves a concrete problem. Document the version and scope so future-you knows what is installed. Write down the installation source and version for any skill you add. Remove what you no longer use.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which layer are you actually using?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Instructions, tools, permissions.&lt;/li&gt;
&lt;li&gt;☐ Instructions — Text you use&lt;/li&gt;
&lt;li&gt;☐ Custom skill — Product-specific package&lt;/li&gt;
&lt;li&gt;☐ Permissions — Tools + access&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A reusable instruction set is not the same as a built-in feature.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://support.claude.com/en/articles/12512198-how-to-create-custom-skills"&gt;Claude — custom skills&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ollama.com/"&gt;Ollama documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/the-ai-task-you-should-keep-reviewing"&gt;The AI task you should keep reviewing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/turn-a-checklist-into-a-reusable-ai-workflow"&gt;Turn a checklist into a reusable AI workflow&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/where-should-ai-need-your-approval"&gt;Where should AI need your approval?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>The AI task you should keep reviewing</title><link>https://it.kituwa.com/blogs/blog/the-ai-task-you-should-keep-reviewing/</link><pubDate>Sat, 10 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/the-ai-task-you-should-keep-reviewing/</guid><description>&lt;p&gt;Some AI output should always have a human review gate.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The AI task you should keep reviewing&lt;/li&gt;
&lt;li&gt;A gate before consequence.&lt;/li&gt;
&lt;li&gt;Draft email — Tone + commitments&lt;/li&gt;
&lt;li&gt;Formula — Test on a copy&lt;/li&gt;
&lt;li&gt;Command — Read flags + paths&lt;/li&gt;
&lt;li&gt;Customer fact — Official source&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Draft emails: review tone, names, commitments, and anything that sounds like a promise.
Spreadsheet formulas: test on a copy, check references, and verify the result.
Generated commands: read every flag, path, and destructive effect before running.
Customer-facing facts: verify against an official source; do not trust a confident sentence.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;A review gate is not distrust; it is the point where consequence meets judgment. Put the gate before send, run, publish, or delete.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Where have you caught a confidently wrong answer?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ A gate before consequence.&lt;/li&gt;
&lt;li&gt;☐ Draft email — Tone + commitments&lt;/li&gt;
&lt;li&gt;☐ Formula — Test on a copy&lt;/li&gt;
&lt;li&gt;☐ Command — Read flags + paths&lt;/li&gt;
&lt;li&gt;☐ Customer fact — Official source&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Some AI output should always have a human review gate.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.nist.gov/itl/ai-risk-management-framework"&gt;NIST AI Risk Management Framework&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/overview"&gt;Anthropic prompt engineering overview&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-reusable-prompt-that-produces-useful-drafts"&gt;A reusable prompt that produces useful drafts&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/ai-skills-are-not-magic-slash-commands"&gt;AI skills are not magic slash commands&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/turn-a-checklist-into-a-reusable-ai-workflow"&gt;Turn a checklist into a reusable AI workflow&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>A reusable prompt that produces useful drafts</title><link>https://it.kituwa.com/blogs/blog/a-reusable-prompt-that-produces-useful-drafts/</link><pubDate>Fri, 09 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/a-reusable-prompt-that-produces-useful-drafts/</guid><description>&lt;p&gt;Use a six-block template.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A reusable prompt that produces useful drafts&lt;/li&gt;
&lt;li&gt;Six blocks, clearer instructions.&lt;/li&gt;
&lt;li&gt;Goal — What should it do?&lt;/li&gt;
&lt;li&gt;Audience — Who reads it?&lt;/li&gt;
&lt;li&gt;Sources — What must it use?&lt;/li&gt;
&lt;li&gt;Constraints — Length, tone, avoid&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Goal: what should the draft accomplish?
Audience: who reads it, and what do they know?
Source material: which facts, documents, or examples must be used?
Constraints: length, tone, format, things to avoid.
Output format: headings, bullets, table, or plain text.
Verification: ask the model to list assumptions and flag anything it could not verify.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Example: a fictional service FAQ. Before: “Write an FAQ.” After: “Write a 6-question FAQ for a small business owner comparing two support plans. Use only the attached plan table. Use plain language, 80-120 words per answer, and flag any missing detail.”&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;The second prompt is not magic; it is clearer about the job. A reusable prompt should include an example of a good answer and a known bad answer. Store it with the source material. Save the template and reuse it; do not retype it every time.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which block do you usually forget?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Six blocks, clearer instructions.&lt;/li&gt;
&lt;li&gt;☐ Goal — What should it do?&lt;/li&gt;
&lt;li&gt;☐ Audience — Who reads it?&lt;/li&gt;
&lt;li&gt;☐ Sources — What must it use?&lt;/li&gt;
&lt;li&gt;☐ Constraints — Length, tone, avoid&lt;/li&gt;
&lt;li&gt;☐ Format — Headings, bullets, table&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Use a six-block template.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/overview"&gt;Anthropic prompt engineering overview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ollama.com/"&gt;Ollama documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/rag-vs-fine-tuning-vs-better-prompting"&gt;RAG vs fine-tuning vs better prompting&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/the-ai-task-you-should-keep-reviewing"&gt;The AI task you should keep reviewing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/ai-skills-are-not-magic-slash-commands"&gt;AI skills are not magic slash commands&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>RAG vs fine-tuning vs better prompting</title><link>https://it.kituwa.com/blogs/blog/rag-vs-fine-tuning-vs-better-prompting/</link><pubDate>Thu, 08 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/rag-vs-fine-tuning-vs-better-prompting/</guid><description>&lt;p&gt;Three paths, different jobs.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;RAG vs fine-tuning vs better prompting&lt;/li&gt;
&lt;li&gt;Three paths, different jobs.&lt;/li&gt;
&lt;li&gt;Prompting — Instructions + format&lt;/li&gt;
&lt;li&gt;RAG — Retrieve current docs&lt;/li&gt;
&lt;li&gt;Fine-tuning — Teach style/pattern&lt;/li&gt;
&lt;li&gt;Review — Check the answer&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Better prompting changes the instructions: role, constraints, examples, output format. It is the cheapest first step.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;RAG retrieves reference material and puts it in the prompt. It is useful when answers depend on documents that change. Retrieval does not guarantee truth; the model can still misread or ignore the source.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;RAG also needs a source of truth and a way to update or remove stale documents; otherwise retrieval can surface outdated policy. Fine-tuning changes model behavior through training data. It can teach style or a narrow pattern, but it is not a database and can become stale. It also needs data, evaluation, and maintenance. Fine-tuning needs an evaluation set so you can detect regressions.&lt;/p&gt;
&lt;h3 id="step-4-what-to-check"&gt;Step 4: what to check&lt;/h3&gt;
&lt;p&gt;A fictional company handbook: prompting can set the format; RAG can fetch the current policy; fine-tuning can teach the tone. Start with the simplest path that solves the problem.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which path matches your changing data?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Three paths, different jobs.&lt;/li&gt;
&lt;li&gt;☐ Prompting — Instructions + format&lt;/li&gt;
&lt;li&gt;☐ RAG — Retrieve current docs&lt;/li&gt;
&lt;li&gt;☐ Fine-tuning — Teach style/pattern&lt;/li&gt;
&lt;li&gt;☐ Review — Check the answer&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Three paths, different jobs.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.ollama.com/"&gt;Ollama documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/overview"&gt;Anthropic prompt engineering overview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://huggingface.co/docs/peft"&gt;Hugging Face PEFT&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/smaller-model-better-workflow"&gt;Smaller model, better workflow?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-reusable-prompt-that-produces-useful-drafts"&gt;A reusable prompt that produces useful drafts&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/the-ai-task-you-should-keep-reviewing"&gt;The AI task you should keep reviewing&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Smaller model, better workflow?</title><link>https://it.kituwa.com/blogs/blog/smaller-model-better-workflow/</link><pubDate>Wed, 07 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/smaller-model-better-workflow/</guid><description>&lt;p&gt;A small model can be the better choice when the job is narrow.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Smaller model, better workflow?&lt;/li&gt;
&lt;li&gt;Narrow task, strong workflow.&lt;/li&gt;
&lt;li&gt;Small model&lt;/li&gt;
&lt;li&gt;Large model&lt;/li&gt;
&lt;li&gt;Best at — One narrow task — Broad reasoning&lt;/li&gt;
&lt;li&gt;Hardware — Modest — More memory/compute&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="test-the-model-on-your-task"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;A small model doing one task (classify, extract, rewrite, answer from a fixed document) can be faster, cheaper, and easier to run locally. A larger model may handle broad reasoning and unfamiliar tasks better, but it needs more hardware and can still be wrong.&lt;/p&gt;
&lt;h3 id="test-the-model-on-your-task_1"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;The workflow matters: retrieval can give a small model the right context; verification catches errors; a human review gate catches the rest.&lt;/p&gt;
&lt;h3 id="test-the-model-on-your-task_2"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;Do not declare one model universally superior. Measure reliability on your task, response time, and hardware limits.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Would you choose reliability on one task or breadth across many?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Narrow task, strong workflow.&lt;/li&gt;
&lt;li&gt;☐ Small model&lt;/li&gt;
&lt;li&gt;☐ Large model&lt;/li&gt;
&lt;li&gt;☐ Best at — One narrow task — Broad reasoning&lt;/li&gt;
&lt;li&gt;☐ Hardware — Modest — More memory/compute&lt;/li&gt;
&lt;li&gt;☐ Speed — Often faster — Often slower&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A small model can be the better choice when the job is narrow.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ollama.com/library"&gt;Ollama library&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ggml-org/llama.cpp"&gt;llama.cpp&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/test-a-model-with-your-own-task"&gt;Test a model with your own task&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/rag-vs-fine-tuning-vs-better-prompting"&gt;RAG vs fine-tuning vs better prompting&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-reusable-prompt-that-produces-useful-drafts"&gt;A reusable prompt that produces useful drafts&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Test a model with your own task</title><link>https://it.kituwa.com/blogs/blog/test-a-model-with-your-own-task/</link><pubDate>Tue, 06 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/test-a-model-with-your-own-task/</guid><description>&lt;p&gt;Pick five questions that represent your real work. Use a fixed prompt, the same settings, and the same source material for each model.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Test a model with your own task&lt;/li&gt;
&lt;li&gt;Five questions, one fixed prompt.&lt;/li&gt;
&lt;li&gt;1 Five questions&lt;/li&gt;
&lt;li&gt;2 Fixed prompt&lt;/li&gt;
&lt;li&gt;3 Timing notes&lt;/li&gt;
&lt;li&gt;4 Factual checks&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;For each answer, record: time to first token, total time, factual errors, missing constraints, and whether you would send it to a customer. A simple 1-5 score is enough if you define what each score means.&lt;/p&gt;
&lt;h3 id="test-the-model-on-your-task"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;Use the same stop conditions and temperature/settings; otherwise you are comparing luck. Do not cherry-pick the best answer. Compare the full set. Run it twice if the model is nondeterministic. Record failures, not just the wins. Keep the test set private and stable so future comparisons are meaningful. Write down the model, version, and settings.&lt;/p&gt;
&lt;h3 id="test-the-model-on-your-task_1"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;The goal is not a leaderboard; it is evidence for your workload. A model that wins a generic benchmark may lose on your documents, language, or format.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What does success look like for your task?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Five questions, one fixed prompt.&lt;/li&gt;
&lt;li&gt;☐ 1 Five questions&lt;/li&gt;
&lt;li&gt;☐ 2 Fixed prompt&lt;/li&gt;
&lt;li&gt;☐ 3 Timing notes&lt;/li&gt;
&lt;li&gt;☐ 4 Factual checks&lt;/li&gt;
&lt;li&gt;☐ 5 Score + review&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Pick five questions that represent your real work.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.ollama.com/"&gt;Ollama documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/overview"&gt;Anthropic prompt engineering overview&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/quantization-without-the-jargon"&gt;Quantization without the jargon&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/smaller-model-better-workflow"&gt;Smaller model, better workflow?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/rag-vs-fine-tuning-vs-better-prompting"&gt;RAG vs fine-tuning vs better prompting&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Quantization without the jargon</title><link>https://it.kituwa.com/blogs/blog/quantization-without-the-jargon/</link><pubDate>Mon, 05 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/quantization-without-the-jargon/</guid><description>&lt;p&gt;Quantization stores model weights at lower precision. Instead of 16-bit or 32-bit numbers, a quantized model might use 8-bit or 4-bit values. That can reduce memory use and sometimes improve speed, but it is not a universal win.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Quantization without the jargon&lt;/li&gt;
&lt;li&gt;Lower precision, real trade-offs.&lt;/li&gt;
&lt;li&gt;Full precision — More memory&lt;/li&gt;
&lt;li&gt;8-bit — Smaller, often close&lt;/li&gt;
&lt;li&gt;4-bit — Smallest, test quality&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="test-the-model-on-your-task"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;The tradeoff: lower precision can change output quality. Some models tolerate it well; others degrade on math, code, or long reasoning. The only reliable test is your task.&lt;/p&gt;
&lt;h3 id="test-the-model-on-your-task_1"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;Quantization is not the same as context length. A 4-bit model can still use a long context, and the KV cache for that context still takes memory. Runtime overhead and other services also count.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Check the model card and quantization format. Test at the context length you actually use. Do not compare file sizes across different quantization methods as if they were equivalent; the format and runtime matter. Do not assume a smaller file is always faster or better.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What would you test first after quantizing?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Lower precision, real trade-offs.&lt;/li&gt;
&lt;li&gt;☐ Full precision — More memory&lt;/li&gt;
&lt;li&gt;☐ 8-bit — Smaller, often close&lt;/li&gt;
&lt;li&gt;☐ 4-bit — Smallest, test quality&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Quantization stores model weights at lower precision.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/ggml-org/llama.cpp/blob/master/tools/quantize/README.md"&gt;llama.cpp quantization&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ollama.com/"&gt;Ollama documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-would-you-use-offline-ai-for"&gt;What would you use offline AI for?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/test-a-model-with-your-own-task"&gt;Test a model with your own task&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/smaller-model-better-workflow"&gt;Smaller model, better workflow?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>What would you use offline AI for?</title><link>https://it.kituwa.com/blogs/blog/what-would-you-use-offline-ai-for/</link><pubDate>Sun, 04 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/what-would-you-use-offline-ai-for/</guid><description>&lt;p&gt;Offline AI is most useful when the job is clear and the cost of a wrong answer is low.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;What would you use offline AI for?&lt;/li&gt;
&lt;li&gt;Clear job, checkable output.&lt;/li&gt;
&lt;li&gt;Draft — Summaries from notes&lt;/li&gt;
&lt;li&gt;Code — Boilerplate + explanations&lt;/li&gt;
&lt;li&gt;Search — Local documents&lt;/li&gt;
&lt;li&gt;Automate — Repetitive tasks&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Good candidates: drafting a summary from notes you provide, renaming files, generating boilerplate, explaining a command, or searching a local document set. Less good: high-stakes medical, legal, or financial decisions without review.&lt;/p&gt;
&lt;h3 id="test-the-model-on-your-task"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;Ask: does it need the internet? Does it need current facts? Can I check the output? Who sees the data? A local model can still be wrong, and it can still leak data through logs or plugins.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Pick one repetitive task and test it for a week.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What would you use offline AI for?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Clear job, checkable output.&lt;/li&gt;
&lt;li&gt;☐ Draft — Summaries from notes&lt;/li&gt;
&lt;li&gt;☐ Code — Boilerplate + explanations&lt;/li&gt;
&lt;li&gt;☐ Search — Local documents&lt;/li&gt;
&lt;li&gt;☐ Automate — Repetitive tasks&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Offline AI is most useful when the job is clear and the cost of a wrong answer is low.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.ollama.com/"&gt;Ollama documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ggml-org/llama.cpp"&gt;llama.cpp&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/size-an-ai-model-honestly"&gt;Size an AI model honestly&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/quantization-without-the-jargon"&gt;Quantization without the jargon&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/test-a-model-with-your-own-task"&gt;Test a model with your own task&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Size an AI model honestly</title><link>https://it.kituwa.com/blogs/blog/size-an-ai-model-honestly/</link><pubDate>Sat, 03 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/size-an-ai-model-honestly/</guid><description>&lt;p&gt;Model size is not a single number. You need to account for weights, quantization, context, and runtime overhead.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Size an AI model honestly&lt;/li&gt;
&lt;li&gt;Weights, context, and overhead.&lt;/li&gt;
&lt;li&gt;1 Weights&lt;/li&gt;
&lt;li&gt;2 Quantization&lt;/li&gt;
&lt;li&gt;3 Context&lt;/li&gt;
&lt;li&gt;4 Memory + VRAM&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="test-the-model-on-your-task"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;A quantized model uses fewer bits per weight, so it needs less memory than the full-precision version. But the file size is not the whole footprint: the runtime, KV cache, context window, and your other applications also need memory.&lt;/p&gt;
&lt;h3 id="test-the-model-on-your-task_1"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;Check the model card and the quantization format. Test with the context length you actually use. A model that fits at a short prompt may fail at a long one.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;The same model can fit at one context size and fail at another; KV cache grows with context and concurrency. Leave headroom for the OS and other services. Do not assume a model that fits in RAM will be fast. CPU inference can be usable for small models; larger models may need a GPU and enough VRAM. The same model can fit at one context size and fail at another; KV cache grows with context and concurrency. Leave headroom for the OS and other services. Measure before you buy hardware.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What is your real context length?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Weights, context, and overhead.&lt;/li&gt;
&lt;li&gt;☐ 1 Weights&lt;/li&gt;
&lt;li&gt;☐ 2 Quantization&lt;/li&gt;
&lt;li&gt;☐ 3 Context&lt;/li&gt;
&lt;li&gt;☐ 4 Memory + VRAM&lt;/li&gt;
&lt;li&gt;☐ 5 Test it&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Model size is not a single number.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ollama.com/library/llama3.1:70b"&gt;Ollama library — Llama 3.1 70B&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ggml-org/llama.cpp/blob/master/tools/quantize/README.md"&gt;llama.cpp quantization&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ollama.com/"&gt;Ollama documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/local-ai-what-actually-stays-local"&gt;Local AI: what actually stays local?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-would-you-use-offline-ai-for"&gt;What would you use offline AI for?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/quantization-without-the-jargon"&gt;Quantization without the jargon&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Local AI: what actually stays local?</title><link>https://it.kituwa.com/blogs/blog/local-ai-what-actually-stays-local/</link><pubDate>Fri, 02 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/local-ai-what-actually-stays-local/</guid><description>&lt;p&gt;Local AI means the model runs on hardware you control. It does not automatically mean every part of the workflow is private.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Local AI: what actually stays local?&lt;/li&gt;
&lt;li&gt;The model is one part of the path.&lt;/li&gt;
&lt;li&gt;Local&lt;/li&gt;
&lt;li&gt;Cloud&lt;/li&gt;
&lt;li&gt;Inference — Your hardware — Provider's servers&lt;/li&gt;
&lt;li&gt;Data path — Check the whole app — Prompts leave your device&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="test-the-model-on-your-task"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;The model weights and inference can stay on your machine. But the app may send prompts to a cloud API, fetch remote data, or log conversations. A browser front end may load assets from the internet. Check each component.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Local models can be useful for offline drafts, private notes, coding help, and repetitive tasks. They can also be slower or less capable than hosted models, depending on hardware and model size.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Decide what must stay local: the prompt, the document, the output, or all three. Then verify the whole path, not just the model. A local model may still download weights, fetch updates, or call a plugin; those are network paths too. A local model is a tool, not a privacy guarantee. Read the app's network behavior. A local model may still download weights, fetch updates, or call a plugin; those are network paths too.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What would you want to keep on your own machine?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ The model is one part of the path.&lt;/li&gt;
&lt;li&gt;☐ Local&lt;/li&gt;
&lt;li&gt;☐ Cloud&lt;/li&gt;
&lt;li&gt;☐ Inference — Your hardware — Provider's servers&lt;/li&gt;
&lt;li&gt;☐ Data path — Check the whole app — Prompts leave your device&lt;/li&gt;
&lt;li&gt;☐ Capability — Hardware-limited — Often larger models&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Local AI means the model runs on hardware you control.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.ollama.com/"&gt;Ollama documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ggml-org/llama.cpp"&gt;llama.cpp&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-server-is-down-what-failed"&gt;Your server is down: what failed?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/size-an-ai-model-honestly"&gt;Size an AI model honestly&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-would-you-use-offline-ai-for"&gt;What would you use offline AI for?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Your server is down: what failed?</title><link>https://it.kituwa.com/blogs/blog/your-server-is-down-what-failed/</link><pubDate>Thu, 01 Jan 2026 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/your-server-is-down-what-failed/</guid><description>&lt;p&gt;Start with the path, not the app.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Your server is down: what failed?&lt;/li&gt;
&lt;li&gt;Follow the path, not the panic.&lt;/li&gt;
&lt;li&gt;1 Power — Cable, PSU, UPS&lt;/li&gt;
&lt;li&gt;2 Network — IP, link, DNS&lt;/li&gt;
&lt;li&gt;3 Service — systemd, compose&lt;/li&gt;
&lt;li&gt;4 Logs — journal, container&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-systemctl-status"&gt;Check &lt;code&gt;systemctl status&lt;/code&gt;&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Power: is the machine on? Check the power cable, PSU, and UPS.&lt;/li&gt;
&lt;li&gt;Network: can you reach the host by IP? Is the link up? Is DNS working?&lt;/li&gt;
&lt;li&gt;Service: is the process running? &lt;code&gt;systemctl status&lt;/code&gt; and &lt;code&gt;docker compose ps&lt;/code&gt; show state.&lt;/li&gt;
&lt;li&gt;Logs: &lt;code&gt;journalctl -u &amp;lt;unit&amp;gt;&lt;/code&gt; or &lt;code&gt;docker compose logs --tail=100&lt;/code&gt; show the error.&lt;/li&gt;
&lt;li&gt;Dependencies: database, reverse proxy, storage, and certificates.&lt;/li&gt;
&lt;li&gt;Recent changes: updates, config edits, or a new deploy.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="make-recovery-practical"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;If you cannot reach the host at all, the problem may be power, link, or routing; if you can reach it but the app fails, move to service and logs. If you cannot reach the host at all, the problem may be power, link, or routing; if you can reach it but the app fails, move to service and logs. Fix one layer at a time and verify. Do not restart everything at once; you lose evidence. Document the last known good state. Test the recovery path. Keep a console path. Write down the failure path and the fix for next time. Document the last known good state. Test the recovery path. Keep a console path.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What was the last thing that changed?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Follow the path, not the panic.&lt;/li&gt;
&lt;li&gt;☐ 1 Power — Cable, PSU, UPS&lt;/li&gt;
&lt;li&gt;☐ 2 Network — IP, link, DNS&lt;/li&gt;
&lt;li&gt;☐ 3 Service — systemd, compose&lt;/li&gt;
&lt;li&gt;☐ 4 Logs — journal, container&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Start with the path, not the app.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.freedesktop.org/software/systemd/man/latest/systemctl.html"&gt;systemctl — failed units&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/journalctl.1.html"&gt;man journalctl&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.docker.com/reference/cli/docker/compose/ps/"&gt;Docker compose ps&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/choose-alerts-that-mean-something"&gt;Choose alerts that mean something&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/local-ai-what-actually-stays-local"&gt;Local AI: what actually stays local?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/size-an-ai-model-honestly"&gt;Size an AI model honestly&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Choose alerts that mean something</title><link>https://it.kituwa.com/blogs/blog/choose-alerts-that-mean-something/</link><pubDate>Wed, 31 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/choose-alerts-that-mean-something/</guid><description>&lt;p&gt;An alert should describe a symptom, a threshold, an owner, and an action.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Choose alerts that mean something&lt;/li&gt;
&lt;li&gt;Symptom, owner, runbook.&lt;/li&gt;
&lt;li&gt;Symptom — What is wrong?&lt;/li&gt;
&lt;li&gt;Threshold — When does it matter?&lt;/li&gt;
&lt;li&gt;Owner — Who responds?&lt;/li&gt;
&lt;li&gt;Channel — Where does it go?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="find-the-real-limit"&gt;Find the real limit&lt;/h3&gt;
&lt;p&gt;Symptom: what is wrong? “Checkout is failing” is better than “CPU is 71%.”
Threshold: when does it matter? A disk at 80% may be fine; at 95% it needs action.
Owner: who is expected to respond? An unowned alert becomes noise.
Channel: where does it go, and what happens after hours?
Runbook: what should the responder check first? Link to it.
Silence: when is the alert expected, and who can silence it?&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Do not page on every CPU spike; page on user-visible symptoms or conditions that will become one. Test the notification path.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Keep a short list of pages that wake someone up; everything else can be a dashboard or a ticket. Keep a short list of pages that wake someone up; everything else can be a dashboard or a ticket. Review alerts after an incident. Delete ones nobody acts on. A smaller set of meaningful alerts beats a wall of dashboards.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which alert would you delete first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Symptom, owner, runbook.&lt;/li&gt;
&lt;li&gt;☐ Symptom — What is wrong?&lt;/li&gt;
&lt;li&gt;☐ Threshold — When does it matter?&lt;/li&gt;
&lt;li&gt;☐ Owner — Who responds?&lt;/li&gt;
&lt;li&gt;☐ Channel — Where does it go?&lt;/li&gt;
&lt;li&gt;☐ Runbook — What to check first?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;An alert should describe a symptom, a threshold, an owner, and an action.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://prometheus.io/docs/practices/alerting/"&gt;Prometheus — alerting practices&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://prometheus.io/docs/alerting/latest/alertmanager/"&gt;Prometheus Alertmanager&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/monitoring-is-not-automatic-repair"&gt;Monitoring is not automatic repair&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-server-is-down-what-failed"&gt;Your server is down: what failed?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/local-ai-what-actually-stays-local"&gt;Local AI: what actually stays local?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Monitoring is not automatic repair</title><link>https://it.kituwa.com/blogs/blog/monitoring-is-not-automatic-repair/</link><pubDate>Tue, 30 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/monitoring-is-not-automatic-repair/</guid><description>&lt;p&gt;Monitoring tells you something is wrong. It does not fix it.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Monitoring is not automatic repair&lt;/li&gt;
&lt;li&gt;Detect, alert, diagnose, repair, verify.&lt;/li&gt;
&lt;li&gt;1 Detect&lt;/li&gt;
&lt;li&gt;2 Alert&lt;/li&gt;
&lt;li&gt;3 Diagnose&lt;/li&gt;
&lt;li&gt;4 Repair&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="find-the-real-limit"&gt;Find the real limit&lt;/h3&gt;
&lt;p&gt;A monitor can check a URL, a port, a disk threshold, or a heartbeat. An alert routes the signal to a human or an automation. Neither step repairs the service.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;A useful chain: detect, alert, diagnose, repair, verify. Write down who owns each step. A green dashboard with no owner is decoration.&lt;/p&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Start with a few high-signal checks: is the service reachable, is the disk filling, is the backup recent? Add more only when you will act on them.&lt;/p&gt;
&lt;h3 id="prove-the-restore"&gt;Prove the restore&lt;/h3&gt;
&lt;p&gt;A monitor with no runbook and no owner is just a notification generator. Write the first three checks for each alert. A monitor with no runbook and no owner is just a notification generator. Write the first three checks for each alert. Test the alert path: stop the service on purpose, confirm the alert arrives, then restore and confirm recovery. Do this on a schedule. Review after every incident. Review after every incident.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What would you want to know before a user tells you?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Detect, alert, diagnose, repair, verify.&lt;/li&gt;
&lt;li&gt;☐ 1 Detect&lt;/li&gt;
&lt;li&gt;☐ 2 Alert&lt;/li&gt;
&lt;li&gt;☐ 3 Diagnose&lt;/li&gt;
&lt;li&gt;☐ 4 Repair&lt;/li&gt;
&lt;li&gt;☐ 5 Verify&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Monitoring tells you something is wrong.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://prometheus.io/docs/practices/alerting/"&gt;Prometheus — alerting practices&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/louislam/uptime-kuma"&gt;Uptime Kuma&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/an-ssh-warning-you-should-not-ignore"&gt;An SSH warning you should not ignore&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/choose-alerts-that-mean-something"&gt;Choose alerts that mean something&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-server-is-down-what-failed"&gt;Your server is down: what failed?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>An SSH warning you should not ignore</title><link>https://it.kituwa.com/blogs/blog/an-ssh-warning-you-should-not-ignore/</link><pubDate>Mon, 29 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/an-ssh-warning-you-should-not-ignore/</guid><description>&lt;p&gt;The SSH warning “REMOTE HOST IDENTIFICATION HAS CHANGED” is not noise.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;An SSH warning you should not ignore&lt;/li&gt;
&lt;li&gt;Verify before you accept.&lt;/li&gt;
&lt;li&gt;MYTH — The warning is always an attack&lt;/li&gt;
&lt;li&gt;REALITY — It can be a reinstall or key rotation. Verify.&lt;/li&gt;
&lt;li&gt;MYTH — Delete known_hosts to fix it&lt;/li&gt;
&lt;li&gt;REALITY — That removes the evidence. Investigate first.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-known_hosts"&gt;Check &lt;code&gt;known_hosts&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;It means the server presented a different host key than the one stored in &lt;code&gt;known_hosts&lt;/code&gt;. That can happen after a legitimate reinstall or key rotation. It can also indicate a man-in-the-middle or a wrong host.&lt;/p&gt;
&lt;h3 id="check-known_hosts_1"&gt;Check &lt;code&gt;known_hosts&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Do not delete &lt;code&gt;known_hosts&lt;/code&gt; just to make the warning go away. Verify the new fingerprint through a separate channel: the provider's console, a signed message, or a colleague who can see the server. If the change is legitimate, remove the old entry and accept the new key.&lt;/p&gt;
&lt;h3 id="check-ssh-keygen-f-host"&gt;Check &lt;code&gt;ssh-keygen -F host&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Use &lt;code&gt;ssh-keygen -F host&lt;/code&gt; to find the stored entry, and compare fingerprints with &lt;code&gt;ssh-keygen -lf&lt;/code&gt;. Compare the fingerprint shown by the server console with the one your client reports; do not trust a fingerprint sent over the same suspicious channel. Compare the fingerprint shown by the server console with the one your client reports; do not trust a fingerprint sent over the same suspicious channel. If you cannot verify the change, stop. A wrong key can expose your credentials and session.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Have you ever checked a host fingerprint?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Exposing a service before authentication and updates are ready.&lt;/li&gt;
&lt;li&gt;Changing several network variables at once.&lt;/li&gt;
&lt;li&gt;Forgetting DNS, TTL, firewall, or rollback details.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Verify before you accept.&lt;/li&gt;
&lt;li&gt;☐ MYTH — The warning is always an attack&lt;/li&gt;
&lt;li&gt;☐ REALITY — It can be a reinstall or key rotation. Verify.&lt;/li&gt;
&lt;li&gt;☐ MYTH — Delete known_hosts to fix it&lt;/li&gt;
&lt;li&gt;☐ REALITY — That removes the evidence. Investigate first.&lt;/li&gt;
&lt;li&gt;☐ MYTH — Fingerprints are optional&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;The SSH warning “REMOTE HOST IDENTIFICATION HAS CHANGED” is not noise.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Exposing a service before authentication and updates are ready.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.openssh.com/manual.html"&gt;OpenSSH manual&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/ssh-keygen.1.html"&gt;man ssh-keygen&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/create-an-ssh-nickname"&gt;Create an SSH nickname&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/monitoring-is-not-automatic-repair"&gt;Monitoring is not automatic repair&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/choose-alerts-that-mean-something"&gt;Choose alerts that mean something&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Create an SSH nickname</title><link>https://it.kituwa.com/blogs/blog/create-an-ssh-nickname/</link><pubDate>Sun, 28 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/create-an-ssh-nickname/</guid><description>&lt;p&gt;An SSH nickname is a short name for a host, user, port, and key. It saves typing and reduces mistakes.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Create an SSH nickname&lt;/li&gt;
&lt;li&gt;Short name, explicit settings.&lt;/li&gt;
&lt;li&gt;Host kituwa&lt;/li&gt;
&lt;li&gt;HostName server.example.com&lt;/li&gt;
&lt;li&gt;User deploy&lt;/li&gt;
&lt;li&gt;Port 2222&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-sshconfig"&gt;Check &lt;code&gt;~/.ssh/config&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Put it in &lt;code&gt;~/.ssh/config&lt;/code&gt;:&lt;/p&gt;
&lt;h3 id="check-sshconfig_1"&gt;Check `sshconfig&lt;/h3&gt;
&lt;p&gt;Host kituwa
HostName server.example.com
User deploy
Port 2222
IdentityFile ~/.ssh/id_ed25519`&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-sshconfig"&gt;Host kituwa
HostName server.example.com
User deploy
Port 2222
IdentityFile ~/.ssh/id_ed25519
&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id="check-ssh-kituwa"&gt;Check &lt;code&gt;ssh kituwa&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Then &lt;code&gt;ssh kituwa&lt;/code&gt; uses those settings. &lt;code&gt;HostName&lt;/code&gt; is the real address; &lt;code&gt;User&lt;/code&gt; is the remote account; &lt;code&gt;Port&lt;/code&gt; must match the server; &lt;code&gt;IdentityFile&lt;/code&gt; points to the private key.&lt;/p&gt;
&lt;h3 id="check-chmod-600"&gt;Check &lt;code&gt;chmod 600&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Use placeholders, not real hostnames or keys, in examples you share. Keep the file readable only by you (&lt;code&gt;chmod 600&lt;/code&gt;), and do not put passwords in it.&lt;/p&gt;
&lt;h3 id="check-host"&gt;Check &lt;code&gt;Host *&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;The same file can hold multiple Host blocks; &lt;code&gt;Host *&lt;/code&gt; applies defaults to every connection. Order matters: the first matching value wins for many options. Keep comments to explain why a host exists. Do not commit the config if it contains real addresses or key paths. A nickname is documentation as well as convenience. The same file can hold multiple Host blocks; &lt;code&gt;Host *&lt;/code&gt; applies defaults to every connection. Order matters: the first matching value wins for many options. Keep comments to explain why a host exists. Do not commit the config if it contains real addresses or key paths. A nickname is documentation as well as convenience. Test with &lt;code&gt;ssh -v kituwa&lt;/code&gt; if it fails; verbose output shows which config and key were used. Test it from a second terminal.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which host would you nickname first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Exposing a service before authentication and updates are ready.&lt;/li&gt;
&lt;li&gt;Changing several network variables at once.&lt;/li&gt;
&lt;li&gt;Forgetting DNS, TTL, firewall, or rollback details.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Short name, explicit settings.&lt;/li&gt;
&lt;li&gt;☐ Host kituwa&lt;/li&gt;
&lt;li&gt;☐ HostName server.example.com&lt;/li&gt;
&lt;li&gt;☐ User deploy&lt;/li&gt;
&lt;li&gt;☐ Port 2222&lt;/li&gt;
&lt;li&gt;☐ IdentityFile ~/.ssh/id_ed25519&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;An SSH nickname is a short name for a host, user, port, and key.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Exposing a service before authentication and updates are ready.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man5/ssh_config.5.html"&gt;man ssh_config&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/service-openssh"&gt;Ubuntu — OpenSSH&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/ssh-keys-in-plain-english"&gt;SSH keys in plain English&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/an-ssh-warning-you-should-not-ignore"&gt;An SSH warning you should not ignore&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/monitoring-is-not-automatic-repair"&gt;Monitoring is not automatic repair&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>SSH keys in plain English</title><link>https://it.kituwa.com/blogs/blog/ssh-keys-in-plain-english/</link><pubDate>Sat, 27 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/ssh-keys-in-plain-english/</guid><description>&lt;p&gt;SSH keys are a pair: a private key that stays on your device and a public key that you place on the server. The server challenges you; your private key proves you hold the matching secret.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;SSH keys in plain English&lt;/li&gt;
&lt;li&gt;A pair, a passphrase, a policy.&lt;/li&gt;
&lt;li&gt;Key pair — Private + public&lt;/li&gt;
&lt;li&gt;Server — authorized_keys&lt;/li&gt;
&lt;li&gt;Fingerprint — Compare, don't paste&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-ssh-keygen-t-ed25519-a-100"&gt;Check &lt;code&gt;ssh-keygen -t ed25519 -a 100&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Use &lt;code&gt;ssh-keygen -t ed25519 -a 100&lt;/code&gt; for a modern key with a strong passphrase, or check your organization's approved algorithms. Generate a modern key, protect it with a passphrase, and copy only the public key. Use &lt;code&gt;ssh-keygen -t ed25519 -a 100&lt;/code&gt; for a modern key with a strong passphrase; check your organization's approved algorithms. Keep an offline backup of the private key if losing it would lock you out. Keep an offline backup of the private key if losing it would lock you out. Do not paste the private key into a chat, ticket, or website. A key without a passphrase is convenient and riskier.&lt;/p&gt;
&lt;h3 id="check-authorized_keys"&gt;Check &lt;code&gt;authorized_keys&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;On the server, &lt;code&gt;authorized_keys&lt;/code&gt; lists the public keys allowed to log in. Remove keys you no longer use. Fingerprints help you compare keys without copying the whole key.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Keys are not a complete access policy: use a non-root account, a firewall, and updates. Test a new key before disabling password login.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which key would you revoke first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Exposing a service before authentication and updates are ready.&lt;/li&gt;
&lt;li&gt;Changing several network variables at once.&lt;/li&gt;
&lt;li&gt;Forgetting DNS, TTL, firewall, or rollback details.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ A pair, a passphrase, a policy.&lt;/li&gt;
&lt;li&gt;☐ Key pair — Private + public&lt;/li&gt;
&lt;li&gt;☐ Server — authorized_keys&lt;/li&gt;
&lt;li&gt;☐ Fingerprint — Compare, don't paste&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;SSH keys are a pair: a private key that stays on your device and a public key that you place on the server.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Exposing a service before authentication and updates are ready.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/ssh-keygen.1.html"&gt;man ssh-keygen&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/service-openssh"&gt;Ubuntu — OpenSSH&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/port-forwarding-or-private-access"&gt;Port forwarding or private access?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/create-an-ssh-nickname"&gt;Create an SSH nickname&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/an-ssh-warning-you-should-not-ignore"&gt;An SSH warning you should not ignore&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Port forwarding or private access?</title><link>https://it.kituwa.com/blogs/blog/port-forwarding-or-private-access/</link><pubDate>Fri, 26 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/port-forwarding-or-private-access/</guid><description>&lt;p&gt;Opening a port is not the only way to reach a service.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Port forwarding or private access?&lt;/li&gt;
&lt;li&gt;Reduce the exposed surface.&lt;/li&gt;
&lt;li&gt;Port forwarding&lt;/li&gt;
&lt;li&gt;Private access&lt;/li&gt;
&lt;li&gt;Exposure — Public internet — Private path first&lt;/li&gt;
&lt;li&gt;Auth — Your service + TLS — VPN/SSH + service&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Port forwarding exposes a service to the internet through your router. It can work, but you are responsible for authentication, TLS, updates, and monitoring. Every exposed service is a target.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;A private access path keeps the service off the public internet: a VPN, a mesh overlay, or an SSH tunnel. You authenticate to the private network first, then reach the service. It adds a dependency, but it reduces the exposed surface.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Choose based on who needs access and from where. A single trusted user may be fine with a VPN; a public website needs a different design. Do not expose an admin panel just because it is convenient.&lt;/p&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;A public site may need a reverse proxy, WAF, and monitoring; a private service may be simpler but still needs patching. Test from outside your network, and keep a recovery path if the tunnel fails. Document the ports and who approved them. A public site may need a reverse proxy, WAF, and monitoring; a private service may be simpler but still needs patching.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which path fits your actual users?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Reduce the exposed surface.&lt;/li&gt;
&lt;li&gt;☐ Port forwarding&lt;/li&gt;
&lt;li&gt;☐ Private access&lt;/li&gt;
&lt;li&gt;☐ Exposure — Public internet — Private path first&lt;/li&gt;
&lt;li&gt;☐ Auth — Your service + TLS — VPN/SSH + service&lt;/li&gt;
&lt;li&gt;☐ Failure — Public outage — Tunnel dependency&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Opening a port is not the only way to reach a service.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.wireguard.com/"&gt;WireGuard&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.openssh.com/manual.html"&gt;OpenSSH manual&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/security-firewall"&gt;Ubuntu — firewall&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/remote-access-planning-checklist"&gt;Remote access planning checklist&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/ssh-keys-in-plain-english"&gt;SSH keys in plain English&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/create-an-ssh-nickname"&gt;Create an SSH nickname&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Remote access planning checklist</title><link>https://it.kituwa.com/blogs/blog/remote-access-planning-checklist/</link><pubDate>Thu, 25 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/remote-access-planning-checklist/</guid><description>&lt;p&gt;Remote access is a door. Plan who can open it, how, and what happens if the key is lost.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Remote access planning checklist&lt;/li&gt;
&lt;li&gt;Six questions before opening a door.&lt;/li&gt;
&lt;li&gt;Authentication — Keys, MFA, revocation&lt;/li&gt;
&lt;li&gt;Network path — VPN or exposed port?&lt;/li&gt;
&lt;li&gt;Firewall — Sources + ports&lt;/li&gt;
&lt;li&gt;Updates — Who patches what?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Six questions:&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Authentication: passwords alone? Keys? MFA? Who can revoke access?&lt;/li&gt;
&lt;li&gt;Network path: VPN, tunnel, or direct port forward? What is exposed?&lt;/li&gt;
&lt;li&gt;Firewall: which source addresses and ports are allowed?&lt;/li&gt;
&lt;li&gt;Updates: who patches the gateway and the service, and how often?&lt;/li&gt;
&lt;li&gt;Logging: what is recorded, where, and for how long?&lt;/li&gt;
&lt;li&gt;Recovery: how do you regain access after a lost key, expired certificate, or broken gateway?&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;Write down the allowed source, the port, the account, and the rollback step for each rule. Review access when a device or person leaves. Remove what you no longer need. Prefer a private path over exposing a service directly. Test from outside your network, then test recovery. Keep an offline copy of the recovery steps.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What is your recovery plan if the gateway dies?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Exposing a service before authentication and updates are ready.&lt;/li&gt;
&lt;li&gt;Changing several network variables at once.&lt;/li&gt;
&lt;li&gt;Forgetting DNS, TTL, firewall, or rollback details.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Six questions before opening a door.&lt;/li&gt;
&lt;li&gt;☐ Authentication — Keys, MFA, revocation&lt;/li&gt;
&lt;li&gt;☐ Network path — VPN or exposed port?&lt;/li&gt;
&lt;li&gt;☐ Firewall — Sources + ports&lt;/li&gt;
&lt;li&gt;☐ Updates — Who patches what?&lt;/li&gt;
&lt;li&gt;☐ Logging — What is recorded?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Remote access is a door.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Exposing a service before authentication and updates are ready.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.openssh.com/manual.html"&gt;OpenSSH manual&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/security-firewall"&gt;Ubuntu — firewall&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.wireguard.com/"&gt;WireGuard&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/vpns-private-path-not-invisibility"&gt;VPNs: private path, not invisibility&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/port-forwarding-or-private-access"&gt;Port forwarding or private access?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/ssh-keys-in-plain-english"&gt;SSH keys in plain English&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>VPNs: private path, not invisibility</title><link>https://it.kituwa.com/blogs/blog/vpns-private-path-not-invisibility/</link><pubDate>Wed, 24 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/vpns-private-path-not-invisibility/</guid><description>&lt;p&gt;A VPN creates a private path between your device and a VPN endpoint. It is not invisibility.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;VPNs: private path, not invisibility&lt;/li&gt;
&lt;li&gt;What a tunnel does and does not do.&lt;/li&gt;
&lt;li&gt;MYTH — A VPN makes you anonymous&lt;/li&gt;
&lt;li&gt;REALITY — Providers, accounts and fingerprints can still identify you.&lt;/li&gt;
&lt;li&gt;MYTH — A VPN secures everything&lt;/li&gt;
&lt;li&gt;REALITY — It protects the tunnel, not malware or phishing.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Myth: a VPN makes you anonymous. Reality: the VPN provider, your account, your browser fingerprint, and the sites you log into can still identify you. A VPN moves trust; it does not erase it.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Myth: a VPN secures everything. Reality: it protects traffic in the tunnel. Malware, phishing, a compromised device, and accounts you are logged into remain risks.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Myth: a VPN makes public Wi-Fi safe. Reality: it reduces local network exposure, but you still need HTTPS, updates, and caution.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Use a VPN for a specific job: remote access to your own network, a trusted path on an untrusted network, or routing traffic through a location you control. Read the provider's logging and security model. A VPN also adds a dependency: if the endpoint is down, your path is down. Keep a fallback for critical access.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What job do you need the VPN to do?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Reusing credentials or recovery material across accounts.&lt;/li&gt;
&lt;li&gt;Storing recovery codes only on the device they protect.&lt;/li&gt;
&lt;li&gt;Skipping MFA or independent verification because it is inconvenient.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ What a tunnel does and does not do.&lt;/li&gt;
&lt;li&gt;☐ MYTH — A VPN makes you anonymous&lt;/li&gt;
&lt;li&gt;☐ REALITY — Providers, accounts and fingerprints can still identify you.&lt;/li&gt;
&lt;li&gt;☐ MYTH — A VPN secures everything&lt;/li&gt;
&lt;li&gt;☐ REALITY — It protects the tunnel, not malware or phishing.&lt;/li&gt;
&lt;li&gt;☐ MYTH — A VPN makes public Wi-Fi safe&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A VPN creates a private path between your device and a VPN endpoint.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Reusing credentials or recovery material across accounts.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.wireguard.com/"&gt;WireGuard&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.openssh.com/manual.html"&gt;OpenSSH manual&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/the-guest-wi-fi-question"&gt;The guest Wi-Fi question&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/remote-access-planning-checklist"&gt;Remote access planning checklist&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/port-forwarding-or-private-access"&gt;Port forwarding or private access?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>The guest Wi-Fi question</title><link>https://it.kituwa.com/blogs/blog/the-guest-wi-fi-question/</link><pubDate>Tue, 23 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/the-guest-wi-fi-question/</guid><description>&lt;p&gt;Guest Wi-Fi is a convenience with boundaries.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The guest Wi-Fi question&lt;/li&gt;
&lt;li&gt;Convenience needs boundaries.&lt;/li&gt;
&lt;li&gt;Guest SSID — Separate name&lt;/li&gt;
&lt;li&gt;Isolation — No LAN access&lt;/li&gt;
&lt;li&gt;Time limit — Access window&lt;/li&gt;
&lt;li&gt;Main network — Keep it separate&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;A separate guest SSID can keep visitors off your main network, but only if the router actually isolates guest clients. Check whether guest devices can reach your NAS, printers, or admin page. If they can, it is a different network name, not isolation.&lt;/p&gt;
&lt;h3 id="check-the-network-path_1"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;Decide: how long should access last, who gets the password, and what bandwidth or content rules apply? Do not reuse the main Wi-Fi password for guests.&lt;/p&gt;
&lt;h3 id="check-the-network-path_2"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;A guest network is not a substitute for securing the devices that matter. Patch them and keep the admin interface off the guest network.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What would you want a guest network to block?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Exposing a service before authentication and updates are ready.&lt;/li&gt;
&lt;li&gt;Changing several network variables at once.&lt;/li&gt;
&lt;li&gt;Forgetting DNS, TTL, firewall, or rollback details.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Convenience needs boundaries.&lt;/li&gt;
&lt;li&gt;☐ Guest SSID — Separate name&lt;/li&gt;
&lt;li&gt;☐ Isolation — No LAN access&lt;/li&gt;
&lt;li&gt;☐ Time limit — Access window&lt;/li&gt;
&lt;li&gt;☐ Main network — Keep it separate&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Guest Wi-Fi is a convenience with boundaries.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Exposing a service before authentication and updates are ready.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://openwrt.org/docs/guide-user/network/wifi/guestwifi/guest-wlan"&gt;OpenWrt — guest Wi-Fi&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc1918"&gt;RFC 1918 — private addresses&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/document-your-home-network"&gt;Document your home network&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/vpns-private-path-not-invisibility"&gt;VPNs: private path, not invisibility&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/remote-access-planning-checklist"&gt;Remote access planning checklist&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Document your home network</title><link>https://it.kituwa.com/blogs/blog/document-your-home-network/</link><pubDate>Mon, 22 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/document-your-home-network/</guid><description>&lt;p&gt;A home network you cannot describe is hard to troubleshoot.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Document your home network&lt;/li&gt;
&lt;li&gt;Write it down before it breaks.&lt;/li&gt;
&lt;li&gt;1 Diagram&lt;/li&gt;
&lt;li&gt;2 Addresses&lt;/li&gt;
&lt;li&gt;3 Devices&lt;/li&gt;
&lt;li&gt;4 Owners&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Write down: a simple diagram, the router and access point addresses, DHCP range, DNS settings, device names and locations, and which services run where. Add the maintenance owner and where the backup of the configuration lives.&lt;/p&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;Do not put passwords, Wi-Fi keys, or recovery codes in the diagram. Store credentials separately in a password manager. A diagram is not a secret store.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;A simple text file or diagram is enough; the goal is shared understanding, not a perfect CMDB. Include the date and a change note so stale details are obvious. Keep the document somewhere you can find it when the network is down, including a printed copy if that helps. Review it after any router or device change. Update it when you add a device or change a setting.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What would you need to know if the router failed tonight?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Exposing a service before authentication and updates are ready.&lt;/li&gt;
&lt;li&gt;Changing several network variables at once.&lt;/li&gt;
&lt;li&gt;Forgetting DNS, TTL, firewall, or rollback details.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Write it down before it breaks.&lt;/li&gt;
&lt;li&gt;☐ 1 Diagram&lt;/li&gt;
&lt;li&gt;☐ 2 Addresses&lt;/li&gt;
&lt;li&gt;☐ 3 Devices&lt;/li&gt;
&lt;li&gt;☐ 4 Owners&lt;/li&gt;
&lt;li&gt;☐ 5 Backup&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A home network you cannot describe is hard to troubleshoot.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Exposing a service before authentication and updates are ready.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man8/ip.8.html"&gt;man ip&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://networkmanager.dev/docs/api/latest/nmcli.html"&gt;NetworkManager nmcli&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/dns-vs-dhcp-vs-ip-address"&gt;DNS vs DHCP vs IP address&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/the-guest-wi-fi-question"&gt;The guest Wi-Fi question&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/vpns-private-path-not-invisibility"&gt;VPNs: private path, not invisibility&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>DNS vs DHCP vs IP address</title><link>https://it.kituwa.com/blogs/blog/dns-vs-dhcp-vs-ip-address/</link><pubDate>Sun, 21 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/dns-vs-dhcp-vs-ip-address/</guid><description>&lt;p&gt;DNS, DHCP, and IP addresses are three different jobs.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;DNS vs DHCP vs IP address&lt;/li&gt;
&lt;li&gt;Three jobs, easy to mix up.&lt;/li&gt;
&lt;li&gt;IP address — Identity on the network&lt;/li&gt;
&lt;li&gt;DHCP — Hands out settings&lt;/li&gt;
&lt;li&gt;DNS — Names to addresses&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;An IP address identifies a device on a network. It can be static or leased. A private address is not directly reachable from the public internet without a translation or tunnel.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;DHCP hands out addresses and often other settings, such as the default gateway and DNS servers. It reduces manual configuration, but a bad DHCP setting can affect every device that uses it.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;DNS translates names into addresses. If DNS fails, a site may be reachable by IP but not by name. DNS is not the same as DHCP, and neither is the same as the address itself.&lt;/p&gt;
&lt;h3 id="check-ip-addr"&gt;Check &lt;code&gt;ip addr&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Use &lt;code&gt;ip addr&lt;/code&gt;, &lt;code&gt;ip route&lt;/code&gt;, and a DNS lookup as read-only checks; they show the address, gateway, and name resolution path. When troubleshooting, ask: does the device have an address, did it get the right settings, and can it resolve a name?&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which of the three would you check first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Exposing a service before authentication and updates are ready.&lt;/li&gt;
&lt;li&gt;Changing several network variables at once.&lt;/li&gt;
&lt;li&gt;Forgetting DNS, TTL, firewall, or rollback details.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Three jobs, easy to mix up.&lt;/li&gt;
&lt;li&gt;☐ IP address — Identity on the network&lt;/li&gt;
&lt;li&gt;☐ DHCP — Hands out settings&lt;/li&gt;
&lt;li&gt;☐ DNS — Names to addresses&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;DNS, DHCP, and IP addresses are three different jobs.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Exposing a service before authentication and updates are ready.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc1918"&gt;RFC 1918 — private addresses&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc2131"&gt;RFC 2131 — DHCP&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc1034"&gt;RFC 1034 — DNS&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/mesh-or-ethernet-backed-access-points"&gt;Mesh or Ethernet-backed access points?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/document-your-home-network"&gt;Document your home network&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/the-guest-wi-fi-question"&gt;The guest Wi-Fi question&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Mesh or Ethernet-backed access points?</title><link>https://it.kituwa.com/blogs/blog/mesh-or-ethernet-backed-access-points/</link><pubDate>Sat, 20 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/mesh-or-ethernet-backed-access-points/</guid><description>&lt;p&gt;Mesh Wi-Fi and Ethernet-backed access points both add coverage, but they trade off differently.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Mesh or Ethernet-backed access points?&lt;/li&gt;
&lt;li&gt;Coverage vs reliability.&lt;/li&gt;
&lt;li&gt;Mesh&lt;/li&gt;
&lt;li&gt;Ethernet APs&lt;/li&gt;
&lt;li&gt;Backhaul — Often wireless — Wired uplink&lt;/li&gt;
&lt;li&gt;Placement — Flexible — Needs cable&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;A mesh system is easy to place and often uses a wireless backhaul. It can be the practical choice when running cable is impossible, but each hop can add latency and reduce throughput.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Ethernet-backed access points use a wired uplink. They are usually more predictable and easier to troubleshoot, but they require cable and a switch.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Check: can you run one cable? How many rooms need coverage? What happens when one node fails? Do you need VLANs or guest isolation?&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which constraint matters more: cable or coverage?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Coverage vs reliability.&lt;/li&gt;
&lt;li&gt;☐ Mesh&lt;/li&gt;
&lt;li&gt;☐ Ethernet APs&lt;/li&gt;
&lt;li&gt;☐ Backhaul — Often wireless — Wired uplink&lt;/li&gt;
&lt;li&gt;☐ Placement — Flexible — Needs cable&lt;/li&gt;
&lt;li&gt;☐ Predictability — Varies by hop — Usually steadier&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Mesh Wi-Fi and Ethernet-backed access points both add coverage, but they trade off differently.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://openwrt.org/docs/guide-user/network/wifi/mesh/80211s"&gt;OpenWrt — 802.11s mesh&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://networkmanager.dev/docs/api/latest/nmcli.html"&gt;NetworkManager nmcli&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/wi-fi-slow-run-these-checks-first"&gt;Wi-Fi slow: run these checks first&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/dns-vs-dhcp-vs-ip-address"&gt;DNS vs DHCP vs IP address&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/document-your-home-network"&gt;Document your home network&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Wi-Fi slow: run these checks first</title><link>https://it.kituwa.com/blogs/blog/wi-fi-slow-run-these-checks-first/</link><pubDate>Fri, 19 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/wi-fi-slow-run-these-checks-first/</guid><description>&lt;p&gt;Wi-Fi slow? Check the simple things before buying new hardware.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Wi-Fi slow: run these checks first&lt;/li&gt;
&lt;li&gt;Measure before replacing hardware.&lt;/li&gt;
&lt;li&gt;1 Signal&lt;/li&gt;
&lt;li&gt;2 Channel&lt;/li&gt;
&lt;li&gt;3 Interference&lt;/li&gt;
&lt;li&gt;4 Device&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Signal: move closer and test again. Walls, floors, and metal matter.&lt;/li&gt;
&lt;li&gt;Channel: a crowded channel can be slower. Use your router's channel scan or a Wi-Fi analyzer.&lt;/li&gt;
&lt;li&gt;Interference: microwaves, cordless phones, and dense neighbors can affect 2.4 GHz.&lt;/li&gt;
&lt;li&gt;Device: test a second device. If only one is slow, the problem may be the device.&lt;/li&gt;
&lt;li&gt;Router and internet: test a wired connection and check the router's CPU/uptime. A reboot is a diagnostic, not a fix.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="check-nmcli"&gt;Check &lt;code&gt;nmcli&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Test at the same spot and time of day; Wi-Fi performance changes with neighbors and load. Record the result before and after each change. If only the internet is slow, the local Wi-Fi may be fine. On Linux, &lt;code&gt;nmcli&lt;/code&gt; can show connection details, and &lt;code&gt;iw&lt;/code&gt; can show link quality if your driver supports it. Results vary by hardware.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What changed before it got slow?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Exposing a service before authentication and updates are ready.&lt;/li&gt;
&lt;li&gt;Changing several network variables at once.&lt;/li&gt;
&lt;li&gt;Forgetting DNS, TTL, firewall, or rollback details.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Measure before replacing hardware.&lt;/li&gt;
&lt;li&gt;☐ 1 Signal&lt;/li&gt;
&lt;li&gt;☐ 2 Channel&lt;/li&gt;
&lt;li&gt;☐ 3 Interference&lt;/li&gt;
&lt;li&gt;☐ 4 Device&lt;/li&gt;
&lt;li&gt;☐ 5 Router + internet&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Wi-Fi slow?&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Exposing a service before authentication and updates are ready.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://networkmanager.dev/docs/api/latest/nmcli.html"&gt;NetworkManager nmcli&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://wireless.wiki.kernel.org/en/users/documentation/iw"&gt;Linux wireless — iw&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/home-networking-in-plain-english"&gt;Home networking in plain English&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/mesh-or-ethernet-backed-access-points"&gt;Mesh or Ethernet-backed access points?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/dns-vs-dhcp-vs-ip-address"&gt;DNS vs DHCP vs IP address&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Home networking in plain English</title><link>https://it.kituwa.com/blogs/blog/home-networking-in-plain-english/</link><pubDate>Thu, 18 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/home-networking-in-plain-english/</guid><description>&lt;p&gt;Home networking is easier when you separate six jobs.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Home networking in plain English&lt;/li&gt;
&lt;li&gt;Six pieces, one path.&lt;/li&gt;
&lt;li&gt;Router — LAN ↔ internet&lt;/li&gt;
&lt;li&gt;Switch — Wired devices&lt;/li&gt;
&lt;li&gt;Access point — Wi-Fi coverage&lt;/li&gt;
&lt;li&gt;IP address — Device identity&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;Router: moves traffic between your network and the internet. Switch: connects wired devices on the same network. Access point: provides Wi-Fi. IP address: identifies a device on the network. DHCP: hands out addresses automatically. DNS: translates names like example.com into addresses.&lt;/p&gt;
&lt;h3 id="check-the-network-path_1"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;Those jobs can live in one box or several. A router with built-in Wi-Fi, switch ports, DHCP, and DNS is common. Separating them can improve coverage or control, but it adds configuration.&lt;/p&gt;
&lt;h3 id="check-the-network-path_2"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;A simple test: can a device get an address, resolve a name, and reach a local service? Each answer narrows the layer. Document the addresses and roles; future-you will not remember which box does what. Labels on cables and devices help. When something fails, ask which job failed: address, name resolution, local link, Wi-Fi, or internet path. That question saves time.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which piece would you rather keep simple?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Exposing a service before authentication and updates are ready.&lt;/li&gt;
&lt;li&gt;Changing several network variables at once.&lt;/li&gt;
&lt;li&gt;Forgetting DNS, TTL, firewall, or rollback details.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Six pieces, one path.&lt;/li&gt;
&lt;li&gt;☐ Router — LAN ↔ internet&lt;/li&gt;
&lt;li&gt;☐ Switch — Wired devices&lt;/li&gt;
&lt;li&gt;☐ Access point — Wi-Fi coverage&lt;/li&gt;
&lt;li&gt;☐ IP address — Device identity&lt;/li&gt;
&lt;li&gt;☐ DHCP — Automatic addresses&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Home networking is easier when you separate six jobs.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Exposing a service before authentication and updates are ready.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc1918"&gt;RFC 1918 — private addresses&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc2131"&gt;RFC 2131 — DHCP&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc1034"&gt;RFC 1034 — DNS&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/passkeys-passwords-and-authenticator-codes"&gt;Passkeys, passwords, and authenticator codes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/wi-fi-slow-run-these-checks-first"&gt;Wi-Fi slow: run these checks first&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/mesh-or-ethernet-backed-access-points"&gt;Mesh or Ethernet-backed access points?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Passkeys, passwords, and authenticator codes</title><link>https://it.kituwa.com/blogs/blog/passkeys-passwords-and-authenticator-codes/</link><pubDate>Wed, 17 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/passkeys-passwords-and-authenticator-codes/</guid><description>&lt;p&gt;Passkeys, passwords, and authenticator codes are different tools, not replacements for thinking about recovery.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Passkeys, passwords, and authenticator codes&lt;/li&gt;
&lt;li&gt;Different factors, different recovery.&lt;/li&gt;
&lt;li&gt;Passkey — Device or sync provider&lt;/li&gt;
&lt;li&gt;Password manager — Unique passwords&lt;/li&gt;
&lt;li&gt;Authenticator — Time-based codes&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="make-recovery-practical"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;A passkey is a credential tied to a device or sync provider; it can resist phishing better than a password. A password manager stores unique passwords and can autofill them. An authenticator app generates time-based codes as a second factor.&lt;/p&gt;
&lt;h3 id="make-recovery-practical_1"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;All three need a recovery plan: what happens if the device is lost, the vault is unavailable, or the codes stop working? Keep recovery codes offline and test one account.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which factor would you trust with your most important account?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Reusing credentials or recovery material across accounts.&lt;/li&gt;
&lt;li&gt;Storing recovery codes only on the device they protect.&lt;/li&gt;
&lt;li&gt;Skipping MFA or independent verification because it is inconvenient.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Different factors, different recovery.&lt;/li&gt;
&lt;li&gt;☐ Passkey — Device or sync provider&lt;/li&gt;
&lt;li&gt;☐ Password manager — Unique passwords&lt;/li&gt;
&lt;li&gt;☐ Authenticator — Time-based codes&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Passkeys, passwords, and authenticator codes are different tools, not replacements for thinking about recovery.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Reusing credentials or recovery material across accounts.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://fidoalliance.org/passkeys/"&gt;FIDO Alliance — passkeys&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bitwarden.com/help/setup-two-step-login-fido/"&gt;Bitwarden — passkey two-step login&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/recovery-codes-before-a-lost-phone"&gt;Recovery codes before a lost phone&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/home-networking-in-plain-english"&gt;Home networking in plain English&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/wi-fi-slow-run-these-checks-first"&gt;Wi-Fi slow: run these checks first&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Recovery codes before a lost phone</title><link>https://it.kituwa.com/blogs/blog/recovery-codes-before-a-lost-phone/</link><pubDate>Tue, 16 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/recovery-codes-before-a-lost-phone/</guid><description>&lt;p&gt;Your phone is also your second factor. If it is lost, stolen, or wiped, can you still get into your accounts?&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Recovery codes before a lost phone&lt;/li&gt;
&lt;li&gt;Store them outside the phone.&lt;/li&gt;
&lt;li&gt;Lost phone — Second factor gone&lt;/li&gt;
&lt;li&gt;Recovery codes — Printed + private&lt;/li&gt;
&lt;li&gt;Backup copy — Separate location&lt;/li&gt;
&lt;li&gt;Tested path — One low-risk account&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="make-recovery-practical"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;Recovery codes are the fallback. Generate them before you need them, store them outside the phone, and keep them somewhere private. A printed copy in a safe place is easier to use when every screen is locked.&lt;/p&gt;
&lt;h3 id="make-recovery-practical_1"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;Test the recovery path on one low-risk account. Confirm where the code is, what it disables, and what you must do afterward. Some services rotate the code after use; save the new one.&lt;/p&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Do not store recovery codes only in the same password manager you might be locked out of. If you use a password manager, export an encrypted backup and keep it offline; do not rely on a single device for both the vault and the second factor. Do not post codes in comments or screenshots.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;When did you last check your recovery codes?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Store them outside the phone.&lt;/li&gt;
&lt;li&gt;☐ Lost phone — Second factor gone&lt;/li&gt;
&lt;li&gt;☐ Recovery codes — Printed + private&lt;/li&gt;
&lt;li&gt;☐ Backup copy — Separate location&lt;/li&gt;
&lt;li&gt;☐ Tested path — One low-risk account&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Your phone is also your second factor.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://bitwarden.com/help/two-step-recovery-code/"&gt;Bitwarden — recovery code for two-step login&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bitwarden.com/help/emergency-access/"&gt;Bitwarden — emergency access&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://fidoalliance.org/passkeys/"&gt;FIDO Alliance — passkeys&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/password-managers-hosted-vs-self-hosted"&gt;Password managers: hosted vs self-hosted&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/passkeys-passwords-and-authenticator-codes"&gt;Passkeys, passwords, and authenticator codes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/home-networking-in-plain-english"&gt;Home networking in plain English&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Password managers: hosted vs self-hosted</title><link>https://it.kituwa.com/blogs/blog/password-managers-hosted-vs-self-hosted/</link><pubDate>Mon, 15 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/password-managers-hosted-vs-self-hosted/</guid><description>&lt;p&gt;Hosted and self-hosted password managers both store secrets; they move responsibility.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Password managers: hosted vs self-hosted&lt;/li&gt;
&lt;li&gt;Both need recovery and backups.&lt;/li&gt;
&lt;li&gt;Hosted manager — Provider runs it&lt;/li&gt;
&lt;li&gt;Self-hosted — You run the server&lt;/li&gt;
&lt;li&gt;Local vault — File you control&lt;/li&gt;
&lt;li&gt;Recovery plan — Codes + restore test&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="make-recovery-practical"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;A hosted manager handles servers, sync, and recovery for you. You still need a strong master password, MFA, recovery codes, and a plan for the provider being unavailable.&lt;/p&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;A self-hosted manager gives you control over the server and data. You also own uptime, backups, updates, TLS, and access control. If the server is lost and the backup is unreadable, the vault is gone.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;A local-only vault (for example KeePassXC) keeps the file in your control, but you must sync and back it up safely.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Write down the recovery path before you need it: master password, MFA device, recovery codes, and where the backup lives. Whichever you choose: use a unique master password, store recovery codes offline, test a restore, and never post vault secrets in comments. A password manager is critical infrastructure; treat its backup like the vault itself.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which responsibility do you want?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Reusing credentials or recovery material across accounts.&lt;/li&gt;
&lt;li&gt;Storing recovery codes only on the device they protect.&lt;/li&gt;
&lt;li&gt;Skipping MFA or independent verification because it is inconvenient.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Both need recovery and backups.&lt;/li&gt;
&lt;li&gt;☐ Hosted manager — Provider runs it&lt;/li&gt;
&lt;li&gt;☐ Self-hosted — You run the server&lt;/li&gt;
&lt;li&gt;☐ Local vault — File you control&lt;/li&gt;
&lt;li&gt;☐ Recovery plan — Codes + restore test&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Hosted and self-hosted password managers both store secrets; they move responsibility.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Reusing credentials or recovery material across accounts.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://bitwarden.com/help/self-host-an-organization/"&gt;Bitwarden — self-host an organization&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bitwarden.com/help/install-on-premise-linux/"&gt;Bitwarden — install on Linux&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://keepassxc.org/docs/"&gt;KeePassXC documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/which-subscription-is-worth-keeping"&gt;Which subscription is worth keeping?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/recovery-codes-before-a-lost-phone"&gt;Recovery codes before a lost phone&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/passkeys-passwords-and-authenticator-codes"&gt;Passkeys, passwords, and authenticator codes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Which subscription is worth keeping?</title><link>https://it.kituwa.com/blogs/blog/which-subscription-is-worth-keeping/</link><pubDate>Sun, 14 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/which-subscription-is-worth-keeping/</guid><description>&lt;p&gt;Audit one subscription at a time.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Which subscription is worth keeping?&lt;/li&gt;
&lt;li&gt;Compare cost, control, and exit.&lt;/li&gt;
&lt;li&gt;Subscription&lt;/li&gt;
&lt;li&gt;Self-hosted&lt;/li&gt;
&lt;li&gt;Cost — Recurring fee — Time + hardware&lt;/li&gt;
&lt;li&gt;Control — Provider's terms — Your server, your rules&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Ask: what job does it do, what would replacing it cost in time, and what happens if the provider changes terms or disappears? A self-hosted alternative can reduce recurring cost and increase control, but it adds updates, backups, and responsibility.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Keep a subscription when it saves more time than it costs and the exit path is clear. Replace it when the job is simple, the data is portable, and you will actually maintain the alternative.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Do not self-host just to avoid a small bill; self-hosting is not free.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which subscription are you unsure about?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Compare cost, control, and exit.&lt;/li&gt;
&lt;li&gt;☐ Subscription&lt;/li&gt;
&lt;li&gt;☐ Self-hosted&lt;/li&gt;
&lt;li&gt;☐ Cost — Recurring fee — Time + hardware&lt;/li&gt;
&lt;li&gt;☐ Control — Provider's terms — Your server, your rules&lt;/li&gt;
&lt;li&gt;☐ Maintenance — Mostly theirs — Yours&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Audit one subscription at a time.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.nextcloud.com/server/latest/admin_manual/"&gt;Nextcloud admin manual&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://immich.app/docs/overview/introduction"&gt;Immich documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/paperless-document-intake"&gt;Paperless document intake&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/password-managers-hosted-vs-self-hosted"&gt;Password managers: hosted vs self-hosted&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/recovery-codes-before-a-lost-phone"&gt;Recovery codes before a lost phone&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Paperless document intake</title><link>https://it.kituwa.com/blogs/blog/paperless-document-intake/</link><pubDate>Sat, 13 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/paperless-document-intake/</guid><description>&lt;p&gt;Paperless-ngx turns scanned documents into a searchable archive. The intake workflow matters as much as the software.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Paperless document intake&lt;/li&gt;
&lt;li&gt;Scan, find, restore.&lt;/li&gt;
&lt;li&gt;1 Scan — PDF + original&lt;/li&gt;
&lt;li&gt;2 OCR — Text, not truth&lt;/li&gt;
&lt;li&gt;3 Tags + review — Human checkpoint&lt;/li&gt;
&lt;li&gt;4 Archive + backup — DB + files&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;A safe sequence: scan to PDF, let OCR extract text, add correspondents/tags/document types, set a retention rule, and back up the database plus the original files. Keep the original PDF alongside the OCR text; the searchable layer is a convenience, not the record. Test a restore of both the database and one original file. Check one document end to end: can you find it by a word in the text, open the original, and restore it from backup?&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Decide what not to scan: passwords, recovery codes, and documents you are legally required to keep in a specific format. Encrypt backups and restrict access.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Start with a small box of documents. Do not feed the whole filing cabinet in until the workflow is boring and repeatable.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What is the first document you would test?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Scan, find, restore.&lt;/li&gt;
&lt;li&gt;☐ 1 Scan — PDF + original&lt;/li&gt;
&lt;li&gt;☐ 2 OCR — Text, not truth&lt;/li&gt;
&lt;li&gt;☐ 3 Tags + review — Human checkpoint&lt;/li&gt;
&lt;li&gt;☐ 4 Archive + backup — DB + files&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Paperless-ngx turns scanned documents into a searchable archive.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/paperless-ngx/paperless-ngx"&gt;Paperless-ngx project&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/immich-photo-organization-with-responsibilities"&gt;Immich: photo organization with responsibilities&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/which-subscription-is-worth-keeping"&gt;Which subscription is worth keeping?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/password-managers-hosted-vs-self-hosted"&gt;Password managers: hosted vs self-hosted&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Immich: photo organization with responsibilities</title><link>https://it.kituwa.com/blogs/blog/immich-photo-organization-with-responsibilities/</link><pubDate>Fri, 12 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/immich-photo-organization-with-responsibilities/</guid><description>&lt;p&gt;Immich is a self-hosted photo and video library with mobile apps, albums, faces, and search. It is a serious project, not a drop-in replacement you can forget.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Immich: photo organization with responsibilities&lt;/li&gt;
&lt;li&gt;Import small, verify, then scale.&lt;/li&gt;
&lt;li&gt;Library — Originals + timeline&lt;/li&gt;
&lt;li&gt;Faces + search — CPU/GPU + memory&lt;/li&gt;
&lt;li&gt;Backups — DB + originals + restore&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Responsibilities: storage grows; backups must cover the database and the original files; upgrades need reading the release notes; face recognition and search use CPU/GPU and memory; mobile backup settings decide what leaves the phone.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Plan before importing: where will originals live, how much space is available, what is backed up, and how do you restore? Storage, compute, and backup capacity should be sized before the first full import, not after. Test with a small library first. A restore test should include the database, not just a photo file. Document the restore steps. Do not delete the source library until the new one is verified.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_2"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Immich can organize your photos; it cannot take responsibility for your backup plan.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What would you verify before importing everything?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/li&gt;
&lt;li&gt;Never testing a restore of a real file.&lt;/li&gt;
&lt;li&gt;Keeping the only copy on the same device or in the same location.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Import small, verify, then scale.&lt;/li&gt;
&lt;li&gt;☐ Library — Originals + timeline&lt;/li&gt;
&lt;li&gt;☐ Faces + search — CPU/GPU + memory&lt;/li&gt;
&lt;li&gt;☐ Backups — DB + originals + restore&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Immich is a self-hosted photo and video library with mobile apps, albums, faces, and search.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://immich.app/docs/overview/introduction"&gt;Immich documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-photos-deserve-an-exit-plan"&gt;Your photos deserve an exit plan&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/paperless-document-intake"&gt;Paperless document intake&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/which-subscription-is-worth-keeping"&gt;Which subscription is worth keeping?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Your photos deserve an exit plan</title><link>https://it.kituwa.com/blogs/blog/your-photos-deserve-an-exit-plan/</link><pubDate>Thu, 11 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/your-photos-deserve-an-exit-plan/</guid><description>&lt;p&gt;Cloud photo services are convenient, but convenience is not an exit plan.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Your photos deserve an exit plan&lt;/li&gt;
&lt;li&gt;Originals, metadata, restore.&lt;/li&gt;
&lt;li&gt;Local NAS — Your hardware&lt;/li&gt;
&lt;li&gt;Cloud export — Download + verify&lt;/li&gt;
&lt;li&gt;External drive — Separate copy&lt;/li&gt;
&lt;li&gt;Verified archive — Tested restore&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Decide where the originals live, how you export them, and how you verify the export. A local NAS, an external drive, a cloud export, or a self-hosted library can all be part of the plan. The important part is that you can leave without losing metadata, albums, and originals.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Test one export: download a small album, open the files, check dates and sizes, and confirm the originals are included. Do not rely on a sync folder as your only copy.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Where would your photos go if the service disappeared tomorrow?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/li&gt;
&lt;li&gt;Never testing a restore of a real file.&lt;/li&gt;
&lt;li&gt;Keeping the only copy on the same device or in the same location.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Originals, metadata, restore.&lt;/li&gt;
&lt;li&gt;☐ Local NAS — Your hardware&lt;/li&gt;
&lt;li&gt;☐ Cloud export — Download + verify&lt;/li&gt;
&lt;li&gt;☐ External drive — Separate copy&lt;/li&gt;
&lt;li&gt;☐ Verified archive — Tested restore&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Cloud photo services are convenient, but convenience is not an exit plan.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://takeout.google.com/"&gt;Google Takeout&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://immich.app/docs/overview/introduction"&gt;Immich documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/phone-photo-backup-verify-the-journey"&gt;Phone photo backup: verify the journey&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/immich-photo-organization-with-responsibilities"&gt;Immich: photo organization with responsibilities&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/paperless-document-intake"&gt;Paperless document intake&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Phone photo backup: verify the journey</title><link>https://it.kituwa.com/blogs/blog/phone-photo-backup-verify-the-journey/</link><pubDate>Wed, 10 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/phone-photo-backup-verify-the-journey/</guid><description>&lt;p&gt;Phone photo backup is a journey, not a single setting.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Phone photo backup: verify the journey&lt;/li&gt;
&lt;li&gt;Test one photo end to end.&lt;/li&gt;
&lt;li&gt;1 Phone albums — Permissions + selection&lt;/li&gt;
&lt;li&gt;2 Transfer — Wi-Fi, charging, retries&lt;/li&gt;
&lt;li&gt;3 Server storage — Originals + space&lt;/li&gt;
&lt;li&gt;4 Verify — Open from another device&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Start with the phone: which albums are included, and what happens when you delete a photo locally? Then the transfer: Wi-Fi only, charging only, or both? Next, the server: where do the files land, and how much space do they use? Finally, the verification: can you open a recent photo from another device, and does the backup include the original file?&lt;/p&gt;
&lt;h3 id="plan-for-growth"&gt;Plan for growth&lt;/h3&gt;
&lt;p&gt;Test with one photo. Note the filename, date, and size. Back it up, then find it on the server and open it. Delete nothing during the test.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;If the app has a “free up space” feature, read exactly what it deletes and where the original is verified before enabling it. Check the failure cases: phone offline, server offline, storage full, and a photo with a duplicate name. A backup that silently stops is worse than no backup because you stop worrying.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Can you find yesterday's photo on the server?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/li&gt;
&lt;li&gt;Never testing a restore of a real file.&lt;/li&gt;
&lt;li&gt;Keeping the only copy on the same device or in the same location.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Test one photo end to end.&lt;/li&gt;
&lt;li&gt;☐ 1 Phone albums — Permissions + selection&lt;/li&gt;
&lt;li&gt;☐ 2 Transfer — Wi-Fi, charging, retries&lt;/li&gt;
&lt;li&gt;☐ 3 Server storage — Originals + space&lt;/li&gt;
&lt;li&gt;☐ 4 Verify — Open from another device&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Phone photo backup is a journey, not a single setting.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://immich.app/docs/overview/introduction"&gt;Immich documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.syncthing.net/"&gt;Syncthing documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/nextcloud-syncthing-or-a-file-server"&gt;Nextcloud, Syncthing, or a file server?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-photos-deserve-an-exit-plan"&gt;Your photos deserve an exit plan&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/immich-photo-organization-with-responsibilities"&gt;Immich: photo organization with responsibilities&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Nextcloud, Syncthing, or a file server?</title><link>https://it.kituwa.com/blogs/blog/nextcloud-syncthing-or-a-file-server/</link><pubDate>Tue, 09 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/nextcloud-syncthing-or-a-file-server/</guid><description>&lt;p&gt;Three tools, three different jobs.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Nextcloud, Syncthing, or a file server?&lt;/li&gt;
&lt;li&gt;Choose by the job, not the logo.&lt;/li&gt;
&lt;li&gt;Nextcloud — Accounts, sync, sharing&lt;/li&gt;
&lt;li&gt;Syncthing — Peer-to-peer sync&lt;/li&gt;
&lt;li&gt;File server — SMB/NFS shares&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Nextcloud is a self-hosted collaboration suite: accounts, file sync, sharing, calendars, and apps. It is a good fit when several people need a shared web interface. It also brings users, permissions, updates, and backups to maintain.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;Syncthing is peer-to-peer file synchronization. Devices sync folders directly; there is no central account server by default. It is a good fit for keeping a few devices in sync, but it is not a shared drive with per-user permissions.&lt;/p&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;A plain file server (SMB/NFS) exposes folders on the network. It is simple and fast on a LAN, but it is not a collaboration portal and remote access needs care.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Choose by the job: collaboration, device sync, or shared folders. Do not expose any of them to the internet until you understand authentication, TLS, and backups. Whichever you choose, write down who owns updates and backups; overlap is fine if the responsibilities are clear.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which job do you actually need?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Choose by the job, not the logo.&lt;/li&gt;
&lt;li&gt;☐ Nextcloud — Accounts, sync, sharing&lt;/li&gt;
&lt;li&gt;☐ Syncthing — Peer-to-peer sync&lt;/li&gt;
&lt;li&gt;☐ File server — SMB/NFS shares&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Three tools, three different jobs.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.nextcloud.com/server/latest/admin_manual/"&gt;Nextcloud admin manual&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.syncthing.net/"&gt;Syncthing documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.samba.org/samba/docs/"&gt;Samba documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/when-did-you-last-restore-a-file"&gt;When did you last restore a file?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/phone-photo-backup-verify-the-journey"&gt;Phone photo backup: verify the journey&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-photos-deserve-an-exit-plan"&gt;Your photos deserve an exit plan&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>When did you last restore a file?</title><link>https://it.kituwa.com/blogs/blog/when-did-you-last-restore-a-file/</link><pubDate>Mon, 08 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/when-did-you-last-restore-a-file/</guid><description>&lt;p&gt;A backup you have never restored is still a hypothesis.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;When did you last restore a file?&lt;/li&gt;
&lt;li&gt;Test one expendable file.&lt;/li&gt;
&lt;li&gt;Backup — Separate copy&lt;/li&gt;
&lt;li&gt;Test folder — New destination&lt;/li&gt;
&lt;li&gt;Restored file — Opened + compared&lt;/li&gt;
&lt;li&gt;Evidence — It worked&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="prove-the-restore"&gt;Prove the restore&lt;/h3&gt;
&lt;p&gt;Pick one expendable file. Restore it into a new folder, open it, and compare it with the original. Note how long it took and what you needed: a password, a key, a specific tool, or a different machine.&lt;/p&gt;
&lt;h3 id="prove-the-restore_1"&gt;Prove the restore&lt;/h3&gt;
&lt;p&gt;If the restore fails, you learned something before an emergency. If it succeeds, you have evidence.&lt;/p&gt;
&lt;h3 id="prove-the-restore_2"&gt;Prove the restore&lt;/h3&gt;
&lt;p&gt;Do not test on your only copy, and do not overwrite the original during the test. A restore test is read-only until you deliberately replace something.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;When did you last restore a file?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/li&gt;
&lt;li&gt;Never testing a restore of a real file.&lt;/li&gt;
&lt;li&gt;Keeping the only copy on the same device or in the same location.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Test one expendable file.&lt;/li&gt;
&lt;li&gt;☐ Backup — Separate copy&lt;/li&gt;
&lt;li&gt;☐ Test folder — New destination&lt;/li&gt;
&lt;li&gt;☐ Restored file — Opened + compared&lt;/li&gt;
&lt;li&gt;☐ Evidence — It worked&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A backup you have never restored is still a hypothesis.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/design-a-3-2-1-backup-plan"&gt;Design a 3-2-1 backup plan&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/nextcloud-syncthing-or-a-file-server"&gt;Nextcloud, Syncthing, or a file server?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/phone-photo-backup-verify-the-journey"&gt;Phone photo backup: verify the journey&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Design a 3-2-1 backup plan</title><link>https://it.kituwa.com/blogs/blog/design-a-3-2-1-backup-plan/</link><pubDate>Sun, 07 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/design-a-3-2-1-backup-plan/</guid><description>&lt;p&gt;3-2-1 is a simple starting rule: at least three copies of important data, on two different media, with one copy off-site.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Design a 3-2-1 backup plan&lt;/li&gt;
&lt;li&gt;Simple rule, tested restore.&lt;/li&gt;
&lt;li&gt;1 Three copies&lt;/li&gt;
&lt;li&gt;2 Two media types&lt;/li&gt;
&lt;li&gt;3 One off-site&lt;/li&gt;
&lt;li&gt;4 Test restore&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Example: the working copy on your laptop, a backup on an external drive, and an off-site copy at a trusted location or cloud service. The off-site copy is what survives a fire, theft, or a local disaster.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;The rule is not a guarantee. It does not tell you how often to copy, how long to keep versions, or whether the backup is restorable. Add a schedule and a restore test. Encrypt sensitive backups and protect the keys.&lt;/p&gt;
&lt;h3 id="prove-the-restore"&gt;Prove the restore&lt;/h3&gt;
&lt;p&gt;Keep at least one copy offline or immutable where ransomware is a concern; a synced copy can be encrypted too. For a small business, write down what is backed up, who runs it, where the copies live, and how a restore is approved. For a home lab, start with the data you cannot recreate.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What is your third copy?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/li&gt;
&lt;li&gt;Never testing a restore of a real file.&lt;/li&gt;
&lt;li&gt;Keeping the only copy on the same device or in the same location.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Simple rule, tested restore.&lt;/li&gt;
&lt;li&gt;☐ 1 Three copies&lt;/li&gt;
&lt;li&gt;☐ 2 Two media types&lt;/li&gt;
&lt;li&gt;☐ 3 One off-site&lt;/li&gt;
&lt;li&gt;☐ 4 Test restore&lt;/li&gt;
&lt;li&gt;☐ 5 Document it&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;3-2-1 is a simple starting rule: at least three copies of important data, on two different media, with one copy off-site.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://restic.readthedocs.io/en/stable/"&gt;restic documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/raid-is-not-a-backup"&gt;RAID is not a backup&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/when-did-you-last-restore-a-file"&gt;When did you last restore a file?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/nextcloud-syncthing-or-a-file-server"&gt;Nextcloud, Syncthing, or a file server?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>One server, too many services?</title><link>https://it.kituwa.com/blogs/blog/one-server-too-many-services/</link><pubDate>Fri, 05 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/one-server-too-many-services/</guid><description>&lt;p&gt;One server can hold a lot of services until it cannot.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;One server, too many services?&lt;/li&gt;
&lt;li&gt;Measure, prioritize, recover.&lt;/li&gt;
&lt;li&gt;Too many services — Boxes stack up&lt;/li&gt;
&lt;li&gt;Contention — CPU, memory, disk&lt;/li&gt;
&lt;li&gt;Recovery order — What comes back first?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Resource contention shows up as slow responses, OOM kills, or a disk that never stops working. Dependency chains matter: if the reverse proxy is down, every web app behind it looks down. Maintenance burden grows with each service: updates, backups, certificates, and alerts.&lt;/p&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Write a recovery priority list. What must come back first: photos, files, chat, or AI? What can wait? What has a tested backup?&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;There is no universal apps-per-GB limit. Measure, document, and decide what belongs on one machine.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which service should recover first after an outage?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Measure, prioritize, recover.&lt;/li&gt;
&lt;li&gt;☐ Too many services — Boxes stack up&lt;/li&gt;
&lt;li&gt;☐ Contention — CPU, memory, disk&lt;/li&gt;
&lt;li&gt;☐ Recovery order — What comes back first?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;One server can hold a lot of services until it cannot.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.docker.com/engine/containers/resource_constraints/"&gt;Docker — resource constraints&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs"&gt;Ubuntu Server documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/check-containers-without-changing-them"&gt;Check containers without changing them&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/raid-is-not-a-backup"&gt;RAID is not a backup&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/design-a-3-2-1-backup-plan"&gt;Design a 3-2-1 backup plan&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Check containers without changing them</title><link>https://it.kituwa.com/blogs/blog/check-containers-without-changing-them/</link><pubDate>Thu, 04 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/check-containers-without-changing-them/</guid><description>&lt;p&gt;Check containers without changing them.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Check containers without changing them&lt;/li&gt;
&lt;li&gt;Status, logs, resources.&lt;/li&gt;
&lt;li&gt;docker compose ps — Services, state, and published ports&lt;/li&gt;
&lt;li&gt;docker compose logs --tail=100 — Recent log lines; redact secrets&lt;/li&gt;
&lt;li&gt;docker stats — Live CPU, memory, network, block I/O&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-docker-compose-ps"&gt;Check &lt;code&gt;docker compose ps&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;docker compose ps&lt;/code&gt; shows the project's services, state, and ports. Run it from the project directory, or use &lt;code&gt;-f&lt;/code&gt; to point at the Compose file.&lt;/p&gt;
&lt;h3 id="check-docker-compose-logs-tail100"&gt;Check &lt;code&gt;docker compose logs --tail=100&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;docker compose logs --tail=100&lt;/code&gt; shows the last 100 log lines. Add a service name to narrow it. Logs can contain tokens, email addresses, or personal data; redact before sharing.&lt;/p&gt;
&lt;h3 id="check-docker-stats"&gt;Check &lt;code&gt;docker stats&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;docker stats&lt;/code&gt; shows live CPU, memory, network, and block I/O per container. Use it to spot a container that is restarting, leaking memory, or saturating a resource.&lt;/p&gt;
&lt;h3 id="check-the-container-state"&gt;Check the container state&lt;/h3&gt;
&lt;p&gt;Permissions matter: if the Docker socket is root-equivalent, membership in the docker group is powerful. Do not run random compose files as a shortcut.&lt;/p&gt;
&lt;h3 id="check-ps"&gt;Check &lt;code&gt;ps&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;If a service is restarting, &lt;code&gt;ps&lt;/code&gt; may show a changing state; note the restart count and read the logs. Use &lt;code&gt;-a&lt;/code&gt; with &lt;code&gt;ps&lt;/code&gt; if you also need stopped containers. These commands are read-only. They tell you what is happening; they do not fix it.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What symptom are you trying to understand?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Deleting a container without checking its volumes and bind mounts.&lt;/li&gt;
&lt;li&gt;Assuming a restart fixed the cause because the service came back.&lt;/li&gt;
&lt;li&gt;Giving broad access to the Docker socket or host.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Status, logs, resources.&lt;/li&gt;
&lt;li&gt;☐ docker compose ps — Services, state, and published ports&lt;/li&gt;
&lt;li&gt;☐ docker compose logs --tail=100 — Recent log lines; redact secrets&lt;/li&gt;
&lt;li&gt;☐ docker stats — Live CPU, memory, network, block I/O&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Check containers without changing them.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Deleting a container without checking its volumes and bind mounts.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.docker.com/reference/cli/docker/compose/ps/"&gt;docker compose ps&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.docker.com/reference/cli/docker/compose/logs/"&gt;docker compose logs&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.docker.com/reference/cli/docker/container/stats/"&gt;docker stats&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/docker-volumes-are-your-app-s-memory"&gt;Docker volumes are your app's memory&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/one-server-too-many-services"&gt;One server, too many services?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/raid-is-not-a-backup"&gt;RAID is not a backup&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Docker volumes are your app's memory</title><link>https://it.kituwa.com/blogs/blog/docker-volumes-are-your-app-s-memory/</link><pubDate>Wed, 03 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/docker-volumes-are-your-app-s-memory/</guid><description>&lt;p&gt;A container is replaceable. Its data is not.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Docker volumes are your app's memory&lt;/li&gt;
&lt;li&gt;Replace the app; keep the data.&lt;/li&gt;
&lt;li&gt;Container — Replaceable instance&lt;/li&gt;
&lt;li&gt;Named volume — Docker-managed data&lt;/li&gt;
&lt;li&gt;Bind mount — Host path + permissions&lt;/li&gt;
&lt;li&gt;Backup copy — Off the host + tested&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-the-container-state"&gt;Check the container state&lt;/h3&gt;
&lt;p&gt;The image is the recipe. The container is a running instance you can delete and recreate. A named volume or bind mount is where persistent data lives: a database, uploads, configuration, notes.&lt;/p&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Named volumes are managed by Docker and easy to reference by name. Bind mounts point at a specific host path, which is convenient but makes you responsible for permissions and backups.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Deleting a container is not a backup strategy. If the volume is gone, recreating the container gives you an empty app. Back up the volume or the data inside it, test a restore, and keep a copy off the host.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_2"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Before you update, note which volumes and bind mounts the service uses. After you update, confirm the data is still there. A backup you have never restored is not yet a backup plan.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which service would hurt most if its data vanished?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Deleting a container without checking its volumes and bind mounts.&lt;/li&gt;
&lt;li&gt;Assuming a restart fixed the cause because the service came back.&lt;/li&gt;
&lt;li&gt;Giving broad access to the Docker socket or host.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Replace the app; keep the data.&lt;/li&gt;
&lt;li&gt;☐ Container — Replaceable instance&lt;/li&gt;
&lt;li&gt;☐ Named volume — Docker-managed data&lt;/li&gt;
&lt;li&gt;☐ Bind mount — Host path + permissions&lt;/li&gt;
&lt;li&gt;☐ Backup copy — Off the host + tested&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A container is replaceable.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Deleting a container without checking its volumes and bind mounts.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.docker.com/engine/storage/volumes/"&gt;Docker — Volumes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.docker.com/engine/storage/bind-mounts/"&gt;Docker — Bind mounts&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/one-app-for-your-first-server"&gt;One app for your first server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/check-containers-without-changing-them"&gt;Check containers without changing them&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/one-server-too-many-services"&gt;One server, too many services?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>One app for your first server</title><link>https://it.kituwa.com/blogs/blog/one-app-for-your-first-server/</link><pubDate>Tue, 02 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/one-app-for-your-first-server/</guid><description>&lt;p&gt;Pick one app for your first server, not five.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;One app for your first server&lt;/li&gt;
&lt;li&gt;Start small, on a trusted network.&lt;/li&gt;
&lt;li&gt;Dashboard — Links + status, gentlest start&lt;/li&gt;
&lt;li&gt;Uptime monitor — Checks + notifications&lt;/li&gt;
&lt;li&gt;Private notes — Accounts + storage + backups&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;A personal dashboard (Homarr or a similar tool) gives you one page for links and status. An uptime monitor (Uptime Kuma) tells you when something is down. A private notes service (Joplin Server or similar) keeps notes in your control.&lt;/p&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Complexity: a dashboard is usually the gentlest start; an uptime monitor adds checks and notifications; a notes service adds accounts, storage, and backups.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Start on a trusted local network. Do not expose a new service to the internet until you understand authentication, updates, and backups.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which daily annoyance would you solve first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Start small, on a trusted network.&lt;/li&gt;
&lt;li&gt;☐ Dashboard — Links + status, gentlest start&lt;/li&gt;
&lt;li&gt;☐ Uptime monitor — Checks + notifications&lt;/li&gt;
&lt;li&gt;☐ Private notes — Accounts + storage + backups&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Pick one app for your first server, not five.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.home-assistant.io/"&gt;Home Assistant&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/louislam/uptime-kuma"&gt;Uptime Kuma&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://joplinapp.org/"&gt;Joplin&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/read-a-compose-file-like-a-map"&gt;Read a Compose file like a map&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/docker-volumes-are-your-app-s-memory"&gt;Docker volumes are your app's memory&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/check-containers-without-changing-them"&gt;Check containers without changing them&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Read a Compose file like a map</title><link>https://it.kituwa.com/blogs/blog/read-a-compose-file-like-a-map/</link><pubDate>Mon, 01 Dec 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/read-a-compose-file-like-a-map/</guid><description>&lt;p&gt;A Compose file is a map of a small application stack. Read it in five sections.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Read a Compose file like a map&lt;/li&gt;
&lt;li&gt;Five sections, one small stack.&lt;/li&gt;
&lt;li&gt;services: the containers&lt;/li&gt;
&lt;li&gt;image: what runs&lt;/li&gt;
&lt;li&gt;ports: who can reach it&lt;/li&gt;
&lt;li&gt;volumes: what persists&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-services"&gt;Check &lt;code&gt;services&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;services&lt;/code&gt;: the containers you want. Each name is a service.
&lt;code&gt;image&lt;/code&gt;: the image to run. Pin a version when you need reproducibility.
&lt;code&gt;ports&lt;/code&gt;: host-to-container port mapping. Exposing a port changes who can reach it.
&lt;code&gt;volumes&lt;/code&gt;: persistent data. A named volume or bind mount survives container replacement.
&lt;code&gt;environment&lt;/code&gt;: configuration passed to the container. Keep secrets out of the file; use an env file or secret store.&lt;/p&gt;
&lt;h3 id="check-yaml"&gt;Check `yaml&lt;/h3&gt;
&lt;p&gt;services:
app:
image: example/app:1.0
ports:
- "127.0.0.1:8080:8080"
volumes:
- app-data:/data
environment:
APP_MODE: demo
volumes:
app-data:`&lt;/p&gt;
&lt;p&gt;Harmless illustrative excerpt (placeholders, not production):&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-yaml"&gt;services:
app:
image: example/app:1.0
ports:
- &amp;quot;127.0.0.1:8080:8080&amp;quot;
volumes:
- app-data:/data
environment:
APP_MODE: demo
volumes:
app-data:
&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id="check-127001"&gt;Check &lt;code&gt;127.0.0.1&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;127.0.0.1&lt;/code&gt; limits the host binding to localhost in this example. It is not a complete security plan. Compose can also define networks and dependencies; start with these five sections before adding complexity. The file describes intent; it does not prove the image is trustworthy or that the host is hardened. Ask what each service writes to disk before you deploy it.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which section would you check first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Deleting a container without checking its volumes and bind mounts.&lt;/li&gt;
&lt;li&gt;Assuming a restart fixed the cause because the service came back.&lt;/li&gt;
&lt;li&gt;Giving broad access to the Docker socket or host.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Five sections, one small stack.&lt;/li&gt;
&lt;li&gt;☐ services: the containers&lt;/li&gt;
&lt;li&gt;☐ image: what runs&lt;/li&gt;
&lt;li&gt;☐ ports: who can reach it&lt;/li&gt;
&lt;li&gt;☐ volumes: what persists&lt;/li&gt;
&lt;li&gt;☐ environment: configuration, no secrets&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A Compose file is a map of a small application stack.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Deleting a container without checking its volumes and bind mounts.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.docker.com/compose/compose-file/"&gt;Docker Compose file reference&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.docker.com/compose/environment-variables/"&gt;Docker Compose environment variables&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/containers-vs-virtual-machines"&gt;Containers vs virtual machines&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/one-app-for-your-first-server"&gt;One app for your first server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/docker-volumes-are-your-app-s-memory"&gt;Docker volumes are your app's memory&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Containers vs virtual machines</title><link>https://it.kituwa.com/blogs/blog/containers-vs-virtual-machines/</link><pubDate>Sun, 30 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/containers-vs-virtual-machines/</guid><description>&lt;p&gt;Containers and virtual machines both isolate workloads, but they isolate different things.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Containers vs virtual machines&lt;/li&gt;
&lt;li&gt;Different isolation, different jobs.&lt;/li&gt;
&lt;li&gt;Containers&lt;/li&gt;
&lt;li&gt;Virtual machines&lt;/li&gt;
&lt;li&gt;Kernel — Shares the host kernel — Runs a guest kernel&lt;/li&gt;
&lt;li&gt;Startup — Fast, process-level — Boots a full OS&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;A container packages an app with its dependencies and shares the host kernel. It starts quickly and is a good fit for one service: a web app, a database, a dashboard. Isolation depends on the runtime and configuration; it is not a perfect security boundary.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;A virtual machine runs a complete guest operating system with its own kernel. It is a good fit when you need a different OS, stronger separation, or a disposable lab. It uses more resources and takes longer to start.&lt;/p&gt;
&lt;h3 id="check-the-container-state"&gt;Check the container state&lt;/h3&gt;
&lt;p&gt;Typical beginner uses: containers for apps on one host; VMs for trying another OS or testing risky changes.&lt;/p&gt;
&lt;h3 id="check-the-container-state_1"&gt;Check the container state&lt;/h3&gt;
&lt;p&gt;Neither is universally safer. A container shares the host kernel, so kernel-level isolation is different from a VM; a VM carries a full OS to patch and boot. Patch both, limit privileges, and back up the data that matters.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Do you want to run an app or experiment with an entire OS?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Deleting a container without checking its volumes and bind mounts.&lt;/li&gt;
&lt;li&gt;Assuming a restart fixed the cause because the service came back.&lt;/li&gt;
&lt;li&gt;Giving broad access to the Docker socket or host.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Different isolation, different jobs.&lt;/li&gt;
&lt;li&gt;☐ Containers&lt;/li&gt;
&lt;li&gt;☐ Virtual machines&lt;/li&gt;
&lt;li&gt;☐ Kernel — Shares the host kernel — Runs a guest kernel&lt;/li&gt;
&lt;li&gt;☐ Startup — Fast, process-level — Boots a full OS&lt;/li&gt;
&lt;li&gt;☐ Best fit — One app or service — Another OS or a lab&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Containers and virtual machines both isolate workloads, but they isolate different things.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Deleting a container without checking its volumes and bind mounts.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.docker.com/get-started/docker-concepts/the-basics/what-is-a-container/"&gt;Docker — What is a container?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.kernel.org/admin-guide/cgroup-v2.html"&gt;Linux kernel — cgroup v2&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.qemu.org/docs/master/"&gt;QEMU documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/mini-pc-laptop-or-tower"&gt;Mini PC, laptop, or tower?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/read-a-compose-file-like-a-map"&gt;Read a Compose file like a map&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/one-app-for-your-first-server"&gt;One app for your first server&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Mini PC, laptop, or tower?</title><link>https://it.kituwa.com/blogs/blog/mini-pc-laptop-or-tower/</link><pubDate>Sat, 29 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/mini-pc-laptop-or-tower/</guid><description>&lt;p&gt;Mini PC, laptop, or tower? The right choice follows the workload, not a spec sheet.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Mini PC, laptop, or tower?&lt;/li&gt;
&lt;li&gt;Follow the workload, not the spec sheet.&lt;/li&gt;
&lt;li&gt;Mini PC — Small, low power, limited expansion&lt;/li&gt;
&lt;li&gt;Laptop — Built-in screen, constrained cooling&lt;/li&gt;
&lt;li&gt;Tower — Drive bays, cards, airflow&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;A mini PC saves space and often uses less power, but expandability is limited. A laptop adds a built-in screen and battery backup, but cooling and drive bays are constrained. A tower gives room for drives, cards, and airflow, but takes space and may use more power.&lt;/p&gt;
&lt;h3 id="check-the-network-path"&gt;Check the network path&lt;/h3&gt;
&lt;p&gt;Check: how many drives do you need, how much RAM can it take, how many network ports, and what happens when a fan fails? Reuse value matters too: a spare laptop you already own may be the cheapest first server.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What spare device do you already have?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Follow the workload, not the spec sheet.&lt;/li&gt;
&lt;li&gt;☐ Mini PC — Small, low power, limited expansion&lt;/li&gt;
&lt;li&gt;☐ Laptop — Built-in screen, constrained cooling&lt;/li&gt;
&lt;li&gt;☐ Tower — Drive bays, cards, airflow&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Mini PC, laptop, or tower?&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/certified"&gt;Ubuntu certified hardware&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs"&gt;Ubuntu Server documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/plan-a-server-before-installing-apps"&gt;Plan a server before installing apps&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/containers-vs-virtual-machines"&gt;Containers vs virtual machines&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/read-a-compose-file-like-a-map"&gt;Read a Compose file like a map&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Plan a server before installing apps</title><link>https://it.kituwa.com/blogs/blog/plan-a-server-before-installing-apps/</link><pubDate>Fri, 28 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/plan-a-server-before-installing-apps/</guid><description>&lt;p&gt;Plan the server before you install apps.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Plan a server before installing apps&lt;/li&gt;
&lt;li&gt;Six questions before the first container.&lt;/li&gt;
&lt;li&gt;Users — Who connects, from where?&lt;/li&gt;
&lt;li&gt;Apps — What job does each do?&lt;/li&gt;
&lt;li&gt;Data growth — What grows, how fast?&lt;/li&gt;
&lt;li&gt;Backups — What, where, restore?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Write down six things:&lt;/p&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Intended users: who connects, from where, and how often?&lt;/li&gt;
&lt;li&gt;Apps: what job does each one do? Can two jobs share one app?&lt;/li&gt;
&lt;li&gt;Data growth: what grows, how fast, and how much room is left?&lt;/li&gt;
&lt;li&gt;Backups: what is copied, how often, where, and how do you restore?&lt;/li&gt;
&lt;li&gt;Network access: LAN only, VPN, or public? Who manages the firewall?&lt;/li&gt;
&lt;li&gt;Maintenance owner: who updates it, checks alerts, and responds when it breaks?&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="plan-for-growth"&gt;Plan for growth&lt;/h3&gt;
&lt;p&gt;A hypothetical household example: two adults, photos, files, a dashboard, and remote access for one person. That is a different plan from a five-person office with chat, email, and customer records.&lt;/p&gt;
&lt;h3 id="step-4-what-to-check"&gt;Step 4: what to check&lt;/h3&gt;
&lt;p&gt;Write the answers down and revisit them when the workload changes. One low-pressure sentence: if you want help turning the worksheet into a build, Kituwa can scope it with you.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which question is hardest for you to answer?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Six questions before the first container.&lt;/li&gt;
&lt;li&gt;☐ Users — Who connects, from where?&lt;/li&gt;
&lt;li&gt;☐ Apps — What job does each do?&lt;/li&gt;
&lt;li&gt;☐ Data growth — What grows, how fast?&lt;/li&gt;
&lt;li&gt;☐ Backups — What, where, restore?&lt;/li&gt;
&lt;li&gt;☐ Network — LAN, VPN, or public?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Plan the server before you install apps.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs"&gt;Ubuntu Server documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/old-laptop-home-server-first-build"&gt;An old laptop as a home server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/mini-pc-laptop-or-tower"&gt;Mini PC, laptop, or tower?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/containers-vs-virtual-machines"&gt;Containers vs virtual machines&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Your computer emergency kit</title><link>https://it.kituwa.com/blogs/blog/your-computer-emergency-kit/</link><pubDate>Wed, 26 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/your-computer-emergency-kit/</guid><description>&lt;p&gt;Build a small emergency kit before you need it.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Your computer emergency kit&lt;/li&gt;
&lt;li&gt;Label it, store it, test it.&lt;/li&gt;
&lt;li&gt;Recovery USB — Labeled and tested&lt;/li&gt;
&lt;li&gt;Backup drive — Separate device&lt;/li&gt;
&lt;li&gt;Recovery codes — Private, not posted&lt;/li&gt;
&lt;li&gt;Device inventory — No secrets&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;A labeled recovery USB, an external backup drive, printed recovery codes, and a written device inventory. Keep the USB and drive somewhere you can find them; keep the codes somewhere private. Never post recovery codes, passwords, tokens, or serial numbers in comments.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;An inventory can be simple: device name, model, operating system, disk encryption status, backup location, and who to contact. Do not include secrets.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_2"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Test that the USB boots and that the backup opens. A kit you have never used is a box of hope.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which non-sensitive item would you add?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Label it, store it, test it.&lt;/li&gt;
&lt;li&gt;☐ Recovery USB — Labeled and tested&lt;/li&gt;
&lt;li&gt;☐ Backup drive — Separate device&lt;/li&gt;
&lt;li&gt;☐ Recovery codes — Private, not posted&lt;/li&gt;
&lt;li&gt;☐ Device inventory — No secrets&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Build a small emergency kit before you need it.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://linuxmint-installation-guide.readthedocs.io/en/latest/boot.html"&gt;Linux Mint Installation Guide — Boot Linux Mint&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/practice-recovery-before-you-need-it"&gt;Practice recovery before you need it&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/old-laptop-home-server-first-build"&gt;An old laptop as a home server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/plan-a-server-before-installing-apps"&gt;Plan a server before installing apps&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Practice recovery before you need it</title><link>https://it.kituwa.com/blogs/blog/practice-recovery-before-you-need-it/</link><pubDate>Tue, 25 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/practice-recovery-before-you-need-it/</guid><description>&lt;p&gt;Practice recovery before you need it. Use a spare device or a virtual machine, not your only working computer.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Practice recovery before you need it&lt;/li&gt;
&lt;li&gt;Rehearse on a spare device or VM.&lt;/li&gt;
&lt;li&gt;Boot menu key&lt;/li&gt;
&lt;li&gt;Live USB&lt;/li&gt;
&lt;li&gt;Recovery key&lt;/li&gt;
&lt;li&gt;Test file&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Rehearsal checklist:&lt;/p&gt;
&lt;h3 id="verify-the-key-path"&gt;Verify the key path&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Locate the boot menu key and the firmware setting that selects USB.&lt;/li&gt;
&lt;li&gt;Start a live USB and confirm it reaches the desktop.&lt;/li&gt;
&lt;li&gt;Mount or open a test file from a spare drive, read-only if possible.&lt;/li&gt;
&lt;li&gt;Exit, reboot, and confirm the internal system is unchanged.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="make-recovery-practical"&gt;Make recovery practical&lt;/h3&gt;
&lt;p&gt;If the disk is encrypted, you may need the recovery key or passphrase. Confirm you have it before an emergency.&lt;/p&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Write down the boot-menu key for each machine you support, and keep the live USB somewhere you can find it. A recovery rehearsal is not a backup test, but it removes the first five minutes of panic when a real failure happens.&lt;/p&gt;
&lt;h3 id="step-5-what-to-check"&gt;Step 5: what to check&lt;/h3&gt;
&lt;p&gt;Do not modify partitions, bypass access controls, or test on data you cannot lose. The goal is familiarity with the path: boot menu → live media → inspect → exit.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;When did you last practice a recovery?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Rehearse on a spare device or VM.&lt;/li&gt;
&lt;li&gt;☐ Boot menu key&lt;/li&gt;
&lt;li&gt;☐ Live USB&lt;/li&gt;
&lt;li&gt;☐ Recovery key&lt;/li&gt;
&lt;li&gt;☐ Test file&lt;/li&gt;
&lt;li&gt;☐ 1 Locate boot menu&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Practice recovery before you need it.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://linuxmint-installation-guide.readthedocs.io/en/latest/boot.html"&gt;Linux Mint Installation Guide — Boot Linux Mint&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/tutorials/try-ubuntu-before-you-install"&gt;Ubuntu — Try Ubuntu before installing&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/immutable-linux-explained-honestly"&gt;Immutable Linux explained honestly&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-computer-emergency-kit"&gt;Your computer emergency kit&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/old-laptop-home-server-first-build"&gt;An old laptop as a home server&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Immutable Linux explained honestly</title><link>https://it.kituwa.com/blogs/blog/immutable-linux-explained-honestly/</link><pubDate>Mon, 24 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/immutable-linux-explained-honestly/</guid><description>&lt;p&gt;Immutable Linux is easier to understand as layers.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Immutable Linux explained honestly&lt;/li&gt;
&lt;li&gt;Layers, limits, and backups.&lt;/li&gt;
&lt;li&gt;Protected base — Atomic update, previous deployment&lt;/li&gt;
&lt;li&gt;Apps — Flatpak, containers, Toolbox&lt;/li&gt;
&lt;li&gt;Rollback — System only, not your data&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;The base system is protected and updated atomically: the new version is staged, then the system switches to it. Fedora Silverblue and Kinoite are desktop examples. If an update goes wrong, you can often boot the previous deployment.&lt;/p&gt;
&lt;h3 id="check-the-container-state"&gt;Check the container state&lt;/h3&gt;
&lt;p&gt;Apps are installed differently: Flatpak for desktop apps, containers for services, and Toolbox or Distrobox for development environments. The base stays clean.&lt;/p&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Rollback has limits. It rolls back the system deployment, not your documents, databases, or every app's state. It does not replace backups, and it does not prevent all compromise. Talos is a Kubernetes-oriented OS, not a gaming distribution.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path_1"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Atomic updates also change troubleshooting: the base is not meant to be edited in place, so fixes usually go into a layered package, a container, or an upstream image. That discipline is useful, but it is still a model with trade-offs, not a guarantee of safety or simplicity.&lt;/p&gt;
&lt;h3 id="test-the-model-on-your-task"&gt;Test the model on your task&lt;/h3&gt;
&lt;p&gt;Immutability changes the maintenance model; it does not remove the need to understand it.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What would you want on the protected base?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Trusting a confident answer without a check.&lt;/li&gt;
&lt;li&gt;Skipping a repeatable test set or factual review.&lt;/li&gt;
&lt;li&gt;Sending private data to an endpoint you have not verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Layers, limits, and backups.&lt;/li&gt;
&lt;li&gt;☐ Protected base — Atomic update, previous deployment&lt;/li&gt;
&lt;li&gt;☐ Apps — Flatpak, containers, Toolbox&lt;/li&gt;
&lt;li&gt;☐ Rollback — System only, not your data&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Immutable Linux is easier to understand as layers.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Trusting a confident answer without a check.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://fedoraproject.org/atomic-desktops/"&gt;Fedora atomic desktops&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.fedoraproject.org/en-US/fedora-silverblue/"&gt;Fedora Silverblue documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/siderolabs/talos"&gt;Sidero Labs Talos&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-should-stay-simple"&gt;What should stay simple?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/practice-recovery-before-you-need-it"&gt;Practice recovery before you need it&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-computer-emergency-kit"&gt;Your computer emergency kit&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>What should stay simple?</title><link>https://it.kituwa.com/blogs/blog/what-should-stay-simple/</link><pubDate>Sun, 23 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/what-should-stay-simple/</guid><description>&lt;p&gt;Two desks can solve one problem.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;What should stay simple?&lt;/li&gt;
&lt;li&gt;Separate the reliable from the experimental.&lt;/li&gt;
&lt;li&gt;Work desk — Stable, supported, backed up&lt;/li&gt;
&lt;li&gt;Lab desk — Experiments, breakage allowed&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;The work desk is the reliable everyday machine: stable release, supported updates, minimal experiments, backups that run.&lt;/p&gt;
&lt;h3 id="check-the-container-state"&gt;Check the container state&lt;/h3&gt;
&lt;p&gt;The lab desk is for testing: new distributions, containers, drivers, and risky changes. If it breaks, work continues.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Separating them reduces interruptions, but it is not free: another machine, another backup, another thing to maintain. On a tight budget, one machine with a virtual machine or a separate user account can still be reasonable, as long as you keep a restore path.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which service would you never want interrupted by a hobby project?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Separate the reliable from the experimental.&lt;/li&gt;
&lt;li&gt;☐ Work desk — Stable, supported, backed up&lt;/li&gt;
&lt;li&gt;☐ Lab desk — Experiments, breakage allowed&lt;/li&gt;
&lt;li&gt;☐ Verify the result&lt;/li&gt;
&lt;li&gt;☐ Record the rollback&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Two desks can solve one problem.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://linuxmint-user-guide.readthedocs.io/en/latest/mintupdate.html"&gt;Linux Mint User Guide — Update Manager&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-safer-update-routine"&gt;A safer update routine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/immutable-linux-explained-honestly"&gt;Immutable Linux explained honestly&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/practice-recovery-before-you-need-it"&gt;Practice recovery before you need it&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>A safer update routine</title><link>https://it.kituwa.com/blogs/blog/a-safer-update-routine/</link><pubDate>Sat, 22 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/a-safer-update-routine/</guid><description>&lt;p&gt;A safer update routine has five steps.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A safer update routine&lt;/li&gt;
&lt;li&gt;Make a bad update recoverable.&lt;/li&gt;
&lt;li&gt;1 Read notices&lt;/li&gt;
&lt;li&gt;2 Confirm backups&lt;/li&gt;
&lt;li&gt;3 Use supported manager&lt;/li&gt;
&lt;li&gt;4 Reboot when required&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Read the notices: release notes, security advisories, and any manual-intervention warnings for your distribution.&lt;/li&gt;
&lt;li&gt;Confirm backups: at least one recent copy on a separate device, and a restore test you trust.&lt;/li&gt;
&lt;li&gt;Use the supported manager: Mint's Update Manager, Ubuntu's apt/Software Updater, or your distribution's documented tool. Do not paste commands from another distro's guide.&lt;/li&gt;
&lt;li&gt;Reboot when required: kernel, driver, and library updates may only take effect after a restart. Save your work first.&lt;/li&gt;
&lt;li&gt;Check important apps: browser, VPN, printer, backups, and anything you need tomorrow.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="protect-the-data-first_1"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Before a major upgrade, read the release notes for your exact edition and make sure the backup is recent enough to matter. If the update requires a reboot, do not postpone it indefinitely; a half-applied kernel or driver update can leave the machine in a confusing state.&lt;/p&gt;
&lt;h3 id="protect-the-data-first_2"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;A rollback plan matters: Timeshift snapshots, a VM snapshot, or a known-good backup. Updates are not guaranteed to be problem-free; the goal is to make a bad update recoverable.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which step do you skip most often?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Make a bad update recoverable.&lt;/li&gt;
&lt;li&gt;☐ 1 Read notices&lt;/li&gt;
&lt;li&gt;☐ 2 Confirm backups&lt;/li&gt;
&lt;li&gt;☐ 3 Use supported manager&lt;/li&gt;
&lt;li&gt;☐ 4 Reboot when required&lt;/li&gt;
&lt;li&gt;☐ 5 Check important apps&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A safer update routine has five steps.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://linuxmint-user-guide.readthedocs.io/en/latest/mintupdate.html"&gt;Linux Mint User Guide — Update Manager&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/package-management"&gt;Ubuntu Server — package management&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://wiki.archlinux.org/title/System_maintenance"&gt;Arch Wiki — System maintenance&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/desktop-environment-vs-distribution"&gt;Desktop environment vs distribution&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-should-stay-simple"&gt;What should stay simple?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/immutable-linux-explained-honestly"&gt;Immutable Linux explained honestly&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Desktop environment vs distribution</title><link>https://it.kituwa.com/blogs/blog/desktop-environment-vs-distribution/</link><pubDate>Fri, 21 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/desktop-environment-vs-distribution/</guid><description>&lt;p&gt;A distribution is not the same thing as a desktop environment.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Desktop environment vs distribution&lt;/li&gt;
&lt;li&gt;Two layers of the same experience.&lt;/li&gt;
&lt;li&gt;Distribution — Packages + release model&lt;/li&gt;
&lt;li&gt;Desktop environment — Panel + workflow&lt;/li&gt;
&lt;li&gt;Apps — Daily tools&lt;/li&gt;
&lt;li&gt;Cinnamon&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Think of a house. The distribution is the foundation and utilities: package management, repositories, release cadence, default security, and update policy. The desktop environment is the interior: panel, menu, window behavior, settings, and bundled apps.&lt;/p&gt;
&lt;h3 id="verify-the-key-path"&gt;Verify the key path&lt;/h3&gt;
&lt;p&gt;Cinnamon, Linux Mint's flagship desktop, emphasizes a traditional layout. GNOME offers a keyboard- and gesture-oriented workflow. KDE Plasma is highly configurable. All three can run on more than one distribution, and distributions can offer more than one desktop.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;So “Which Linux?” is two questions: which foundation, and which interior? A familiar desktop can make a new distribution easier; a well-supported distribution can make an unfamiliar desktop safer.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path_1"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Distribution defaults also shape what you get out of the box: update policy, security settings, driver choices, and software sources. The desktop can be changed later, but the foundation is harder to replace. That is why compatibility and support should come before visual preference.&lt;/p&gt;
&lt;h3 id="step-5-what-to-check"&gt;Step 5: what to check&lt;/h3&gt;
&lt;p&gt;Pick the combination, not a ranking.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which would you choose first: a familiar interior or a foundation your vendor supports?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Two layers of the same experience.&lt;/li&gt;
&lt;li&gt;☐ Distribution — Packages + release model&lt;/li&gt;
&lt;li&gt;☐ Desktop environment — Panel + workflow&lt;/li&gt;
&lt;li&gt;☐ Apps — Daily tools&lt;/li&gt;
&lt;li&gt;☐ Cinnamon&lt;/li&gt;
&lt;li&gt;☐ GNOME&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A distribution is not the same thing as a desktop environment.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://linuxmint.com/"&gt;Linux Mint&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.gnome.org/"&gt;GNOME&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://kde.org/"&gt;KDE&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/linux-myths-worth-retiring"&gt;Linux myths worth retiring&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-safer-update-routine"&gt;A safer update routine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/what-should-stay-simple"&gt;What should stay simple?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Linux myths worth retiring</title><link>https://it.kituwa.com/blogs/blog/linux-myths-worth-retiring/</link><pubDate>Thu, 20 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/linux-myths-worth-retiring/</guid><description>&lt;p&gt;Three Linux myths worth retiring.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Linux myths worth retiring&lt;/li&gt;
&lt;li&gt;Balanced corrections, with exceptions.&lt;/li&gt;
&lt;li&gt;MYTH — All work needs a terminal&lt;/li&gt;
&lt;li&gt;REALITY — Desktops have graphical tools; some tasks are easier in a terminal.&lt;/li&gt;
&lt;li&gt;MYTH — Linux cannot get malware&lt;/li&gt;
&lt;li&gt;REALITY — Malware exists; updates, repos, sandboxing and least privilege reduce risk.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Myth: everything requires the terminal. Reality: desktops have graphical software centers, settings, and update tools. Some troubleshooting is easier in a terminal, but it is not a daily requirement for everyone.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Myth: Linux cannot get malware. Reality: Linux malware exists. Sandboxing, repository trust, timely updates, and least privilege reduce risk; none makes a system immune. Flatpak sandboxes depend on permissions and configuration.&lt;/p&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;Myth: switching always saves time. Reality: a migration costs time: backups, app checks, hardware quirks, and learning. It may pay off later, but it is not automatic.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which misconception kept you from trying Linux?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Balanced corrections, with exceptions.&lt;/li&gt;
&lt;li&gt;☐ MYTH — All work needs a terminal&lt;/li&gt;
&lt;li&gt;☐ REALITY — Desktops have graphical tools; some tasks are easier in a terminal.&lt;/li&gt;
&lt;li&gt;☐ MYTH — Linux cannot get malware&lt;/li&gt;
&lt;li&gt;☐ REALITY — Malware exists; updates, repos, sandboxing and least privilege reduce risk.&lt;/li&gt;
&lt;li&gt;☐ MYTH — Switching always saves time&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Three Linux myths worth retiring.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/desktop"&gt;Ubuntu Desktop&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/security/notices"&gt;Ubuntu security notices&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.flatpak.org/en/latest/sandbox-permissions.html"&gt;Flatpak sandbox permissions&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/before-you-paste-a-terminal-command"&gt;Before you paste a terminal command&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/desktop-environment-vs-distribution"&gt;Desktop environment vs distribution&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-safer-update-routine"&gt;A safer update routine&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Before you paste a terminal command</title><link>https://it.kituwa.com/blogs/blog/before-you-paste-a-terminal-command/</link><pubDate>Wed, 19 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/before-you-paste-a-terminal-command/</guid><description>&lt;p&gt;Before you paste a command, read it in five parts.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Before you paste a terminal command&lt;/li&gt;
&lt;li&gt;Read it in five parts.&lt;/li&gt;
&lt;li&gt;ls -lh ~/Downloads&lt;/li&gt;
&lt;li&gt;Program — ls&lt;/li&gt;
&lt;li&gt;Options — -lh&lt;/li&gt;
&lt;li&gt;Target — ~/Downloads&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-ls"&gt;Check &lt;code&gt;ls&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Program: what runs? &lt;code&gt;ls&lt;/code&gt; lists; &lt;code&gt;rm&lt;/code&gt; removes.
Options: flags change behavior. &lt;code&gt;-r&lt;/code&gt; often means recursive; &lt;code&gt;-f&lt;/code&gt; often means force. Check the manual page.
Target: which path or device? A typo can point at the wrong disk.
Elevation: &lt;code&gt;sudo&lt;/code&gt; is not a magic prefix; it runs the command with root privileges.
Effects: read-only, writes, deletes, downloads, or pipes to another program?&lt;/p&gt;
&lt;h3 id="check-ls-lh-downloads"&gt;Check &lt;code&gt;ls -lh ~/Downloads&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Harmless sample: &lt;code&gt;ls -lh ~/Downloads&lt;/code&gt; lists a directory with human-readable sizes. No writes.&lt;/p&gt;
&lt;h3 id="check-curl-sh"&gt;Check &lt;code&gt;curl … | sh&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Piping an unknown download into a shell (&lt;code&gt;curl … | sh&lt;/code&gt;) means you are executing code you have not inspected. Download it, read it, check the source, then run it if you understand it.&lt;/p&gt;
&lt;h3 id="check-man-program"&gt;Check &lt;code&gt;man &amp;lt;program&amp;gt;&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Use &lt;code&gt;man &amp;lt;program&amp;gt;&lt;/code&gt; or &lt;code&gt;&amp;lt;program&amp;gt; --help&lt;/code&gt; to confirm what an option does. If a command includes a device path, run &lt;code&gt;lsblk&lt;/code&gt; first and read the output; device names are not stable across reboots or ports.&lt;/p&gt;
&lt;h3 id="step-5-what-to-check"&gt;Step 5: what to check&lt;/h3&gt;
&lt;p&gt;If you cannot explain a command in plain language, do not run it. Ask.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which part of a command do you check first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Read it in five parts.&lt;/li&gt;
&lt;li&gt;☐ ls -lh ~/Downloads&lt;/li&gt;
&lt;li&gt;☐ Program — ls&lt;/li&gt;
&lt;li&gt;☐ Options — -lh&lt;/li&gt;
&lt;li&gt;☐ Target — ~/Downloads&lt;/li&gt;
&lt;li&gt;☐ Elevation — none needed&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Before you paste a command, read it in five parts.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/curl.1.html"&gt;man curl — piping and options&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.gnu.org/software/bash/manual/bash.html"&gt;GNU Bash manual&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/mint-vs-arch-without-the-arguments"&gt;Mint vs Arch without the arguments&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/linux-myths-worth-retiring"&gt;Linux myths worth retiring&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/desktop-environment-vs-distribution"&gt;Desktop environment vs distribution&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Mint vs Arch without the arguments</title><link>https://it.kituwa.com/blogs/blog/mint-vs-arch-without-the-arguments/</link><pubDate>Tue, 18 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/mint-vs-arch-without-the-arguments/</guid><description>&lt;p&gt;Mint and Arch are built for different goals. That is not an intelligence contest.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Mint vs Arch without the arguments&lt;/li&gt;
&lt;li&gt;Different goals, not different intelligence.&lt;/li&gt;
&lt;li&gt;Linux Mint&lt;/li&gt;
&lt;li&gt;Arch Linux&lt;/li&gt;
&lt;li&gt;Setup — Guided installer, curated defaults — Guided installer, more choices&lt;/li&gt;
&lt;li&gt;Releases — Ubuntu LTS bases, point releases — Rolling releases&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Setup: Mint's installer and defaults get you to a working desktop quickly. Arch's guided installer helps, but you still make more choices; the wiki is part of the workflow.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Release model: Mint follows Ubuntu LTS bases and point releases. Arch is rolling; packages move continuously. Rolling means frequent updates, not automatic stability.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Learning: Mint is a gentle first Linux; Arch exposes the pieces and expects you to read documentation. Both teach you things.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path_1"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Maintenance: Mint's Update Manager and software choices are curated. Arch expects you to read news, merge configuration changes, and avoid partial upgrades.&lt;/p&gt;
&lt;h3 id="step-5-what-to-check"&gt;Step 5: what to check&lt;/h3&gt;
&lt;p&gt;Official repositories versus community packaging: both use official repositories; Arch's AUR is community-maintained and should be treated accordingly. Mint's base is Ubuntu plus Mint repositories.&lt;/p&gt;
&lt;h3 id="step-6-what-to-check"&gt;Step 6: what to check&lt;/h3&gt;
&lt;p&gt;Choose Mint for minimal maintenance, Arch for hands-on customization. Neither is “for smart people only”.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which fits your next six months?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Different goals, not different intelligence.&lt;/li&gt;
&lt;li&gt;☐ Linux Mint&lt;/li&gt;
&lt;li&gt;☐ Arch Linux&lt;/li&gt;
&lt;li&gt;☐ Setup — Guided installer, curated defaults — Guided installer, more choices&lt;/li&gt;
&lt;li&gt;☐ Releases — Ubuntu LTS bases, point releases — Rolling releases&lt;/li&gt;
&lt;li&gt;☐ Learning — Gentle first Linux — Documentation-driven&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Mint and Arch are built for different goals.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://archlinux.org/"&gt;Arch Linux&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://wiki.archlinux.org/title/Arch_Linux"&gt;Arch Wiki — Arch Linux&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://wiki.archlinux.org/title/System_maintenance"&gt;Arch Wiki — System maintenance&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://linuxmint.com/download_all.php"&gt;Linux Mint — supported releases&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/the-app-you-wish-had-a-linux-version"&gt;The app you wish had a Linux version&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/before-you-paste-a-terminal-command"&gt;Before you paste a terminal command&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/linux-myths-worth-retiring"&gt;Linux myths worth retiring&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>The app you wish had a Linux version</title><link>https://it.kituwa.com/blogs/blog/the-app-you-wish-had-a-linux-version/</link><pubDate>Mon, 17 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/the-app-you-wish-had-a-linux-version/</guid><description>&lt;p&gt;Which app keeps you on Windows or macOS?&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The app you wish had a Linux version&lt;/li&gt;
&lt;li&gt;Name the feature, not the whole suite.&lt;/li&gt;
&lt;li&gt;Native alternative — Different app, same job&lt;/li&gt;
&lt;li&gt;Browser version — Vendor-supported web app&lt;/li&gt;
&lt;li&gt;Compatibility tool — Wine, Proton, CrossOver&lt;/li&gt;
&lt;li&gt;Keep another OS — Dual boot, VM, spare PC&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="step-1-what-to-check"&gt;Step 1: what to check&lt;/h3&gt;
&lt;p&gt;Name the app and the one feature you actually rely on, not the whole suite. Then consider four paths:&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Native alternative: a different app that does the same job.&lt;/li&gt;
&lt;li&gt;Browser version: works if the vendor supports your browser and the feature set fits.&lt;/li&gt;
&lt;li&gt;Compatibility tool: Wine, Proton, or CrossOver can run some Windows software, but support varies by app and version.&lt;/li&gt;
&lt;li&gt;Keep another OS: a dual boot, virtual machine, or spare computer when the app is non-negotiable.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;None of these promises feature parity. Test the exact workflow, file formats, plugins, and peripherals before switching.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What is the app, and which feature matters most?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Name the feature, not the whole suite.&lt;/li&gt;
&lt;li&gt;☐ Native alternative — Different app, same job&lt;/li&gt;
&lt;li&gt;☐ Browser version — Vendor-supported web app&lt;/li&gt;
&lt;li&gt;☐ Compatibility tool — Wine, Proton, CrossOver&lt;/li&gt;
&lt;li&gt;☐ Keep another OS — Dual boot, VM, spare PC&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Which app keeps you on Windows or macOS?&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://wiki.winehq.org/"&gt;WineHQ Wiki&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ValveSoftware/Proton"&gt;ValveSoftware Proton&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/find-what-is-filling-your-linux-disk"&gt;Find what is filling your disk&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/mint-vs-arch-without-the-arguments"&gt;Mint vs Arch without the arguments&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/before-you-paste-a-terminal-command"&gt;Before you paste a terminal command&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>APT, Flatpak, AppImage</title><link>https://it.kituwa.com/blogs/blog/apt-flatpak-appimage/</link><pubDate>Sat, 15 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/apt-flatpak-appimage/</guid><description>&lt;p&gt;APT, Flatpak, and AppImage can all put software on your Linux desktop, but they are not interchangeable.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;APT, Flatpak, or AppImage?&lt;/li&gt;
&lt;li&gt;Same job. Different trade-offs.&lt;/li&gt;
&lt;li&gt;APT&lt;/li&gt;
&lt;li&gt;Flatpak&lt;/li&gt;
&lt;li&gt;AppImage&lt;/li&gt;
&lt;li&gt;Source — Distro repos — Bundled runtime — Single file&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-apt"&gt;Check &lt;code&gt;apt&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;APT uses your distribution's repositories. Packages are installed system-wide with &lt;code&gt;apt&lt;/code&gt;, updates arrive through the normal system update flow, and desktop integration is usually tight. Trust depends on the repository you use.&lt;/p&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Flatpak packages an app with a runtime and can sandbox it. Sandboxing depends on the permissions the app declares and the settings you grant; not every Flatpak is automatically safe. Updates come through Flatpak remotes such as Flathub. Integration is good, but permissions deserve a look.&lt;/p&gt;
&lt;h3 id="check-the-assumptions_1"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;AppImage is a single executable file. You download it, make it executable, and run it without a traditional install. Updates depend on the app and its update mechanism; sandboxing is not automatic. Desktop integration is optional.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;A realistic choice: use distro packages for system tools and drivers; use Flatpak for a current desktop app from a publisher you trust; use an AppImage when a vendor ships that format and you accept manual updates.&lt;/p&gt;
&lt;h3 id="step-5-what-to-check"&gt;Step 5: what to check&lt;/h3&gt;
&lt;p&gt;Check the publisher, the source, and who maintains it before choosing. The format is not a safety guarantee.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which format do you reach for first?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ APT, Flatpak, or AppImage?&lt;/li&gt;
&lt;li&gt;☐ Same job. Different trade-offs.&lt;/li&gt;
&lt;li&gt;☐ APT&lt;/li&gt;
&lt;li&gt;☐ Flatpak&lt;/li&gt;
&lt;li&gt;☐ AppImage&lt;/li&gt;
&lt;li&gt;☐ Source — Distro repos — Bundled runtime — Single file&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;APT, Flatpak, and AppImage can all put software on your Linux desktop, but they are not interchangeable.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.debian.org/doc/manuals/apt-guide/"&gt;Debian APT user guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.flatpak.org/en/latest/"&gt;Flatpak documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.flatpak.org/en/latest/sandbox-permissions.html"&gt;Flatpak sandbox permissions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.appimage.org/"&gt;AppImage documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-first-linux-frustration"&gt;Your first Linux frustration&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/find-what-is-filling-your-linux-disk"&gt;Find what is filling your disk&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/the-app-you-wish-had-a-linux-version"&gt;The app you wish had a Linux version&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>RAID Is Not a Backup: Availability, Recovery, and What to Do Instead</title><link>https://it.kituwa.com/blogs/blog/raid-is-not-a-backup/</link><pubDate>Sat, 15 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/raid-is-not-a-backup/</guid><description>&lt;p&gt;RAID is a storage technique that combines multiple disks into one logical device. It can keep a system running when a disk fails, and it can improve read performance in some configurations. Those are useful properties. They are not the same as a backup.&lt;/p&gt;
&lt;p&gt;A backup is a separate copy of data that you can restore after deletion, corruption, ransomware, a bad update, a fire, or a failed migration. RAID is about &lt;strong&gt;availability&lt;/strong&gt;; backup is about &lt;strong&gt;recovery&lt;/strong&gt;. Confusing the two is how people lose data while their disks are still “healthy.”&lt;/p&gt;
&lt;h2 id="what-raid-can-do"&gt;What RAID can do&lt;/h2&gt;
&lt;p&gt;RAID can provide redundancy or performance depending on the level:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;RAID 0&lt;/strong&gt; stripes data across disks for performance. It has no redundancy; one disk failure can lose the array.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;RAID 1&lt;/strong&gt; mirrors data across two or more disks. It can survive some disk failures, depending on how many mirrors remain.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;RAID 5&lt;/strong&gt; uses parity across at least three disks. It can survive one disk failure in a healthy array.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;RAID 6&lt;/strong&gt; uses dual parity and can survive two disk failures in a healthy array.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;RAID 10&lt;/strong&gt; combines mirroring and striping, often with good performance and redundancy, at the cost of usable capacity.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The exact behavior depends on the implementation, the number of disks, the controller, and the array state. Do not assume every RAID layout behaves the same way.&lt;/p&gt;
&lt;h2 id="what-raid-cannot-do"&gt;What RAID cannot do&lt;/h2&gt;
&lt;p&gt;RAID does not protect against:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Accidental deletion.&lt;/strong&gt; If you delete a file, the array mirrors or writes the deletion.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Ransomware or malicious changes.&lt;/strong&gt; The array does not keep a historical copy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Filesystem corruption or a bad write.&lt;/strong&gt; The redundancy may preserve the damaged state.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A bad controller, cable, or firmware bug.&lt;/strong&gt; A single logical failure domain can affect every disk.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fire, theft, flood, or power damage.&lt;/strong&gt; The disks are usually in the same place.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A botched rebuild.&lt;/strong&gt; Rebuilds put stress on remaining disks and can fail.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;RAID can keep a service online while you replace a disk. It cannot take you back to yesterday.&lt;/p&gt;
&lt;h2 id="rebuild-is-not-restore"&gt;Rebuild is not restore&lt;/h2&gt;
&lt;p&gt;When a disk fails, a RAID array may rebuild redundancy onto a replacement disk. That process is not a file-level restore. It reconstructs the array state from the surviving disks and parity. If the data was already wrong, deleted, or encrypted by malware, the rebuild preserves that state.&lt;/p&gt;
&lt;p&gt;A rebuild can also take hours or days, depending on disk size and load. During that window, the array may be more vulnerable. Do not treat “the rebuild completed” as proof that your data is recoverable.&lt;/p&gt;
&lt;h2 id="read-only-health-checks"&gt;Read-only health checks&lt;/h2&gt;
&lt;p&gt;On Linux software RAID, these commands are read-only and useful for understanding the array:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-bash"&gt;cat /proc/mdstat
sudo mdadm --detail /dev/mdX
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Replace &lt;code&gt;/dev/mdX&lt;/code&gt; with the array device. &lt;code&gt;mdstat&lt;/code&gt; shows the array state and member disks; &lt;code&gt;mdadm --detail&lt;/code&gt; shows the RAID level, state, and device roles. Read the output carefully. Do not run repair, grow, or remove commands until you understand the array and have a backup.&lt;/p&gt;
&lt;h2 id="what-a-backup-looks-like"&gt;What a backup looks like&lt;/h2&gt;
&lt;p&gt;A backup is a separate copy with a restore path. A practical plan includes:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;A separate copy&lt;/strong&gt; on a different device from the working array.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A second copy&lt;/strong&gt; on a different medium or location.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An off-site copy&lt;/strong&gt; for fire, theft, or site loss.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A schedule&lt;/strong&gt; that matches how much data you can afford to lose.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A restore test&lt;/strong&gt; with a real file, into a new destination.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Encryption and key management&lt;/strong&gt; if the backup leaves your control.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The 3-2-1 rule is a starting point: three copies, two media types, one off-site. It is not a guarantee; you still need to test restores and protect the backup from the same threats.&lt;/p&gt;
&lt;h2 id="raid-plus-backup"&gt;RAID plus backup&lt;/h2&gt;
&lt;p&gt;RAID and backup solve different problems, and they work well together:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;RAID keeps the service available through some disk failures.&lt;/li&gt;
&lt;li&gt;Backup lets you recover from deletion, corruption, ransomware, and site loss.&lt;/li&gt;
&lt;li&gt;A spare disk and a documented replacement procedure reduce downtime.&lt;/li&gt;
&lt;li&gt;A tested restore procedure reduces panic.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you have RAID but no backup, you have availability without recovery. If you have a backup but no RAID, you may have more downtime but you can still recover. Most important data deserves both, plus an off-site copy.&lt;/p&gt;
&lt;h2 id="a-short-checklist"&gt;A short checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ I know which RAID level I am running and what it can survive.&lt;/li&gt;
&lt;li&gt;☐ I know how to read the array state without changing it.&lt;/li&gt;
&lt;li&gt;☐ I have a spare disk or a replacement plan.&lt;/li&gt;
&lt;li&gt;☐ I have a separate backup, not just a mirror.&lt;/li&gt;
&lt;li&gt;☐ One backup copy is off-site or offline.&lt;/li&gt;
&lt;li&gt;☐ I have tested a restore of a real file.&lt;/li&gt;
&lt;li&gt;☐ I have documented the rebuild and restore procedures.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;p&gt;All links checked 2026-11-05.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Linux kernel — software RAID (md): &lt;a href="https://docs.kernel.org/admin-guide/md.html"&gt;https://docs.kernel.org/admin-guide/md.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;mdadm(8)&lt;/code&gt; manual: &lt;a href="https://man7.org/linux/man-pages/man8/mdadm.8.html"&gt;https://man7.org/linux/man-pages/man8/mdadm.8.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Ubuntu — backups and restore planning: &lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;https://ubuntu.com/server/docs/how-to/backups&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-a-second-opinion-on-the-array"&gt;Need a second opinion on the array?&lt;/h2&gt;
&lt;p&gt;If you are unsure what your RAID level can survive, or whether your backup is actually restorable, Kituwa can review the setup with you. Start with the read-only health checks and the checklist above.&lt;/p&gt;</description></item><item><title>Your first Linux frustration</title><link>https://it.kituwa.com/blogs/blog/your-first-linux-frustration/</link><pubDate>Fri, 14 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/your-first-linux-frustration/</guid><description>&lt;p&gt;Your first Linux frustration is usually not a broken computer. It is a permission message, an app that will not install, a printer that worked yesterday, or a word you have never seen.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Your first Linux frustration&lt;/li&gt;
&lt;li&gt;It has a learnable cause.&lt;/li&gt;
&lt;li&gt;Permissions — Read the exact message&lt;/li&gt;
&lt;li&gt;App installs — Different sources&lt;/li&gt;
&lt;li&gt;Printers — Drivers + discovery&lt;/li&gt;
&lt;li&gt;Jargon — Compressed docs&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="check-the-assumptions"&gt;Check the assumptions&lt;/h3&gt;
&lt;p&gt;Permissions exist to stop one user or program from changing everything. Package formats have different sources and update paths. Printers depend on drivers and network discovery. Jargon is compressed documentation, not a secret handshake.&lt;/p&gt;
&lt;h3 id="step-2-what-to-check"&gt;Step 2: what to check&lt;/h3&gt;
&lt;p&gt;None of that means you are “bad at computers”. It means you met a new system with its own rules. The useful next step is to read the exact message, search the exact wording, and change one thing at a time.&lt;/p&gt;
&lt;h3 id="verify-the-result"&gt;Verify the result&lt;/h3&gt;
&lt;p&gt;Test the change on a spare device or virtual machine first. Check the exact behavior you care about, not just whether the screen looks right. Record what you tested and what you expected.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;What was your first stumbling block — and what tip would you give another beginner?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ It has a learnable cause.&lt;/li&gt;
&lt;li&gt;☐ Permissions — Read the exact message&lt;/li&gt;
&lt;li&gt;☐ App installs — Different sources&lt;/li&gt;
&lt;li&gt;☐ Printers — Drivers + discovery&lt;/li&gt;
&lt;li&gt;☐ Jargon — Compressed docs&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Your first Linux frustration is usually not a broken computer.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/"&gt;Linux man-pages — user and permission commands&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://documentation.ubuntu.com/"&gt;Ubuntu documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-home-folder-backup-you-can-verify"&gt;A home folder backup you can verify&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/apt-flatpak-appimage"&gt;APT, Flatpak, AppImage&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/find-what-is-filling-your-linux-disk"&gt;Find what is filling your disk&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>A home folder backup you can verify</title><link>https://it.kituwa.com/blogs/blog/a-home-folder-backup-you-can-verify/</link><pubDate>Thu, 13 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/a-home-folder-backup-you-can-verify/</guid><description>&lt;p&gt;A backup you never restore is a hope, not a verified backup. Test the whole path with one small folder.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A backup you can verify&lt;/li&gt;
&lt;li&gt;Copy, check, restore.&lt;/li&gt;
&lt;li&gt;COPY&lt;/li&gt;
&lt;li&gt;RESTORE&lt;/li&gt;
&lt;li&gt;Copy to a separate drive&lt;/li&gt;
&lt;li&gt;Check the copy&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="prove-the-restore"&gt;Prove the restore&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Pick an expendable test folder with a few files.&lt;/li&gt;
&lt;li&gt;Copy it to an external drive. Use a tool you understand; check the copy completed without errors.&lt;/li&gt;
&lt;li&gt;Compare what arrived: file count, sizes, and open a couple of files from the external drive.&lt;/li&gt;
&lt;li&gt;Eject or unmount the drive safely, then reconnect it.&lt;/li&gt;
&lt;li&gt;Restore the folder into a new location and open a file. Do not overwrite the original.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="protect-the-data-first"&gt;Protect the data first&lt;/h3&gt;
&lt;p&gt;That last step is the one people skip. Copying is only one part of a backup plan. Also decide how often you copy, how many versions you keep, and where the second copy lives. A drive in the same bag as the laptop travels with the same risk.&lt;/p&gt;
&lt;h3 id="check-rsync"&gt;Check &lt;code&gt;rsync&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;On Linux, a file manager copy is enough for this test; &lt;code&gt;rsync&lt;/code&gt; is useful later for repeatable jobs. Just do not run a command you cannot explain.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Test one expendable file today. Did the restore open?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/li&gt;
&lt;li&gt;Never testing a restore of a real file.&lt;/li&gt;
&lt;li&gt;Keeping the only copy on the same device or in the same location.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ A backup you can verify&lt;/li&gt;
&lt;li&gt;☐ Copy, check, restore.&lt;/li&gt;
&lt;li&gt;☐ COPY&lt;/li&gt;
&lt;li&gt;☐ RESTORE&lt;/li&gt;
&lt;li&gt;☐ Copy to a separate drive&lt;/li&gt;
&lt;li&gt;☐ Check the copy&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;A backup you never restore is a hope, not a verified backup.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Treating RAID, sync, or a cloud gallery as a complete backup.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;Ubuntu — backups and restore planning&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://man7.org/linux/man-pages/man1/rsync.1.html"&gt;man rsync&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/linux-mint-vs-ubuntu-desktop"&gt;Linux Mint vs Ubuntu Desktop&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-first-linux-frustration"&gt;Your first Linux frustration&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/apt-flatpak-appimage"&gt;APT, Flatpak, AppImage&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Linux Mint vs Ubuntu Desktop</title><link>https://it.kituwa.com/blogs/blog/linux-mint-vs-ubuntu-desktop/</link><pubDate>Wed, 12 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/linux-mint-vs-ubuntu-desktop/</guid><description>&lt;p&gt;Linux Mint and Ubuntu Desktop both get you to a working desktop, but they make different trade-offs.&lt;/p&gt;
&lt;p&gt;This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.&lt;/p&gt;
&lt;h2 id="what-this-guide-covers"&gt;What this guide covers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Linux Mint vs Ubuntu Desktop&lt;/li&gt;
&lt;li&gt;Two desktops, three trade-offs.&lt;/li&gt;
&lt;li&gt;Linux Mint&lt;/li&gt;
&lt;li&gt;Ubuntu Desktop&lt;/li&gt;
&lt;li&gt;Layout — Traditional panel — Top bar + dock&lt;/li&gt;
&lt;li&gt;Software — Flatpak-first — Snaps + .deb&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;
&lt;p&gt;The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.&lt;/p&gt;
&lt;h2 id="a-practical-walkthrough"&gt;A practical walkthrough&lt;/h2&gt;
&lt;h3 id="verify-the-key-path"&gt;Verify the key path&lt;/h3&gt;
&lt;p&gt;Daily workflow: Mint's Cinnamon layout will feel familiar if you are coming from Windows. Ubuntu's GNOME is more keyboard- and gesture-oriented.&lt;/p&gt;
&lt;h3 id="use-the-supported-update-path"&gt;Use the supported update path&lt;/h3&gt;
&lt;p&gt;Desktop experience: Mint adds its own Update Manager, Software Manager, and Timeshift snapshot tool. Ubuntu ships a more opinionated GNOME setup.&lt;/p&gt;
&lt;h3 id="step-3-what-to-check"&gt;Step 3: what to check&lt;/h3&gt;
&lt;p&gt;Software availability: Mint's current line is built on an Ubuntu LTS base, so most Ubuntu packages and guides apply. Mint enables Flatpak and disables the Snap Store by default; Ubuntu uses snaps for some first-party apps. Both can run .deb packages and AppImages.&lt;/p&gt;
&lt;h3 id="step-4-what-to-check"&gt;Step 4: what to check&lt;/h3&gt;
&lt;p&gt;Maintenance: both offer long-term-support releases. Mint follows Ubuntu LTS bases; Ubuntu also offers interim releases. Check the current official release pages before you download, and do not choose by version number alone.&lt;/p&gt;
&lt;h3 id="step-5-what-to-check"&gt;Step 5: what to check&lt;/h3&gt;
&lt;p&gt;A compatibility-first recommendation: if a vendor or workplace explicitly supports Ubuntu, start there. If you want a familiar layout, Flatpak-first software, and a gentler first week, try Mint from a live USB.&lt;/p&gt;
&lt;h2 id="your-turn"&gt;Your turn&lt;/h2&gt;
&lt;p&gt;Which matters more to you: a familiar layout or following mainstream Ubuntu tutorials?&lt;/p&gt;
&lt;h2 id="what-to-verify"&gt;What to verify&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Use the official documentation for the exact version you run.&lt;/li&gt;
&lt;li&gt;Test on a spare device or virtual machine before changing a working system.&lt;/li&gt;
&lt;li&gt;Keep a backup and a rollback path.&lt;/li&gt;
&lt;li&gt;Record what changed and how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="common-mistakes"&gt;Common mistakes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Changing more than one thing at a time.&lt;/li&gt;
&lt;li&gt;Skipping the official documentation for your version.&lt;/li&gt;
&lt;li&gt;Assuming a warning means you should delete or reset data.&lt;/li&gt;
&lt;li&gt;Not recording what you changed or how you verified it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Two desktops, three trade-offs.&lt;/li&gt;
&lt;li&gt;☐ Linux Mint&lt;/li&gt;
&lt;li&gt;☐ Ubuntu Desktop&lt;/li&gt;
&lt;li&gt;☐ Layout — Traditional panel — Top bar + dock&lt;/li&gt;
&lt;li&gt;☐ Software — Flatpak-first — Snaps + .deb&lt;/li&gt;
&lt;li&gt;☐ Maintenance — Ubuntu LTS base — LTS + interim&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="faq"&gt;FAQ&lt;/h2&gt;
&lt;h3 id="what-is-the-first-step"&gt;What is the first step?&lt;/h3&gt;
&lt;p&gt;Linux Mint and Ubuntu Desktop both get you to a working desktop, but they make different trade-offs.&lt;/p&gt;
&lt;h3 id="what-should-i-avoid"&gt;What should I avoid?&lt;/h3&gt;
&lt;p&gt;Changing more than one thing at a time.&lt;/p&gt;
&lt;h3 id="where-can-i-verify-the-current-details"&gt;Where can I verify the current details?&lt;/h3&gt;
&lt;p&gt;Use the official references below; versions and interfaces change.&lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://linuxmint.com/download_all.php"&gt;Linux Mint — supported releases&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/desktop"&gt;Ubuntu Desktop&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ubuntu.com/about/release-cycle"&gt;Ubuntu release cycle&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="related-guides"&gt;Related guides&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/ssd-or-ram-which-upgrade-helps"&gt;SSD or RAM: which upgrade helps?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/a-home-folder-backup-you-can-verify"&gt;A home folder backup you can verify&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://it.kituwa.com/blogs/blog/your-first-linux-frustration"&gt;Your first Linux frustration&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-help"&gt;Need help?&lt;/h2&gt;
&lt;p&gt;If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.&lt;/p&gt;</description></item><item><title>Turn an Old Laptop into a Home Server: A Safe First Build</title><link>https://it.kituwa.com/blogs/blog/old-laptop-home-server-first-build/</link><pubDate>Wed, 12 Nov 2025 09:00:00 -0500</pubDate><guid>https://it.kituwa.com/blogs/blog/old-laptop-home-server-first-build/</guid><description>&lt;p&gt;An old laptop can be a useful home server. It has a built-in screen and keyboard for setup, a battery that can ride out short power blips, and often enough CPU and RAM for a dashboard, a backup target, or a small file share. It is also a machine with constraints: limited cooling, limited drive bays, a battery that may be aging, and firmware that may not be designed for unattended operation.&lt;/p&gt;
&lt;p&gt;This guide is a safe first build. It focuses on suitability checks, a wired network, one modest service, and the maintenance habits that keep the machine from becoming a liability. It is not a promise that every laptop should run 24/7.&lt;/p&gt;
&lt;h2 id="1-decide-whether-the-laptop-is-suitable"&gt;1. Decide whether the laptop is suitable&lt;/h2&gt;
&lt;p&gt;Before installing anything, inspect the hardware.&lt;/p&gt;
&lt;h3 id="battery-check"&gt;Battery check&lt;/h3&gt;
&lt;p&gt;Look for swelling, deformation, a bulging trackpad, or a case that no longer sits flat. A swollen lithium battery is a safety issue. Stop using the machine, disconnect power, and dispose of the battery through a proper battery-recycling channel. Do not leave a swollen battery charging unattended.&lt;/p&gt;
&lt;p&gt;If the battery is healthy, decide whether you want it installed. A battery can act as a small UPS, but it also adds heat and another aging component. Some people remove the battery and run on AC; only do that if the model supports it and you understand the firmware behavior.&lt;/p&gt;
&lt;h3 id="storage-health"&gt;Storage health&lt;/h3&gt;
&lt;p&gt;Check the drive before trusting it with data. On Linux, &lt;code&gt;smartctl&lt;/code&gt; from the &lt;code&gt;smartmontools&lt;/code&gt; package can read SMART health data when the drive and adapter expose it:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-bash"&gt;sudo smartctl -a /dev/sdX
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Replace &lt;code&gt;/dev/sdX&lt;/code&gt; with the correct whole device. Read the health summary and the error counters; do not treat one number as a complete diagnosis. If the drive is failing, replace it before building the server.&lt;/p&gt;
&lt;h3 id="cooling-and-placement"&gt;Cooling and placement&lt;/h3&gt;
&lt;p&gt;A laptop on a bed, carpet, or soft bag will overheat. Put it on a hard, ventilated surface. Keep the fan intake and exhaust clear. If the fan is noisy or the machine throttles under light load, clean the cooling system or choose a different machine.&lt;/p&gt;
&lt;h3 id="ports-and-network"&gt;Ports and network&lt;/h3&gt;
&lt;p&gt;Wired Ethernet is preferable for a server. It is less sensitive to interference, does not depend on Wi-Fi credentials, and is easier to keep stable across reboots. If the laptop has no Ethernet port, a USB Ethernet adapter can work, but test it before relying on it.&lt;/p&gt;
&lt;h2 id="2-pick-one-modest-first-job"&gt;2. Pick one modest first job&lt;/h2&gt;
&lt;p&gt;Do not start with five services. Pick one job that solves a real annoyance:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A private dashboard for links and service status.&lt;/li&gt;
&lt;li&gt;A backup target for one computer.&lt;/li&gt;
&lt;li&gt;A local file share for documents or photos.&lt;/li&gt;
&lt;li&gt;A small uptime monitor for your network.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A dashboard is usually the gentlest start. It is useful immediately, it does not need much storage, and it gives you a reason to learn the server's update and backup routine. Home Assistant is another popular first project, but it has a larger surface area and more integrations to maintain. Choose one and finish it before adding another.&lt;/p&gt;
&lt;h2 id="3-install-a-server-operating-system"&gt;3. Install a server operating system&lt;/h2&gt;
&lt;p&gt;Ubuntu Server is a common choice with long-term-support releases and extensive documentation. The official installation tutorial walks through the installer, storage, user account, and OpenSSH setup:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Ubuntu Server installation tutorial: &lt;a href="https://ubuntu.com/tutorials/install-ubuntu-server"&gt;https://ubuntu.com/tutorials/install-ubuntu-server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Ubuntu Server documentation: &lt;a href="https://ubuntu.com/server/docs/installation"&gt;https://ubuntu.com/server/docs/installation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;During installation:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Use a clear hostname and a strong admin account.&lt;/li&gt;
&lt;li&gt;Install OpenSSH only if you need remote shell access.&lt;/li&gt;
&lt;li&gt;Read the storage screen carefully. If you do not understand an option, stop and ask; the installer can erase disks.&lt;/li&gt;
&lt;li&gt;Do not expose the machine to the public internet during setup.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you prefer a different distribution, use its official server documentation. Do not paste partitioning or bootloader commands from an unrelated guide.&lt;/p&gt;
&lt;h2 id="4-make-the-network-predictable"&gt;4. Make the network predictable&lt;/h2&gt;
&lt;p&gt;A server that changes IP addresses is annoying to use. The simplest fix is often a DHCP reservation on your router: find the laptop's MAC address and reserve a fixed address. The alternative is a static address configured on the server, but that requires understanding your network's gateway, subnet, and DNS settings.&lt;/p&gt;
&lt;p&gt;Keep the first build on your trusted local network. Do not forward ports or publish the service to the internet until you understand authentication, updates, backups, and the firewall. Ubuntu's firewall documentation covers UFW if you want a host firewall:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Ubuntu Server firewall: &lt;a href="https://ubuntu.com/server/docs/security-firewall"&gt;https://ubuntu.com/server/docs/security-firewall&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="5-handle-the-lid-and-power-behavior"&gt;5. Handle the lid and power behavior&lt;/h2&gt;
&lt;p&gt;A laptop may suspend when you close the lid. That is not useful for a server. &lt;code&gt;systemd-logind&lt;/code&gt; documents the lid-switch settings in &lt;code&gt;logind.conf&lt;/code&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;systemd-logind&lt;/code&gt; configuration: &lt;a href="https://www.freedesktop.org/software/systemd/man/latest/logind.conf.html"&gt;https://www.freedesktop.org/software/systemd/man/latest/logind.conf.html&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;On many systems, the setting is in &lt;code&gt;/etc/systemd/logind.conf&lt;/code&gt;:&lt;/p&gt;
&lt;pre&gt;&lt;code class="language-ini"&gt;HandleLidSwitch=ignore
HandleLidSwitchExternalPower=ignore
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Read the documentation before changing these values, and test the result. Restarting &lt;code&gt;systemd-logind&lt;/code&gt; can affect active sessions, so do it deliberately. If the laptop still suspends, check the desktop environment's power settings or the firmware.&lt;/p&gt;
&lt;p&gt;Also check what happens after a power loss. Some firmware has a “restore on AC power” option; others do not. Test it with a non-critical workload before you depend on it.&lt;/p&gt;
&lt;h2 id="6-test-storage-updates-and-remote-access"&gt;6. Test storage, updates, and remote access&lt;/h2&gt;
&lt;p&gt;Before adding the first app:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Confirm the drive is detected and healthy.&lt;/li&gt;
&lt;li&gt;Apply the supported updates and reboot if required.&lt;/li&gt;
&lt;li&gt;Confirm SSH works with a key, not just a password, if you enabled it.&lt;/li&gt;
&lt;li&gt;Confirm the machine comes back after a reboot.&lt;/li&gt;
&lt;li&gt;Confirm you can reach it from another device on the LAN.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Ubuntu's OpenSSH documentation covers key-based access and server configuration:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Ubuntu Server OpenSSH: &lt;a href="https://ubuntu.com/server/docs/service-openssh"&gt;https://ubuntu.com/server/docs/service-openssh&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Do not enable passwordless public SSH or broad port forwarding as a shortcut. Keep remote access on the LAN or behind a VPN until you have a specific reason and a plan.&lt;/p&gt;
&lt;h2 id="7-add-one-app-and-one-backup"&gt;7. Add one app and one backup&lt;/h2&gt;
&lt;p&gt;Install one service, then immediately write down:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Where its data lives.&lt;/li&gt;
&lt;li&gt;How it is updated.&lt;/li&gt;
&lt;li&gt;How it is backed up.&lt;/li&gt;
&lt;li&gt;How you restore it.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If the service uses Docker, named volumes or bind mounts hold the persistent data. Back up the data, not just the container. If it uses a database, use the database's documented backup method. Test a restore into a separate location.&lt;/p&gt;
&lt;p&gt;A backup on the same laptop is not enough. Keep a copy on a separate device, and check that the copy opens. Ubuntu's backup guidance is a good starting point:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Ubuntu backups and restore planning: &lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;https://ubuntu.com/server/docs/how-to/backups&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="8-maintain-it-like-a-server"&gt;8. Maintain it like a server&lt;/h2&gt;
&lt;p&gt;A home server is not finished when the app loads. Put a small routine in place:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Apply supported updates on a schedule.&lt;/li&gt;
&lt;li&gt;Reboot when required and confirm services return.&lt;/li&gt;
&lt;li&gt;Check disk space and SMART health.&lt;/li&gt;
&lt;li&gt;Check the backup job and restore one file periodically.&lt;/li&gt;
&lt;li&gt;Review logs for repeated errors, not just the last line.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If the laptop is noisy, hot, unstable, or has a damaged battery, stop treating it as a server. A used mini PC or a small tower may be a better long-term host. The point of the first build is to learn the pattern, not to force old hardware to do a job it cannot do safely.&lt;/p&gt;
&lt;h2 id="quick-checklist"&gt;Quick checklist&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;☐ Battery checked; no swelling or damage.&lt;/li&gt;
&lt;li&gt;☐ Drive health checked.&lt;/li&gt;
&lt;li&gt;☐ Hard, ventilated surface; fan clear.&lt;/li&gt;
&lt;li&gt;☐ Wired Ethernet tested.&lt;/li&gt;
&lt;li&gt;☐ One first job chosen.&lt;/li&gt;
&lt;li&gt;☐ Server OS installed from official media.&lt;/li&gt;
&lt;li&gt;☐ DHCP reservation or static address documented.&lt;/li&gt;
&lt;li&gt;☐ Lid and power-loss behavior tested.&lt;/li&gt;
&lt;li&gt;☐ Updates applied; reboot tested.&lt;/li&gt;
&lt;li&gt;☐ SSH keys and LAN-only access verified.&lt;/li&gt;
&lt;li&gt;☐ App data location documented.&lt;/li&gt;
&lt;li&gt;☐ Backup copied off the host and restore tested.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;p&gt;All links checked 2026-11-05.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Ubuntu Server installation tutorial: &lt;a href="https://ubuntu.com/tutorials/install-ubuntu-server"&gt;https://ubuntu.com/tutorials/install-ubuntu-server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Ubuntu Server documentation: &lt;a href="https://ubuntu.com/server/docs/installation"&gt;https://ubuntu.com/server/docs/installation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Ubuntu Server firewall: &lt;a href="https://ubuntu.com/server/docs/security-firewall"&gt;https://ubuntu.com/server/docs/security-firewall&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Ubuntu Server OpenSSH: &lt;a href="https://ubuntu.com/server/docs/service-openssh"&gt;https://ubuntu.com/server/docs/service-openssh&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Ubuntu backups and restore planning: &lt;a href="https://ubuntu.com/server/docs/how-to/backups"&gt;https://ubuntu.com/server/docs/how-to/backups&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;systemd-logind lid behavior: &lt;a href="https://www.freedesktop.org/software/systemd/man/latest/logind.conf.html"&gt;https://www.freedesktop.org/software/systemd/man/latest/logind.conf.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;smartmontools: &lt;a href="https://www.smartmontools.org/"&gt;https://www.smartmontools.org/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="need-a-hand-scoping-the-first-build"&gt;Need a hand scoping the first build?&lt;/h2&gt;
&lt;p&gt;If you want help checking the hardware or choosing the first service, Kituwa can review the plan with you. Start with the checklist above; it will make the conversation much more useful.&lt;/p&gt;</description></item></channel></rss>