=== maxb_ is now known as maxb | ||
blut | What is the debconf database called during the installation? I tried 'debconf-set grub-installer/bootdev ${primary_disk}' during an early command, however, it is not registered. | 15:09 |
---|---|---|
blut | I think it might not be in the correct database. | 15:09 |
blut | even with 'd-i grub-installer/bootdev string /dev/sde' in somefile and debconf-set-selections somefile the d-i still insists that the device is not specified | 15:13 |
blut | What is the debconf database called during the installation? | 15:13 |
blut | So that I might do a debconf-dumpdb just to check if it might be a different option | 15:14 |
cjwatson | /var/lib/cdebconf/questions.dat | 15:14 |
cjwatson | more likely some twisty flow in grub-installer though. the DEBCONF_DEBUG=developer boot parameter is the usual way to start puzzling this sort of thing out | 15:15 |
blut | cjwatson: thank you. | 15:18 |
blut | I just restarted the installation to figure it out. | 15:19 |
blut | Oh the database is called configdb btw. | 15:22 |
cjwatson | Oh, sure, if you mean the internal name. | 15:28 |
cjwatson | I'd have just opened the raw file in nano to check though :) | 15:28 |
=== santa is now known as Guest43478 | ||
=== Guest43478 is now known as santa_ | ||
=== xnox_ is now known as xnox | ||
=== superm1_ is now known as superm1 | ||
=== cjwatson_ is now known as cjwatson | ||
=== carvite_ is now known as carvite |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!