Exercise 2: Why a Dedicated /boot Partition Matters More With More OSes — Possible Solution
====================================================================

Explanation:

The chapter's own reasoning names the "reinstall temptation" directly:
in a multi-OS setup, "just reinstall this one distro" is described as
a real, common temptation, and it genuinely gets riskier the more
entangled /boot is with a root filesystem that's about to be wiped
and rebuilt. With only two operating systems sharing a disk, a
reinstall of one Linux distro is a relatively contained event -- there's
only one other OS's own entries that need to survive the process. But
as more operating systems accumulate on the same disk (three, four, or
more, as this chapter's own worked example demonstrates), the boot
configuration ends up representing correspondingly more work to
rebuild correctly if it's accidentally destroyed along with a
reformatted root filesystem -- os-prober has to rediscover every other
OS all over again, and any custom entries or the specific choice of
which distro is authoritative has to be reestablished from scratch.

A dedicated, separate /boot partition sidesteps this entirely: since
it's a distinct partition from root, wiping and reformatting a
distro's root filesystem during a reinstall doesn't touch /boot at
all, meaning the existing, working boot configuration for every other
OS on the disk survives completely untouched, regardless of how many
operating systems are actually sharing that same physical disk. The
more OSes involved, the more there is to lose from an accidental
/boot wipe, and correspondingly the more valuable it becomes to have
kept /boot deliberately separate from the start.

WHY THIS WORKS AS AN ANSWER
------------------------------
This directly connects the "reinstall temptation" language from the
chapter to the specific risk that scales with OS count (more
os-prober-discovered entries to potentially lose), rather than just
restating that a separate /boot partition is generally a good idea.