Marcin Owsiany <[EMAIL PROTECTED]> writes:
> On Fri, Nov 24, 2000 at 09:07:17PM +0300, Michael Sobolev wrote:
> > On Fri, Nov 24, 2000 at 12:49:02AM +0100, Marcin Owsiany wrote:
> > > > So it looks like one should normalize the list of available keyboards in one of
> > > > the places...
> > >
>
On Fri, Nov 24, 2000 at 09:07:17PM +0300, Michael Sobolev wrote:
> On Fri, Nov 24, 2000 at 12:49:02AM +0100, Marcin Owsiany wrote:
> > > So it looks like one should normalize the list of available keyboards in one of
> > > the places...
> >
> > Maybe the arch prefixes in langs/*.src should be cut
On Fri, Nov 24, 2000 at 12:49:02AM +0100, Marcin Owsiany wrote:
> > So it looks like one should normalize the list of available keyboards in one of
> > the places...
>
> Maybe the arch prefixes in langs/*.src should be cut off at
> build time?
Looking at utilities/dbootstrap/kbdconfig.c I would s
On Fri, Nov 24, 2000 at 02:46:09AM +0300, Michael Sobolev wrote:
> On Thu, Nov 23, 2000 at 11:41:24PM +0100, Marcin Owsiany wrote:
> > No, this is simpler then I thought at first. LC code in
> > main_menu passes "i386/qwerty/pl" to configure_keyboard, which
> > then compares it against list of str
On Thu, Nov 23, 2000 at 11:41:24PM +0100, Marcin Owsiany wrote:
> No, this is simpler then I thought at first. LC code in
> main_menu passes "i386/qwerty/pl" to configure_keyboard, which
> then compares it against list of strings like "qwerty/pl" (no
> arch prefix). It doesn't find a match, and pr
On Thu, Nov 23, 2000 at 10:05:36PM +0100, Marcin Owsiany wrote:
> On Tue, Nov 21, 2000 at 06:35:12AM -0500, Adam Di Carlo wrote:
> >
> > I looked into it myself to see what the deal was and I couldn't figure
> > out why it was failing.
No, this is simpler then I thought at first. LC code in
main
On Thu, Nov 23, 2000 at 10:05:36PM +0100, Marcin Owsiany wrote:
> On Tue, Nov 21, 2000 at 06:35:12AM -0500, Adam Di Carlo wrote:
> >
> > I looked into it myself to see what the deal was and I couldn't figure
> > out why it was failing.
Just an idea: am I right that the failing keymap load is cal
On Tue, Nov 21, 2000 at 06:35:12AM -0500, Adam Di Carlo wrote:
>
> I looked into it myself to see what the deal was and I couldn't figure
> out why it was failing.
Hmm... I wonder if it's a good idea to set keymap in a bterm.
Isn't it a bit like setting a keymap in an xterm?
Marcin
--
Marcin
Michael Sobolev <[EMAIL PROTECTED]> writes:
> On Sun, Nov 19, 2000 at 01:52:51PM -0500, Adam Di Carlo wrote:
> > After selecting the english language, the keymap setting it attempted
> > at 'i386/qwerty/us', which is not a valid keymap on i386. It is
> > supposed to be 'qwerty/us' I think.
> Hm
On Sun, Nov 19, 2000 at 01:52:51PM -0500, Adam Di Carlo wrote:
> After selecting the english language, the keymap setting it attempted
> at 'i386/qwerty/us', which is not a valid keymap on i386. It is
> supposed to be 'qwerty/us' I think.
Hmm... It looks I do not quite understand what you mean h
Adam Di Carlo <[EMAIL PROTECTED]> writes:
> After selecting the english language, the keymap setting it attempted
> at 'i386/qwerty/us', which is not a valid keymap on i386. It is
> supposed to be 'qwerty/us' I think.
Nope, that's not it.
I dunno, maybe the match logic in kbdconfig.c line 203
Package: boot-floppies
Version: CVS-2000-11-19
After selecting the english language, the keymap setting it attempted
at 'i386/qwerty/us', which is not a valid keymap on i386. It is
supposed to be 'qwerty/us' I think.
This is a nasty problem.
--
.Adam Di [EMAIL PROTECTED]http://www.onShor
12 matches
Mail list logo
