Improved version reporting
From: "Albert D. Cahalan" <[email protected]>
> On Wed, 14 Mar 2001 [email protected] wrote:
>>> +o Console Tools # 0.3.3 # loadkeys -V
>>> +o Mount # 2.10e # mount --version
>>
>> Concerning mount: (i) the version mentioned is too old,
Exactly why? Mere missing features don't make for a required upgrade. Version number inflation should be resisted.
These days you can mount filesystems several places. That means that the choice one used to have -- after
# mount dev dir both # umount dev and # umount dir would unmount -- has disappeared, and only # umount dir is (guaranteed to be) right today. These days you can mount several filesystems at the same mount point. The old mount does not understand this at all. Recent versions of mount act better in this respect, even though it is still easy to confuse them.
Such things mean that it is best to have a really recent mount (although, of course, if you only want the mount(2) system call executed some five year old version will also do that for you).
On the other hand, there are no important changes between mount-2.10d and 2.10e, so I see no justification for writing 2.10e. It is difficult to say what the "right" version is. There is a long series of minor improvements. Probably I would write 2.10r.
Andries
Quoted 11 lines · [email protected] wrote:
Quoted 6 lines · On Wed, 14 Mar 2001 [email protected] wrote:
Quoted 5 lines
Review
Quoted 3 lines
(quoted diff) +2
-0+o Console Tools # 0.3.3 # loadkeys -V +o Mount # 2.10e # mount --versionConcerning mount: (i) the version mentioned is too old,
On the other hand, there are no important changes between mount-2.10d and 2.10e, so I see no justification for writing 2.10e. It is difficult to say what the "right" version is. There is a long series of minor improvements. Probably I would write 2.10r.
Guys,
How about making a column that says: "recommended".
So in this case we'd see 2.10r as recommended, but 2.10e as required.
An explanation could state that:
if you happen to have the version under "required", but a higher version is listed under "recommended", then that newer version is available, and but it is likely that one you have will work for you. There is no urgent reason to upgrade. But if you happen to be upgrading, you are advised upgrade to at least the version in the "recommended" column, as that has fixes over the one mentioned in the "required" column.
Best regards,
Roger.
Signature · 4 lines
** [email protected] ** http://www.BitWizard.nl/ ** +31-15-2137555 ** *-- BitWizard writes Linux device drivers for any device you may have! --* * There are old pilots, and there are bold pilots. * There are also old, bald pilots.
Quoted 10 lines · Andries.Brouwer
Quoted 10 lines
From: "Albert D. Cahalan" <[email protected]>
Quoted 6 lines · On Wed, 14 Mar 2001 [email protected] wrote:
Quoted 5 lines
Review
Quoted 3 lines
(quoted diff) +2
-0+o Console Tools # 0.3.3 # loadkeys -V +o Mount # 2.10e # mount --versionConcerning mount: (i) the version mentioned is too old,
Exactly why? Mere missing features don't make for a required upgrade. Version number inflation should be resisted.
...
Quoted 4 lines
These days you can mount several filesystems at the same mount point. The old mount does not understand this at all.
Recent versions of mount act better in this respect,
even though it is still easy to confuse them.
The rule should be like this:
List the lowest version number required to get 2.2.xx-level features while running a 2.4.xx kernel.
Remember what the purpose of the table is. It is a list of REQUIRED upgrades. Failure to upgrade should result in a broken system. So pppd must be listed, since somebody changed the kernel API for 2.4.1.
If I run the mount command from Red Hat 6.2, using it as intended for a 2.2.xx kernel, doesn't everything work? There won't be any multi-mount confusion because 2.2.xx can't do that anyway. There isn't any problem with NFSv3 either, since 2.2.xx lacks NFSv3.
Basically I ask: would existing scripts for a 2.2.xx kernel break? If the old mount can still do what it used to do, then "mount" need not be listed at all.
Hi Albert.
Quoted 12 lines
Quoted 11 lines
Quoted 6 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
+o Mount # 2.10e # mount --version
Concerning mount: (i) the version mentioned is too old,
Exactly why? Mere missing features don't make for a required upgrade. Version number inflation should be resisted.
These days you can mount several filesystems at the same mount point. The old mount does not understand this at all. Recent versions of mount act better in this respect, even though it is still easy to confuse them.
Quoted 4 lines
The rule should be like this:
List the lowest version number required to get 2.2.xx-level features while running a 2.4.xx kernel.
That's a meaningless definition, and can only be taken as such. What use would such a list be to somebody wishing (like I recently was) to upgrade a system running the 2.0.12 kernel so it runs the 2.4.2 kernel instead?
The ONLY kernel version that any list can be meaningful for is that of the kernel source tree it is a member of, and that leads to the following definition for the versions to be included in such a list:
List the lowest version number required to compile this kernel, and to allow the resulting kernel to be used as the heart of a running system.
Basically, required upgrades can fall into any of the following categories, and need to be dealt with accordingly:
1. Development tools used to compile and/or link the kernel.
2. System libraries needed to run these development tools:
3. System tools that interact intimately with the kernel. If the kernel interface changes in an incompatible way, these will also need to be updated.
4. System tools that analyse kernel-supplied information and advise the user of the results.
5. Other tools that are dependant on kernel version.
6. Other tools that have been upgraded.
My opinion is that only tools that fall in category (6) should be omitted from the list.
Quoted 10 lines
Remember what the purpose of the table is. It is a list of REQUIRED upgrades. Failure to upgrade should result in a broken system. So pppd must be listed, since somebody changed the kernel API for 2.4.1.
If I run the mount command from Red Hat 6.2, using it as intended for a 2.2.xx kernel, doesn't everything work? There won't be any multi-mount confusion because 2.2.xx can't do that anyway. There isn't any problem with NFSv3 either, since 2.2.xx lacks NFSv3.
Whilst that's a good question, it misses the whole point of such a list. Can I replace it with a more realistic one:
If I take a random Linux-based system and boot it using the kernel I've just compiled using this kernel source tree, will it work? If not, what is the minimum that I need to upgrade to make it work?
Remember, there's absolutely NOTHING in ANY of the kernel source trees that depends on what a particular user is running on their system before they get that source tree.
Quoted 3 lines
Basically I ask: would existing scripts for a 2.2.xx kernel break? If the old mount can still do what it used to do, then "mount" need not be listed at all.
Replace that "a 2.2.xx" with "my current" and remove all restrictions on what the current kernel is, and that becomes an important question.
After all, if I take the network print server I'm running with a 2.0.19 kernel and drop a 2.4.2 kernel in, will it work without any other changes?
Best wishes from Riley.
Quoted 9 lines · Riley Williams
Quoted 4 lines
The rule should be like this:
List the lowest version number required to get 2.2.xx-level features while running a 2.4.xx kernel.
That's a meaningless definition, and can only be taken as such. What use would such a list be to somebody wishing (like I recently was) to upgrade a system running the 2.0.12 kernel so it runs the 2.4.2 kernel instead?
...
Quoted 6 lines
Quoted 3 lines
Basically I ask: would existing scripts for a 2.2.xx kernel break? If the old mount can still do what it used to do, then "mount" need not be listed at all.
Replace that "a 2.2.xx" with "my current" and remove all restrictions on what the current kernel is, and that becomes an important question.
No, not "my current" but "the previous stable". I say "2.2.xx" because that is the previous stable kernel.
If you upgrade from 2.0.xx, you should read the 2.2.xx changes file.
The important thing is to avoid version number inflation. I don't even bother reading the changes file, because I know it is bogus. Nearly all of my old software works great with a 2.4.xx kernel.
Hi Albert.
Quoted 16 lines
Quoted 9 lines
Quoted 4 lines
The rule should be like this:
List the lowest version number required to get 2.2.xx-level features while running a 2.4.xx kernel.
That's a meaningless definition, and can only be taken as such. What use would such a list be to somebody wishing (like I recently was) to upgrade a system running the 2.0.12 kernel so it runs the 2.4.2 kernel instead?
...
Quoted 3 lines
Quoted 3 lines
Basically I ask: would existing scripts for a 2.2.xx kernel break? If the old mount can still do what it used to do, then "mount" need not be listed at all.
Quoted 5 lines
Quoted 2 lines
Replace that "a 2.2.xx" with "my current" and remove all restrictions on what the current kernel is, and that becomes an important question.
No, not "my current" but "the previous stable". I say "2.2.xx" because that is the previous stable kernel.
Again, saying either "2.2.xx" or "the previous stable" is meaningless. Saying "The 2.2 kernel series" might have some meaning if it was not for the fact that the requirements differ for different members of that (or any other) kernel series.
On Saturday night, I had the pleasure of upgrading a system from the 2.2.4 kernel to the 2.4.2 one, and another system from the 2.2.14 kernel to the 2.4.2 one. Although the target kernel version was the same, several subsystems needed upgrading on the former that did NOT need upgrading on the latter, and that was just to compile the thing!
According to you, both of these upgrades would have required EXACTLY THE SAME upgrades to be made, but that isn't the case.
Quoted 1 line
If you upgrade from 2.0.xx, you should read the 2.2.xx changes file.
Fairy Nuff.
However, your argument still fails, simply because of its reliance on the assumption that an entire kernel series has static requirements when such just isn't the case.
Quoted 3 lines
The important thing is to avoid version number inflation. I don't even bother reading the changes file, because I know it is bogus. Nearly all of my old software works great with a 2.4.xx kernel.
The fact that you said "Nearly all" shows that your argument is false, since your argument has been that NO software needs upgrading.
Can I suggest that you re-read my previous missive, and actually look at the points raised. If you do, we might just get a sensible discussion on this subject...
Incidentally, your argument to date has assumed that everybody always installs every single kernel version. In my opinion, that is a very dangerous assumption to make. A more responsible assumption would be that the person wishing to upgrade to the version in this particular kernel source tree has a random system installed, and wishes to know:
1. What is the absolute minimum upgrades required to compile the kernel in the source tree I have just downloaded?
2. What is the absolute minimum upgrades required to install the kernel in the source tree I have just downloaded and compiled?
3. What is the absolute minimum upgrades required to enable me to run the kernel I have just compiled from this source tree, assuming that I wish to retain the use of the shell scripts that I developed under my previous kernel?
4. What other upgrades are recommended for reasons of system security or stability?
5. What further upgrades are required to enable me to make use of the advertised new facilities in this kernel?
6. What additional subsystems could be upgraded if desired?
7. I note that some upgrades are only required if certain of the subsystems are installed. Which upgrades are these, and which subsystems are they dependant on?
Personally, I'd be quite willing to work on a system to document the requirements and classifying each requirement according to the above system. However, as a pre-requisite, I would need agreement that such was (a) worth doing, and (b) of interest to the kernel developers.
Best wishes from Riley.
Quoted 11 lines · Riley Williams
Hi Albert.
Quoted 9 lines
Quoted 8 lines
Quoted 4 lines
The rule should be like this:
List the lowest version number required to get 2.2.xx-level features while running a 2.4.xx kernel.
Replace that "a 2.2.xx" with "my current" and remove all restrictions on what the current kernel is, and that becomes an important question.
Quoted 7 lines
Quoted 2 lines
No, not "my current" but "the previous stable". I say "2.2.xx" because that is the previous stable kernel.
Again, saying either "2.2.xx" or "the previous stable" is meaningless. Saying "The 2.2 kernel series" might have some meaning if it was not for the fact that the requirements differ for different members of that (or any other) kernel series.
Oh please. List whatever the hell is needed for an upgrade from any of 2.2, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, ..., 2.2.255 of course. Also include previous 2.4.xx kernels, in case some bastard decided to break stuff within a stable kernel series... like PPP for example.
Quoted 5 lines
On Saturday night, I had the pleasure of upgrading a system from the 2.2.4 kernel to the 2.4.2 one, and another system from the 2.2.14 kernel to the 2.4.2 one. Although the target kernel version was the same, several subsystems needed upgrading on the former that did NOT need upgrading on the latter, and that was just to compile the thing!
So what? Your point is??? Obviously one system was partly upgraded.
Quoted 2 lines
According to you, both of these upgrades would have required EXACTLY THE SAME upgrades to be made, but that isn't the case.
I never claimed that.
Quoted 7 lines
Quoted 1 line
If you upgrade from 2.0.xx, you should read the 2.2.xx changes file.
Fairy Nuff.
However, your argument still fails, simply because of its reliance on the assumption that an entire kernel series has static requirements when such just isn't the case.
There is no such assumption.
If 2.2.4 needs foo-1.7 while 2.2.5 and 2.4.4 need foo-1.8, then foo gets listed. If 2.1.99 needs bar-0.6 while 2.2.0 and 2.4.4 need bar 0.7, then there is no need to list bar. Never mind that both foo and bar are up to version 666, since that isn't needed.
Quoted 10 lines
Quoted 3 lines
The important thing is to avoid version number inflation. I don't even bother reading the changes file, because I know it is bogus. Nearly all of my old software works great with a 2.4.xx kernel.
The fact that you said "Nearly all" shows that your argument is false, since your argument has been that NO software needs upgrading.
Can I suggest that you re-read my previous missive, and actually look at the points raised. If you do, we might just get a sensible discussion on this subject...
Try it yourself, w/o alcohol. I didn't argue "NO software...".
Quoted 3 lines
Incidentally, your argument to date has assumed that everybody always installs every single kernel version. In my opinion, that is a very dangerous assumption to make.
Nope. Most people go from one stable series to the next, often skipping the first and last few revisions. (2.2.6, 2.2.9, 2.2.17, 2.4.3, 2.4.8...)
Quoted 3 lines
A more responsible assumption would be
that the person wishing to upgrade to the version in this particular kernel source tree has a random system installed, and wishes to know:
That random system should be capable of working with at least one kernel from the previous stable series.
Quoted 6 lines
1. What is the absolute minimum upgrades required to compile the kernel in the source tree I have just downloaded?
2. What is the absolute minimum upgrades required to install the kernel in the source tree I have just downloaded and compiled?
Quoted 7 lines
3. What is the absolute minimum upgrades required to enable me to run the kernel I have just compiled from this source tree, assuming that I wish to retain the use of the shell scripts that I developed under my previous kernel?
4. What other upgrades are recommended for reasons of system security or stability?
Good, assuming "reasons of system security or stability" relates to problems that a kernel upgrade might cause.
Quoted 2 lines
5. What further upgrades are required to enable me to make use of the advertised new facilities in this kernel?
This is noise. Such upgrades are not required.
Quoted 1 line
6. What additional subsystems could be upgraded if desired?
This is worse noise: "...and The GIMP is now at version..."
Quoted 3 lines
7. I note that some upgrades are only required if certain of the subsystems are installed. Which upgrades are these, and which subsystems are they dependant on?
This is getting too fancy.
Hi Albert.
Since you appear to be determined to ignore reason and stick to your misguided guns I'll leave you to destroy all the good work that has gone into the Linux kernel's documentation and make it something even Bill Gates would be proud of. However, I'll stick to documentation that actually tells people what they need to know whilst you do so.
Best wishes from Riley.
*********************************************************************
Quoted 112 lines · Albert D. Cahalan
Quoted 11 lines · Riley Williams
Hi Albert.
Quoted 9 lines
Quoted 8 lines
Quoted 4 lines
The rule should be like this:
List the lowest version number required to get 2.2.xx-level features while running a 2.4.xx kernel.
Replace that "a 2.2.xx" with "my current" and remove all restrictions on what the current kernel is, and that becomes an important question.
Quoted 7 lines
Quoted 2 lines
No, not "my current" but "the previous stable". I say "2.2.xx" because that is the previous stable kernel.
Again, saying either "2.2.xx" or "the previous stable" is meaningless. Saying "The 2.2 kernel series" might have some meaning if it was not for the fact that the requirements differ for different members of that (or any other) kernel series.
Oh please. List whatever the hell is needed for an upgrade from any of 2.2, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, ..., 2.2.255 of course. Also include previous 2.4.xx kernels, in case some bastard decided to break stuff within a stable kernel series... like PPP for example.
Quoted 5 lines
On Saturday night, I had the pleasure of upgrading a system from the 2.2.4 kernel to the 2.4.2 one, and another system from the 2.2.14 kernel to the 2.4.2 one. Although the target kernel version was the same, several subsystems needed upgrading on the former that did NOT need upgrading on the latter, and that was just to compile the thing!
So what? Your point is??? Obviously one system was partly upgraded.
Quoted 2 lines
According to you, both of these upgrades would have required EXACTLY THE SAME upgrades to be made, but that isn't the case.
I never claimed that.
Quoted 7 lines
Quoted 1 line
If you upgrade from 2.0.xx, you should read the 2.2.xx changes file.
Fairy Nuff.
However, your argument still fails, simply because of its reliance on the assumption that an entire kernel series has static requirements when such just isn't the case.
There is no such assumption.
If 2.2.4 needs foo-1.7 while 2.2.5 and 2.4.4 need foo-1.8, then foo gets listed. If 2.1.99 needs bar-0.6 while 2.2.0 and 2.4.4 need bar 0.7, then there is no need to list bar. Never mind that both foo and bar are up to version 666, since that isn't needed.
Quoted 10 lines
Quoted 3 lines
The important thing is to avoid version number inflation. I don't even bother reading the changes file, because I know it is bogus. Nearly all of my old software works great with a 2.4.xx kernel.
The fact that you said "Nearly all" shows that your argument is false, since your argument has been that NO software needs upgrading.
Can I suggest that you re-read my previous missive, and actually look at the points raised. If you do, we might just get a sensible discussion on this subject...
Try it yourself, w/o alcohol. I didn't argue "NO software...".
Quoted 3 lines
Incidentally, your argument to date has assumed that everybody always installs every single kernel version. In my opinion, that is a very dangerous assumption to make.
Nope. Most people go from one stable series to the next, often skipping the first and last few revisions. (2.2.6, 2.2.9, 2.2.17, 2.4.3, 2.4.8...)
Quoted 3 lines
A more responsible assumption would be
that the person wishing to upgrade to the version in this particular kernel source tree has a random system installed, and wishes to know:That random system should be capable of working with at least one kernel from the previous stable series.
Quoted 6 lines
1. What is the absolute minimum upgrades required to compile the kernel in the source tree I have just downloaded?
2. What is the absolute minimum upgrades required to install the kernel in the source tree I have just downloaded and compiled?
Quoted 7 lines
3. What is the absolute minimum upgrades required to enable me to run the kernel I have just compiled from this source tree, assuming that I wish to retain the use of the shell scripts that I developed under my previous kernel?
4. What other upgrades are recommended for reasons of system security or stability?
Good, assuming "reasons of system security or stability" relates to problems that a kernel upgrade might cause.
Quoted 2 lines
5. What further upgrades are required to enable me to make use of the advertised new facilities in this kernel?
This is noise. Such upgrades are not required.
Quoted 1 line
6. What additional subsystems could be upgraded if desired?
This is worse noise: "...and The GIMP is now at version..."
Quoted 3 lines
7. I note that some upgrades are only required if certain of the subsystems are installed. Which upgrades are these, and which subsystems are they dependant on?
This is getting too fancy.