mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jarek Poplawski <jarkao2@o2.pl>
Subject: Re: [PATCH] Documentation/Changes -> Documentation/Requirements
Date: Fri, 30 Nov 2007 13:09:21 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.0.9999.0711301256520.7197@localhost.localdomain> (raw)
In-Reply-To: <200711301747.lAUHlDdM006716@tazenda.hos.anvin.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 3115 bytes --]

On Fri, 30 Nov 2007, H. Peter Anvin wrote:

> diff --git a/Documentation/Requirements b/Documentation/Requirements
> new file mode 100644
> index 0000000..bd7bc2c
> --- /dev/null
> +++ b/Documentation/Requirements
> @@ -0,0 +1,394 @@

> +Minimal Runtime Requirements
> +============================
> +
> +Upgrade to at *least* these software revisions before thinking you've
> +encountered a bug!  If you're unsure what version you're currently
> +running, the suggested command should tell you.
> +
> +Again, keep in mind that this list assumes you are already
> +functionally running a Linux 2.4 kernel.  Also, not all tools are
> +necessary on all systems; obviously, if you don't have any ISDN
> +hardware, for example, you probably needn't concern yourself with
> +isdn4k-utils.
> +
> +o  util-linux             2.10o                   # fdformat --version
> +o  module-init-tools      0.9.10                  # depmod -V

given that, on my F8 system, i'm up to module-init-tools 3.4, is
something as old as 0.9.10 still adequate?

> +o  e2fsprogs              1.29                    # tune2fs
> +o  jfsutils               1.1.3                   # fsck.jfs -V
> +o  reiserfsprogs          3.6.3                   # reiserfsck -V 2>&1|grep reiserfsprogs
> +o  xfsprogs               2.6.0                   # xfs_db -V
> +o  pcmciautils            004                     # pccardctl -V

same here -- f8 has pcmciautils version 014, so 004 is getting
ancient.

> +o  quota-tools            3.09                    # quota -V

quota-tools is actually just the "quota" package on fedora, but that's
probably not worth obsessing over.

> +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.2.0                   # ps --version
> +o  oprofile               0.9                     # oprofiled --version
> +o  udev                   081                     # udevinfo -V
> +o  grub                   0.93                    # grub --version
> +
> +
> +Kernel Compilation Requirements
> +===============================
> +
> +On all systems, minimal requirements (see below for additional notes):
> +
> +o  Gnu C                  3.2                     # gcc --version
> +o  Gnu make               3.79.1                  # make --version
> +o  binutils               2.12                    # ld -v
> +o  Gnu bc                 1.06                    # bc -v

you need bc?  for what?  i just did a defconfig build for x86 with no
need for bc.

> +o  Perl                   5.6.0(?)                # perl -v

if you mention perl, you should also mention sed and awk, no?  and
perhaps suggest running scripts/ver_linux.

more later.

rday

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================

  reply	other threads:[~2007-11-30 18:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30  0:19 [PATCH] Avoid overflows in kernel/time.c H. Peter Anvin
2007-11-30  1:54 ` Andrew Morton
2007-11-30  3:01   ` H. Peter Anvin
2007-11-30  3:27   ` [PATCH] Documentation/Changes -> Documentation/Requirements H. Peter Anvin
2007-11-30  3:32   ` [PATCH] Documentation/Changes -> Documentation/Requirements (resend without truncated comment text) H. Peter Anvin
2007-11-30  7:16     ` Jarek Poplawski
2007-11-30 17:40       ` H. Peter Anvin
2007-11-30 17:47       ` [PATCH] Documentation/Changes -> Documentation/Requirements H. Peter Anvin
2007-11-30 18:09         ` Robert P. J. Day [this message]
2007-11-30 18:20           ` H. Peter Anvin
2007-11-30  1:59 ` [PATCH] Avoid overflows in kernel/time.c Chris Snook
2007-11-30  3:04   ` H. Peter Anvin
2007-11-30  3:40     ` Arjan van de Ven
2007-11-30  3:54       ` H. Peter Anvin
2007-12-02 18:37         ` Pavel Machek
2007-12-03 14:53         ` Jan Engelhardt
2007-12-10 16:37           ` H. Peter Anvin
2007-12-01  0:33 ` Adrian Bunk
2007-12-01  4:19   ` H. Peter Anvin
2007-12-01 13:20   ` Alan Cox
2007-12-01 13:33     ` Alan Cox
2007-12-02  1:53     ` H. Peter Anvin
2007-12-07  0:22   ` Jeremy Fitzhardinge
2007-12-04 11:29 ` Andrew Morton
2007-12-10 16:46   ` H. Peter Anvin
2007-12-10 18:59   ` H. Peter Anvin
2007-12-10 22:04     ` Andrew Morton

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=alpine.LFD.0.9999.0711301256520.7197@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=jarkao2@o2.pl \
    --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

all inboxes | Powered by JetHome®