lkml.org 
[lkml]   [2000]   [Jul]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH] 2.4.0-test3-pre6 cosmetic cleanups
Date
This patch does all of the following:

(a) Makes some cosmetic fixes in Configure.help.

(b) Starts updating the README file for a 2.4 release (however, it still
leaves the various development kernel warnings in, as we're only at
2.4.0-test, not 2.4.0-pre). Also, "new bzip2 format" is changed to
"newer bzip2 formats", as bzip2 isn't exactly new anymore (although
it's still newer than gzip) and "format" is actually referring to both
gzip and bzip2 in that sentence.

(c) Updates net/socket.c so that it prints "Linux NET4.0 for Linux 2.4"
at startup (as opposed to "for Linux 2.3").

(d) Does some cosmetic cleanup on REPORTING-BUGS: The paragraph indentation
was inconsistent, and since one paragraph had no indentation and all the
paragraphs were separated by blank lines anyway, I removed the
indentations. Afterward, the first lines of some of the paragraphs had
large gaps, so I cleaned up the word wrapping where necessary. Finally,
I made a few minor punctuation changes.

(e) Updates the comment at the top of fs/ntfs/fs.c to say "NTFS driver for
Linux 2.4.x" instead of 2.3.x.

If this is too much for a single patch or there are other objections, I can
split this patch up.

-Barry K. Nathan <barryn@pobox.com>

--- linux-2.4.0test3pre6/Documentation/Configure.help Fri Jul 7 21:54:41 2000
+++ linux-2.4.0test3pre6bkn/Documentation/Configure.help Sat Jul 8 22:25:33 2000
@@ -478,7 +478,7 @@

Use multi-mode by default
CONFIG_IDEDISK_MULTI_MODE
- If you get this error, try to say Y here:
+ If you get this error, try saying Y here:

hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
hda: set_multmode: error=0x04 { DriveStatusError }
@@ -716,7 +716,7 @@

It is normally safe to answer Y; however, the default is N.

-Various ATA, Work(s) In Progress (EXPERIMENTAL)
+Various ATA Work(s) In Progress (EXPERIMENTAL)
CONFIG_IDEDMA_PCI_WIP
If you enable this you will be able to use and test highly
developmental projects. If you say N, this configure script will
@@ -793,7 +793,11 @@
AMD Viper ATA-66 Override support (WIP)
CONFIG_AMD7409_OVERRIDE
This option auto-forces the ata66 flag.
- This effect can be also invoked by calling "idex=ata66"
+
+ This effect can be also invoked by using the "idex=ata66" kernel
+ boot parameter, where x is the ide channel (0 for primary, 1 for
+ secondary).
+
If unsure, say N.

CMD64X chipset support
@@ -7319,7 +7323,7 @@
"IP: use FWMARK value as routing key").

At the moment, few devices support fast switching (tulip is one of
- them, a modified 8390 driver can be found at
+ them; a modified 8390 driver can be found at
ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).

