From: Linus Torvalds <torvalds@osdl.org>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add getdents32t syscall
Date: Thu, 26 Feb 2004 22:16:19 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0402262212340.2563@ppc970.osdl.org> (raw)
In-Reply-To: <403E9E4D.6090301@redhat.com>
On Thu, 26 Feb 2004, Ulrich Drepper wrote:
>
> > In other words, why doesn't glibc ever just make a new major number and
> > make its "struct dirent" be the 64-bit version?
>
> You can't be serious. Can you even imagine the pain this would cause?
Do you know how much pain it causes when you make changes and you do _not_
change the major number?
At some point you need to clean up.
This issue has been with us for years and years. I don't understand why
you'd want to add a totally new system call now. Instead, I'd suggest you
just put this on the long list of things to fix for when a new major
number is to be used.
And yes, you should use a new major number at some point. It is
_senseless_ to never update the majors. Just make a clean break, go
through every little nagging ugly thing (and there are a _lot_ of them
that have accumulated over the years), and make ready for "libc-3.0".
No, I'm not suggesting you do it for this one thing, obviously. But
there's bound to be _thousands_ of these stupid things where glibc has
compatibility crap that makes no sense.
Linus
next prev parent reply other threads:[~2004-02-27 6:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 19:38 Jakub Jelinek
2004-02-26 22:03 ` Randy.Dunlap
2004-02-26 22:15 ` Linus Torvalds
2004-02-26 22:25 ` Linus Torvalds
2004-02-26 22:29 ` Ulrich Drepper
2004-02-26 23:00 ` Linus Torvalds
2004-02-26 22:32 ` Jakub Jelinek
2004-02-26 23:15 ` Linus Torvalds
2004-02-27 1:33 ` Ulrich Drepper
2004-02-27 6:16 ` Linus Torvalds [this message]
2004-02-27 7:05 ` Ulrich Drepper
2004-02-28 23:21 ` Jamie Lokier
2004-02-27 1:46 ` Andreas Dilger
2004-02-27 3:36 ` Theodore Ts'o
2004-02-29 0:25 ` Jamie Lokier
2004-02-27 19:28 ` Linus Torvalds
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=Pine.LNX.4.58.0402262212340.2563@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®