Documentation/Changes: phase out Changes file that hasn't changed
Subsystems (7)
PATCH 1/1 Documentation/Changes: phase out Changes file that hasn't changed
It has been over two years since this file has been touched, and even that prior change was just to delete some ancient text.
Looking at the bigger picture, the need for this file has simply passed. It was trying to detail required versions of userspace packages, in order to cater to hand-crafted systems. But now the majority of users get their userspace all at once from some kind of distro, and we are probably a lot more serious about avoiding breaking userspace than we were a dozen years ago.
The remaining data in the file, like (probably stale) links to old package versions, etc. is also no longer of any real value today, so let us just remove the file and all references to it.
For a couple references, where it was obvious the surrounding text was also super ancient (e.g. 1.2.x kernels or similar), the whole paragraph with the reference was removed.
--- Documentation/00-INDEX | 2 - Documentation/Changes | 415 ------------------------------------ Documentation/HOWTO | 5 - Documentation/filesystems/locks.txt | 4 - Documentation/isdn/README | 3 +- Documentation/ja_JP/HOWTO | 5 - Documentation/ko_KR/HOWTO | 4 - Documentation/networking/PLIP.txt | 3 +- Documentation/zh_CN/HOWTO | 3 - README | 16 +- drivers/net/ppp/Kconfig | 5 +- drivers/pcmcia/Kconfig | 3 +- fs/Kconfig.binfmt | 6 - fs/fuse/Kconfig | 1 - net/Kconfig | 7 +- scripts/ver_linux | 1 - 16 files changed, 8 insertions(+), 475 deletions(-) delete mode 100644 Documentation/Changes
Documentation/00-INDEX +0 -2
@@ -17,8 +17,6 @@ ABI/ BUG-HUNTING - brute force method of doing binary search of patches to find bug. -Changes - - list of changes that break older software packages. CodingStyle - how the maintainers expect the C code in the kernel to look. DMA-API.txt
Documentation/Changes deleted +0 -415
415 lines not on this page · raw message
Documentation/HOWTO +0 -5
@@ -87,11 +87,6 @@ required reading: what is necessary to do to configure and build the kernel. People who are new to the kernel should start here. - Documentation/Changes - This file gives a list of the minimum levels of various software - packages that are necessary to build and run the kernel - successfully. - Documentation/CodingStyle This describes the Linux kernel coding style, and some of the rationale behind it. All new code is expected to follow the
Documentation/filesystems/locks.txt +0 -4
@@ -17,10 +17,6 @@ release of the 2.1.x kernel series, support for the old emulation has been totally removed, so that we don't need to carry this baggage forever. -This should not cause problems for anybody, since everybody using a -2.1.x kernel should have updated their C library to a suitable version -anyway (see the file "Documentation/Changes".) - 1.2 Allow Mixed Locks Again ---------------------------
Documentation/isdn/README +1 -2
@@ -320,8 +320,7 @@ README for the ISDN-subsystem ATTENTION! - Always use the latest module utilities. The current version is - named in Documentation/Changes. Some old versions of insmod + Always use the latest module utilities. Some old versions of insmod are not capable of setting the driver-Ids correctly. 3. Lowlevel-driver configuration.
Documentation/ja_JP/HOWTO +0 -5
@@ -122,11 +122,6 @@ [email protected] に送ることを勧めます。 ています。カーネルに関して初めての人はここからスタートすると良いで しょう。 - Documentation/Changes - このファイルはカーネルをうまく生成(訳注 build )し、走らせるのに最 - 小限のレベルで必要な数々のソフトウェアパッケージの一覧を示してい - ます。 - Documentation/CodingStyle これは Linux カーネルのコーディングスタイルと背景にある理由を記述 しています。全ての新しいコードはこのドキュメントにあるガイドライン
Documentation/ko_KR/HOWTO +0 -4
@@ -98,10 +98,6 @@ [email protected]의 메인테이너에게 보낼 것을 권장한다. 빌드하기 위해 필요한 것을 설명한다. 커널에 입문하는 사람들은 여기서 시작해야 한다. - Documentation/Changes - 이 파일은 커널을 성공적으로 빌드하고 실행시키기 위해 필요한 다양한 - 소프트웨어 패키지들의 최소 버젼을 나열한다. - Documentation/CodingStyle 이 문서는 리눅스 커널 코딩 스타일과 그렇게 한 몇몇 이유를 설명한다. 모든 새로운 코드는 이 문서에 가이드라인들을 따라야 한다. 대부분의
Documentation/networking/PLIP.txt +1 -2
@@ -101,8 +101,7 @@ in which case a long timeout would stall the machine when, for whatever reason, bits are dropped. A utility that can perform this change in Linux is plipconfig, which is part -of the net-tools package (its location can be found in the -Documentation/Changes file). An example command would be +of the net-tools package. An example command would be 'plipconfig plipX trigger 10000', where plipX is the appropriate PLIP device.
Documentation/zh_CN/HOWTO +0 -3
@@ -93,9 +93,6 @@ Linux内核代码中包含有大量的文档。这些文档对于学习如何与 文件简要介绍了Linux内核的背景,并且描述了如何配置和编译内核。内核的 新用户应该从这里开始。 - Documentation/Changes - 文件给出了用来编译和使用内核所需要的最小软件包列表。 - Documentation/CodingStyle 描述Linux内核的代码风格和理由。所有新代码需要遵守这篇文档中定义的规 范。大多数维护者只会接收符合规定的补丁,很多人也只会帮忙检查符合风格
README +1 -15
@@ -46,9 +46,7 @@ DOCUMENTATION: - There are various README files in the Documentation/ subdirectory: these typically contain kernel-specific installation notes for some drivers for example. See Documentation/00-INDEX for a list of what - is contained in each file. Please read the Changes file, as it - contains information about the problems, which may result by upgrading - your kernel. + is contained in each file. - The Documentation/DocBook/ subdirectory contains several guides for kernel developers and users. These guides can be rendered in a
@@ -118,17 +116,6 @@ INSTALLING the kernel source: You should now have the sources correctly installed. -SOFTWARE REQUIREMENTS - - Compiling and running the 3.x 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 - excessively old versions of these packages can cause indirect - errors that are very difficult to track down, so don't assume that - you can just update packages when obvious problems arise during - build or operation. - BUILD directory for the kernel: When compiling the kernel, all output files will per default be
@@ -257,7 +244,6 @@ CONFIGURING the kernel: COMPILING the kernel: - Make sure you have at least gcc 3.2 available. - For more information, refer to Documentation/Changes. Please note that you can still run a.out user programs with this kernel.
drivers/net/ppp/Kconfig +2 -3
@@ -14,9 +14,8 @@ config PPP To use PPP, you need an additional program called pppd as described in the PPP-HOWTO, available at - <http://www.tldp.org/docs.html#howto>. Make sure that you have - the version of pppd recommended in <file:Documentation/Changes>. - The PPP option enlarges your kernel by about 16 KB. + <http://www.tldp.org/docs.html#howto>. The PPP option enlarges your + kernel by about 16 KB. There are actually two versions of PPP: the traditional PPP for asynchronous lines, such as regular analog phone lines, and
drivers/pcmcia/Kconfig +1 -2
@@ -26,8 +26,7 @@ config PCMCIA only using 32-bit CardBus cards, say Y or M here. To use 16-bit PCMCIA cards, you will need supporting software in - most cases. (see the file <file:Documentation/Changes> for - location and details). + most cases. To compile this driver as modules, choose M here: the module will be called pcmcia.
fs/Kconfig.binfmt +0 -6
@@ -17,12 +17,6 @@ config BINFMT_ELF Information about ELF is contained in the ELF HOWTO available from <http://www.tldp.org/docs.html#howto>. - If you find that after upgrading from Linux kernel 1.2 and saying Y - here, you still can't run any ELF binaries (they just crash), then - you'll have to install the newest ELF runtime libraries, including - ld.so (check the file <file:Documentation/Changes> for location and - latest version). - config COMPAT_BINFMT_ELF bool depends on COMPAT && BINFMT_ELF
fs/fuse/Kconfig +0 -1
@@ -11,7 +11,6 @@ config FUSE_FS installed if you've installed the "fuse" package itself. See <file:Documentation/filesystems/fuse.txt> for more information. - See <file:Documentation/Changes> for needed library/utility version. If you want to develop a userspace FS, or if you want to use a filesystem based on FUSE, answer Y or M.
net/Kconfig +2 -5
@@ -15,8 +15,7 @@ menuconfig NET If you are upgrading from an older kernel, you should consider updating your networking tools too because changes in the kernel and the tools often go hand in hand. The tools are - contained in the package net-tools, the location and version number - of which are given in <file:Documentation/Changes>. + contained in the package net-tools. For a general introduction to Linux networking, it is highly recommended to read the NET-HOWTO, available from
@@ -147,9 +146,7 @@ menuconfig NETFILTER Various modules exist for netfilter which replace the previous masquerading (ipmasqadm), packet filtering (ipchains), transparent - proxying, and portforwarding mechanisms. Please see - <file:Documentation/Changes> under "iptables" for the location of - these packages. + proxying, and portforwarding mechanisms. if NETFILTER
scripts/ver_linux +0 -1
@@ -5,7 +5,6 @@ # differ on your system. # echo 'If some fields are empty or look unusual you may have an old version.' -echo 'Compare to the current minimal requirements in Documentation/Changes.' echo ' ' uname -a
Signature · 1 line
1.8.1.2
Hi,
Quoted 6 lines · Paul Gortmaker
Looking at the bigger picture, the need for this file has simply passed. It was trying to detail required versions of userspace packages, in order to cater to hand-crafted systems. But now the majority of users get their userspace all at once from some kind of distro, and we are probably a lot more serious about avoiding breaking userspace than we were a dozen years ago.
Is there any file describing the needed tools (and minimum versions) to _build_ the kernel? I agree that trying to describe such for the run-time userspace does not belong to the kernel tree, but the required/supported versions of build tools should be still maybe documented...
A.
Quoted 9 lines · Aaro Koskinen
Hi,
Quoted 6 lines · Paul Gortmaker
Looking at the bigger picture, the need for this file has simply passed. It was trying to detail required versions of userspace packages, in order to cater to hand-crafted systems. But now the majority of users get their userspace all at once from some kind of distro, and we are probably a lot more serious about avoiding breaking userspace than we were a dozen years ago.
You're right, there's no such thing as "embedded linux", nobody creates their own hand-crafted systems, or assembles cross-compiling environments to target hardware other than x86. That's crazy talk.
Quoted 4 lines
Is there any file describing the needed tools (and minimum versions) to _build_ the kernel? I agree that trying to describe such for the run-time userspace does not belong to the kernel tree, but the required/supported versions of build tools should be still maybe documented...
Documentation/changes _is_ the file that describes the kernel's build-time prerequisites. It hasn't changed in a while because we've been maintaining backwards compatability, especially for several non-x86 targets where it's fiddly to get newer toolchain versions.
(Personally I use the last GPLv2 releases of each package, so gcc 4.2.1, binutils 2.17, make 3.81, and busybox.)
I agree squashfs and such aren't build time prerequisites. It might make more sense to move some of these to menuconfig text for the appropriate option. But that's not the same as not documenting it at all, and "this document has been true for a long time and remains true, therefore we must discard it" strikes me as a really weird document retention criteria.
Rob
Randy Dunlap
reviewerQuoted 11 lines · Rob Landley
Quoted 9 lines · Aaro Koskinen
Hi,
Quoted 6 lines · Paul Gortmaker
Looking at the bigger picture, the need for this file has simply passed. It was trying to detail required versions of userspace packages, in order to cater to hand-crafted systems. But now the majority of users get their userspace all at once from some kind of distro, and we are probably a lot more serious about avoiding breaking userspace than we were a dozen years ago.
Quoted 8 lines
You're right, there's no such thing as "embedded linux", nobody creates their own hand-crafted systems, or assembles cross-compiling environments to target hardware other than x86. That's crazy talk.
Quoted 4 lines
Is there any file describing the needed tools (and minimum versions) to _build_ the kernel? I agree that trying to describe such for the run-time userspace does not belong to the kernel tree, but the required/supported versions of build tools should be still maybe documented...
Documentation/changes_is_ the file that describes the kernel's build-time prerequisites. It hasn't changed in a while because we've been maintaining backwards compatability, especially for several non-x86 targets where it's fiddly to get newer toolchain versions.
and if this file is removed, I'll just have to refer to it in older kernel releases to at least get hints about what tools to use, where to find them, and what used to be the version requirements....
Quoted 3 lines
(Personally I use the last GPLv2 releases of each package, so gcc 4.2.1, binutils 2.17, make 3.81, and busybox.)
I agree squashfs and such aren't build time prerequisites. It might make more sense to move some of these to menuconfig text for the appropriate option. But that's not the same as not documenting it at all, and "this document has been true for a long time and remains true, therefore we must discard it" strikes me as a really weird document retention criteria.
Signature · 1 line
~Randy
Quoted 13 lines · Rob Landley
Quoted 10 lines · Aaro Koskinen
Hi,
Quoted 6 lines · Paul Gortmaker
Looking at the bigger picture, the need for this file has simply passed. It was trying to detail required versions of userspace packages, in order to cater to hand-crafted systems. But now the majority of users get their userspace all at once from some kind of distro, and we are probably a lot more serious about avoiding breaking userspace than we were a dozen years ago.
Quoted 3 lines
You're right, there's no such thing as "embedded linux", nobody creates their own hand-crafted systems, or assembles cross-compiling environments to target hardware other than x86. That's crazy talk.
Aside from the obvious sarcasm, what are you trying to say here? The above
seems like a classic strawman argument to me, since _none_ of the above are
things that I have said or implied. And if pressed, I can give many counter
examples to drive that point home. Do I really need to?
Quoted 11 lines
Quoted 5 lines
Is there any file describing the needed tools (and minimum versions) to _build_ the kernel? I agree that trying to describe such for the run-time userspace does not belong to the kernel tree, but the required/supported versions of build tools should be still maybe documented...
Documentation/changes_is_ the file that describes the kernel's build-time prerequisites. It hasn't changed in a while because we've been maintaining backwards compatability, especially for several non-x86 targets where it's fiddly to get newer toolchain versions.
See the mail from hpa --- what may be the "latest" for some less common arch may also be simply too old for another arch. Hence this kind of stuff needs to be in an arch specific file, let alone not in a mis-named "Changes" file.
Quoted 3 lines
(Personally I use the last GPLv2 releases of each package, so gcc 4.2.1, binutils 2.17, make 3.81, and busybox.)
And this works on every arch that linux supports?
Quoted 6 lines
I agree squashfs and such aren't build time prerequisites. It might make more sense to move some of these to menuconfig text for the appropriate option. But that's not the same as not documenting it at all, and "this document has been true for a long time and remains true, therefore we must discard it" strikes me as a really weird document retention criteria.
Again, a strawman. You suggest I said the above with your "this document..." quote, but I never said anything like that, and it totally mis-represents why I suggested we should remove it.
Lets move forward from here and not descend into arguing over details.
To that end, if we create a required-packages.txt that covers the generic stuff like "make" version, and then the arch specific stuff (in arch specific files) for key stuff like gcc version, and gas version, etc, would you not see that as an improvement over what is currently in the mis-named and largely abandoned Changes file?
Paul.
--
Quoted 7 lines
Rob--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Randy Dunlap
reviewerQuoted 57 lines · Paul Gortmaker
Quoted 13 lines · Rob Landley
Quoted 10 lines · Aaro Koskinen
Hi,
Quoted 6 lines · Paul Gortmaker
Looking at the bigger picture, the need for this file has simply passed. It was trying to detail required versions of userspace packages, in order to cater to hand-crafted systems. But now the majority of users get their userspace all at once from some kind of distro, and we are probably a lot more serious about avoiding breaking userspace than we were a dozen years ago.
Quoted 3 lines
You're right, there's no such thing as "embedded linux", nobody creates their own hand-crafted systems, or assembles cross-compiling environments to target hardware other than x86. That's crazy talk.
Aside from the obvious sarcasm, what are you trying to say here? The above
seems like a classic strawman argument to me, since _none_ of the above are
things that I have said or implied. And if pressed, I can give many counter
examples to drive that point home. Do I really need to?Quoted 11 lines
Quoted 5 lines
Is there any file describing the needed tools (and minimum versions) to _build_ the kernel? I agree that trying to describe such for the run-time userspace does not belong to the kernel tree, but the required/supported versions of build tools should be still maybe documented...
Documentation/changes_is_ the file that describes the kernel's build-time prerequisites. It hasn't changed in a while because we've been maintaining backwards compatability, especially for several non-x86 targets where it's fiddly to get newer toolchain versions.See the mail from hpa --- what may be the "latest" for some less common arch may also be simply too old for another arch. Hence this kind of stuff needs to be in an arch specific file, let alone not in a mis-named "Changes" file.
Quoted 3 lines
(Personally I use the last GPLv2 releases of each package, so gcc 4.2.1, binutils 2.17, make 3.81, and busybox.)
And this works on every arch that linux supports?
Quoted 6 lines
I agree squashfs and such aren't build time prerequisites. It might make more sense to move some of these to menuconfig text for the appropriate option. But that's not the same as not documenting it at all, and "this document has been true for a long time and remains true, therefore we must discard it" strikes me as a really weird document retention criteria.
Again, a strawman. You suggest I said the above with your "this document..." quote, but I never said anything like that, and it totally mis-represents why I suggested we should remove it.
Quoted 7 lines
Lets move forward from here and not descend into arguing over details.
To that end, if we create a required-packages.txt that covers the generic stuff like "make" version, and then the arch specific stuff (in arch specific files) for key stuff like gcc version, and gas version, etc, would you not see that as an improvement over what is currently in the mis-named and largely abandoned Changes file?
Yes, a list of required packages with their locations (URLs) and other metadata would be both Good and Sufficient IMO.
Thanks.
Signature · 1 line
~Randy
Hi,
Quoted 8 lines · Rob Landley
Quoted 4 lines · Aaro Koskinen
Is there any file describing the needed tools (and minimum versions) to _build_ the kernel? I agree that trying to describe such for the run-time userspace does not belong to the kernel tree, but the required/supported versions of build tools should be still maybe documented...
Documentation/changes_is_ the file that describes the kernel's build-time prerequisites.
So, in that case the file should not be deleted.
A.
Quoted 9 lines · Aaro Koskinen
Hi,
Quoted 6 lines · Rob Landley
Quoted 4 lines · Aaro Koskinen
Is there any file describing the needed tools (and minimum versions) to _build_ the kernel? I agree that trying to describe such for the run-time userspace does not belong to the kernel tree, but the required/supported versions of build tools should be still maybe documented...
Quoted 4 lines
Quoted 2 lines
Documentation/changes_is_ the file that describes the kernel's build-time prerequisites.So, in that case the file should not be deleted.
Or, we could create a real required-packages.txt that isn't a decade out of date (and poorly named), and have that in turn reference the arch specific files with the arch specific data.
C'mon folks, have an open mind here. Put yourself in the perspective
of the new user, and the issues that he/she faces. Try and forget the
knowledge that you implicitly have gained of linux over time. Pointing
these new users at this ancient Changes file is a good way to simply drive them away.
We can do better. I know we can. And I know we all want that exact same thing once we cut away all the BS.
Thanks,
Paul.
---
Quoted 7 lines
A.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/