Also, it doesn't recognize that complicated locale strings, it uses just two characters. DSL does not include locales, so that setting is only used to set the timezone and the keymap.
Here are the ones I think would suit you: ch) KEYTABLE="sg-latin1" CHARSET="iso8859-15" TZ="Europe/Zurich" fr) KEYTABLE="fr-latin1" CHARSET="iso8859-15" TZ="Europe/Paris"
so, lang=fr would set those three variables and load the french latin1 keymap..I see, thanks!
I had mixed up the keyboard setting with the lang setting in that case. I guess that neither of ch or fr would do it for me, as I'm in the minority part of Switzerland, speaking french. If I use ch, I'd get a Swiss-German keyboard, and if I use fr, I'd get a French keyboard (AZERTY). I'll continue to set it up manually; that's fine for me.
For newbies, it may be a bit strange to specifically be able to set lang=XX in the Pendrive install, and then see that it was not being used anyhow. If one is proficient enough to go change the menu.lst file anyhow (and that's what's required), then I don't see the need to bother asking for the extra bootcodes in the Pendrive install procedure?
Totally apart, and for the perfectionist in me, I see that "SwitchWM" is not available in the JWM right-click menu, while it is in the Fluxbox menu.I think it's just about convenience to ask for the extra bootcodes, than just say "go edit the file".Hi danielp!
Just put this line in opt/bootlocal.sh and your preferred keyboard will be loaded at boot time:
loadkeys fr_CH-latin1
I think this is the keyboard you are using. In that case this is the solution.
Have fun and hope everything works out, meo
EDIT: Well what I mentioned above probably doesn't belong to this thread so I'm going to disguise my input with something that does. When it comes to the famous Dmix there is another thing I'm wondering over. If the "rec" button is being clicked at a yellow dot indicates that it is on but if you click on it again it doesn't change (like the mute button for example) so that the yellow dot disappears. I don't know if it is supposed to be that way but that is the way it is. So I would like some comment on that issue.danielp wrote
Quote
... apparently the first one takes precedence?
A minor bug anyhow, once you know how to fix it.
The first boot code does not take precedence. This is quite obvious by the use of the vga=normal boot code given that the cdrom has vga=791 embedded in it. The getbootparam function returns the last occurence of any specified boot option. You can easily verify by a three line script.
Perhaps it is the grouping as Curaga has pointed out. This grouping of lang/keyboard/timezone is original Knoppix code. Likely this should be the area that could use improvement, or be replaced by specifying each independently.Next Page...
original here.