All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Venkata Ravella <Venkata.Ravella@synopsys.com>
Cc: linux-kernel@vger.kernel.org,
	Ramki Balasubramanian <Ramki.Balasubramanium@synopsys.com>,
	ab@californiadigital.com
Subject: Re: Automount/NFS issues causing executables to appear corrupted
Date: Sun, 18 Apr 2004 16:06:00 -0700	[thread overview]
Message-ID: <408309D8.4010601@zytor.com> (raw)
In-Reply-To: <20040418212346.GA23560@rearview.synopsys.com>

Venkata Ravella wrote:
> The current kernel we use is default 7.2 kernel with two modifications:
> 1) BM patch applied to extend address space for a single process to 3.6GB
> 2) mnt patch applied to allow upto 1024 nfs mount points
> 
> uname -r output:
> 2.4.7-10mntBMsmp

In other words, you're using an ancient kernel with plenty of known 
problems, applied two additional patches to it, and are surprised you're 
having problems?

 > Unfortunately, upgrading to a newer kernel is not an option for us at 
 > the moment.

Sucks to be you.

	-hpa


  reply	other threads:[~2004-04-18 23:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-18 21:23 Automount/NFS issues causing executables to appear corrupted Venkata Ravella
2004-04-18 23:06 ` H. Peter Anvin [this message]
2004-04-19  1:07 ` Ian Kent
  -- strict thread matches above, loose matches on Subject: below --
2004-04-19 15:56 Venkata Ravella
2004-04-20  0:08 Venkata Ravella
2004-04-20  0:24 ` H. Peter Anvin
2004-04-20  0:24   ` H. Peter Anvin
2004-04-20  1:27   ` Ian Kent
2004-04-20  1:27     ` Ian Kent
     [not found]     ` <20040420042811.GE20474@rearview.synopsys.com>
2004-04-20  5:24       ` Ian Kent

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=408309D8.4010601@zytor.com \
    --to=hpa@zytor.com \
    --cc=Ramki.Balasubramanium@synopsys.com \
    --cc=Venkata.Ravella@synopsys.com \
    --cc=ab@californiadigital.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 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.