From: Jeff Layton <jlayton@redhat.com>
To: nfs@lists.sourceforge.net
Subject: Re: What's slated for inclusion in 2.6.24-rc1 from the NFS client git tree...
Date: Fri, 5 Oct 2007 08:24:43 -0400 [thread overview]
Message-ID: <20071005082443.ce34b904.jlayton@redhat.com> (raw)
In-Reply-To: <20071005082513.4b5a058c@poseidon.drzeus.cx>
On Fri, 5 Oct 2007 08:25:13 +0200
Pierre Ossman <drzeus-list@drzeus.cx> wrote:
>
> > It would be better to identify these applications and get them
> > fixed. The world is evolving and it is time for them to do so.
> >
>
> Print a warning or something so that they can be found. Don't go
> breaking systems left and right. People have better things to do than
> to fix the build systems for ever program they use.
>
Unfortunately, the kernel doesn't have any way to know that the app is
not built with LFS defines. glibc uses the same syscalls regardless of
how it's built. If you want to print a warning you'll have to modify
glibc to do so, and then you have the problem of where to send this
output...
--
Jeff Layton <jlayton@redhat.com>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-10-05 12:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 23:41 What's slated for inclusion in 2.6.24-rc1 from the NFS client git tree Trond Myklebust
2007-10-03 23:41 ` Trond Myklebust
2007-10-03 23:52 ` Jeff Garzik
2007-10-04 6:52 ` Pierre Ossman
2007-10-04 6:52 ` Pierre Ossman
2007-10-04 14:00 ` [NFS] " Trond Myklebust
2007-10-04 14:00 ` Trond Myklebust
2007-10-04 16:43 ` Pierre Ossman
2007-10-04 18:42 ` Andrew Morton
2007-10-04 18:42 ` [NFS] " Andrew Morton
2007-10-04 19:16 ` Trond Myklebust
2007-10-04 19:16 ` Trond Myklebust
2007-10-04 19:41 ` Peter Staubach
2007-10-04 19:41 ` [NFS] " Peter Staubach
2007-10-05 6:25 ` Pierre Ossman
2007-10-05 6:25 ` [NFS] " Pierre Ossman
2007-10-05 12:24 ` Jeff Layton [this message]
2007-10-05 17:36 ` Trond Myklebust
2007-10-05 17:54 ` Pierre Ossman
2007-10-05 17:54 ` [NFS] " Pierre Ossman
2007-10-04 19:59 ` Andrew Morton
2007-10-04 19:59 ` Andrew Morton
2007-10-05 0:58 ` Trond Myklebust
2007-10-05 0:58 ` Trond Myklebust
2007-10-05 17:30 ` Valdis.Kletnieks
2007-10-05 17:30 ` [NFS] " Valdis.Kletnieks
2007-10-05 17:52 ` Trond Myklebust
2007-10-05 17:52 ` Trond Myklebust
2007-10-05 18:00 ` Jeff Layton
2007-10-05 18:00 ` [NFS] " Jeff Layton
2007-10-08 8:36 ` Greg Banks
2007-10-05 18:12 ` Jeff Layton
2007-10-05 18:12 ` Jeff Layton
2007-10-07 22:56 ` David Chinner
2007-10-04 20:16 ` Chuck Lever
2007-10-05 17:31 ` Trond Myklebust
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=20071005082443.ce34b904.jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.