On Fri 14 Dec 2012 at 21:43:13 -0700, Bob Proulx wrote: > Richard Owlett wrote: > > Bob Proulx wrote: > > >Richard Owlett wrote: > > >>d-i console-keymaps-at/keymap select us > > >>d-i keyboard-configuration/xkb-keymap select us > > > > > >In Wheezy they changed these to different strings. It caught me too. > > >See Bug#693493. In Wheezy instead of "console-keymaps-at/keymap" use > > >"keymap select us". > > > > > > d-i keymap select us > > > > > >The documentation for Testing Wheezy is: > > > > > > http://d-i.alioth.debian.org/manual/en.amd64/apbs04.html#preseed-l10n > > > > As I indicated in my original post, I'm using Squeeze. > > I tried your suggestion to see if Squeeze had the same bug. > > Evidently not. > > Sorry. Because you were having problems with this I assumed you were > using Wheezy. Because in Squeeze this works fine. If you are having > a problem in Squeeze then we need to dig deeper. Because it > definitely works fine there.
Is that "working fine" working fine as in "I have my preseed file in the initrd"? Richard may not be doing it that way but, as yet, he has not revealed what he is doing. > How are you trying to preseed the keyboard? > > Note that the only two valid places are on the command line as a > kernel boot parameter and in an initrd file. The keyboard question is > asked very early and those are the only two places that are available > by the time the question needs to be asked. Putting it in a file to > be loaded later is too late to be used. How does 'auto=true' on the kernel command line fit into this picture? > http://www.debian.org/releases/stable/i386/apbs04.html.en#preseed-l10n > "Setting localization values will only work if you are using initrd > preseeding. With all other methods the preconfiguration file will > only be loaded after these questions have been asked." That is very definite. But is it definitive? I have 'auto=true' in mind. > Even though it says initrd preseeding I think it works okay using > command line parameters too. So it should. > > >Are you sure that is an error message and not simply the normal user > > >dialog asking the keyboard question. > > > > Depends on definition of "error". It has the same format as screens > > presented during a un-preseeded install. > > Right. That isn't an error message. It is the user interaction > dialog. The preseed for it isn't happening before it is asked and > therefore it is still asked. Agreed. > > To me that meant "error" as preseeding should eliminate all > > questions. > > No. Often preseeding is used to only answer some of the questions. > Very usefully it can set the mirror to a fast local mirror for > example. Or increase a dhcp timeout due to a slow dhcp server. Just > setting those would leave all of the other questions available. There > isn't any global setting that says that providing one preseed disables > all interactive dialog. Indeed. > > I just double checked by running a text mode expert install - that > > screen never appears. > > That does seem like a bug that it would ask it normally but not during > the expert install. I haven't tried to recreate it yet myself. With a straightforward expert install the keyboard question is asked. Maybe something has been added to the command line. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121215193909.GV6940@desktop
