https://blog.lazy-evaluation.net/deContents © 2025 <a href="mailto:dzu@member.fsf.org">Detlev Zundel</a> Wed, 10 Dec 2025 16:11:11 GMTNikola (getnikola.com)http://blogs.law.harvard.edu/tech/rsshttps://blog.lazy-evaluation.net/de/posts/linux/fwupdate-linux.html?pk_campaign=feedDetlev Zundel<div><div style="text-align:center" class="imageblock" id="org3891fba"> <div id="orgccb53a3" class="figure"> <p><img src="https://blog.lazy-evaluation.net/de/images/nvme-logo.png" alt="nvme-logo.png" title="NVMe logo" align="middle" width="250"> </p> </div> </div> <p><a href="https://blog.lazy-evaluation.net/de/posts/linux/fwupdate-linux.html?pk_campaign=feed">Weiterlesen…</a> (5 min verbleiben zum Lesen)</p></div>https://blog.lazy-evaluation.net/de/posts/linux/fwupdate-linux.htmlTue, 05 Aug 2025 22:01:27 GMThttps://blog.lazy-evaluation.net/de/posts/linux/nvme-fwupdate.html?pk_campaign=feedDetlev Zundel<div><div style="text-align:center" class="imageblock" id="orgfa02f3a"> <div id="org04c176d" class="figure"> <p><img src="https://blog.lazy-evaluation.net/de/images/nvme-logo.png" alt="nvme-logo.png" title="NVMe logo" align="middle" width="250"> </p> </div> </div> <p> As the NAND storage technology reaches speeds that cannot be satiated with SATA anymore, the modern SSDs are attached over <a href="https://en.wikipedia.org/wiki/PCI_Express">PCIe</a>, the descendant of the very successful <a href="https://en.wikipedia.org/wiki/Peripheral_Component_Interconnect">Peripheral Component Interconnect</a> standard that allowed for many extension cards in the IBM PC ecosystem. But where most PCI cards could not be software upgraded in the field, the question on how to update firmware on attached PCI devices is not obviously standardized (or am I missing something?). So under Windows, the manufacturers of NVMe modules deliver their proprietary update tool, but what do we do in a Free Operating system like GNU/Linux? </p> <p> In this blog post I will take a quick look at how I was able to upgrade the firmware of my <b>Kingston SA2000M8250G</b> NVMe drive in my desktop system. </p> <p><a href="https://blog.lazy-evaluation.net/de/posts/linux/nvme-fwupdate.html?pk_campaign=feed">Weiterlesen…</a> (3 min verbleiben zum Lesen)</p></div>https://blog.lazy-evaluation.net/de/posts/linux/nvme-fwupdate.htmlThu, 03 Apr 2025 22:01:27 GMThttps://blog.lazy-evaluation.net/de/posts/reclaiming-vm-space-virtualbox.html?pk_campaign=feedDetlev Zundel<div><img alt="Compress Image" class="align-center" src="https://blog.lazy-evaluation.net/images/compress.png" style="width: 300px;"> <p>Creating a virtual machine requires specifying the amount of space to allocate for the virtual hard disk as one of the first steps. Dreading the notorious "not enough disk space" message, one usually aims to be on the safe side and reserves a generous amount at this stage. If the assignment is done in a static fashion then the allocated space is immediately claimed from the underlying file system and one thus has to come up with a pretty good guess in order not to waste space. Thankfully most VM solutions allow dynamic allocations which can grow on demand limited only by an upper bound making this a very attractive choice.</p> <p>A newly created VM with such an dynamic disk image indeed starts out nice and space saving but over time the image will eventually take up all the committed underlying disk space even though the VM reports to use only a subset of it. Reflecting on why this is the case leads us to an elegant setup reclaiming unused storage space on the host system.</p> <p><a href="https://blog.lazy-evaluation.net/de/posts/reclaiming-vm-space-virtualbox.html?pk_campaign=feed">Weiterlesen…</a> (6 min verbleiben zum Lesen)</p></div>https://blog.lazy-evaluation.net/de/posts/reclaiming-vm-space-virtualbox.htmlMon, 20 Jan 2020 21:14:32 GMT