<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Bootloading operating systems, some opening bits and the current state in personal computing</title>
	<atom:link href="http://thetarpit.org/2019/bootloading-operating-systems/feed" rel="self" type="application/rss+xml" />
	<link>http://thetarpit.org/2019/bootloading-operating-systems</link>
	<description>"Now I feel like I know less about what that blog is about than I did before."</description>
	<pubDate>Sun, 12 Apr 2026 16:52:49 +0000</pubDate>
	<generator>http://thetarpit.org</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: On open sores supply chainz &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2019/bootloading-operating-systems#comment-4071</link>
		<dc:creator>On open sores supply chainz &#171; The Tar Pit</dc:creator>
		<pubDate>Thu, 20 Apr 2023 18:06:56 +0000</pubDate>
		<guid isPermaLink="false">http://thetarpit.org/?p=346#comment-4071</guid>
		<description>[...] likely want to scrape the second-hand markets for items lacking the usual deadweights such as UEFI, ME, TPM and other baked-in modules used for imperial vetting. This approach is especially useful [...]</description>
		<content:encoded><![CDATA[<p>[...] likely want to scrape the second-hand markets for items lacking the usual deadweights such as UEFI, ME, TPM and other baked-in modules used for imperial vetting. This approach is especially useful [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: On intellectual feudalism &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2019/bootloading-operating-systems#comment-3011</link>
		<dc:creator>On intellectual feudalism &#171; The Tar Pit</dc:creator>
		<pubDate>Sun, 18 Sep 2022 16:19:07 +0000</pubDate>
		<guid isPermaLink="false">http://thetarpit.org/?p=346#comment-3011</guid>
		<description>[...] motherboards without EFI, but that's only a small part of the taint. Now do you even begin to grasp the knowledge needed to [...]</description>
		<content:encoded><![CDATA[<p>[...] motherboards without EFI, but that's only a small part of the taint. Now do you even begin to grasp the knowledge needed to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 2019 in review &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2019/bootloading-operating-systems#comment-423</link>
		<dc:creator>2019 in review &#171; The Tar Pit</dc:creator>
		<pubDate>Wed, 14 Oct 2020 06:46:04 +0000</pubDate>
		<guid isPermaLink="false">http://thetarpit.org/?p=346#comment-423</guid>
		<description>[...] about December, having spent most of it fixing various personal issues and some time examining the sad state of personal computers, with a particular focus on the bootloading stage. Which concludes 2019, which looks like a great [...]</description>
		<content:encoded><![CDATA[<p>[...] about December, having spent most of it fixing various personal issues and some time examining the sad state of personal computers, with a particular focus on the bootloading stage. Which concludes 2019, which looks like a great [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TMSR OS, January 2020 Statement &#171; Dorion Mode</title>
		<link>http://thetarpit.org/2019/bootloading-operating-systems#comment-232</link>
		<dc:creator>TMSR OS, January 2020 Statement &#171; Dorion Mode</dc:creator>
		<pubDate>Mon, 27 Jan 2020 04:12:49 +0000</pubDate>
		<guid isPermaLink="false">http://thetarpit.org/?p=346#comment-232</guid>
		<description>[...] stepped up to the plate here and published his initial report on Bootlading Operating Systems December 31st, through which, the decision to support a dozen or two motherboards per architecture [...]</description>
		<content:encoded><![CDATA[<p>[...] stepped up to the plate here and published his initial report on Bootlading Operating Systems December 31st, through which, the decision to support a dozen or two motherboards per architecture [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spyked</title>
		<link>http://thetarpit.org/2019/bootloading-operating-systems#comment-228</link>
		<dc:creator>spyked</dc:creator>
		<pubDate>Thu, 23 Jan 2020 09:34:46 +0000</pubDate>
		<guid isPermaLink="false">http://thetarpit.org/?p=346#comment-228</guid>
		<description>&#62; how many of those named distributors have you looked into so far ?

I haven't looked systematically recently, will definitely have to give it a (documented, this time) go. Last time I looked circa four months ago, &lt;a href="https://www.varia-store.com/" rel="nofollow"&gt;Varia&lt;/a&gt; were the only ones selling APU1 units, most (all?) others only had APU2 and above.

Anyway, I'd prefer not dealing with Swiss import/export taxes and the likes if possible, so I'll look deeper at this in February.

&#62; I'm open to splitting the list with you to accelerate the hunt.

Sure, that'd work, though I think I'd be able to do it reasonably fast (~1 week?) once I get to it. Notice that the list has many duplicates, so as a matter of fact there are only a few EU providers, another few in the US etc.

&#62; The x200 that I'm most familiar with use Core 2 Duo Penryn.

I'll look into x200 as well, the &lt;a href="http://archive.is/1DWrh" rel="nofollow"&gt;Coreboot page&lt;/a&gt; seems to have quite a few details on support. I also have an x220 at home, AFAIK the Coreboot people have struggled for years to get the ME gangrene out. Perhaps worth taking a brief look at that as well.</description>
		<content:encoded><![CDATA[<p>&gt; how many of those named distributors have you looked into so far ?</p>
<p>I haven't looked systematically recently, will definitely have to give it a (documented, this time) go. Last time I looked circa four months ago, <a href="https://www.varia-store.com/" rel="nofollow">Varia</a> were the only ones selling APU1 units, most (all?) others only had APU2 and above.</p>
<p>Anyway, I'd prefer not dealing with Swiss import/export taxes and the likes if possible, so I'll look deeper at this in February.</p>
<p>&gt; I'm open to splitting the list with you to accelerate the hunt.</p>
<p>Sure, that'd work, though I think I'd be able to do it reasonably fast (~1 week?) once I get to it. Notice that the list has many duplicates, so as a matter of fact there are only a few EU providers, another few in the US etc.</p>
<p>&gt; The x200 that I'm most familiar with use Core 2 Duo Penryn.</p>
<p>I'll look into x200 as well, the <a href="http://archive.is/1DWrh" rel="nofollow">Coreboot page</a> seems to have quite a few details on support. I also have an x220 at home, AFAIK the Coreboot people have struggled for years to get the ME gangrene out. Perhaps worth taking a brief look at that as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robinson Dorion</title>
		<link>http://thetarpit.org/2019/bootloading-operating-systems#comment-227</link>
		<dc:creator>Robinson Dorion</dc:creator>
		<pubDate>Wed, 22 Jan 2020 18:18:36 +0000</pubDate>
		<guid isPermaLink="false">http://thetarpit.org/?p=346#comment-227</guid>
		<description>&lt;blockquote&gt;
Not even close. 
&lt;/blockquote&gt;

Trinque's &lt;a href="http://trinque.org/2020/01/20/a-republican-os-part-3/" rel="nofollow"&gt;latest hit&lt;/a&gt; further cemented how not even close.

Re APU1, &lt;a href="https://pcengines.ch/apu.htm" rel="nofollow"&gt;pcengines&lt;/a&gt; says it's in production, how many of those named &lt;a href="https://pcengines.ch/order.htm" rel="nofollow"&gt;distributors&lt;/a&gt; have you looked into so far ? I'm open to splitting the list with you to accelerate the hunt.

http://logs.ossasepia.com/log/trilema/2019-12-09#1954653

&lt;blockquote&gt;
Intel started infecting their CPUs with crapware, e.g. Management Engine, as soon as they switched from Core Duo to Core i3/5/7
&lt;/blockquote&gt;

That is my understanding as well. The x200 that I'm most familiar with use Core 2 Duo Penryn.</description>
		<content:encoded><![CDATA[<blockquote><p>
Not even close.
</p></blockquote>
<p>Trinque's <a href="http://trinque.org/2020/01/20/a-republican-os-part-3/" rel="nofollow">latest hit</a> further cemented how not even close.</p>
<p>Re APU1, <a href="https://pcengines.ch/apu.htm" rel="nofollow">pcengines</a> says it's in production, how many of those named <a href="https://pcengines.ch/order.htm" rel="nofollow">distributors</a> have you looked into so far ? I'm open to splitting the list with you to accelerate the hunt.</p>
<p><a href="http://logs.ossasepia.com/log/trilema/2019-12-09#1954653" rel="nofollow">http://logs.ossasepia.com/log/trilema/2019-12-09#1954653</a></p>
<blockquote><p>
Intel started infecting their CPUs with crapware, e.g. Management Engine, as soon as they switched from Core Duo to Core i3/5/7
</p></blockquote>
<p>That is my understanding as well. The x200 that I'm most familiar with use Core 2 Duo Penryn.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spyked</title>
		<link>http://thetarpit.org/2019/bootloading-operating-systems#comment-206</link>
		<dc:creator>spyked</dc:creator>
		<pubDate>Mon, 13 Jan 2020 15:28:02 +0000</pubDate>
		<guid isPermaLink="false">http://thetarpit.org/?p=346#comment-206</guid>
		<description>@&lt;b&gt;Mircea Popescu&lt;/b&gt;: AFAIK right now we only have &lt;a href="http://archive.is/q8meH" rel="nofollow"&gt;APU1&lt;/a&gt; and the IBM x60 board, and sadly the latter is 32-bit only. I have a few more that I could list as "doesn't require EFI", though much of the hardware I have is Intel-based, which I expect will cause some hives among the L1.

Guess I should get a list/table with known-to-work items started soon.

@&lt;b&gt;Robinson Dorion&lt;/b&gt;: I'm happy you enjoyed reading the article!

&gt; Apologies for the delayed comment

I'm off to a slow start this year myself, so I can't really complain.

&gt; Is this "stage 2" program "init" ?

Not even close. The bootloader stage2 is usually found somewhere in /boot, e.g. for Grub it's /boot/grub/core.img and kernel.img -- a decent description of these images can be found &lt;a href="http://archive.is/RKuEq" rel="nofollow"&gt;here&lt;/a&gt;. Not only that, but Grub can dynamically load modules for e.g. filesystems, so that it can look up the Linux kernel image, usually found in /boot/vmlinuz-something. Only after the kernel is loaded, the hardware is probed and configured and the root filesystem is mounted, only then will the kernel launch "init" into execution. All in all a long road, paved by a history of ad-hoc (as opposed to principled, I guess) developments in both hardware and software.

&gt; Start small, build out incrementally, let late comers either scramble of hardware scraps already supported, buy from surplus l1/2 accumulates or invest in extending the support for boards not yet V-ified themselves.

This sounds reasonable IMHO and resonates with footnote 12 above. I believe there's a market there for x86 (64-bit) vintage without EFI, weird BIOSen and so on. For example I've been finding it hard to get ahold of an APU1 and getting it from an in-WoT supplier would be a great win IMHO.

&gt; all Intel is shit

Intel started infecting their CPUs with crapware, e.g. Management Engine, as soon as they switched from Core Duo to Core i3/5/7. I don't know about Nehalems, but Sandy Bridges (the CPUs on which e.g. x220 Thinkpads run) are clearly infected. Still, TMSR-OS would boot on those by virtue of the BIOS not being (completely) stolen by UEFI yet, and perhaps there's lower-criticality applications (gaming, writing) where they'd work.</description>
		<content:encoded><![CDATA[<p>@<b>Mircea Popescu</b>: AFAIK right now we only have <a href="http://archive.is/q8meH" rel="nofollow">APU1</a> and the IBM x60 board, and sadly the latter is 32-bit only. I have a few more that I could list as "doesn't require EFI", though much of the hardware I have is Intel-based, which I expect will cause some hives among the L1.</p>
<p>Guess I should get a list/table with known-to-work items started soon.</p>
<p>@<b>Robinson Dorion</b>: I'm happy you enjoyed reading the article!</p>
<p>> Apologies for the delayed comment</p>
<p>I'm off to a slow start this year myself, so I can't really complain.</p>
<p>> Is this "stage 2" program "init" ?</p>
<p>Not even close. The bootloader stage2 is usually found somewhere in /boot, e.g. for Grub it's /boot/grub/core.img and kernel.img -- a decent description of these images can be found <a href="http://archive.is/RKuEq" rel="nofollow">here</a>. Not only that, but Grub can dynamically load modules for e.g. filesystems, so that it can look up the Linux kernel image, usually found in /boot/vmlinuz-something. Only after the kernel is loaded, the hardware is probed and configured and the root filesystem is mounted, only then will the kernel launch "init" into execution. All in all a long road, paved by a history of ad-hoc (as opposed to principled, I guess) developments in both hardware and software.</p>
<p>> Start small, build out incrementally, let late comers either scramble of hardware scraps already supported, buy from surplus l1/2 accumulates or invest in extending the support for boards not yet V-ified themselves.</p>
<p>This sounds reasonable IMHO and resonates with footnote 12 above. I believe there's a market there for x86 (64-bit) vintage without EFI, weird BIOSen and so on. For example I've been finding it hard to get ahold of an APU1 and getting it from an in-WoT supplier would be a great win IMHO.</p>
<p>> all Intel is shit</p>
<p>Intel started infecting their CPUs with crapware, e.g. Management Engine, as soon as they switched from Core Duo to Core i3/5/7. I don't know about Nehalems, but Sandy Bridges (the CPUs on which e.g. x220 Thinkpads run) are clearly infected. Still, TMSR-OS would boot on those by virtue of the BIOS not being (completely) stolen by UEFI yet, and perhaps there's lower-criticality applications (gaming, writing) where they'd work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robinson Dorion</title>
		<link>http://thetarpit.org/2019/bootloading-operating-systems#comment-205</link>
		<dc:creator>Robinson Dorion</dc:creator>
		<pubDate>Sat, 11 Jan 2020 03:45:28 +0000</pubDate>
		<guid isPermaLink="false">http://thetarpit.org/?p=346#comment-205</guid>
		<description>I really enjoyed this; while I had a decent grasp, really helps to break down the details. Apologies for the delayed comment, I'm getting back to normal this week and cutting down on latency moving forward.

&lt;blockquote&gt;
the bootloader will have to bootstrap itself by loading a "stage 2" program
&lt;/blockquote&gt;

Is this "stage 2" program "init" ?

&lt;blockquote&gt;
The "PC-AT" boot environment presents significant challenges to innovation within the industry.
&lt;/blockquote&gt;

They "just want" &lt;a href="http://ossasepia.com/2018/12/10/my-talk-of-bitcoin-at-reading-uni/?b=discussion&#38;e=sequence.#select" rel="nofollow"&gt;s/innovation/subversion/&lt;/a&gt;.

&lt;blockquote&gt;
I guess a starting point would be to select one or two boards that are both available and supported by Coreboot, genesize all the software required to get the operating system loaded
&lt;/blockquote&gt;

This does look like a good starting point. Start small, build out incrementally, let &lt;a href="http://trilema.com/2014/people-us-dollars-are-not-worth-a-fifth-of-a-bitcent-stop-selling/?b=They%20tend&#38;e=collect#select" rel="nofollow"&gt;late comers&lt;/a&gt; either scramble of hardware scraps already supported, buy from surplus l1/2 accumulates or invest in extending the support for boards not yet V-ified themselves.

&lt;a href="http://fixpoint.welshcomputing.com" rel="nofollow"&gt;Jacob&lt;/a&gt; worked out the process of flashing the x200 thinkpads with Coreboot using chip clips of offline flashing, though those aren't widely available - for sure a scrap market. 

That being said, I've allowed the &lt;a href="http://dorion-mode.com/2019/11/jwrd-computing-the-why-how-what-and-way-forward/#comment-31" rel="nofollow"&gt;all Intel is shit&lt;/a&gt; discussion to slide down priority, probably a good time to revisit prior to selecting the worthy chips to start with.</description>
		<content:encoded><![CDATA[<p>I really enjoyed this; while I had a decent grasp, really helps to break down the details. Apologies for the delayed comment, I'm getting back to normal this week and cutting down on latency moving forward.</p>
<blockquote><p>
the bootloader will have to bootstrap itself by loading a "stage 2" program
</p></blockquote>
<p>Is this "stage 2" program "init" ?</p>
<blockquote><p>
The "PC-AT" boot environment presents significant challenges to innovation within the industry.
</p></blockquote>
<p>They "just want" <a href="http://ossasepia.com/2018/12/10/my-talk-of-bitcoin-at-reading-uni/?b=discussion&amp;e=sequence.#select" rel="nofollow">s/innovation/subversion/</a>.</p>
<blockquote><p>
I guess a starting point would be to select one or two boards that are both available and supported by Coreboot, genesize all the software required to get the operating system loaded
</p></blockquote>
<p>This does look like a good starting point. Start small, build out incrementally, let <a href="http://trilema.com/2014/people-us-dollars-are-not-worth-a-fifth-of-a-bitcent-stop-selling/?b=They%20tend&amp;e=collect#select" rel="nofollow">late comers</a> either scramble of hardware scraps already supported, buy from surplus l1/2 accumulates or invest in extending the support for boards not yet V-ified themselves.</p>
<p><a href="http://fixpoint.welshcomputing.com" rel="nofollow">Jacob</a> worked out the process of flashing the x200 thinkpads with Coreboot using chip clips of offline flashing, though those aren't widely available - for sure a scrap market. </p>
<p>That being said, I've allowed the <a href="http://dorion-mode.com/2019/11/jwrd-computing-the-why-how-what-and-way-forward/#comment-31" rel="nofollow">all Intel is shit</a> discussion to slide down priority, probably a good time to revisit prior to selecting the worthy chips to start with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ejb plan: week 3 (Jan 6 - Jan 12) &#171; Young Hands Club</title>
		<link>http://thetarpit.org/2019/bootloading-operating-systems#comment-202</link>
		<dc:creator>ejb plan: week 3 (Jan 6 - Jan 12) &#171; Young Hands Club</dc:creator>
		<pubDate>Sun, 05 Jan 2020 19:30:24 +0000</pubDate>
		<guid isPermaLink="false">http://thetarpit.org/?p=346#comment-202</guid>
		<description>[...] as some of jfw's writings on the topic. My earlier concerns about UEFI were validated once I read spyked's recent article as well. So, in a sense I was able to get somewhat organized ahead of [...]</description>
		<content:encoded><![CDATA[<p>[...] as some of jfw's writings on the topic. My earlier concerns about UEFI were validated once I read spyked's recent article as well. So, in a sense I was able to get somewhat organized ahead of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mircea Popescu</title>
		<link>http://thetarpit.org/2019/bootloading-operating-systems#comment-201</link>
		<dc:creator>Mircea Popescu</dc:creator>
		<pubDate>Thu, 02 Jan 2020 03:48:10 +0000</pubDate>
		<guid isPermaLink="false">http://thetarpit.org/?p=346#comment-201</guid>
		<description>Keks, send man to examine artefact, watch man come back horrified.

&#62;  ideally before buying it.

I really don't give shit one about buying a buncha onsies mobos, to supplement whatever l1/2 can report of their own hardware. There's really no rule we must cover "all" nor any need to attempt. Getting a dozen or two alternatives listed is arch-sufficient. Let the rest fucking wither ; and let them learn &lt;a href="http://trilema.com/2016/the-necessary-prerequisite-for-any-change-to-the-bitcoin-protocol/" rel="nofollow"&gt;the miner lesson&lt;/a&gt; in the process.

&#62; I've never booted any PC off the network,

I have, actually. Not recently, but for a while back there in the pre-pentium era it was the ~only way to handle a fleet.</description>
		<content:encoded><![CDATA[<p>Keks, send man to examine artefact, watch man come back horrified.</p>
<p>&gt;  ideally before buying it.</p>
<p>I really don't give shit one about buying a buncha onsies mobos, to supplement whatever l1/2 can report of their own hardware. There's really no rule we must cover "all" nor any need to attempt. Getting a dozen or two alternatives listed is arch-sufficient. Let the rest fucking wither ; and let them learn <a href="http://trilema.com/2016/the-necessary-prerequisite-for-any-change-to-the-bitcoin-protocol/" rel="nofollow">the miner lesson</a> in the process.</p>
<p>&gt; I've never booted any PC off the network,</p>
<p>I have, actually. Not recently, but for a while back there in the pre-pentium era it was the ~only way to handle a fleet.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
