Re: boot parameters and bootkbd
On Sat, Jan 16, 1999 at 02:02:55PM -0500, Adam Di Carlo wrote:
> On 16 Jan 1999 15:12:46 -0000, ezanard@master.debian.org said:
> > CVSROOT: /debian/home/sr1/lib/cvs Module name: . Changes by:
> > ezanard 99/01/16 09:12:46
>
> > Modified files: boot-floppies/utilities/dinstall: dinstall.h
> > kbdconfig.c main.c main_menu.c
> > boot-floppies/utilities/dinstall/messages: lang_C.h lang_es.h
>
> > Log message: Added support for selecting the keymap using a boot
> > parameter (bootkbd).
>
> What is the benefit of doing it this way? How does it affect the
> keyboard selection later?
dbootstrap reads boot parameters form /proc/cmdline . If bootkbd is
defined, and it's one of the keymaps on the disk, it will load it and
write /tmp/kbdconf as if we had selected it on the keyboard selection,
and then dbootstrap will skip the keyboard selection step.
If bootkbd is not defined or not one of those keymaps, dbootstrap will
make us go through the "Configure keyboard" step, as usual.
That way we can "automatize" that step. If we have to install Debian in
many machines, and all of them use (say) spanish keyboards, just adding
"bootkbd=qwerty/es" on syslinux.cfg on the rescue floppy means we won't
have to go through the keyboard selection step for each machine.
The same may be easily done for the "Color or Monochrome" step and the
tzconfig step.
I plan to go on adding boot parameters for other steps to reduce
interactivity as much as I can. Also I plan to implement a "save
configuration" menu option. After the user installs Debian on
a machine, he may use that option to write a syslinux.cfg to the rescue
disk that will repeat that installation non-interactively (as much as
possible). That will make installing several "clones" really easy.
I guess I won't go too far for slink, but I hope to have something ready
for potato.
--
Enrique Zanardi ezanardi@ull.es
Reply to: