> 1) I seem to be unable to change my keyboard settings (I'm stuck with a
> US keymap no matter what I select - I tried almost all of them).
> A related note: When selecting one of the dk*.map files, the test box
> that can be used to try out the keyboard before accepting does not accept
> input of the 3 special danish chars (same problem with Intel version),
> works fine after pressing '1' to accept though (on Intel that is, Alpha
> sticks with US map :-( ).
After looking at the "setup" source for a litle while, I don't even
understand why it would work on Intel. The problem lies in how the
installed system is setup, and how the keymap script expects it to be
setup. setup calls /usr/lib/setup/SeTkeymap, which always expects your
keymap files to be stored in /usr/lib/kbd/keytables.
On the rootdisk, that's where they are stored. But on the intalled
system, there isn't even a /usr/lib/kbd/keytables directory. There's a
/usr/lib/keymaps directory, but subdirectories exist within that. So it's
not an easy fix. And since the keymaps don't exist where they are
expected to be, you can't change the layout.
In the morning, I'll send Patrick a mail about this problem. We'll see
what he has to say, and if is any good fix for it. Problems with the
setup program are all pretty much his domain.
> 2) In the INSTALL document you refer to the kernel image as
> '/vmlinux.gz', but when running 'CONFIGURE' from 'setup' the 'INSTALL
> LINUX KERNEL' menu expects the image to be called '/vmlinuz' and will
> complain about a missing kernel if it's named vmlinux.gz as per the
> INSTALL document and the 'skip' option is selected:
>
> CONTINUE WITHOUT A KERNEL?
> WARNING: no Linux kernel is currently installed on your
> system, so generating a bootdisk and LILO installation are
> not going to work -- if you continue without an installed
> kernel you'll need to have some other means of booting your
> system. LOADLIN or the installation bootdisk will work. If
> you're sure you want to continue without installing a kernel,
> select YES. Otherwise, select NO and you'll be returned to
> the kernel installation menu.
>
> < Yes > < No >
>
>
> I would think changing the name to 'vmlinuz' would be the easiest fix.
Expect to see this entire section (along with the bookdisk and installing
LILO parts) to disappear from the Alpha setup program at some point in the
future. I just haven't gotten that far along yet. Eventually, there will
be some sort of aboot/milo configuration section, but we're not there yet.
I'd prefer to get the body of the distribution stabilized and relatively
bug-free first.
> 3) If I answer 'NO' too the 'CONFIGURE NETWORK?' question, I'm promptly
> asked again ;-) So I have to decline twice before moving on with the
> configuration.
Please check in /var/log/setup to make sure that you don't have two
different scripts that call setup.netconfig, or that you don't have two
different scripts that attempt to configure networking on their own. I
have to admit that I've never seen this problem before.
> 4) I have noticed that when setting a root password with the slackware
> install procedure, no 'dialog' box is used. I have written a patch for
> 'dialog-0.6z' that implements a password-box type (simply a input-box
> that does not echo its input back to the user). I have used this in
> scripts of my own to keep the 'dialog' look 'n' feel even when changing
> user passwords. If it is of interrest then I'll put the patch up for
> download.
You're right. We just drop out of setup to the console to run passwd.
I'd be happy to take a look at your patch when I get to working on the
setup program, as there's really no need to drop out of dialog if we don't
have to.
--
Chris Lumens - chris@slackware.com - KG6CIH
@n=(-42,-85,-83,-19,65,2,-10,-10,-15,-3,2,-10,73,-4,8,-4,2,79,8,17,15,7,14,2);
print map{chr(-$n[$i++]+ord)} sort(split(//,'place random string here')),"\n";
This archive was generated by hypermail 2b30 : Fri May 09 2003 - 10:00:02 PDT