If unsure, say N.
@@ -7328,7 +7332,7 @@
CONFIG_NET_HW_FLOWCONTROL
This option enables NIC (Network Interface Card) hardware throttling
during periods of extremal congestion. At the moment only a couple
- of device drivers support it (really only one -- tulip, a modified
+ of device drivers support it (really only one -- tulip; a modified
8390 driver can be found at
ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).

--- linux-2.4.0test3pre6/README Thu Jan 6 14:46:18 2000
+++ linux-2.4.0test3pre6bkn/README Sat Jul 8 23:17:03 2000
@@ -1,9 +1,12 @@
- Linux kernel release 2.3.xx
+ Linux kernel release 2.4.xx

-These are the release notes for Linux version 2.3. Read them carefully,
+These are the release notes for Linux version 2.4. 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.

+[This is a 2.4.0-test kernel, not a 2.4.xx release kernel, so the following
+warnings (originally for Linux 2.3.xx) still apply for now.]
+
Linux version 2.3 is a DEVELOPMENT kernel, and not intended for general
public use. Different releases may have various and sometimes severe
bugs. It is *strongly* recommended that you back up the previous kernel
@@ -62,13 +65,13 @@
- If you install the full sources, do a

cd /usr/src
- gzip -cd linux-2.3.XX.tar.gz | tar xvf -
+ gzip -cd linux-2.4.XX.tar.gz | tar xvf -

to get it all put in place. Replace "XX" with the version number of the
latest kernel.

- - You can also upgrade between 2.3.xx releases by patching. Patches are
- distributed in the traditional gzip and the new bzip2 format. To
+ - You can also upgrade between 2.4.xx releases by patching. Patches are
+ distributed in the traditional gzip and the newer bzip2 formats. To
install by patching, get all the newer patch files and do

cd /usr/src
@@ -105,7 +108,7 @@

SOFTWARE REQUIREMENTS

- Compiling and running the 2.3.xx kernels requires up-to-date
+ Compiling and running the 2.4.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
--- linux-2.4.0test3pre6/net/socket.c Fri Jul 7 21:54:54 2000
+++ linux-2.4.0test3pre6bkn/net/socket.c Sat Jul 8 20:48:17 2000
@@ -1669,7 +1669,7 @@
{
int i;

- printk(KERN_INFO "Linux NET4.0 for Linux 2.3\n");
+ printk(KERN_INFO "Linux NET4.0 for Linux 2.4\n");
printk(KERN_INFO "Based upon Swansea University Computer Society NET3.039\n");

/*
--- linux-2.4.0test3pre6/REPORTING-BUGS Wed Apr 12 09:16:31 2000
+++ linux-2.4.0test3pre6bkn/REPORTING-BUGS Sat Jul 8 22:49:01 2000
@@ -1,22 +1,22 @@
[Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]

- What follows is a suggested procedure for reporting Linux bugs. You
-aren't obliged to use the bug reporting format, it is provided as a guide
-to the kind of information that can be useful to developers - no more.
+What follows is a suggested procedure for reporting Linux bugs. You aren't
+obliged to use the bug reporting format; it is provided as a guide to the
+kind of information that can be useful to developers - no more.

- If the failure includes an "OOPS:" type message in your log or on
-screen please read "Documentation/oops-tracing.txt" before posting your
-bug report. This explains what you should do with the "Oops" information
-to make it useful to the recipient.
+If the failure includes an "OOPS:" type message in your log or on screen
+please read "Documentation/oops-tracing.txt" before posting your bug report.
+This explains what you should do with the "Oops" information to make it
+useful to the recipient.

- Send the output the maintainer of the kernel area that seems to
-be involved with the problem. Don't worry too much about getting the
-wrong person. If you are unsure send it to the person responsible for the
-code relevant to what you were doing. If it occurs repeatably try and
-describe how to recreate it. That is worth even more than the oops itself.
-The list of maintainers is in the MAINTAINERS file in this directory.
+Send the output the maintainer of the kernel area that seems to be involved
+with the problem. Don't worry too much about getting the wrong person. If
+you are unsure, send it to the person responsible for the code relevant to
+what you were doing. If it occurs repeatably, try and describe how to
+recreate it. That is worth even more than the oops itself. The list of
+maintainers is in the MAINTAINERS file in this directory.

- If you are totally stumped as to whom to send the report, send it to
+If you are totally stumped as to whom to send the report, send it to
linux-kernel@vger.rutgers.edu. (For more information on the linux-kernel
mailing list see http://www.tux.org/lkml/).

@@ -25,10 +25,9 @@
overlook things, and easier for the developers to find the pieces of
information they're really interested in. Don't feel you have to follow it.

- First run the ver_linux script included as scripts/ver_linux or
-at <URL:ftp://ftp.sai.msu.su/pub/Linux/ver_linux> It checks out
-the version of some important subsystems. Run it with the command
-"sh scripts/ver_linux"
+First run the ver_linux script included as scripts/ver_linux or at
+<URL:ftp://ftp.sai.msu.su/pub/Linux/ver_linux>. It checks out the version of
+some important subsystems. Run it with the command "sh scripts/ver_linux".

Use that information to fill in all fields of the bug report form, and
post it to the mailing list with a subject of "PROBLEM: <one line
--- linux-2.4.0test3pre6/fs/ntfs/fs.c Fri Jul 7 21:54:51 2000
+++ linux-2.4.0test3pre6bkn/fs/ntfs/fs.c Sat Jul 8 23:01:48 2000
@@ -1,6 +1,6 @@
/*
* fs.c
- * NTFS driver for Linux 2.3.x
+ * NTFS driver for Linux 2.4.x
*
* Copyright (C) 1995-1997, 1999 Martin von Löwis
* Copyright (C) 1996 Richard Russon
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:57    [from the cache]
©2003-2011 Jasper Spaans