public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [patch] Linux 2.6.4 requires procps 3.2
Date: 23 Feb 2004 15:16:38 -0500	[thread overview]
Message-ID: <1077567398.8121.211.camel@cube> (raw)

Now that the /dev/pts filesystem uses 20-bit minor
numbers, a new procps is required. Version 3.2 will
work even if you don't upgrade glibc. Failure to
upgrade procps will leave you with a messed-up TTY
column when more than 255 or 256 PTYs are used.

http://procps.sf.net/

diff -Naurd old/Documentation/Changes new/Documentation/Changes
--- old/Documentation/Changes	2004-02-21 03:27:13.000000000 -0500
+++ new/Documentation/Changes	2004-02-23 12:33:22.000000000 -0500
@@ -62,7 +62,7 @@
 o  PPP                    2.4.0                   # pppd --version
 o  isdn4k-utils           3.1pre1                 # isdnctrl 2>&1|grep version
 o  nfs-utils              1.0.5                   # showmount --version
-o  procps                 3.1.13                  # ps --version
+o  procps                 3.2.0                   # ps --version
 o  oprofile               0.5.3                   # oprofiled --version
 
 Kernel compilation




                 reply	other threads:[~2004-02-23 22:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1077567398.8121.211.camel@cube \
    --to=albert@users.sf.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