All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Matthew Wilcox <willy@debian.org>
Cc: debian-hppa@lists.debian.org,
	parisc-linux@lists.parisc-linux.org,
	debian-glibc@lists.debian.org,
	John David Anglin <dave@hiauly1.hia.nrc.ca>,
	Randolph Chung <tausq@debian.org>
Subject: [parisc-linux] Re: GNU/Libc 2.3.1 on HP-PARISC requires >= 2.4.19 kernel.
Date: Thu, 5 Dec 2002 10:39:49 -0500	[thread overview]
Message-ID: <20021205153949.GB27054@systemhalted> (raw)
In-Reply-To: <20021205133139.C5327@parcelfarce.linux.theplanet.co.uk>

> > Why?
> > ====
> > - More testing.
> > - Bugs fixed in unaligned handlers.
> > - Trap handler fixes.
> > - More things than you can shake a stick at, and all thanks to the
> >   wonderful kernel hacking team that parisc-linux has.
> 
> That's great, but there are still problems with 2.4.19 and 2.4.20.  I think
> you're doing our users a disservice by requiring them to upgrade to 2.4.19.
> Why not relax the minimum version requirement down to 2.4.17?

I agree that it was probably a mistake at the time since 2.4.19 seemed
to solve a lot of problems... though in hindsight they are still too
unstable to push forward on all of our users.

Hrmm... *Carlos mulls for a few hours*

I'll relax it to 2.4.17 in debian, but I'll leave the upstream
requirement of 2.4.19.

c.

  reply	other threads:[~2002-12-05 15:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05  1:08 [parisc-linux] GNU/Libc 2.3.1 on HP-PARISC requires >= 2.4.19 kernel Carlos O'Donell
2002-12-05 13:31 ` [parisc-linux] " Matthew Wilcox
2002-12-05 13:31 ` Matthew Wilcox
2002-12-05 15:39   ` Carlos O'Donell [this message]
2002-12-05 15:39   ` Carlos O'Donell
2002-12-05 16:50 ` John David Anglin
2002-12-05 16:50 ` John David Anglin
2002-12-05 18:10   ` b.gunreben

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=20021205153949.GB27054@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=debian-glibc@lists.debian.org \
    --cc=debian-hppa@lists.debian.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=tausq@debian.org \
    --cc=willy@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.