Re: First version of automated test for dual boot activated (Was: Automated testing of d-i)

To: debian-live@lists.debian.org
Subject: Re: First version of automated test for dual boot activated (Was: Automated testing of d-i)
From: Jonathan Carter <jcc@debian.org>
Date: Tue, 24 Jun 2025 14:20:48 +0200
Message-id: <[🔎] e0050cf8-b6b0-4c5b-87a2-bb56ad34ff47@debian.org>
In-reply-to: <[🔎] 24b37286-ba68-4dd4-9c0a-9df02fa5abff@rclobus.nl>
References: <2824eb4b-6f9e-4851-b0d6-fa90180083f7@rclobus.nl> <7fb53f2e-53c6-4854-9127-f2ec895d6617@rclobus.nl> <[🔎] 24b37286-ba68-4dd4-9c0a-9df02fa5abff@rclobus.nl>

Hi Roland

On 2025/06/23 20:42, Roland Clobus wrote:

The test is:
* Install Windows to an empty HD
* Use Windows onboard partitioning tools to provide space for Debian
* Install Debian in the free space (using Calamares)
* Reboot to Debian
* Do a smoke test of Debian after the installation
* Reboot to Windows

Next step: use d-i.

Very nice! My understanding is that cryptsetup now (well actually evensince Debian 12) supports BitLocker. It would be great to implement thisat some point for dual-boot users, but would also need a lot of testing,so this sounds like it could be very useful for that in the future!


-Jonathan

Reply to:

References:
- Re: First version of automated test for dual boot activated (Was: Automated testing of d-i)
  - From: Roland Clobus <rclobus@rclobus.nl>

Prev by Date: Re: First version of automated test for dual boot activated (Was: Automated testing of d-i)
Previous by thread: Re: First version of automated test for dual boot activated (Was: Automated testing of d-i)
Index(es):
- Date
- Thread