Comment 2 for bug 268580

Revision history for this message
Dustin Kirkland  (kirkland) wrote : Re: Prompt for BOOT_DEGRADED=true|false in thre

According to cjwatson, this should be fixed in mdadm and partman-md, not partman-target.

<cjwatson> kirkland: firstly, I think this should be in partman-md, not partman-target; you can add a new check.d script for it there
<cjwatson> kirkland: *bing* sorry, a lightbulb just went off
<cjwatson> kirkland: you want the translated text in mdadm too, right? great. put it there, and *also* put it in mdadm-udeb, along with the check.d script!
<cjwatson> no more translation syncing problem
<cjwatson> that will make it much more comfortable and less namespace-violating to call the template mdadm/boot_degraded
<cjwatson> kirkland: you'll need a slightly awkward trick to get the answer to the question into /target; this is necessary because (presumably) you don't want to ask the question when mdadm is actually installed, but instead during partman
<cjwatson> kirkland: this trick is: db_get mdadm/boot_degraded; echo mdadm mdadm/boot_degraded boolean "$RET" | debconf-set-selections
<cjwatson> with a comment explaining that you're doing this so that the value gets set in /target's debconf database before mdadm is installed
<cjwatson> kirkland: in the template, you should avoid "yes"; we try to write templates so that they're agnostic of changes in the debconf frontend. We usually prefer language such as "you might want to boot your system even with a degraded RAID if ..."
<cjwatson> kirkland: I think perhaps the short description could be clearer. Maybe "Do you want to boot normally even if your RAID becomes degraded?"