public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: acahalan@cs.uml.edu, viro@math.psu.edu
Cc: Andries.Brouwer@cwi.nl, alan@lxorguk.ukuu.org.uk,
	linus@transmeta.com, linux-kernel@vger.kernel.org,
	rhw@memalpha.cx, seberino@spawar.navy.mil
Subject: Re: [PATCH] Improved version reporting
Date: Thu, 15 Mar 2001 10:52:25 +0100 (MET)	[thread overview]
Message-ID: <UTC200103150952.KAA451302.aeb@vlet.cwi.nl> (raw)

    From: "Albert D. Cahalan" <acahalan@cs.uml.edu>

    > On Wed, 14 Mar 2001 Andries.Brouwer@cwi.nl 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

             reply	other threads:[~2001-03-15  9:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15  9:52 Andries.Brouwer [this message]
2001-03-15 11:05 ` [PATCH] Improved version reporting Rogier Wolff
2001-03-17  4:35 ` Albert D. Cahalan
2001-03-17 17:51   ` Riley Williams
2001-03-19  6:50     ` Albert D. Cahalan
2001-03-19  9:15       ` Riley Williams
2001-03-23  8:33         ` Albert D. Cahalan
2001-03-23  9:42           ` Riley Williams
  -- strict thread matches above, loose matches on Subject: below --
2001-03-17 10:20 Andries.Brouwer
2001-03-17  1:07 Andries.Brouwer
2001-03-17 17:17 ` Riley Williams
2001-03-16 12:45 Andries.Brouwer
2001-03-16 13:30 ` Nick Holloway
2001-03-16 23:28 ` Riley Williams
2001-03-14 19:29 Andries.Brouwer
2001-03-14 23:39 ` Russell King
2001-03-16 10:54 ` Riley Williams
2001-03-14 16:51 Andries.Brouwer
2001-03-14 16:01 Andries.Brouwer
2001-03-14 16:26 ` Alexander Viro
2001-03-15  4:12   ` Albert D. Cahalan
2001-03-14 16:36 ` Henning P. Schmiedehausen
2001-03-14 17:28 ` Riley Williams
     [not found] <11a40b11caeb.11caeb11a40b@nosc.mil>
2001-03-14 10:39 ` Riley Williams

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=UTC200103150952.KAA451302.aeb@vlet.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=acahalan@cs.uml.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linus@transmeta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rhw@memalpha.cx \
    --cc=seberino@spawar.navy.mil \
    --cc=viro@math.psu.edu \
    /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