Hi! I get confused by the versioning system of Linux. I would like to know why the versions are so cryptic and not easy to remember and understand like in the Redmond.
I guess the general rule is:
Software whose version has many odd nos. ---> Bad ( o.k. not so good ;-) even nos.---> Good Am I right?
Also I've read that the first version of Linux kernel was 0.1 Why 0.1 ??? when it could have been 1 or 1.0 or whatever Also I've seen that kernels have huge version nos. My kernel version no. is 2.2.14-12 Does it provide any (useful) info ?
Please enlighten.
On Thu, 17 Jan 2002, Nikhil Joshi wrote:
I get confused by the versioning system of Linux. I would like to know why the versions are so cryptic and not easy to remember and understand like in the Redmond.
Actually, the version numbers are probably the simplest to understand. We'll get to redmond in a moment, first linux.
Software whose version has many odd nos. ---> Bad ( o.k. not so good ;-) even nos.---> Good Am I right?
No. Version numbers are made up of three parts:
major, minor, release, and there's also the distributor patch, so we have: xx.yy.zz-dd
xx is major, yy is minor, zz or release, and dd is distro patch which we won't bother about any more.
minor number even == stable kernel ==> no major changes will happen in it, and it has been tested well. Features are never added or removed to different releases of the same minor version. At least not supposed to.
minor number odd == development kernel ==> a lot of major changes are happening in it. Features are added and removed at will. Lots of testing is done. When the feature set has stabilised, it is moved to the next stable release.
major numbers tell you the level of maturity of the product. linux has been in version 2 for a very long time, and that's the level of its maturity.
Also I've read that the first version of Linux kernel was 0.1 Why 0.1 ??? when it could have been 1 or 1.0 or whatever
The first kernel was very minimal, had almost no features, and was not usable on its own. In other words, it was not mature enough to be used. Version 1 is generally reserved for things that have matured enough to be used by the general public.
Also I've seen that kernels have huge version nos. My kernel version no. is 2.2.14-12 Does it provide any (useful) info ?
i've already told you about the major and minor.
the release (or revision) - the third number - tells you which release in the current version is being used. Releases normally have bugfixes for older releases. Bugs are associated with a release, so you would say kernel 2.4.10 fixed bug X from kernel 2.4.9. kernel 2.4.16 has a driver for hardware Y, but kernel 2.4.15 does not.
The last part - after the - is a distro patch, or a fork from the actual kernel.
eg: 2.2.14-12 (redhat 6.2 I think), means that redhat 6.2 uses a 2.2.14 kernel. However, they have applied some of their own patches to the kernel after it was released. Possibly to fix certain bugs that came up.
They cannot just put in a new kernel, because that may not have been thoroughly tested. Instead, they only patch major bugs that are found, and do not include features of newer kernels. Sometimes, they may add drivers that are not in the default tree.
You also have other forks like the alan cox tree, which has the -acN suffix (where N is the alan cox patch number). So you'd see thinks like 2.4.17-ac1, 2.4.17-ac2.
And finally, the prerelease tree. Before features are put into the stable kernel proper, they are put into pre releases, and if nothing breaks, the prerelease becomes the release.
So 2.4.17-pre1, 2.4.17-pre2 ... 2.4.17-pre6 were all prereleases that built incrementally into 2.4.17.
The idea is to throw features in as soon as possible - release early, release often. This is so that people can test new features as soon as they are coded instead of waiting for the developer to first test, and then release - Given enough eyeballs, all bugs are shallow.
Now, as far as Microsoft goes. How does a version number named after the year of release tell you anything about its features?
Windows ver 1 to 2 to 3 to 3.1 to 3.11 to 95 to 98 to 2000 to XP now that is confusing. there is absolutely no pattern.
if the difference in version numbers is 0.1, does that mean a very small change? In fact, there were major changes between 3.0 and 3.1. real mode dissappeared for one.
Even then, you'd expect 3.1 and 3.11 to be much closer. well, 3.11 was really windows for workgroups. 3.1 with networking features. Does that warrant a version change of 0.01?
Then, the next step. From 3.11 to 95 (or 4.001.95 to be exact). Is that a big change or what?
And then, 95 OSR A, 95 OSR B (also known as 96), 95 OSR C (known as 97), and finally 98.
OSR C had fat32 support - a major change, yet the major, minor and release numbers remained the same.
then, 98 to 2000 - that's a big change. I haven't seen any other software that is in version 2000. To a new comer, that would imply 1999 versions before it. Then suddenly XP. What does that mean and why does it look like a Mac?
HTH
Philip
On Thu, 17 Jan 2002, Philip S Tellis wrote:
then, 98 to 2000 - that's a big change. I haven't seen any other software that is in version 2000. To a new comer, that would imply
lol I guess Norton has security software which has huge versions: 2001 and now even 2002 !!!
Thanks Philip for the detailed info on the versioning system. It has cleared my doubts.
I have a query though. Is it mandatory that one adhere to the rules of the versioning system while developing a software for Linux ( having GPL ) ?
P.S. Thanks Philip again for the wonderful tutorial for Pine. It removed my inital fear of Pine. Now it is now my 'default' mail client :-)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Friday 18 January 2002 09:28, Nagarjuna G. wrote:
On Sat, Jan 19, 2002 at 07:31:45AM +0530, Nikhil Joshi wrote:
P.S. Thanks Philip again for the wonderful tutorial for Pine. It removed my inital fear of Pine. Now it is now my 'default' mail client :-)
Do look at the features of mutt before settling with pine.
What I like in mutt is the automatic configuration of GnuPG. Mutt automatically detects GnuPG or PGP; simply copy the sample configuration file of mutt to your home dir and comment out what you don't want and thats it.
Also mutt has a feature for binding keys and there is a sample-conf file with mutt which maps your keys similar to pine key bindings.
for more info simple press F1 after starting mutt.
regards
- -- Pankaj Jangid National Centre for Software Technology
Alt Email : pankaj@ncst.ernet.in Yahoo ID : pankaj_jangid GnuPG Key : http://ashoka.ncst.ernet.in/~pankaj/gpg.txt
On Fri, Jan 18, 2002 at 09:28:58AM +0530, Nagarjuna G. wrote:
On Sat, Jan 19, 2002 at 07:31:45AM +0530, Nikhil Joshi wrote:
P.S. Thanks Philip again for the wonderful tutorial for Pine. It removed my inital fear of Pine. Now it is now my 'default' mail client :-)
Do look at the features of mutt before settling with pine.
I swear!
--- Nikhil Joshi nikhiljoshy@yahoo.com wrote:
I have a query though. Is it mandatory that one adhere to the rules of the versioning system while developing a software for Linux ( having GPL) ?
Well you can say that is a side-effect of the tools that most GPL'ed tools use. CVS is used to maintain the sourcecode, and it has support for all these features about versions, releases, etc. So it is very common to see such numbering in most projects.
SameerDS.
===== -- MTech Student Reconfigurable Computing Lab KReSIT, IIT-Bombay
__________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/
hey there luggers...:)
I am on the look out for budding talent that who share team spirit and like writing technical content.
Puttin it plain n simple...I want freelancers who r real geeks in wat they do..:)) . They the pple we luv workin with.
SO if u hav a flair for technical writing do get in touch ASAP. Subjects for technical writing vary from Linux Implementaion nd deployment/Kernel Internals/Network Security/ Operating System Architecture/ Protocol Specifics/ Code analysis/ Appln testin and Benchmarking/ Codin Tutes/ Highly researched Technical papers on various breakthrough technologies/ Java/ PHP/ etc....
The right talent will be well compensated.
Do get intouch ASAP ...
The rest.....I hav tried my best to highlight the commercial base of the mail. So if u still wanna rant. i'll welcome it off the list.
Trevor Warren 9820349221
===== ( >- LINUX, It's all about CHOICE -< ) /~\ __ http://www.qmailtheeasyway.com __ /~\ | ) / mailto: trevorwarren@yahoo.com \ (/ | |_|_ \ Urgent ->9820349221@maxtouch.co.in / _|_| ___________________________________/
__________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/
On Sat, 19 Jan 2002, Nikhil Joshi wrote:
I have a query though. Is it mandatory that one adhere to the rules of the versioning system while developing a software for Linux ( having
No, it isn't mandatory, although, it does make life simpler for users of the software. personally, I adhere to this standard for my projects, I've even released a version 0.1.b (I used the b to mean beta, but dropped it in later releases).
Philip
--- Philip S Tellis philip.tellis@iname.com wrote:
Then suddenly XP. What does that mean and why does it look like a Mac?
LOL!
SameerDS.
===== -- MTech Student Reconfigurable Computing Lab KReSIT, IIT-Bombay
__________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/