linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: M Sweger <mikesw@ns1.whiterose.net>
To: linux-kernel@vger.kernel.org
Subject: Re: linux 2.2.19pre14 is marked as pre13, plus some config/other problems. (fwd)
Date: Tue, 27 Feb 2001 06:56:02 -0500 (EST)	[thread overview]
Message-ID: <Pine.BSF.4.21.0102270655440.49899-100000@ns1.whiterose.net> (raw)



> A). The version of the linux 2.2.19pre14 on 2.2.18
>     is compiling and saying it is pre13. Thus the
>     make file has the wrong version.

Yep. Harmless

> B). After doing "make menuconfig". The textboxes
>     displayed for the menu options "Processor family"
>     and "Maximum Physical memory" are displayed
>     incorrectly (half missing). 
>     If I move the keyboard cursor arrow up and down
>     for each of the above menus, then the display is
>     redrawn with all of the missing menu options, color
>     and graphics. Note: I have libcurses v5.0beta1 which
>     didn't have problems in linux 2.2.19pre5 or earlier.

I cant support beta curses libraries. The code was changed so that the 
hardware cursor accurately reflected the position of the menu item. That is
vital to blind users

> C). Errors during "make dep". 
>     note: I have md5sum from textutils v1.22.
>     If my config file will help here, I can send it.

The md5sum one is also ok. The ISDN code in 2.2.19pre14 isnt certified or
intended to be

Alan


             reply	other threads:[~2001-02-27 12:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 11:56 M Sweger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-26 22:05 linux 2.2.19pre14 is marked as pre13, plus some config/other problems. (fwd) M Sweger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.BSF.4.21.0102270655440.49899-100000@ns1.whiterose.net \
    --to=mikesw@ns1.whiterose.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).