From: "Josef 'Jeff' Sipek" <jeffpc@optonline.net>
To: Linus Torvalds <torvalds@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH][TRIVIAL][2.6] Bugzilla bug # 984 - 2.6 readme is still for 2.5
Date: Mon, 04 Aug 2003 19:35:23 -0400 [thread overview]
Message-ID: <200308041935.23177.jeffpc@optonline.net> (raw)
The README still contains bunch of 2.5.x. Even though we are technically not
yet in 2.6, the file can (and should) be "fixed" now, so that we don't have to think
about such trivial things later.
Josef "Jeff" Sipek
--- linux-2.6.0-test2-vanilla/README 2003-07-27 13:08:22.000000000 -0400
+++ linux-2.6.0-test2-tmp/README 2003-07-27 15:14:20.000000000 -0400
@@ -1,12 +1,9 @@
- Linux kernel release 2.5.xx
+ Linux kernel release 2.6.xx
-These are the release notes for Linux version 2.5. Read them carefully,
+These are the release notes for Linux version 2.6. Read them carefully,
as they tell you what this is all about, explain how to install the
kernel, and what to do if something goes wrong.
-NOTE! As with all odd-numbered releases, 2.5.x is a development kernel.
-For stable kernels, see the 2.4.x maintained by Marcelo Tosatti.
-
WHAT IS LINUX?
Linux is a Unix clone written from scratch by Linus Torvalds with
@@ -55,7 +52,7 @@
directory where you have permissions (eg. your home directory) and
unpack it:
- gzip -cd linux-2.5.XX.tar.gz | tar xvf -
+ gzip -cd linux-2.6.XX.tar.gz | tar xvf -
Replace "XX" with the version number of the latest kernel.
@@ -64,15 +61,15 @@
files. They should match the library, and not get messed up by
whatever the kernel-du-jour happens to be.
- - You can also upgrade between 2.5.xx releases by patching. Patches are
+ - You can also upgrade between 2.6.xx releases by patching. Patches are
distributed in the traditional gzip and the new bzip2 format. To
install by patching, get all the newer patch files, enter the
- top level directory of the kernel source (linux-2.5.xx) and execute:
+ top level directory of the kernel source (linux-2.6.xx) and execute:
- gzip -cd ../patch-2.5.xx.gz | patch -p1
+ gzip -cd ../patch-2.6.xx.gz | patch -p1
or
- bzip2 -dc ../patch-2.5.xx.bz2 | patch -p1
+ bzip2 -dc ../patch-2.6.xx.bz2 | patch -p1
(repeat xx for all versions bigger than the version of your current
source tree, _in_order_) and you should be ok. You may want to remove
@@ -99,7 +96,7 @@
SOFTWARE REQUIREMENTS
- Compiling and running the 2.5.xx kernels requires up-to-date
+ Compiling and running the 2.6.xx kernels requires up-to-date
versions of various software packages. Consult
./Documentation/Changes for the minimum version numbers required
and how to get updates for these packages. Beware that using
reply other threads:[~2003-08-04 23:35 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=200308041935.23177.jeffpc@optonline.net \
--to=jeffpc@optonline.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®